Portfolio work is centered on blue-team thinking, visibility, secure workflows, and lab-first iteration.
Blue-team projects, authenticated labs, and the systems I keep rebuilding until they are worth showing.
vmoor.com is shifting from a simple launcher into a single home base for defensive security work, hands-on lab experiments, and a few side projects that show how I approach shipping on the web.
Public notes stay visible on the site while protected lab content moves behind session-based auth.
Design system, shared shell, and lab route structure are now aligned across the site and API.
Where the portfolio is headed
The site now has one structure: public portfolio pages in front, authenticated lab workflows behind them, and live builds around the edges.
Cybersecurity Labs
Public lab notes, protected workspaces, and the first place new security content will land.
Go to LabsCoursework library
Semester-by-semester course pages collect reports, papers, screenshots, and public coursework without burying the class context.
Open CourseworkPortfolio system
Shared styling, shared shell, cleaner paths, and room for future writeups without adding another disconnected page.
See Repository WorkCurrent portfolio surfaces
These are the live pages already running inside the new shell while the security-first sections keep expanding.
Cybersecurity Labs
Public lab catalog, protected routes, and authenticated content previews backed by the API session layer.
Enter LabsCoursework Archive
Reports, research briefs, papers, screenshots, and course artifacts organized by semester and course.
Open ArchiveSleeper Dashboard
A fantasy football dashboard that stays online as a live build inside the same portfolio system.
Open SleeperStream Hub
Streaming experiments stay available publicly while protected security content moves into the labs area.
Open StreamsGitHub Repositories
Source code, experiments, and in-progress builds stay visible there while the site itself gets more curated.
Open GitHub