Markdown-first newsletter purity vs full blog ecosystem
Buttondown's design philosophy is deliberate: a focused newsletter tool that does one thing exceptionally well and resists the feature-bloat temptation that eventually turns every SaaS into a platform. Justin Duke has stuck to that philosophy for nearly a decade. The result is a tool that Markdown-first writers love precisely because it does not try to be everything. The Hacker News community trusts it. The indie-web crowd recommends it. That trust is earned, not marketed. The limitation is structural: Buttondown's web archive is a public-facing list of newsletter issues, not a content platform designed for organic search. There is no per-post SEO configuration, no JSON-LD structured data, no sitemap integration that signals content freshness to search engines. For creators whose audience arrives entirely through the newsletter (via word of mouth, social sharing, or developer community referrals) that is fine — SEO is irrelevant when you do not need search traffic. But for creators who want their writing to compound in search rankings over time, the blog layer matters. A 2,000-word deep-dive published on Buttondown's archive will not rank for anything. The same piece on a VeloCMS blog with proper metadata has a realistic shot at accumulating long-tail search traffic for years. The question is what kind of audience growth you are optimizing for.
When “one tool that does everything” becomes friction vs simplicity
The dual-tool setup — Buttondown for the newsletter, a separate blog for content, Gumroad for products — is genuinely fine at small scale. Many successful indie creators run exactly this stack. The friction surfaces at three inflection points. First, when you want newsletter subscribers and blog subscribers to be the same list. Managing opt-ins from two different sources into two different tools, syncing them via Zapier, and keeping unsubscribes consistent is manageable overhead until it suddenly is not. Second, when you want a past newsletter issue to rank in search — impossible in Buttondown's archive, straightforward in VeloCMS's blog. Third, when you add commerce: if your monetization is a paid newsletter subscription, Buttondown handles it cleanly. If you want to sell anything beyond the subscription — an ebook, a course, a design resource — you immediately need a third tool. That is not a criticism of Buttondown, which was never designed to be a commerce platform. It is a description of where VeloCMS earns its position for creators who have outgrown the focused-tool stage.
Newsletter platform cluster: five-platform comparison (Substack / Beehiiv / Kit / Mailchimp / Buttondown / VeloCMS)
The newsletter platform market has fractured into distinct positions that rarely overlap. Substack is the largest network with the most powerful discovery layer — but it takes 10% of subscription revenue and offers minimal design flexibility. Beehiiv is the growth-hacking platform: referral programs, ad network, and recommendation feeds at 2.5% on paid tiers. Kit (formerly ConvertKit) is the automation engine for creators with complex email sequences, tagging, and conditional logic for large audiences. Mailchimp is the legacy tool: full-featured, expensive at scale, and still used by organizations who started email marketing before the newsletter renaissance. Buttondown is the Markdown-first independent choice: flat-fee pricing, no revenue cut, minimalist admin, and a solo-developer ethos that its community genuinely appreciates. VeloCMS sits in a different position entirely: it is not a newsletter-first tool. It is a blog-first platform that includes a full newsletter engine, digital product checkout, and 30 design themes — built for creators who want a single brand platform rather than a stack of specialized tools. The choice between Buttondown and VeloCMS is ultimately a question of what comes first. If the newsletter is the product and the blog is secondary (or absent), Buttondown is the cleaner choice. If the blog is the product and the newsletter is how you build the relationship with your readers, VeloCMS is designed for that priority order.