Local Developer Ships Blog Platform From Scratch
A publishing tool built for writers, not algorithms — Go backend meets Next.js frontend in a platform that puts reading first
By ERIC LUEC | Staff Engineer
All the Code That's Fit to Ship
A publishing tool built for writers, not algorithms — Go backend meets Next.js frontend in a platform that puts reading first
By ERIC LUEC | Staff Engineer
Most blogging platforms are built for scale, not for the writer. They bury the reading experience under layers of ads, pop-ups, and algorithmic feeds. The words themselves become secondary to engagement metrics. What gets lost is the simple pleasure of reading something well-written in a well-designed space.
Quotes, too, have no proper home. They live in screenshots, notes apps, and bookmarks that never get revisited. There is no single place to collect, organize, and resurface the words that mattered enough to save.
Post IT was born from this gap: a platform where publishing is frictionless, reading is beautiful, and quotes live alongside long-form content as first-class citizens. It answers the question every writer eventually asks — where can I write without fighting the tool?
The content model treats blog posts and quotes as parallel entities with shared tagging and search. A post can reference quotes; a quote can stand alone. This dual nature gives the platform its character — part journal, part commonplace book.
Every design decision was tested against one criterion: does this help or hinder the act of reading? Animations were stripped to near-zero. Chrome was reduced to the bare minimum. Typography was given room to breathe.
“The best writing tools disappear. You should feel the words, not the software.”
The backend is written entirely in Go, chosen for its performance characteristics and clean concurrency model. It handles content storage, user authentication, and API routing with minimal overhead. Every endpoint is deliberate — no framework magic, no ORM abstraction layer.
The frontend is a Next.js application that prioritizes typography and reading comfort above all else. Server-side rendering ensures fast initial loads, while the component architecture keeps the content management interface responsive and predictable.
Two languages, one philosophy: keep it simple, make it fast, let the content breathe. The Go server handles what servers do best — data and logic. Next.js handles what React does best — interfaces and interactions.
Go
Std-lib HTTP server. RESTful API. Zero framework deps. Clean concurrency.
Next.js
Server-rendered React. Typography-first. Optimized for reading speed.
Auth
Session-based authentication. Secure cookies. No third-party OAuth needed.
Search
Full-text search across posts and quotes. Shared tagging for discovery.
Postgres
Structured data storage. Reliable transactions. Clean schema design.
Docker
Containerized deployment. Single compose file. Dev and prod parity.
Typography
Serif-first design. Generous whitespace. Warm color palette throughout.
Markdown
Native markdown support. Code blocks, quotes, lists. Write in plain text.
Next Project
Budget Tracker