What I Learned Building My Own Angular Portfolio
The idea As an Angular Architect
The tech stack
- Angular 17 with standalone components
- TailwindCSS + DaisyUI for fast, consistent styling
- Static SSR (SSG) for pre-rendering and speed
- Hosted on Vercel
Performance and optimization
Angular often gets labeled as “heavy,” but it doesn’t have to be. By paying attention to details early, I avoided most of the usual problems. Here’s what helped:
- Using Static SSR (prerender) instead of CSR for instant content
- Optimizing assets,converting PNG to WebP and adding proper dimensions
- Preloading only the hero image and lazy-loading the rest
- Keeping bundles small and routes modular
The result? Every page: Home, About Me, Blog scores 100 / 100 / 100 on Lighthouse (Performance, Accessibility, SEO). That alone made all the careful tuning worth it.
Accessibility and SEO
Even on a personal site, accessibility matters. I focused on the basics, done well clean HTML, meaningful tags, readable contrast, and proper alt text. Nothing fancy, just consistent structure that works for everyone. For SEO, I implemented:
- Dynamic and unique meta tags per route
- Proper canonical URLs
- Open Graph tags for social previews
- Sitemap and robots.txt for proper crawling
- JSON-LD structured data for better indexing
And because everything is pre-rendered with SSG, search engines instantly read the real HTML, no waiting for JavaScript to run.
The small details that matter
Final thoughts
This project reminded me how much quality lives in the details. Building the portfolio wasn’t about pushing Angular to its limits, it was about applying care and intention at every step.
"The best web experiences don’t come from big tricks, they come from small, thoughtful decisions stacked together."
That’s what this project became for me: a showcase of precision, simplicity, and everything I enjoy about modern frontend development.
Patrick Linguerri
Angular Frontend Engineer