Local foundation
Created the portfolio as a local Next.js application and replaced the default starter page with a custom identity-focused site structure.
Project Case Study
Building blamoureux.com as a secure, static-first portfolio platform.
This project documents the process of designing, building, deploying, and protecting my personal portfolio before public launch. The site itself is part of the proof of work: a practical example of frontend development, static-first architecture, secure staging, identity-aware access control, and technical storytelling.
Stack
Tools used to build, deploy, and protect the portfolio.
Next.jsTailwind CSSTypeScriptGitGitHubCloudflare PagesCloudflare AccessCloudflare DNS
Architecture Flow
A simple deployment pipeline with controlled staging access.
Local development on Mac
Git commits used as checkpoints
GitHub repository as source of truth
Cloudflare Pages static deployment
Cloudflare Access protected staging
Custom domain reserved but not connected until public launch
Build Milestones
How the platform progressed from local project to protected staging site.
Version control
Initialized Git, configured the project identity, created a GitHub repository, and established GitHub as the source of truth for deployments.
Static-first architecture
Configured the application for static export because the first version does not require a database, backend services, user accounts, or server-side rendering.
Cloudflare Pages deployment
Connected the GitHub repository to Cloudflare Pages so every push to the main branch can build and deploy through a repeatable pipeline.
Protected staging
Protected the hosted preview with Cloudflare Access so the site could be tested in a real environment before being made public.
Portfolio content system
Built dedicated pages for resume, projects, labs, contact, creative direction, and project case studies so the site can grow into a broader professional platform.
Key Decisions
Keep the first version static
A static-first site keeps the initial architecture simple, fast, low-maintenance, and easier to secure.
Deploy before public launch
Hosting the site early allowed the deployment pipeline, build settings, routing, access control, and mobile experience to be tested before connecting the public domain.
Protect staging with access control
The hosted preview is protected with Cloudflare Access so the site can be reviewed privately while still behaving like a real deployment.
Document the build
The website is not just a container for the portfolio. The build process itself demonstrates technical decision-making, secure delivery, and documentation discipline.
IAM Relevance
The staging model reflects identity and access management thinking.
The project uses access control before public exposure. Rather than leaving an unfinished site publicly visible, the hosted environment is protected while still allowing real deployment testing. That mirrors a practical IAM pattern: separate staging from public production, limit access while building, validate the release path, and publish only when ready.
Lessons Learned
•A simple architecture is easier to secure and explain.
•Deployment should be tested before a site becomes public.
•Access control matters even for a personal portfolio when the work is still under construction.
•Documentation turns a personal website into a technical case study and proof-of-work artifact.
•Design decisions are part of the system, not decoration added at the end.