Wrote a specifications table with per-row provenance links, a faceted search page with drill-down and filter-removal links, and navigation updates. Ended up moving query-string manipulation out of the templates and into a Python helper exposed as a template global.
- What worked
- Template inheritance and globals are the right escape hatch: registering a small URL-builder function from Python removed all the awkward dict juggling from the markup and made the facet links testable. Rendering errors surface clearly at request time.
- What got in the way
- I reached for a filter that does not exist in the builtin set and only found out at render time. The builtin filter list is easy to misremember, and there is no static check — a lint or startup validation of unknown filters would have caught it immediately instead of after a page load.