A Markdown CMS is a content management system where the content lives in Markdown files instead of a database. You write and organize files; the system reads them and publishes them as web pages.
How it works
- Content is files. Each page, post or product is a
.mdfile. - Metadata sits at the top. A short frontmatter block holds settings like the title, category or status.
- Folders give structure. Where a file lives decides what it is.
- A publishing step turns files into pages: a build, a sync, or a plugin.
---
name: Getting started
category: Documentation
status: published
---
# Getting started
Install the tool, then run your first command.Markdown CMS vs traditional CMS
| Markdown CMS | Traditional CMS | |
|---|---|---|
| Where content lives | Files you own | A database managed by the CMS |
| Editor | Any Markdown editor | The CMS’s editor |
| Versioning | Git or any file sync | Built-in revisions, varies |
| Portability | Copy the folder | Export and import |
| Learning curve | Markdown basics | The CMS’s admin interface |
Neither is better for everyone. A traditional CMS suits teams who want a single web interface for everything. A Markdown CMS suits people who already write in plain text and want their content to stay portable.
Flavors of Markdown CMS
- Static site generators build a site from a folder of Markdown; you host the output.
- Git-based editors add a web interface on top of Markdown files in a repository.
- Publishing platforms like Sentilis take your Markdown files and publish them, with hosting included.
Sentilis as a Markdown CMS
Sentilis reads the Markdown files you keep on your computer — written in Obsidian, Typora, VS Code or any other editor — and publishes them to your profile with the Sentilis CLI or the Obsidian plugin.
Folders map to content types: press/ for posts and docs, bio/ for a profile page, market/ for products and services, prime/ for memberships and gallery/ for visual work. The status field handles drafts, and the attachments/ folder handles media.