IA and UX Strategy
This is the operating strategy for a docs-first website that serves both humans and AI agents.
Product objective
- Make first success happen in under 5 minutes.
- Maximize install success and post-install task completion.
- Keep content easy to maintain through markdown-first authoring.
- Support all project types: libraries, applications, games, servers, protocols.
Information architecture
Top-level navigation:
- Home (single-fold landing)
- Overview (long-form “what is AE”)
- Get Started
- Install
- Use
- Hub
- Know
- Develop
- MCP
- Troubleshooting
- Reference
Role-based onboarding
- Beginner: understand, install, verify.
- Developer: install, verify, execute one practical workflow.
- Agent: discover machine docs, execute deterministic command flow, recover by code.
UX standards
- Every task page includes: prerequisites, command, expected result, recovery.
- One task per page to reduce cognitive and retrieval overhead.
- Search enabled locally for sub-100ms feel on typical docs sets.
- Navigation supports linear onboarding plus deep reference traversal.
Flow diagram
mermaid
flowchart TD
home[Home] --> overview[Overview]
home --> getStarted[GetStarted]
overview --> getStarted
getStarted --> beginnerTrack[BeginnerTrack]
getStarted --> developerTrack[DeveloperTrack]
getStarted --> agentTrack[AgentTrack]
beginnerTrack --> installPage[InstallPage]
developerTrack --> installPage
agentTrack --> mcpGuide[McpGuide]
installPage --> verifyStep[VerifyInstall]
verifyStep --> firstSuccess[FirstSuccessTask]
firstSuccess --> useGuides[UseGuides]
useGuides --> developGuides[DevelopGuides]
mcpGuide --> referenceDocs[ReferenceDocs]
referenceDocs --> llmsIndex[llmsTxt]
referenceDocs --> llmsFull[llmsFullTxt]