The portal content system became part of the product
How the website grew from portfolio pages into a long-form documentation and notes surface.
Why this mattered
The site started as a public face for projects, but the projects needed more room than a gallery card could provide.
This belongs in the development timeline because Julian Wiley Portal is not a single feature. It is the public Next.js site that hosts project writing, notes, docs, and an auth-gated admin view of the homelab. The project only became useful once its infrastructure decisions were written down well enough to be repeated.
Design decision
Blog posts carry narrative, docs carry reusable guidance, and notes carry reference material that would otherwise stay buried in repositories.
The practical stack around this decision includes Next.js 15, React 18, TypeScript, Ant Design, Pro Components, NextAuth, gray-matter, react-markdown, Docker, GHCR, Kubernetes, Cloudflare Tunnel. I try to keep the interfaces small: configuration describes intent, runtime code owns behavior, and operational notes explain what a future maintainer should check first.
What I would repeat
The portal is now the index for the workspace rather than a separate brochure.
The repeatable pattern is to make the boring path explicit. For this project that means clear repository boundaries, documented setup, predictable deployment commands, and enough observability to know whether the system is healthy or merely quiet.
Reader takeaway
If you are building something similar, start with the workflow you need to repeat every week. Then add only the platform pieces that make that workflow easier to recover, explain, and extend.