Streamline
A tech publication with a structured editorial backend.
- Year
- 2023
- Type
- Web
- Role
- Design & build
- Stack
- 3 technologies
The problem
Most personal tech blogs are either a static folder of markdown that nobody but the author can update, or a heavyweight CMS that outweighs the writing. Neither works if you want to publish regularly and let someone else edit.
What I built
Streamline pairs a React frontend with Sanity as the editorial backend. Content models are defined as schemas — posts, authors, categories — so structure is enforced at the source rather than patched in the template. Editors write in Sanity Studio; the frontend renders whatever shape they publish.
The outcome
Publishing stopped requiring a deploy. The content model is explicit enough that the site layout can change without touching a single post.
Schema-first content
Posts, authors and categories are modelled in Sanity, so the frontend never guesses at shape.
Editing without deploying
Studio-based authoring means new posts go live without a build.
Built with
- React
- Sanity
- Vercel
Moviemix
Ratings, reviews and where to watch — across films and television.