This engineering portfolio
Gaulatti.com
A React-based portfolio connecting engineering experience, project stories, and public source.
I designed and built this project independently, using my own resources.
Explore the project
Public repository
Browse the live website or inspect its public source.
Technologies
01 / Context
The problem behind the project
A résumé lists roles, while source repositories explain implementation. Project pages connect the two with enough context to understand the work.
This website needs to do two jobs: provide a quick overview of my engineering work and give each project a durable page that can stand alone when shared from LinkedIn. Expanding coverage should preserve the existing portfolio’s visual identity rather than replace it with a different product.
Because social crawlers often do not execute application JavaScript, a client-rendered detail route is insufficient. The first HTML response needs the project’s actual content and preview metadata.
02 / Implementation
Design and implementation
I build and maintain this website, its content model, and the project pages used to explain my engineering work.
I maintain the React Router site, curated catalog, individual project pages, résumé data, search/grouping, and static publication output. The catalog is editorially reviewed; source discovery does not automatically approve content or publish private repository links.
The build projects approved data into a browser-safe catalog, pre-renders each detail page, generates a project-specific preview image, and exports canonical links. The S3 hosting output includes extensionless HTML objects so clean URLs can return their own document.
The index retains the established image-and-text rows and decorative artwork. The added detail pages extend that navigation with architecture, design decisions, evidence, and related systems.
03 / Architecture
Architecture and workflow
Curate and approve
Record project facts, source visibility, and explicit publication approval.
Generate public output
Export approved browser data, project HTML, preview images, sitemap entries, and link listings.
Verify direct links
Check actual static HTTP responses so deep links do not receive a generic homepage.
Publish separately
Keep source changes, build validation, deployment, and live verification as separate milestones.
04 / Approach
Engineering decisions
One project, one durable URL
Each project has an individual page that can be linked from a résumé, a professional profile, or a technical conversation.
Keep the facts in one place
A curated catalog feeds the project index and detail pages, with publication and public-source checks.
05 / Evidence
Evidence and outcomes
The local verification checks publication guards, complete public-repository coverage, initial project HTML, canonical/preview metadata, image dimensions, and the actual preview server’s direct-link behavior.
Desktop and mobile browser checks exercise category filters, search, title/artwork navigation, repository/application links, and résumé layout. The same generated project data feeds the index and detail pages so a content correction reaches both surfaces.
06 / Current scope
Where it stands
This site uses React Router and Bleecker. The previous Astro implementation is preserved in Git history.
The website is a static publication with an explicit approval boundary. A repository discovered during research is not automatically added to the public catalog, and a private implementation is not linked merely because it is mentioned in a project story.