primetimetank21.github.io [active]
Portfolio: a browsable site with an optional terminal
A static-first engineering portfolio with native project navigation, an optional terminal, and tested delivery to GitHub Pages.
- Astro
- TypeScript
- GSAP
- Vitest
- Playwright
- GitHub Actions
- Shared typed content
- Static pages + native links
- Optional terminal + themes
Problem
A terminal is a playful way to explore engineering work, but it should not be a prerequisite for reading it. This portfolio pairs that interaction with a browsable site: identity, experience, project details, and contact links remain available without learning commands or enabling JavaScript.
Approach
Astro renders typed content into static HTML for GitHub Pages. Homepage cards and standalone studies reuse one content source and the same study-body component. Native links provide ordinary navigation; independent details/summary disclosures keep the featured studies optional on the homepage. The terminal layers command history, completion, and structured output over that content. Its open command accepts only named local destinations, requests tabs synchronously with opener isolation, and always provides a native fallback link. Shared theme tokens and reduced-motion handling keep presentation separate from the reading path.
Engineering trade-off
Static output keeps the content available without a client-side application, but edits still require a build and publication. The terminal deliberately cannot open arbitrary URLs or paths. A null window.open result is not treated as proof of a blocked tab, because opener isolation can also produce null on success. Motion and theme switching are enhancements, not requirements for accessing the pages.
Evidence
Vitest covers shared content, command parsing, destination boundaries, history, and motion helpers. Playwright exercises native disclosures, no-JS navigation, keyboard behavior, theme persistence, real isolated tabs, fallback handling, and nested 404s against a production build. GitHub Actions separates build/check, unit, functional E2E, and blocking visual comparison; visual baselines use a pinned official Playwright container and a workflow with an optional artifact-only review mode. These checks provide regression evidence, not measured recruiting impact, full accessibility conformance, or physical-device validation. The linked files describe the reviewed engineering baseline, before this study was added.