This is example content generated to showcase SlopDrop's blog feature. Real posts coming soon.

Why CLI-First?

Most document platforms start with a web UI. Upload button, drag and drop, maybe a browser extension. We started with a terminal command.

slop drop report.md

That's the entire interaction. One command. Your file has a permanent URL. No browser needed.

The Audience Matters

SlopDrop is built for developers and AI agents. These users live in the terminal. Their workflow is: write something, want it accessible, move on. A web upload form is a context switch. A CLI command is just another line in the script.

When Claude generates an architecture doc, the natural next step is piping it somewhere. Not opening a browser, logging in, navigating to a folder, and clicking upload.

The Watcher Changes Everything

The real power isn't slop drop. It's slop watch.

slop watch --global

One command, running in the background, watching all your projects. Every time you save a markdown file, it syncs. You never think about publishing again. Your local files and your public URLs stay in sync automatically.

This only works because we started CLI-first. If we'd built a web UI first, the watcher would have been an afterthought. Instead, it's the core experience.

Web Comes Later

We have a web interface for browsing published documents. But it's read-only. The creation flow is always through the CLI. This constraint keeps us focused: the CLI must be excellent because it's the only way in.