Technical content agency · Website and CMS blog
CodeContent
A blog an agency could actually publish to
- Client
- CodeContent
- Sector
- Technical content agency
- Built with
- Webflow, Webflow CMS, Technical SEO
- Live site
- Since rebuilt elsewhere
About the project
CodeContent pair engineer-writers with developer tools companies, which means their own blog is not a marketing extra, it is the proof. An agency that sells publishing gets judged on how often it publishes, and a quiet blog is worse than no blog at all. The obstacle is almost never willingness, it is friction: when putting a post up means wrestling a layout, the cadence slips inside a month. So the build put its effort into making publishing the easy path.
- The blog modeled as a CMS collection, not a folder of pages
- Categories and authors modeled before the first post went up
- A post template that holds at four hundred words and at four thousand
- Services and work sections they can extend without help
- Edits absorbed quickly during the build rather than queued
What I actually did
- 01
Model the blog as content
Categories, authors and related posts were structured up front. That is the difference between a blog where the second post inherits everything the first one taught the site, and one where every post is a small build.
- 02
One template, both extremes
Technical writing does not have a predictable length. The post layout was checked at both ends, so a short update and a long tutorial both read properly instead of one of them being the case nobody tested.
- 03
Move quickly and take the edits
Agencies review work for a living and their feedback is specific. Building in a way that made changes cheap mattered more here than getting the first version perfect.
More work
Let's talk
Send me a message on Upwork and tell me what you are working on. If you already have a site and it is not doing its job, that is the more interesting conversation.
New builds, redesigns, and taking over a site somebody else left half finished.