Markdown content as the source of truth
Pages, blog posts, products, navigation, SEO titles, canonical URLs, and localized site settings live in content files that are easy to review.
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.
Jenna Press
Static-first Nuxt publishing for multilingual project websites
Jenna Press helps small teams build official project sites, documentation-style pages, blogs, and template-driven content hubs from Markdown without turning a simple website into a backend CMS.
What Jenna Press is built for
- Static site generation from Markdown content
- Template-driven page, blog, and product rendering
- Multilingual routes for English, German, Chinese, Spanish, and Greek
- Clean content structure for SEO and AI search extraction
Reusable blocks
Same content
Different template
A focused alternative to heavy CMS stacks
Jenna Press is for websites where most real work is content, structure, translation, and presentation rather than dashboards, accounts, runtime APIs, or database operations.
Templates stay separate from content
Visual design belongs in templates, so a landing page, documentation site, product catalog, or blog can change appearance without rewriting routing logic.
Static output stays fast and portable
The generated site can be deployed to static hosting, CDN storage, object storage, or simple web servers without a live CMS backend.
Multilingual publishing is structural
Localized files follow the same slug and route model, making international project sites easier to maintain and easier for search engines to understand.
SEO and GEO start with clear information architecture
Jenna Press favors descriptive page titles, canonical URLs, category routes, concise summaries, and extractable answer sections over keyword stuffing.
AI agents get safe work boundaries
Content agents update content, template agents update templates, and framework code stays stable unless the task is explicitly framework development.
Current support level
The framework is intentionally small, but the supported surface already covers the common needs of static project websites and content hubs.
5
language tracks
English, German, Chinese, Spanish, and Greek use the same publishing model.
3
content families
Page, blog, and product referral content are handled through generic static routes.
0
runtime CMS dependencies
Core website content is rendered from files and generated as static output.
What Jenna Press is trying to prove
Jenna Press is built around a practical claim: many project websites do not need a live CMS, a runtime database, or a custom dashboard to be useful. They need a clean publishing contract.
That contract is simple.
- Content lives in Markdown and front matter.
- Templates control layout, visual hierarchy, and content-type rendering.
- Framework rules control routing, validation, localization, static generation, and safe AI-assisted editing.
This makes Jenna Press a good fit for teams searching for a Nuxt static site framework, a Markdown CMS for multilingual websites, a template-driven static CMS, or a no-backend website framework for official project communication.
The project also treats AI-search visibility as a content-structure problem. Search engines and answer engines work better when pages answer real questions, use stable URLs, keep claims current, and make entities such as product names, categories, templates, and languages easy to extract.
Jenna Press keeps those choices visible instead of hiding them behind a database or plugin layer.