Static output is the default delivery model
Core site content should render from files and generate static pages. Runtime APIs are not required for normal page, blog, or product content.
A static-first Nuxt CMS starter built on a unified content schema
JennaPress helps teams build company websites and landing pages with reusable content models, switchable templates, and AI-friendly generation workflows. It is designed for fast static deployment, consistent rendering, and flexible visual customization on top of the same data contract.
Core principles
These rules keep Jenna Press useful as a lightweight static website framework instead of letting it drift into a hidden application platform.
Content is the source of truth
Editors should update Markdown and front matter. Generated files may exist, but they are outputs, not the hand-written source.
Templates are isolated design systems
A template controls layout, theme styling, and content-type presentation inside its own folder and asset namespace.
Routes remain generic
Pages, blog categories, blog posts, products, and localized routes should use shared framework patterns instead of business-specific route files.
Multilingual content uses stable slugs
Localized pages should preserve the same logical slug, while non-default languages receive predictable URL prefixes.
SEO and GEO need explicit metadata
Page titles, descriptions, canonical URLs, summaries, dates, categories, and author/site signals should be present in content rather than implied.
Reusable blocks
Same content
Different template
Collaboration rules
Jenna Press is designed to be maintained by humans and AI agents without blurring the difference between content, templates, and framework code.
Content tasks stay in content
A content update should not modify routes, loaders, shared components, types, dependencies, or build configuration.
Template tasks stay in templates
A template can change visual structure, blog/product presentation, theme CSS, and template assets, but should not patch framework internals.
Framework work must be explicit
If a requirement needs new block types, schema changes, route changes, server APIs, or dependencies, it is framework development and should be reviewed as such.
Internal links should match real routes
Links should point to generated pages, blog category routes, product category routes, or external destinations with clear intent.
Claims should stay current
Release notes, support status, and SEO/GEO guidance should use dates and concrete wording so readers and AI systems can evaluate freshness.
Search visibility should serve readers
Keyword coverage is useful only when it answers real questions with clear explanations, examples, and next steps.
Project rules that protect the framework
Jenna Press Principles
These principles prevent a common failure mode: a project starts as a simple website and slowly loses its boundaries.
In Jenna Press, a content file is editable, but it should not become a place to hide application logic. A template is flexible, but it should not quietly redefine the framework. A generated file is allowed, but it should be treated as generated output.
That discipline also helps SEO and GEO. Search engines, answer engines, and AI agents can understand a site more reliably when the site has stable URLs, descriptive titles, clear categories, visible dates, consistent language versions, and pages that answer concrete questions.
Jenna Press stays useful only if those lines remain visible.