sparx CMS is a calm, fast place to publish — a block editor, a media library, structured content, and SEO that does its homework. It runs standalone: a publisher, a docs site, or a portfolio needs no shop. Render it on a hosted sparx site, or pull it headless through the API.
Every page and post moves the same calm path — write, hand it off, set the date, ship. Autosave and revisions ride along the whole way, so nothing is ever lost between drafts.
A distraction-free block editor. Autosave every 30 seconds; the last 10 revisions kept and any one restorable — write freely, never lose a word.
Share a private preview link so an editor reads the exact published layout before it goes out. Notes stay on the record.
Future-date a post and it publishes itself at the minute you chose. Plan a week or a quarter of content without staying up to hit publish.
Live on your domain, in the sitemap, with JSON-LD and an RSS entry. Change the slug later and a 301 redirect is created for you — no link rot.
A blog is one shape; a case study, a recipe, or a team profile is another. Define your own content types with typed fields and sparx generates the editing form — then serves it back as clean, typed JSON over the same API.
Built on a real rich-text engine — type, format, embed, link. No nested-popover maze, no mystery markup underneath. Everything alongside is a capability you get on day one.
Headings, lists, quotes, tables with resizable columns, code blocks, and rules.
Drop in images with captions, or embed a YouTube or Vimeo URL inline.
Link to any page, post, product, or collection — with a nofollow option for external.
Saves every 30s; the last 10 versions kept, any one restorable in a click.
Every page gets a live audit as you write — not a report you run later. Title and meta lengths, a unique H1, alt text, internal links, and word count, each scored before you publish. Sitemaps and JSON-LD generate themselves.
The CMS isn’t just an editor — it’s the whole content layer, with the parts most tools charge extra for already in the box.
Drag-drop uploads auto-transcode to WebP and responsive sizes, served from the CDN. Search by name or alt text, with a usage count per asset.
Multiple authors, categories and tags, featured images, excerpts, reading time, and an RSS feed — with related posts wired by tag.
Build header, footer, and mega menus that link to any page, post, product, collection, or external URL — no theme code required.
Manual 301s plus auto-redirects when a slug changes, with chain and loop detection. Bulk-import a CSV when you migrate.
Language variants per page with hreflang generated, separate SEO per language, and a subdirectory or subdomain URL structure.
About, contact, policies, and campaign pages — all the static content a site needs, with the same editor and SEO tooling.
CMS is its own module. A publisher, a docs site, or a content team can run entirely on sparx without a cart in sight — and pull it any way they like.
Pair CMS with Builder and your pages and posts render on your own domain — fast, on the CDN, with SSL handled. Selling stays optional; turn Commerce on the day you want it.
Query content over REST and GraphQL and render it in Next.js, Astro, SvelteKit, or a native app. The @sparx/site-sdk ships typed helpers for every content type.
Content lives in the same database as everything else on sparx — no separate CMS to sync, no plugin sprawl, no platform that holds your archive hostage. Export the whole thing whenever you want.
Standalone use, headless access, SEO, and how it fits your stack — answered straight. Still deciding? Read the CMS docs or start the 14-day trial.
Yes — CMS is a standalone module. A publisher, a documentation site, a portfolio, or a content team can run entirely on sparx CMS without ever turning on Commerce. The content engine and the commerce engine are deliberately separate, so you only pay for what you use.