Building the Audit Report UI

Now that we've covered Normalizing Page Text for Spellchecking, our app can turn messy scraped HTML into cleaner text chunks with useful context.

That is the backend half of the feature.

Now we need the product half: a user-facing audit report.

A useful report should answer three questions quickly:

What page was checked?
   ↓
How many issues were found?
   ↓
Where should I fix them?

This is where the spellchecker starts feeling like a SaaS feature instead of a script. The user should not need to read terminal output, raw JSON, or Django admin rows. They should see a focused page that helps them take action.

In this lesson, we'll build the shape of that report UI in Django: route, view context, template sections, issue cards, and empty states.