Personal Portfolio
A static-first developer portfolio combining an architectural design system, responsive layouts, and purposeful motion to present projects and engineering capabilities.

Lead Developer & Designer
Project context
A distinctive developer portfolio that demonstrates how design and engineering decisions work together in practice.
The problem
Most developer portfolios list skills without demonstrating how design and engineering decisions work together. The challenge was to create a distinctive experience that remains readable, responsive, accessible, and straightforward to maintain.
Technical approach
Built static-first pages with Astro, reusable content-driven components, and a consistent Tailwind CSS design system. JavaScript is reserved for focused interactions such as navigation, galleries, and presentation motion, with reduced-motion preferences respected where animation is used.
Design goal
Present the work as readable case studies rather than isolated screenshots. The portfolio connects the project’s purpose, technical choices, and visible interface so a reader can understand both what was built and the reasoning supported by the available documentation.
Architecture and content
Astro generates the portfolio pages from reusable components and structured project data. Project descriptions, technologies, links, and galleries belong to the content layer, while layouts define how they are presented. This makes it possible to update a case study without rebuilding its page structure by hand.
Project data model
A typed Project interface defines titles, descriptions, technologies, dates, external links, and optional galleries. The catalogue feeds the list, home-page showcase, and detail routes. Optional fields allow a developer tool and a visual website to share the same content model.
Routes and translations
Astro generates project routes from the catalogue at build time. English and French copy is organized in translation trees and applied to marked interface elements. Section anchors identify reading destinations within each case study, independently of the language used for their visible titles.
Interface and motion
The visual system uses consistent spacing, typography, and grid lines to connect the home page, project index, and case studies. Tailwind CSS supports the responsive layouts, while GSAP and focused browser scripts handle presentation motion and interactions. Reduced-motion preferences are considered wherever animation is used.
Motion responsibilities
GSAP supports presentation motion while focused scripts handle navigation and galleries. Animation is a separate responsibility from the project content: the description and main reading order remain available in the generated HTML. Motion should support orientation without taking control of the reading pace.
Reading and accessibility
Case-study headings provide a structured reading order and direct section links. The gallery supports keyboard activation and a dialog for full-size images. Responsive layouts move the contents navigation above the article on narrow screens, keeping navigation reachable without squeezing the text column.
Key capabilities
- Responsive multi-page portfolio
- Reusable, content-driven Astro components
- Animated project presentation and image galleries
- Accessible navigation and reduced-motion support
Outcome
A cohesive, performant portfolio that stands apart through purposeful motion and clean architecture.
Maintenance and evolution
The portfolio is a living presentation of engineering work. Its value depends on keeping descriptions, screenshots, and links aligned with each project’s actual state. The component and data structure supports that editorial work, while accessibility and responsive behavior remain considerations as new sections are added.
Content maintenance
A shared page template makes layout changes available to every case study. Project-specific explanations remain in structured content, so their accuracy still requires editorial review as projects evolve. Screenshots and external links should be reviewed alongside the written descriptions.



