epic: Rossoctl Documentation and Usability Improvements

[mrsabath]

Problem

Rossoctl's documentation and user experience have gaps that make it difficult for new users to understand, install, and operate the platform. Docs are spread across repos, mix audiences (developer vs operator vs architect), and lack a cohesive narrative about what Rossoctl is, what it does, and where it's going.

For the project to grow adoption, users need:

• A clear overview of what Rossoctl is and why it matters
• Straightforward installation instructions
• Component documentation that explains each piece and how they fit together
• A visible strategic direction (North Star) so contributors and adopters can plan
• Links to current news, publications, and community updates
• Polished usability across the platform (UI, CLI, APIs)

Scope

Documentation and usability improvements across Rossoctl. Each sub-issue is independently deliverable.

---

Sub-Issues

Tracked natively as GitHub sub-issues (see the sidebar). Current status:

v0.7 website docs (active)

Item	Status
Docs Information Architecture + content strategy for v0.7 (#2117)	OPEN — the active driver for the website docs
Move .github repo from Experimental to Core on org profile (#2292)	OPEN — merged via rossoctl/.github#106

Related merged work (PRs — cannot be linked as sub-issues, referenced here):

• Feat: migrate marketing site to Docusaurus (rossoctl) with synced docs .github#88 — Migrate marketing site to Docusaurus with synced docs (website-docs foundation) — MERGED
• Docs: Organize docs for website #2253 — Docs: Organize docs for website (categories, draft-marking) — MERGED
• Docs: Rework docs for 0.7 part 2 #2287 — Docs: Rework docs for 0.7 part 2 — MERGED
• docs: move .github repo from Experimental to Core .github#106 — Move .github to Core on org profile (closes Move .github repo from Experimental to Core on org profile #2292) — MERGED
• Companion website-enable PR: Docs: Enable documentation section of website .github#95

Documentation

Item	Status
AuthBridge documentation (security model, deployment, demos, roadmap) (#1470)	CLOSED / done
AuthBridge demo docs fixes (#1679)	CLOSED / done
Rewrite AuthBridge sidecar injection guide for 0.7 (#1794)	OPEN
Installation guide improvements (#1471)	OPEN
Component overview (#1472)	OPEN
North Star / long-term strategic vision (#1473)	OPEN (labeled stale)
News, publications, and community hub (#1474)	OPEN
Document UI-driven config for agents and tools (#1436)	OPEN
How to create a Keycloak client on kind (#1329)	OPEN
Feature-flag endpoint path fix in CLAUDE.md (#1132)	CLOSED / done
Stale Weather/GitHub-issue demo docs (#920)	CLOSED / done

Usability

Item	Status
General usability improvements (UI, CLI, onboarding) (#1475)	OPEN

Rollup: 5 closed, 10 open sub-issues (as of 2026-07-28).

---

Success Criteria

• New user can understand what Rossoctl is within 2 minutes of landing on the repo
• Installation from zero to running cluster documented with <10 steps
• Every major component has a one-paragraph explanation and link to detailed docs
• Strategic direction visible to adopters and contributors
• Blog posts and publications linked and discoverable
• First-time user experience is smooth (UI, agent deployment, auth)

---

Renamed Kagenti → Rossoctl and status refreshed 2026-07-28. #2117 moved here from the closed rename epic #1997.