How we write the Growpost blog

We get asked occasionally how this blog actually gets made, partly because we build a tool for exactly this workflow, so it seemed worth writing down honestly instead of pretending it's more automated than it is.

Where posts start

Most posts start as a single line in a running list, not a fully formed idea. Something we noticed helping creators — a question that comes up repeatedly, a mistake we see often enough to be worth writing about, a product decision worth explaining. The list is unglamorous: a plain text file with one-line entries, added to whenever something occurs to us, not on a schedule.

Turning a line into a draft

When it's time to actually write, we pick from that list based on what feels most useful right now, not strictly in order. The first pass is almost always rougher than what ends up published — we write to figure out what we actually think, then cut the parts that were just us finding the argument.

The biggest editing move on this blog is almost always deletion — cutting the paragraph where we were still figuring out what we meant, and keeping only the version where we'd already figured it out.

What we check before publishing

• Does it say something specific? If a paragraph could apply to any platform or any creator, we either sharpen it or cut it.
• Is there a claim we can't actually back up? We don't cite invented statistics — if we don't have a real source or a defensible heuristic, we don't state it as fact.
• Would this help someone in the next ten minutes? Posts that are purely inspirational without a concrete takeaway get reworked until there's something a reader could actually do differently after reading.

The actual mechanics

Every post is an MDX file in the site's content folder, with a small frontmatter block: title, description, date, tags, and occasionally a platform tag when a post is specific to one. Writing it as a file in the same repo as the rest of the site, rather than in a separate CMS, means a post goes from draft to live with the same review process as any other change to the site — nothing special-cased for content.

Why we don't write on a fixed schedule

We'd rather publish something we'd actually recommend to a creator than hit an arbitrary weekly quota with something thinner. That means the cadence of this blog is uneven by design — more posts in weeks where we have more worth saying, fewer in weeks where we don't. It's the same argument we'd make to any creator asking about their own posting schedule: consistency of quality matters more than consistency of frequency, even if frequency is the easier thing to measure.

What changes as we go

This process itself isn't fixed — we've changed how we track ideas, how much editing happens before something counts as ready, and how strict we are about avoiding fabricated specifics. If something about how this blog is written stops working, we change it, the same way we'd expect any creator to adjust their own process once they notice what isn't working.