Clonesite Docs

Architecture

The first-pass architecture for the Clonesite marketing skeleton.

Surfaces

The repository has three active surfaces:

  • web/: public marketing shell and SSR routes.
  • content/docs/: internal planning and review docs.
  • design-canvas/: isolated design review workspace.

Runtime Boundary

web/ should stay thin until the new product requirements are known. It owns routing, layout, theming, locale routing, and static marketing content. It does not own authentication, billing, persistent app state, or task execution.

Design Boundary

design-canvas/ can explore product ideas freely, but stabilized UI should be rebuilt intentionally in web/. Do not import canvas-only prototype screens into the production app.

Content Boundary

Fumadocs is for internal review. If the new site needs public SEO content, add a separate public content model instead of exposing content/docs as the blog.