Skip to content
Inkwell CMS studio for editorial teams

Publish once. Shape every channel.

A structured publishing workspace for your content team, with editorial admin, public reader pages, media workflow, moderation, analytics, and compliance controls ready to customise.

Draft state
Ready
Channels
4
Compliance
Wired

Editorial desk

Scheduled

Designing an editorial system

SEO fieldsWeb preview

Omnichannel delivery

One editorial action, four public surfaces.

The marketing story is not a terminal command. It is content moving through channels without making editors think about infrastructure.

Web article

/blog/editorial-systems

Mobile preview

Reader-safe layout

RSS + sitemap

Generated on publish

Social card

OG image + summary

Editor workflow

Built around how editors actually publish.

Your editors keep draft state, preview, revisions, scheduling, comments, and analytics close to the story instead of jumping through generic admin screens.

1

Draft with structure

Markdown, metadata, category, tags, and featured image sit in one calm editorial surface.

2

Preview every channel

Check the public article, social card, RSS payload, and static page fit before publishing.

3

Publish with evidence

Schedule, archive, revise, moderate comments, and track views without leaving the CMS.

CMS surfaces

The pieces a real content site needs.

Public reader

Blog index, article pages, static pages, reading progress, related content, SEO metadata, RSS, and sitemap.

Content organisation

Hierarchical categories, flat tags, generated slugs, reading-time estimates, and search across title and body.

Comments and moderation

Reader comments with an admin queue for approve, reject, and delete decisions.

Editorial analytics

Server-side post view tracking, popular posts, category trends, and content performance views.

Media workflow

Upload, optimise, browse, and reuse images for featured artwork and social previews.

Compliance scaffold

compliance scaffold legal routes, consent, DSAR export, account deletion, audit log, and secure webhook posture.

Public reader

Editorial Systems for Teams

Seeded posts render through the public reader with metadata, featured media, comments, progress, related content, RSS, and sitemap support.

Reader and SEO

The public site is part of the CMS, not an afterthought.

Blog listing, article pages, static pages, canonical metadata, social cards, RSS, and sitemap generation stay connected so your publication can launch from one content model.

Analytics and moderation

Know what shipped, what worked, and what needs review.

Use this surface for editorial performance, moderation queues, scheduled content, and media-library signals once your real content is flowing.

Views this week

12.8k

Pending comments

18

Scheduled posts

4

Media assets

126

Ship a real publication

Start from the CMS studio, not a blank app shell.