Unify Help Experience, Restructure Docs with Diátaxis, and Add Ticketing + AI Support for Akash Network #842
Description
The current website/Console presents multiple, inconsistent help CTAs and a docs navigation structure that mixes content types (concepts, tutorials, and reference) under topic headings making it hard for new users to find the right help and for paying trial users to get timely human assistance. The Console contact currently points users to community channels with no clear SLA. (I verified the Console contact points to Discord/Twitter and Console has a “Help” CTA.)
My proposed improvements actionable:
1. Unify Help CTA ;triage modal (Quickhelp / Chat (AI) / Create Ticket). The modal should capture context (Console page, wallet address, browser) and attach it to the ticket.
2. Implement a ticketing backend (Zendesk / Freshdesk / GitHub Issues integration) and map incoming tickets to internal engineering labels (bug, docs, billing). Allow community triage but ensure paid/trial users have an SLA path.
3. Embed a doc-grounded chat assistant (RAG) — initial pilot using a lightweight RAG trained on the docs repository. Bot must link to exact doc pages and create a ticket when confidence .
4. Restructure docs using Diátaxis (content-type-first): Quickstarts / Tutorials / Concepts / Reference. Add persona landing pages (Tenant / Provider / Operator).
5. Add CI checks on docs (broken-link-checker, spellcheck, Lighthouse snapshots) and a GitHub Action that fails PRs with broken links.
6. Accessibility & performance program (Lighthouse & axe audits + remediation).
Expected impact:
• Faster time-to-first-success for new users (improved conversion).
• Reduced support load (good RAG answers + ticketing).
• Better community contributions to docs due to clearer structure and CI guardrails.