Track unsearchable plans in monthly analytics
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 12
- Forks
- 2
- Avg merge
- 13d 3h
- Merged PRs (30d)
- 1
Description
Currently we track overall councils with a plan, but don't detail the "unsearchable" ones (html sites we haven't indexed).
There weren't many of these last time I checked, but this is important to understand in terms of basing analysis on "all plans", if there are plans we're missing from search (especially if that's because they're doing something we otherwise like for acccessbility reasons!)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the monthly analytics code and the existing metric for councils with a plan. Trace how unsearchable HTML sites are represented, then add a separate count for them; the work is done when monthly analytics distinguish these plans from the overall total.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100