Open-Source CMS · nuxt

content

Nuxt Content is a file-based CMS module for Nuxt 3 applications that reads Markdown, YAML, CSV, and JSON files from a content directory and exposes them as a queryable data layer. It supports Vue components embedded in Markdown, code highlighting via Shiki, and works in serverless and edge environments.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/nuxt/content

3.6k

GitHub stars

747

Forks

TypeScript

Primary language

MIT

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	nuxt/content
Owner	nuxt
Primary language	TypeScript
License	MIT — OSI-approved
Stars	3.6k
Forks	747
Open issues	58
Latest release	v3.15.0 (2026-07-02)
Last updated	2026-07-06
Source	https://github.com/nuxt/content

What content is

A TypeScript-based Nuxt module that parses flat-file content (primarily Markdown with MDC syntax support), indexes it into a SQLite-backed query layer, and provides fully typed collection queries and navigation generation. Includes hot module replacement in dev and optimized builds for edge runtimes.

Quickstart

Get the content source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/nuxt/content.git2cd content3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Documentation and Blog Sites

Git-friendly, version-controlled content storage with instant preview via HMR. Ideal for developer blogs, API documentation, and knowledge bases where content lives alongside code.

Content-Heavy Nuxt Applications

Embed interactive Vue components directly in Markdown using MDC syntax. Build marketing sites, guides, and tutorials with rich interactivity without external CMS APIs.

Edge-Deployed Applications

Supports serverless and edge environments (Cloudflare Workers). Pre-indexed SQLite queries eliminate runtime parsing overhead for globally distributed content delivery.

Implementation considerations

Content must live in a `content/` directory at project root; directory structure becomes your content organization. Plan information architecture early.
Requires Node.js/pnpm build toolchain and Nuxt 3 framework. CI/CD pipeline must rebuild and redeploy on content changes unless using Nuxt Studio.
SQLite indexing happens at build time; query performance is excellent but adding new content requires a full rebuild and redeploy cycle.
MDC syntax for Vue components in Markdown requires developer familiarity; no WYSIWYG editor unless integrated with external tools like Nuxt Studio.
TypeScript support is full; ensure team has TypeScript skills to leverage fully typed collections and IDE autocomplete.

When to avoid it — and what to weigh

Multi-User Editorial Workflows Required — No built-in user management, permissions, or collaborative editing UI. Git-based storage assumes developer-level content management; not suitable for non-technical editors without custom tooling.
Large, Frequently Changing Content Sets — File-based structure and rebuild cycles can become cumbersome with thousands of pages or real-time content updates. Traditional headless CMS better suited for high-volume, dynamic content.
Non-Nuxt Projects — Tightly coupled to Nuxt 3 ecosystem. No standalone or framework-agnostic deployment available; requires full Nuxt application.
Complex Data Relationships — Designed for flat, document-oriented content. Relational queries, joins, and complex filtering across large datasets not optimized compared to database-backed CMSes.

License & commercial use

MIT License. Permissive open-source license allowing commercial use, modification, and distribution with attribution. No patent claims or restrictions on commercial applications.

MIT is a clear permissive license suitable for commercial use. No special restrictions or commercial licensing tiers noted in the provided data. However, if using Nuxt Studio for editing UI, review its separate terms.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Strong
License clarity	Clear
Deployment complexity	Low
DEV.co fit	Strong
Assessment confidence	High

Security considerations

Content is file-based and versioned in Git; no user-facing authentication or injection vectors within the module itself. Ensure git repository and deployed content are access-controlled. SQLite database is build-time indexed; no runtime SQL injection risk. Vue components in Markdown inherit Vue 3 security model; sanitize untrusted content if rendering dynamic Markdown. No security incidents or advisories mentioned in provided data; conduct own review for production use.

Alternatives to consider

Strapi / Contentful

Full-featured headless CMS with multi-user editorial UI, real-time APIs, and media management. Use if you need non-developer content editors or dynamic content without rebuilds.

VitePress / Astro

Static site generators with similar file-based Markdown workflows but framework-agnostic. VitePress is Vue-first; Astro is framework-agnostic. Lighter footprint if no Nuxt ecosystem lock-in.

Ghost / Statamic

Traditional CMS platforms with visual editors, user management, and built-in hosting. Better for content-first sites without tight framework coupling.

Software development agency

Build on content with DEV.co software developers

Nuxt Content is ideal for documentation, blogs, and marketing sites. If you need multi-user editing or complex workflows, consider a headless CMS integration.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

pruvious tinacms woonuxt

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source CMS Web App Development Cloud Deployment Custom Software Development Talk to DEV.co

content FAQ

Do I need Nuxt Studio to use Nuxt Content?

No. Nuxt Content works standalone with Git-based file editing. Nuxt Studio is optional and adds a visual editor UI; it requires a separate account and is not included in the module.

Can I use Nuxt Content without rebuilding every time content changes?

Not by default. File-based content requires a build-time indexing step. Nuxt Studio can automate rebuilds on content updates, but standalone usage requires manual CI/CD triggers or webhook integrations.

Is Nuxt Content suitable for real-time collaborative editing?

No. Git-based storage assumes single-editor or code-review workflows. Not designed for simultaneous multi-user editing; use a headless CMS for that use case.

What file formats are supported?

Markdown (.md), YAML (.yml), CSV (.csv), and JSON (.json). Markdown with MDC syntax for Vue components is the primary use case.

Software developers & web developers for hire

DEV.co helps companies turn open-source tools like content into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source cms stack.

Ready to Build Content-Rich Nuxt Apps?

Nuxt Content is ideal for documentation, blogs, and marketing sites. If you need multi-user editing or complex workflows, consider a headless CMS integration.

Talk to DEV.co Schedule a Consultation