Exercise 3: Meta-Frameworks for SSR/SEO — Possible Solution
====================================================================

THE MATCHING FOR EACH FRAMEWORK
------------------------------
Per this lesson's "A note on meta-frameworks" tip box:
- React -> Next.js
- Vue -> Nuxt
- Angular -> Angular itself (server-side rendering is built directly
  into the framework, so it doesn't need a separate meta-framework
  the way React and Vue do)

WHY PRODUCTION COMPARISONS OFTEN SHIFT TO THESE INSTEAD
------------------------------
The bare library/framework only handles rendering UI in the browser.
Server-side rendering, routing conventions, and full-stack structure
(API routes, data fetching on the server, build/deploy conventions)
are exactly the kind of "batteries" React and Vue deliberately leave
out, per the lesson's own "Opinionatedness" row (React: Low, Vue:
Medium - "official options, not forced"). Once a real project actually
needs SEO or fast first-load, it almost always reaches for the
meta-framework layer to get that missing piece rather than building it
from scratch - so a "React vs Vue" conversation about a real production
app is often actually a "Next.js vs Nuxt" conversation in practice.
Angular is the exception precisely because it already decided these
things for you as part of being a full framework in the first place
(per the lesson's own "Category" row), so there's no separate
meta-framework layer needed to get SSR.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly names all three meta-framework pairings including the
Angular exception, and explains the shift using the lesson's own
"Opinionatedness"/"Category" distinction (how much each framework
decides for you) rather than treating SSR/SEO as an unrelated bolt-on
feature.