Content Workflows: Static, Hybrid, and Live
AstroWEBTheme supports three content workflows in the same project — Git-based static files, live D1-backed editing, and a hybrid mix — so the publishing model fits the team instead of the other way round.
Not every team wants to publish the same way. A solo founder is comfortable committing Markdown to Git. An editorial team wants a form, a preview, and a publish button. AstroWEBTheme does not force a single answer — a project can mix workflows per collection.
Static files and an AI-assisted Git workflow
Content can live as MDX files under src/site/content/, edited directly or through a coding agent such as Claude Code or Codex working from the documented safe edit zones in AGENTS.md. Every change is a reviewable diff, which suits developers, founders, and technical teams who are comfortable with Git.
Live content with D1
Collections configured with a hybrid or database-backed source store entries as rows in Cloudflare D1 instead of files. This supports structured editing without committing code for every content change, while reusing the same layouts, metadata, feeds, and LLMS output as static entries.
Hybrid: both, by collection
A single project can run static content for stable pages — like the homepage, documentation, and legal pages — alongside D1-backed content for a blog or news section that changes often. The contentSource configuration in src/site/config/content.mjs sets this per collection, so the choice is explicit rather than all-or-nothing.
Where a full CMS still makes sense
Some teams need drafts, scheduled publishing, media libraries, and editor roles beyond what a Git workflow or a lightweight D1 table comfortably provides. AstroWEBTheme’s content model is designed so a headless CMS can sit in front of a collection as a project-specific adapter without redesigning the rest of the site.
Not sure which workflow fits your editorial team? NViewsWEB can assess your content model and configure the right mix.
