Skip to content

Built pastthe demo.

Professor Flow is a public field notebook for people who build Salesforce automation that has to survive real data, real users, and real release cycles.

Professor Newton drawing a branching Flow on an easel

The standard

Source before slogans

A component is only useful when you can inspect how it works and where it came from.

Limits stay visible

Every implementation has trade-offs. Good documentation names them before production does.

Builders deserve the full path

Discovery, installation, release history, and guidance belong in one trustworthy record.

What runs underneath

Next.js and React provide the application shell. MDX and Velite keep every component, article, and contributor reviewable in source. Vercel carries the published site. The stack is ordinary on purpose; the documentation is the product.

Inspect the component index

Search

Search components, articles, and tags