Pluto

[!WARNING] 🚧 Work In Progress: Pluto is experimental. Breaking changes are expected. Not production ready yet.

Pluto is a modular, layer-driven Content Management System (CMS) built with Nuxt. A modern alternative to monolithic systems like WordPress. Extend functionality through Nuxt Layers: choose only what is needed (auth, storage, e-commerce, blog, database connectors, etc.).

Highlights

• Nuxt + Nuxt Layers architecture
• Headless-first: consume via API (with typed routes!) or built-in composables (like useAuth or useProduct)
• Opt-in feature layers (Supabase, Blog, Shop, DB connectors, etc.)
• Core primitives: Content Types, Taxonomies, Custom Fields, Media, Permissions
• Deploy anywhere: Node, Edge, Serverless, Static (hybrid), Docker
• Developer-focused: composables, typed schemas, minimal core
• Dashboard is owned: fork as needed or just use it as is

Getting Started

First, install typescript as a dev dependency if you haven't already. This is required for Nuxt Layers to function properly.

npm i -D typescript

Then, extend your Nuxt configuration to include the Pluto layer, setting the install option to true, so Pluto's dependencies are installed automatically.

// nuxt.config.ts
export default defineNuxtConfig({
  extends: [
    ['github:plutocms/pluto', { install: true }],

    // Then, add any additional layers you want to use here
    ['github:plutocms/supabase', { install: true }],
    ['github:plutocms/blog', { install: true }],
    ['github:plutocms/shop', { install: true }],
  ],
})

Core Concepts

• Content Types: Define structured entities (e.g. Post, Product, Page)
• Fields: Primitive & custom (string, rich text, media, relation, JSON, computed)
• Taxonomies: Hierarchical or flat classification
• Media: Pluggable storage (e.g. Supabase, S3, local)
• Auth & Identity: Provided by optional layers (e.g. Supabase)
• Policies: Role / capability mapping (planned)

Layer Examples (Planned / In Progress)

| Layer | Purpose | | ------------------------- | ----------------------------------------------- | | core | Base CMS engine + schema registry | | supabase | Auth, file storage, row-level security hooks | | blog | Post model, categories, tags, markdown pipeline | | shop | Product model, pricing, inventory abstraction | | mysql / postgres / sqlite | Database connectors | | analytics | Basic event/log capture | | search | Index + query adapters (e.g. Meilisearch) |

[!NOTE] Actual availability depends on roadmap progress.

For now, some layers are being developed (/layers directory) in this same repository, but will eventually be extracted into their own packages.

[!NOTE] Optional layers may require environment variables; see ./env.example when added.

Roadmap (Subject to Change)

Check the roadmap here.

Contributing

• Open issues for design discussion before large PRs
• Keep layers isolated and opt-in
• Prefer typed contracts and explicit interfaces
• Add tests where possible (testing stack TBD)

Philosophy

• Minimal core, everything is a layer
• Transparent, hackable dashboard (no locked UI bundle)
• Declarative schemas
• Runtime flexibility: choose infra, not dictated by core

Why Not Just WordPress?

• Modern SSR + SPA hydration via Nuxt
• TypeScript-first developer experience
• Layer-based opt-in features instead of plugin global mutations
• Deployment portability (Edge / Serverless friendly)
• Headless usage is primary, not an afterthought
• If you're a Vue developer, you'll feel right at home.

Security

Do not deploy to production yet. No security audit performed. Auth / ACL model incomplete.

License

TBD (likely MIT). Not final.

Status

Experimental. Expect refactors.

Naming Note

"Pluto" is a working name; subject to rename if conflicts arise.