Embed Notice

@tanepiper @deadparrot @zachleat @dries YYYYYYUP. For dedicated teams/orgs with engineering resources, I think those decisions have clearer tradeoffs — go headless to get a cleaner foundation, then invest your time building more of the flow/experience on top of it.

It's smaller organizations, or ones that work with agencies that are only there for the design/build/launch phase, that can be really screwed by the gaps if they buy into a simple “Headless === Faster/Better”