I used to believe publishing meant ownership. For years, I wrote on Web2 platforms like Medium. They were polished, easy to use, and had built-in distribution. You could focus on writing and let the platform handle everything else.\ But over time, I started to feel the tradeoff: I was creating content, but I didn’t really control its fate. My writing lived inside someone else’s product, someone else’s rules, someone else’s business model. Then I entered the Web3 world.

When building Blogit Admin, I wasn’t looking for a generic rich text editor. I wanted an editor that felt good for writing while still preserving Markdown. For Blogit, the source of truth is always the Markdown files in the Git repository.\ So the editor in the admin has to satisfy two things at the same time: It needs to be friendly enough for normal users It needs to be faithful enough to Markdown That is why I ultimately chose Milkdown.

This post demonstrates common Markdown capabilities supported by Blogit, including headings, lists, links, blockquotes, code blocks, tables, images, and LaTeX. Headings Level 3 Heading Level 4 Heading You can write bold text, italic text, bold italic text, ~~strikethrough~~, and inline code like . Links OpenAI GitHub Lists Unordered List Write locally Track changes with Git Publish with CI/CD Ordered List Create a post folder Add an Commit and push Task List [x] Markdown