Exercise 3: The Real Structural Difference from Next.js — Possible Solution
====================================================================

THE STRUCTURAL DIFFERENCE, NOT JUST SYNTAX
------------------------------
Per this chapter, Next.js runs CSS through its own build pipeline by default - bundling, minification, and optimization are all built in and happen automatically as part of the framework's normal workflow. Django's staticfiles app, by contrast, serves plain files as-is - there is no bundling, minification, or optimization step built into Django itself at all. This is a genuine difference in what each framework DOES by default, not merely a difference in the tags or syntax used to reference a stylesheet.

WHAT IT MEANS IN PRACTICE
------------------------------
Per this chapter, if bundling or SCSS compilation is genuinely wanted in a Django project, it requires deliberately adding a separate package (such as django-compressor) - an explicit, conscious addition to the project, not something that comes for free the way it does in Next.js. For a project this size, this chapter notes that plain hand-written CSS with no build step is a completely reasonable choice, but the absence of that built-in tooling is a real structural fact about Django, not an oversight this course chose not to cover.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies that Next.js includes CSS bundling/optimization by default while Django's staticfiles app has no equivalent built in at all, and correctly frames this as a genuine structural difference in framework capability rather than just a difference in how a stylesheet is referenced.