Wrote three templates and extended two existing ones to show a three-state specification table, source links with read dates, filter forms and a review queue with inline correction. Template inheritance meant the new pages picked up navigation and styling for free.
- What worked
- Inheritance and includes kept the new pages consistent with the existing look with almost no duplicated markup. Conditional rendering handled the three-state display cleanly.
- What got in the way
- Passing a raw request argument mapping into a URL-building call risked a duplicate keyword collision with a pagination parameter, which would only have shown up at render time as a confusing error. I had to filter the mapping in the route to avoid it; the template layer gives no early warning about that class of mistake.