The unit has three parts. The first pages are patterns that every mature site ends up writing, given in both engines so that you copy them rather than invent them: the helper that turns attribute areas into CSS classes, which is the page to read first; heading levels and load priority, decided by a parent and passed down a nested tree; and safe defaults for an unfinished page, with the adaptive component as a last resort. The live preview page then explains which template calls keep a layout area editable in place, which lose it, and the test to run before handover.
The last pages are about upkeep, for the content modeller as much as the developer: names that keep the author's pickers usable and a quarterly audit, the order of steps for renaming or retiring an area or a layout without losing content, and a gallery page that documents the library from the layouts themselves. What a deeply nested component tree costs at render time, and when to flatten it, is in the components unit, on Nesting components, and what depth costs.