About This Website

A static portfolio system built to present shipped game work, playable prototypes, tools, engineering evidence, and supporting creative archives.

Static HTML output SCSS component styling Plain JavaScript modules Gulp delivery workflow

Portfolio Infrastructure

This site is both a public portfolio and a production exercise: content is authored in source pages, components, data files, and SCSS, then compiled into static output for fast hosting and simple deployment.

Project Evidence

Case studies, playable game mirrors, media galleries, project summaries, and technical detail groups are organized around hiring and production review.

Engineering Inventory

The engineering page works as a searchable technical inventory for engines, languages, platforms, tools, workflows, and production support experience.

Archive Surface

Web, video, and music sections keep supporting work accessible without competing with the primary game engineering portfolio path.

Build System

Source-first pages and assets compiled into static delivery output.

Technical Stack

Generation

Static Site Workflow

NPM and Gulp build tasks
Reusable HTML includes and data-driven loops
Source/output separation for generated pages
Cache-busted static assets

Styling

SCSS Architecture

Shared frame, action, hero, and content styles
Page-specific stylesheets for portfolio sections
Responsive layout utilities and compact content cards
BEM-informed component naming where useful

Behavior

Browser Modules

Plain JavaScript modules instead of jQuery
Feature detection with Modernizr
Debounced and throttled interaction support
PhotoSwipe galleries and Prism syntax highlighting

Presentation

Content System

Project cards and case-study components
Structured JSON for repeated portfolio data
Responsive media and WebP image delivery
Shared action cards across major site paths

Maintenance Priorities

Keep the site fast, inspectable, and easy to update as the portfolio changes.

Ongoing Design Rules

Fast Static Delivery

Pages stay static, assets stay optimized, and the delivery path avoids runtime dependencies that are not needed for portfolio browsing.

Asset Discipline

Compiled image references use WebP delivery assets, while source-format raster files stay in development folders.

Primary hiring paths lead to work, engineering, tools, about, resume, and contact, with creative archives grouped separately.

Engineering focus

Project-backed systems, skills, and contact paths.

WorkGame project case studies EngineeringSystems, tools, and stack ToolsUtilities and workflow apps AboutBackground and focus RésuméPDF career summary ContactHiring and project contact

Supporting creative and web work.

Web SystemsSites and browser demos VideoUnreal cinematics and edits MusicAudio work and covers