Portfolio & CV ecosystem
Portfolio and online CV built as one system, so a wording or theme change publishes to both without a frontend deploy.
The problem
I keep a public portfolio and an online CV. Maintained separately, the two drift: a job changes, one gets updated, the other quietly goes stale. I rebuilt them in 2026 as one system with a single content source.
One place to change text or visual style, with the change appearing on both surfaces.
The solution
- Standalone components and signals; content and design tokens fetched at runtime from the CV repo.
- Zero content in the app repo, so copy changes never require a frontend deploy.
- Deployed by GitHub Actions on every push.
Technology
Angular 22TypeScriptSCSSGitHub ActionsGitHub Pages
Want to tell me what needs to be built for you?