Exercise 2: Why Page Isn't Scaffolded Directly — Possible Solution
====================================================================

WHY SCAFFOLD ISN'T RUN AGAINST Page
------------------------------
Per this chapter, scaffold's generated views assume a plain, flat, non-hierarchical resource - they have no concept of a parent picker, reparenting logic, or a delete guard tied to whether a record still has children. Page's own self-referencing tree structure requires exactly those things, none of which scaffold's default output provides.

WHY THIS MATCHES BOTH SIBLING COURSES' OWN REASONS
------------------------------
Per this chapter, this is the same underlying reason Django's and Laravel's own admin interfaces both needed hand-written code too - a generic starting point, whether it's Django's live-introspected admin or Rails' one-time-generated scaffold, still runs out of coverage exactly where a specific model's own real complexity begins. A tree-shaped model with reparenting and cascade logic is exactly that kind of complexity in every one of the three frameworks.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that scaffold's default output has no support for the tree-specific features Page actually needs, and correctly ties this back to the same underlying reason both sibling courses' own admin interfaces needed hand-written code as well.