AI Search UX for Large Wikis
A large wiki needs guided discovery. Visitors may not know whether they need setup, memory, tools, security, automation, or troubleshooting.
When this matters
This page is for operators who want Rocky to produce usable work without turning the system into a mystery box. Use it when you need a practical path, a clear verification step, and a boundary between suggestion and action.
The operating pattern
- Support plain language. Rank pages by title, tags, category, summary, and practical intent.
- Add process chips. Offer common goals like start here, fix a problem, connect tools, or stay secure.
- Show instant previews. Return titles, categories, and summaries before navigation.
- Keep article search compact. Inside pages, search should be available but not dominate the reading flow.
- Measure gaps. No-result searches are topic ideas.
Pre-flight checklist
- Search accepts symptoms and goals
- Results are visibly ranked
- Chips help beginners start
- No-result state suggests alternatives
- Mobile search is easy to use
Common failure modes
- Keyword-only thinking: Users often search with goals, not official labels.
- Huge scroll walls: A list of 200 pages without guidance feels like clutter.
- Hidden search: On a wiki homepage, search should be obvious.
Verification
A page is not done because it was drafted. Verify the source, run the workflow, inspect the output, and record what changed. If a step touches money, customers, accounts, permissions, or private data, keep it behind an explicit human approval gate.