Framework, static and storage

Every website is framework or static. Your agent picks this at creation. A third kind, storage, holds shared files instead of a site: see Sharing files.

Framework (default)

Typed React source with a fixed file model (pages, components, global.css, and so on). Webly builds it through the quality gate, then serves the result.

Use this when the agent is writing a real app-like site and you want drafts, checks, and structured source in the dashboard.

Static

Raw files (index.html, CSS, assets) uploaded as a tree. No React build: what you deploy is what gets served after publish.

Use this for simple sites, hand-written HTML, or when the agent is shipping a finished folder.

Same extras on both

Forms, custom domains, and analytics work on either kind once the site is claimed. New content, including posts, products and FAQs, goes in the site's source files. Sites that already use Webly's CMS or a managed blog keep working, and your agent keeps editing that content there until you ask it to move it into source files.

For the full contract, see the API or llms.txt.