{"id":50459988,"title":"Show HN: Lettercamp – open-source static blog framework","points":3,"user":"justswim","time":1794437450,"time_ago":"10 hours ago","type":"link","content":"

Hi HN,

I’m Eric and I’m building Lettercamp, an open-source static blog framework. The repo is at https://github.com/lettercamp/lettercamp and the homepage is online at https://www.lettercamp.com.

Writing good content has always been the #1 way that I’ve grown the reach of products I’ve worked on in the past. However, it’s always bothered me how many little things get in the way of writing and publishing high quality, first party content onto the web.

Building a performant, SEO-optimized blog from scratch was always distracting from development on the actual product, and setting up a 3rd party CMS meant that my content always lived in someone else’s database. Storing content in a non-markdown format also made it difficult to draft and edit with the help of an AI agent.

Lettercamp is a modern approach to creating a content site. It ships with all the little features you’d expect in a blog: pagination, authors, metadata, search, cross linking, related posts and more. It’s also statically built, which means that all your content lives in markdown in your codebase, so a deployed version is performant with no database to maintain. This means that you can focus on writing good content instead of vibe-coding a whole blog.

I want to add more features to the framework over time, including better support for AI agents, built in localization, email sign ups, and more.

The repo is released under the MIT license so that anyone can use the framework to create a content site. The goal isn’t to charge individual developers. The monetization path is to provide a cloud hosted version, that has an online editor that content teams can use. The main advantage of this is to decouple the blog from product deploys, so that teams can publish content without needing to push code.

I would love to get your feedback on if this is a problem that might resonate with you or your team. I know that a lot of products create a /blog section at some point, and I wonder what solutions people are using today. My hope is that over time, Lettercamp can be the go-to solution for teams looking to set this up.

Try it out: https://github.com/lettercamp/lettercamp and let me know what you think!","url":"https://github.com/lettercamp/lettercamp","domain":"github.com","comments":[],"comments_count":0}