Small sites become accidental apps
A project site often needs pages, articles, translations, templates, and search-friendly metadata, not user accounts, runtime editing, custom APIs, and database operations.
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.
The problem Jenna Press is solving
Many project websites begin as simple publishing work, then slowly accumulate backend assumptions that make them harder to maintain than the content actually requires.
Content work needs reviewable files
Markdown and front matter make the source of truth visible in version control, which helps both humans and AI agents make narrower, safer changes.
Templates should be replaceable
A static site should be able to switch from a SaaS landing page to a corporate site, documentation-style layout, or product showcase without changing framework routes.
Multilingual routing should be predictable
Default and localized content should follow one URL model so search engines, users, and maintainers can understand which page is authoritative.
SEO should be structural, not decorative
Titles, summaries, canonical URLs, content categories, and descriptive internal links should be part of the publishing model rather than a last-minute checklist.
GEO needs extractable answers
AI search systems need clear entities, concise definitions, examples, and stable claims that can be cited or summarized accurately.
Reusable blocks
Same content
Different template
Why this project was started
About Jenna Press
Jenna Press exists because the middle ground between a hand-written static site and a full CMS is still useful.
Many teams need an official website that can explain a project, publish documentation-like pages, maintain a small blog, and support more than one language. They also need the result to be fast, crawlable, and easy to deploy. What they often do not need is a live application server just to render marketing copy.
The project is intentionally narrow:
- It uses Nuxt as the application and generation layer.
- It stores site content in Markdown and front matter.
- It keeps templates inside isolated template folders.
- It keeps framework routing generic and stable.
- It supports page, blog, and product-referral content without adding ecommerce, accounts, comments, or CMS editing.
That makes Jenna Press a practical option for teams searching for a static-first CMS starter, a Nuxt Markdown website framework, a multilingual static site generator, or a template-driven project website framework.
The project is also designed for AI-assisted maintenance. A content agent should update content. A template agent should update templates. A framework task should be explicit. That separation keeps the work reviewable and prevents a normal copy update from turning into a hidden framework change.