Most small studios keep their notes to themselves. The thinking behind a decision gets made once in a meeting, written down nowhere, and then rediscovered the hard way eighteen months later. The Zlog exists to stop that.
It is a blog about the work: website strategy, design, deployment, and the unglamorous part — keeping a site healthy long after anyone calls it new.
What this is for
Three things, in priority order.
1. Writing down the process. Most of what we know is repeatable, and repeatable work should not depend on one person’s memory. Putting it here means the reasoning survives the person who had it.
2. Answering questions before they become emails. A small business owner asking whether they need a CMS deserves a real answer. If we have written it once, we can point at it instead of typing it a fourth time.
3. Showing the work honestly. Portfolio pages show results. A blog shows judgement, including the parts that were corrected later.
What we will not do here
No growth-hacking listicles, no recycled industry statistics, and no post that exists only to rank for a keyword. If a piece is here, it is because we learned it the expensive way and think it is worth the reading time.
How it is built
The honest answer is that there is almost nothing to it. Each entry is a single Markdown file with a date in the filename, sitting in one folder. The host builds it into a dated page and publishes it. No dashboard, no database, no admin panel to secure, no plugin that breaks when it is three years old.
That sounds unremarkable because it is. It is also the entire reason the writing will keep happening, because publishing an entry is a text file and a commit rather than a production.
If it is not worth writing down, it is not worth doing twice.
The first entry
This one. There will be more, and they will be uneven in length, because some things take a paragraph and some take an afternoon.
If there is a question you would like answered here, tell us what to write about next — that is genuinely how the list gets built.