How I built my blog in one day
In this technical retrospective (2012), @erjjones shares practical architectural lessons learned from running, scaling, or migrating production software under lean constraints.
Core Principles for Independent Builders:
Defaulting to simpler architectures (such as monolithic frameworks, SQLite, or managed VPS) prevents early engineering bankruptcy.
Evaluating true compute and egress costs reveals that high cloud bills can often be slashed by 80%+ through judicious re-platforming.
Code you write at 2 AM as a solo engineer must be easy to debug six months later without complex microservice dependencies.
Community Debate Themes:
HN engineers debated the tradeoffs between cloud convenience and raw server economics, database indexing strategies, and resisting premature architectural complexity.
CATEGORY Frugal Engineering →
HISTORICAL ERA Web 2.0 Genesis (2007–2013)
COMMUNITY SCORE ★ 129 points
TOTAL DISCUSSIONS 62 comments
First of all, I hate the "here is my weekend project I created in x seconds/minutes/days", but I consider the title of this post to be an ellipsis: "How I built my blog in one day and you can too!".
If you click on the link, you'll see that it's a project that is not there to promote the submitter nor stroke their ego, but to help other people simplify something many find to be tedious and difficult - and in an incredibly well-presented way.
I know about the Twitter Bootstrap like everyone and their dog, but I only see articles of praise rather than articles that praise by showing instead of telling through a guide and demonstrating the result in the form of the site itself.
Well done. This is the best article I have seen on Twitter Bootstrap.
The problem with these "I made this X in 5 minutes" announcements is that frequently, it looks like you made it in five minutes (and I don't mean that in a good way). This phrasing " I did X in Y time" is obviously meant to highlight one's skill and speed, but if the product looks crappy, the forest is missed for the trees.
I think this is a neat collection of frontend tools to make your Jekyll (or other static) blog snazzy. It's a good article in that respect: "Here are all the tools you need for a full featured Jekyll blog." But making the point of it being a "fast setup", as someone else pointed out, is a weak point, since wordpress and others are just as fast or faster.
thanks for this. one barrier for me is that it is a requirement for the code snippets to render nicely in google reader, but this can probably be solved by using markdown instead of gists. another barrier is that i can't write special code, like a vanity url redirector, to keep my SEO juice when content moves, but maybe this is not so big an issue as i originally thought it was.
what is your draft management workflow like? this is important to me too, more important in fact than optimizing for people to actually read the blog, because if draft management sucks then i don't blog enough to get readers.
I did something similar last week -- you should invest in theming your site away from the default bootstrappy look/feel. Also it would be helpful to add details some more details about applying/switching themes and perhaps mention customizing the page lists used in navigation via declaring pages in a defined group in the YAML front-matter of a page and iterating over them in your layout's default.html.
How I built my blog in one day:
Sat down with Go, wrote a web handler (they already have http support). Added code to parse a tree of directories containing blog posts. Write markdown code in individual files in those directories. Blog code reads the markdown, parses it, and inserts it into a template. Add Disqus to taste and serve.
Final step: don't submit it to hacker news, profit :)