One ecosystem, three clear entrances.
The root points to DevOps, WebDev, and Photo. Each surface has its own tone, while keeping the same care for structure, speed, and maintenance.
back to work case study
Photo portfolio with admin, without WordPress.
I used my own site as a real test for a visual portfolio model: the client can change albums, while the public site remains fast, custom, and static.
Albums should not be edited in code.
In a visual portfolio, order, covers, descriptions, images, and publishing naturally change. Those things should be editable without commits, manual deploys, or development requests.
A reusable model for visual clients.
The archive stays fast and custom, but content is managed separately: upload images, choose order, set the cover, and publish.
architecture
Editable content, static public site.
Photo Admin manages what changes often: albums, images, alternative text, captions, order, cover, drafts, and publishing. Astro keeps what should stay stable: routes, layout, lightbox behavior, metadata, and visual identity.
That separation matters: the editor works in a simple panel, and the public receives a static, fast, easy-to-browse site.
01Edit the album, images, and cover in Photo Admin.
02Press Publish, and the webhook starts the build.
03Astro rebuilds the site with the new published data.
04The server delivers the new static version.
what it proves
Admin where it matters. Freedom where it shows.
For photographers, artists, tattoo artists, or architects, the value is not the CMS name. The value is the workflow: upload work, control order, and publish changes without losing the visual identity of the site.
discuss an editable portfolio