Demo · Sample data
Writer portfolio
Published clips, projects, a gallery and a blog, all editable from a built-in admin panel and all published as a static site.
A process, considered.
One codebase builds two artifacts. The public site is a static export served from GitHub Pages: no server to keep alive, nothing to hack. The CMS is a separate server the owner logs into. Publishing is a rebuild: the static site is rendered from whatever the CMS holds at the moment the build runs, on every change, hourly, or on demand. Nothing is hardcoded to one writer.
Delivered capabilities
- Clips, spot news, projects, internships
- Photo gallery and blog
- Built-in admin panel
- Static export, nothing to attack
- Rebuild on push, hourly, or on demand
These screens demonstrate implemented workflows, not unverified revenue, time savings or returns.