Exercise 1: Why Kanji's Two Original Constraints No Longer Apply — Possible Solution
====================================================================

THE TWO ORIGINAL REASONS
------------------------------
Per this chapter, kanji pages were kept separate for two real reasons: first, fixed depth - the site's old three-level subject/subtopic/page model had no natural slot for "a flat grid of individual characters." Second, no self-contained-fragment convention - a kanji page is a complete, standalone document with its own inline stroke-animation markup and CSS, genuinely different in shape from an ordinary lesson fragment meant to drop into a shared template.

WHY NEITHER CONSTRAINT SURVIVES THIS REBUILD
------------------------------
Per this chapter's own central finding, both constraints were artifacts of the OLD model, not permanent properties of kanji content itself. Chapter 2's Page model supports genuinely arbitrary depth, so a path like japanese/kanji/水 fits exactly as naturally as any deep course path - the fixed-depth problem simply doesn't exist in this rebuild's own architecture. Chapter 4's {{ page.body|safe }} already renders real, admin-authored HTML directly for every page - a kanji page's own stroke-animation markup and inline CSS can live in body and render through that identical existing mechanism, so the fragment-only limitation doesn't exist either. Both original justifications depended on specific properties of the OLD site's model that this rebuild's own architecture simply doesn't share.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly names both original constraints (fixed depth, no fragment convention) and correctly explains that each one was a limitation of the old model specifically, already resolved by this rebuild's own Chapter 2 and Chapter 4 work, rather than a limitation inherent to kanji content itself.