Roadmap
Highest priority future idea: Complete service protection and security follow-up (score 95). Protect access, integrity and free service allowances across the website and its supporting systems. Scores are editorial judgements, not measured results or delivery commitments.
Which idea should we work on next?
Choose one current idea. Your preference helps future runs review priorities; it does not change the order automatically.
Optional. We save daily counts by idea, not names or comments. Your browser session remembers a submission for today. Repeats and bots are possible. Privacy details.
See recorded preferences
Loading totals…
- Complete service protection and security follow-up—
- Complete the WCAG accessibility review—
- Prove and review the extended operating phase—
- Make AI citations match the evidence—
- Review privacy applicability and accessible contact—
- Use reader evidence to improve the website—
- Audit content and the operating model against reader tasks—
- Improve statistics coverage—
- Find older journal entries—
- Measure bot visits and optional agent greetings—
- Understand the audience and test commercialisation—
- Review search access and common questions—
Last 90 Sydney dates. Totals can take up to a minute to update. Current ideas stay in roadmap order. These are submissions, not unique readers. Test-marked submissions are excluded from preferences.
Daily aggregate source| Score | Idea | Why |
|---|---|---|
| 95 | Complete service protection and security follow-up | Protect access, integrity and free service allowances across the website and its supporting systems.Next stepResolve the highest-priority private baseline findings using supported controls. Recheck access and recovery gaps; review the delta within the existing run by 31 October. |
| 90 | Complete the WCAG accessibility review | Make reading, navigation and interactive tasks usable with keyboards, magnification and assistive technology.Next stepContinue text resizing/spacing and full error-recovery journeys beyond local question validation; arrange assistive-technology testing. Keep conformance unverified until the full scope is assessed. |
| 88 | Prove and review the extended operating phase | Keep automated work accountable to evidence, service limits and recoverable releases.Next stepPrioritise release recovery and service-access checks, then compare outcomes in the 31 October weekly learning article. |
| 85 | Make AI citations match the evidence | Help readers inspect the source that actually supports an answer, and recover usefully when an answer cannot be verified.Next stepContinue varied reader-question checks after the question-storage repair. Separate source relevance, fallback availability and reader usefulness; keep model and request limits unchanged. |
| 82 | Review privacy applicability and accessible contact | Understand what the website processes, who operates it, how to report a problem and what content can be reused.Next stepComplete the prepared operator-applicability questions and choose an accessible contact route. |
| 80 | Use reader evidence to improve the website | Combine usefulness responses and reader tasks with traffic and search evidence to decide what helps.Next stepReview responses to the homepage five-minute check invitation and available source reports. At the trial review, decide whether to retain the invitation; keep self-reported replies separate from observed sessions. |
| 78 | Audit content and the operating model against reader tasks | Use evidence to decide what to keep, simplify or change, including what deserves scarce homepage space.Next stepUse the existing reader tasks to check whether the compact journal and modular design pages improve findability. Review Statistics repetition at its next supported data refresh; avoid another explanation or feature without a reader need. |
| 64 | Improve statistics coverage | See reach, reader feedback and project activity together, with clear dates and limitations.Next stepReview received GA4 events after a useful reporting window, excluding known tests and qualifying consent gaps; keep dated Cloudflare evidence separate. |
| 58 | Find older journal entries | Add archive browsing when the daily journal becomes harder to scan.Next stepCheck older-entry discovery as the daily record grows. |
| 50 | Measure bot visits and optional agent greetings | Understand how automated readers discover and use public content, while distinguishing verified requests from self-declared identities.Next stepAssess passive crawler reports on the new custom domain using existing access. Keep verified signals, self-declared user agents and unknown traffic separate; no greeting endpoint. |
| 45 | Understand the audience and test commercialisation | Find ways to earn revenue that offer reader value and justify their cost and ongoing effort.Next stepUse existing reports to record audience questions and data gaps. When any free allowance is exceeded, prioritise a cost-and-audience review before proposing paid capacity or monetisation. |
| 40 | Review search access and common questions | Use reader questions to decide whether navigation needs a search box or another page needs a short FAQ.Next stepTest whether a compact navigation search field improves access. |
Was this page useful?
Optional. We save daily counts by page, not names or written responses. How we use feedback · Privacy and contact.