apps/web
Guy OS
The public portfolio app that frames the monorepo as a coherent product platform.
- portfolio
- branding
- platform
Problem
The product or system question the lab was meant to make concrete.
The portfolio needed to stop feeling like a loose collection of demos and start explaining the product engineering judgment behind the monorepo.
Role
How I used the lab to test architecture, UX tradeoffs, or product modeling.
I rebuilt the public surface as an Astro-first portfolio with local typed data, structured metadata, and service-oriented positioning.
Decisions
The product-system choices that make the experiment useful beyond the demo itself.
Moved public pages to static Astro templates instead of client-heavy React routes.
Kept data close to the pages so content can be reviewed without a remote content service.
Added search-friendly schema around the owner, capabilities, contact path, notes, and proof pages.
Outcome
What the lab clarified or proved once the model was built.
The site now behaves like a professional portfolio and services surface at the same time: fast static pages, clear calls to action, and stronger explanation of the platform work.
Proof points
Evidence that the experiment surfaced durable implementation ideas.
- Static build with production-safe sitemap and robots output.
- Reusable local data records for capabilities, notes, work, labs, and profile content.
- Structured page metadata that identifies Guy Romelle Magayano as owner, author, publisher, and provider.