Portfolio sites get built on heavyweight CMSes and then spend the next decade being patched against vulnerabilities in features their owner never used. Pholio takes the other route: content is plain JSON on disk, every page is rendered at build time, and there is no application server in the request path at all. What the visitor hits is a static file.

Deploys are atomic. Each build lands in its own timestamped release directory and a symlink swaps to it in one move, so a rollback is the same operation pointed the other way, and a request arriving mid-deploy never sees a half-replaced site.

The site you are reading is the proving ground — every structural idea is tried here before it becomes part of the product.