ADR 13: Sites converge on a visual builder
Webstudio is the destination; the ported system is the bridge.
Status: adopted (2026-07-19), revised same day with owner input
Context
The fleet began as legacy Webflow static exports, which is why the custom sites system exists. Owner direction: moving forward, sites come from Framer, Webflow, or custom builds, the fleet is entirely marketing/agency sites, and rebuilding existing sites is desired, not avoided.
Decision
- Destination: self-hosted Webstudio (closest open-source Webflow experience, AGPL, actively developed) as the standard builder for all marketing sites, running on our substrate, publishing to Vercel or ops-1, with domains, analytics, forms, and the registry staying in the Backpack console.
- Bridge: the ported-sites system. It keeps every legacy site fully managed (CMS, AI editing, forms, analytics) until that site is rebuilt. No site goes unmanaged while it waits.
- Rebuild pipeline: sites are rebuilt into Webstudio opportunistically: when a client pays for a redesign, when a site needs structural work the HTML system makes painful, or when AI-assisted rebuild makes it cheap. Each rebuild flips the site’s lane in the registry; the console modules keep working unchanged.
- The invariant is long-term editability, not a specific stack: Webstudio is the default builder, and React-based marketing sites are fine when a project calls for React (Plasmic or code + our CMS layer, chosen at build time). Every site lands in the console with a real editing story either way.
Consequences
- The ported system is maintained but no longer extended with major features; new capability investment goes to the Webstudio lane and the console modules that serve both.
- Next infrastructure task: stand up self-hosted Webstudio (builder needs Postgres, auth, and a proper deployment; it is NOT a one-command compose like Twenty) and validate the full loop: design, publish, domain, analytics, forms.
- Pilot rebuild candidate: one small existing site, to price the rebuild effort honestly before scheduling the fleet.