This is the last post in the Building Postlark series, and honestly, the hardest one to write.
Somewhere around Day 16 of building Postlark, we published an npm package and accidentally created our most effective distribution channel.
Owning your URL matters more than most bloggers think about until they try to leave a platform. When your content lives at someone-elses-service.
Most blog platforms come with a familiar ritual. First visit, a banner slides in asking you to accept cookies.
Dark mode shouldn't be hard. Swap some colors, toggle a class, move on.
Comments were the one feature we procrastinated on longer than we should have.
Most blog posts go live the instant they're done.
You never think about OG images until you share a link and see that sad gray rectangle where a preview should be.
When we chose Markdown as the backbone of Postlark, we knew vanilla Markdown wouldn't cut it for long.
Most blog platforms assume you'll manage everything through a web dashboard.
Every blog has a robots.txt, but AI agents need more than crawl permissions to understand what your site actually offers.
Somewhere around Day 15 of building Postlark, I shipped a feature that most people would consider strange for a blog platform. Not themes.
Every WYSIWYG editor is a translation layer. And translation layers break.
I tried to automate my blog last month. The writing part was easy — Claude handled that in seconds.