docs.slopdrop.dev / slopdrop / blog / 2026-04-08-blog-feature.md
Raw

The Laziest Blog Platform on the Internet

You know the drill.

You want to write a blog post. So you pick a static site generator. Hugo, Astro, 11ty, doesn't matter which. You spend an afternoon on setup. Configure the theme. Fight with the build. Wire up a deploy pipeline. Write your first post, push to git, wait for CI, and finally your words are on the internet.

Next week you want to write again. But the Node version changed, the theme broke, or you forgot how frontmatter works in this particular generator. You fix the build. You don't write.

A month later: a blog with one post and a graveyard of config files.

What If You Just... Saved a File?

SlopDrop is a markdown file hosting service with a CLI watcher. You save a .md file, it appears at a permanent URL. That's all it was built for.

Then we noticed people were already using it as a blog. Drop markdown files, share URLs, done. The only thing missing was an index page and an RSS feed.

So we added those. In a single session. ~300 lines of logic, zero dependencies.

Any folder on SlopDrop becomes a blog when you add a blog.md to it.

You write a markdown file. You save it. It's live. That's the entire workflow.

The Setup (All of It)

Drop a blog.md in any folder. This triggers blog mode. Its frontmatter becomes your blog's config:

---
title: My Build Log
description: Notes from the trenches.
---

Write posts as markdown files. Add date and published: true:

---
title: My First Post
date: 2026-04-08
description: Summary for the index and RSS feed.
published: true
---

Your content here.

Save. The watcher syncs it. Your post is live. Your RSS feed updates. The index shows your new post at the top.

Want to unpublish? Change published to false. Save. Gone from the index, still accessible by direct URL.

What You Get

A blog index page with your posts listed by date. An Atom feed that readers can subscribe to. Draft support. OG tags for social sharing. One clean default design that stays out of the way.

That's it. We stopped there on purpose. Comments? Link to a discussion thread. Newsletter? Pipe the RSS feed into Buttondown. Themes? You're here for the writing.

Every feature we skipped is a build step that won't break at midnight.

How It Actually Works

The gap between "file hosting" and "blog" is embarrassingly small. SlopDrop already had markdown rendering, permanent URLs, a file watcher, and versioning. We added three things:

  1. A frontmatter parser (custom, zero dependencies because we're not adding supply chain risk for a YAML parser)
  2. A blog index that replaces the directory listing when blog.md exists
  3. An Atom feed generator

Metadata gets cached in the database on upload, so the index loads from a single query. The whole feature is a separate module that can be toggled off without touching anything else.

Try It

mkdir blog
echo '---
title: My Blog
description: Writing things down.
---' > blog/blog.md

slop drop --project myproject blog/blog.md

Your blog is live at yourname.slopdrop.dev/myproject/blog/.

Nothing broke. Nothing to deploy. Just your words on the internet, the way it should've worked all along.

The laziest blog platform on the internet. And we're okay with that.