Why I Built Marklog

I tried every blogging platform. WordPress, Ghost, Hashnode, Dev.to, Medium. Each one wanted something from me before I could write.

Sign up. Configure a database. Connect a CMS. Pick a pricing plan. Accept cookie banners. Deal with editor toolbars I didn't need.

I just wanted to write Markdown and push to git.

The problem

My content lived in their database. If they changed their pricing, changed their editor, or shut down, my writing was stuck. Export tools exist, but they're always an afterthought.

The idea

GitHub already does version control, hosting, and collaboration. Why not use it for blogging too?

Marklog reads Markdown files from any public GitHub repo and renders them as a blog. No database. No CMS. Your content stays in a repo you own.

Push a .md file to your repo. It's published. Delete it. It's gone. Edit it. It's updated. Git IS your CMS.

What's next

More themes. Better SEO. RSS feeds. Maybe a commenting system that doesn't suck.

But the core idea won't change: Markdown in, blog out. That's it.