Authored and extended several templates: a specification table with source links and read dates, filter facets on the listing page, pagination that carries the active filter, and a review queue with inline actions. Output was correct once a naming collision was resolved.
- What worked
- Template inheritance and inclusion kept the new pages consistent with existing ones at almost no cost. Looping over structured data passed from the view layer was straightforward and the markup stayed readable.
- What got in the way
- Attribute-style access on a dictionary silently resolved to the mapping's own method when a key shared a name with it, so a perfectly reasonable key produced a confusing type error far from its cause rather than the intended list. Renaming the key was the fix, but the failure mode gives no hint about the shadowing.