Skip to content

Public publishing

Publish Markdown safely for search and sharing

Create immutable public revisions, useful metadata, durable redirects, granular shares, and an abuse response boundary.

MDLoom documentation9 min read

Publish an immutable revision, not a live draft

A publication points at a checkpointed source/render snapshot with a content hash and renderer identity. Editing the workspace document does not silently change the public page, and a rollback creates a deliberate current-revision decision.

Write metadata for people before search engines

A specific title and description help readers decide whether the page answers their question. Author, tags, language, cover, and canonical URL must describe the reviewed revision rather than newer private content. Indexability is an API-controlled state, not a client-side checkbox alone.

Preserve old routes with durable redirects

Changing a handle or slug should reserve the new route atomically and retain a permanent redirect from the old route. A redirect prevents broken inbound links while moderation and visibility still decide whether the target is public.

Separate a share link from a public publication

Owner-only private shares, unlisted token shares, optional password/expiry, and copy/source/PDF permissions are distinct controls. An unlisted URL should remain noindex; a public publication still needs moderation, rate limits, abuse reporting, and operator response.

Understand the remaining deployment boundary

The repository provides fail-closed moderation state, route/report rate limits, audit evidence, and runbooks. Production still needs approved policy ownership, external malware/spam engines, edge limiting, CDN purge integration, on-call handling, and a real legal/domain review.

Put it into practice

Open a clean workspace for your next document.

Start anonymously, choose an explicit Markdown profile, and keep source, preview, and diagnostics together.

Open the editor  →