Skip to content
JL/
All work
04 / PROJECTWeb DevelopmentIn Progress

This Portfolio: Cybersecurity, Next.js & CMS

What started as a cybersecurity course requirement became a full publishing platform for my work. I built it to make projects, labs, certifications, and lessons easy to document and manage from one place — turning a personal portfolio into a product I actively maintain, refine, and expand.

It Started as a Course Requirement

The original goal was simple: create somewhere to present work from the Google Cybersecurity Professional Certificate. The suggested solutions were a folder, Google Drive, Google Sites, or a Git repository.

I decided to build the platform instead.

From Portfolio to Publishing System

As I added software projects, networking labs, cybersecurity exercises, certifications, journals, and creative work, manually editing the site stopped making sense. I built an administrative CMS so the portfolio could grow without every content update becoming a coding task.

The CMS now manages projects, labs, journal entries, certifications, media, skills, metadata, drafts, publishing states, featured work, and different content structures for different kinds of work.

The Hard Part Wasn't Adding Pages

Most of the meaningful work happened after the first version already existed. I had to improve unreliable editor saves, media handling, content relationships, publishing behavior, search, responsive admin tables, dark-mode inconsistencies, dialogs, metadata controls, and cache synchronization.

Features that sounded small often crossed several parts of the system. For example, changing the homepage from 'latest projects' to intentionally selected Featured Work required new CMS controls, limits, validation, and public-site behavior.

Designing the Admin as Part of the Product

I wanted the administrative side to feel like the same product as the public portfolio. Forms, tables, dialogs, notifications, media management, editors, and custom controls all follow the same Bauhaus-inspired visual system rather than falling back to a generic dashboard.

What This Project Demonstrates

This portfolio is both the place where I present my work and one of the clearest examples of how I work. It has grown through repeated cycles of building, finding weak assumptions, troubleshooting them, and improving the system without discarding everything that already works.

What began as a course activity became a long-running product that I actively maintain and use.