A Markdown blog keeps each post as a text file. You write in any editor, keep the files wherever you like, and your archive never depends on one platform’s database. This guide gets a Markdown blog running with Sentilis Press.
Why a Markdown blog
- Portable. Plain text files open anywhere, today and in years.
- Fast to write. No editor to learn; headings, links and lists are a few characters.
- Easy to back up and version. Copy the folder, sync it, or keep it in Git.
Write your first post
Create a press/ folder and a file inside it:
---
name: Why I write in plain text
category: Essays
tags: writing, tools
---
# Why I write in plain text
Every post on this blog is a Markdown file on my laptop…
That is a complete post. name is the title, category groups posts, and tags are lowercase keywords (use hyphens for multi-word tags, like note-taking).
Drafts and archive
Use status to manage your workflow:
status: draft— you are still working on it; readers don’t see it.status: published— live. This is the default.status: archived— taken down, kept in your folder for the record.
Posts with images
When a post has local images, give it a folder:
press/
└── a-week-in-lisbon/
├── a-week-in-lisbon.md
└── attachments/
├── cover.jpg
└── tram.jpg
A cover.jpg (or .png, .jpeg, .webp) in attachments/ becomes the image shown when the post is shared. Videos (.mp4, .webm) can be embedded too. Keep each post’s media under 5 MB.
Publish
npm i -g @sentilis/cli
sentilis auth login <your-token>
sentilis sync ./my-content
Each published post appears in your post list, with its category as a label and each tag linking to a filtered list.
Keep posts private or protected
Set visibility: private to keep a post off your list. Add a password to a private post to share it only with people who have the link and the password.
Grow beyond the blog
Next to press/, the same folder can hold your bio (bio/), products and services (market/), memberships (prime/) and a visual portfolio (gallery/).