12 of 14
Platforms
Enterprise Content Platform
A custom CMS for a university doing 2M+ daily reads. Publishing went from two days to fifteen minutes. Editors don't need an engineer to push a post any more.
- Built at
- TechnicalBind
- Scale
- 2M+ daily reads.
- Category
- Platforms

- To Publish
- 15 min
- Load Time
- <50ms
Context
Every new article meant a code change and a deploy. Editors waited days. Engineers did weekend pushes.
Challenge
Hand editors a self-service workflow without putting the public site at risk.
Non-negotiables
- Multi-language support
- Fast page loads
Calls I made
- 01
Editor and reader split
Decoupled the editor from the public site. Editor downtime never reaches visitors.
- 02
Pre-rendered pages in memory
Published pages are pre-rendered and served from memory, so traffic spikes are absorbed cleanly.
Trade-offs accepted
- Optimised for readers first. The editor is functional rather than visual, while the public site is fast.
- Accepted that search takes a few minutes to update after publishing.
Outcome
Editors publish on their own now. Page loads came in under 50ms. And engineering is out of the publishing loop entirely.
Stack
- Python
- Django
- TypeScript
- React
- Tailwind CSS
- PostgreSQL
- Docker
- GitHub Actions for CI/CD
- Linux VPS
- Celery
Got something similar in mind?
Send 3 lines. I reply within a day.