Case study / 03
Institutional
Publishing System
Three public static websites plus one private admin app, with shared packages and staff publishing workflows.
Type
Publishing system
Platform
Cloudflare Pages
Status
Built institutional system
Stack
Next.js · R2 · Monorepo
Overview
Institutions need to manage notices, PDFs, galleries, metadata, and public updates without depending on a developer for every small change.
This system gives staff controlled publishing workflows across public sites while keeping a private admin app for day-to-day content operations.
System architecture
Public sites
3 static websites
Admin app
Private staff control
Shared packages
UI · config · content · storage · validation
Storage
R2
Deployment
Cloudflare Pages
Handover
Docs + build/QA commands
Problem
Every content update was a developer task, and the institutions had no way to manage their own public presence.
What it does
- Notices and updates
- PDF and gallery management
- Metadata management
- Staff publishing workflows
- Public site + private admin split
What this proves
- Business and admin system delivery.
- Multi-site monorepo architecture.
- Staff publishing workflows in production.
- Cloudflare deployment planning, production readiness, and handover discipline.