Static-only by default
Jenna Press does not rely on runtime APIs or a built-in server to render core page 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
Themes are equal citizens
No template should encode a hidden priority order between dark, light, and pink. Theme logic belongs to shared framework rules.
Content is the source of truth
Editors should modify markdown source files. Generated files may exist, but they are outputs rather than hand-written truth.
Reusable blocks
Same content
Different template
Collaboration rules
Minimal code modification
Code changes should stay narrow, traceable, and review-friendly rather than mixing fixes with opportunistic refactors.
Templates should stay isolated
Template changes belong in template directories. Framework changes should not casually drift into content decisions.
Routing and persistence must stay predictable
Language and theme persistence should feel stable across refreshes, internal navigation, and static deployment.
Project rules that protect the framework
These principles exist to prevent a common failure mode: a project that starts simple, then slowly loses its boundaries.
In Jenna Press, a generated file is allowed, but it must be treated as generated. A template is allowed, but it must not quietly redefine the framework. A content file is editable, but it should not become a place to hide application logic.
The framework stays useful only if those lines remain visible.