Present cybersecurity projects, labs, credentials, and investigations in a way that recruiters and technical reviewers can understand quickly.
Aegis Portfolio System
A responsive portfolio system designed around clear evidence, accessible navigation, and focused presentation of cybersecurity work.
30-second summary
A multi-page static portfolio with a reusable visual system, persistent light and dark themes, responsive content layouts, and keyboard-accessible interactions.
Reduce visual noise so project scope, evidence, technologies, limitations, and actions remain easy to scan.
Audience and information architecture
Can quickly find experience, current focus, verified credentials, featured projects, and a resume without parsing every page.
Can open case studies and inspect architecture, technologies, engineering decisions, limitations, and repository links.
Can browse hands-on labs, written investigations, and writeups grouped by subject rather than hidden in one dense list.
Receive the same content hierarchy with stacked layouts, large touch targets, collapsible details, and no reliance on hover.
How the site works
and structure
Design system
Dark green-black surfaces establish a restrained technical character. Light mode uses neutral parchment surfaces and dark green text so the day experience remains professional rather than washed out.
Instrument Serif carries editorial project and section headings, while DM Sans provides clear navigation, labels, body text, and interface controls.
Shared buttons, pill tags, project metadata, case-study sections, tables, details panels, tables of contents, and closing CTAs maintain continuity across pages.
CSS custom properties centralize background, surface, text, muted text, borders, accent, and foreground colors for consistent light and dark rendering.
Content and interaction features
The theme control follows system preference on first visit and saves the selected light or dark mode in local storage.
Credentials include image previews and direct verification links where an issuer URL is available.
The lab interface supports search, category tabs, and progressively expanded lists so content stays useful without becoming visually overloaded.
Each flagship page moves from a short executive summary to architecture, technical decisions, limitations, quality work, and closing actions.
Featured work is separated from smaller entries, giving flagship projects stronger hierarchy while retaining a complete project inventory.
The site is built from semantic HTML and static assets, allowing hosting as plain files without an application server.
Accessibility and responsive behavior
Semantic landmarks, one primary page heading, descriptive section headings, native links, buttons, tables, lists, and dialog elements improve navigation and assistive technology support.
Controls expose visible focus states, interactive elements retain native keyboard behavior, and motion is avoided where it does not communicate a state change. The layout respects the user’s reduced-motion preference.
Grid and flex layouts collapse into single columns, tables receive a bounded scroll region, navigation wraps without widening the document, and text reflows at narrow widths.
Accessibility testing approach
Manual checks cover keyboard reachability, visible focus, theme contrast, mobile document width, image alternative text, heading order, external-link behavior, and use of native controls. Automated browser checks are appropriate as a supplement, not a replacement for manual testing.
Engineering decisions
Semantic HTML, modern CSS, dialogs, CSS grid, and browser APIs are used before adding an abstraction.
Why: Less JavaScript and fewer dependencies reduce the surface that needs maintenance.The theme choice is stored under a single key, and interactive state is reflected in the document’s data attributes and control labels.
Why: State is predictable across page loads and easy to inspect.The flagship case study is a real HTML document rather than hidden modal-only content.
Why: It works without application state, can be indexed, shared, bookmarked, and opened in another tab.The static entries are included explicitly in the Vite build configuration and served through a standard preview workflow.
Why: Vite provides repeatable local builds and production asset handling while preserving a largely static architecture.Performance and security approach
No framework runtime is required for the primary static interface, and supplementary visual behavior is isolated to small JavaScript modules.
Long lists are displayed or filtered through user actions where appropriate instead of forcing every item into immediate dense visual prominence.
External links identify new-tab behavior and use rel="noopener noreferrer" when they open in a separate browsing context.
The portfolio does not collect application credentials, accept user data through a backend, or execute untrusted server-side content.
What I measure rather than promise
For performance work, the appropriate validation is measured browser evidence: document and asset size, mobile network behavior, layout stability, interaction responsiveness, and production build output. I have not added invented Lighthouse scores or load-time claims to the portfolio.
Problems solved
Day-mode surfaces lacked enough contrast
Problem: Light-mode surfaces used near-transparent or overly pale colors that made cards, controls, and borders difficult to distinguish.
Fix: Theme-specific surface and text tokens were separated, borders were strengthened, and light-mode cards were given consistent readable backgrounds.
Lesson: Changing theme colors is not enough; each component family should be reviewed against its actual hierarchy.
Theme switching was inconsistent across pages
Problem: Secondary pages could initialize with the wrong color scheme or fail to update controls because behavior depended on page-specific markup.
Fix: Every HTML entry uses an early theme initialization script, the document stores one theme key, and JavaScript guards optional controls.
Lesson: Color preference and persistence belong at the document level before rendering begins.
Long lab lists could overwhelm the page
Problem: Multiple hands-on lists made the browser view dense and made the intended evidence difficult to scan.
Fix: Search, category filtering, section tabs, and progressive expansion separate discovery from full inventory.
Lesson: Information architecture should control density as strongly as visual styling does.
Quality checklist
- Build validation: Static pages are included in the production build and checked through the local Vite preview server.
- Cross-page consistency: Header, theme control, navigation, cards, case-study sections, and closing links share the same styles and patterns.
- Responsive review: Desktop and narrow viewport layouts are checked for horizontal overflow and readable line lengths.
- Content review: Project claims are separated from assumptions; invented metrics and unsupported production claims are not added to project summaries.
- Navigation review: Internal section links, case-study links, document titles, external repository links, and CTAs are checked for the correct destination.
Current limitations and next work
New case studies are currently maintained as standalone HTML, so repeated navigation and metadata must be updated carefully across pages.
Visual and accessibility checks can be expanded with repeatable browser tests, automated link validation, and production build checks.
Images should continue to be audited for dimensions, format, loading behavior, alternative text, and display-specific crops.
Adding analytics would require balancing portfolio insight against privacy, consent, and unnecessary third-party tracking.
How I built it
I mapped the portfolio audience first, organized content around a recruiter-to-engineer reading journey, built the reusable visual system, added interactions only where they improved navigation, and reviewed each page in both themes and across viewport sizes.
Project outcome