There is no CMS to learn. Content is MDX files in content/, validated at build time, and a lockdown on what MDX can contain means an agent can edit those files directly, without a database or an admin panel.

Most agencies using this go from clone to a live client preview in an afternoon: swap the token file, drop in the client's copy and logo, pick block variants per section. The parts that used to take a week (layout, spacing, responsive behavior) are already decided.

Most take an afternoon. A rebrand is a token swap rather than a rebuild: the block tree and the copy stay exactly where they are while the design tokens carry the new palette, type, and spacing across every section at once.

You build it once, following the same props-and-schema pattern as every other block, and it slots into the registry alongside the built-ins. It is an addition to the template rather than a fork of it, so the next client project gets it for free too.

Today it only reads from MDX in git. The registry is a mapping from a type string to a component, but the safety guarantee comes from the lockdown that inspects MDX at build time. Swap the source and you'd rebuild that check, not just add an adapter.

Yes. The site builds to a standard Next.js app, so you can host it on your own infrastructure as long as your servers can run the production build and provide the environment variables your project uses.

Yes. It ships MIT-licensed specifically so agencies can rebrand, resell, and reuse it across client engagements without asking permission or crediting the template anywhere client-facing. That includes the footer: there is no attribution line to keep or link back to, so the only name in a client's footer is the client's own.