Skip to content

Restructure the platform docs for the console - #1119

Closed
blkt wants to merge 4 commits into
chore/ai-gateway-docs-groundworkfrom
feat/platform-console-docs
Closed

Restructure the platform docs for the console#1119
blkt wants to merge 4 commits into
chore/ai-gateway-docs-groundworkfrom
feat/platform-console-docs

Conversation

@blkt

@blkt blkt commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Stacked on #1118, which is stacked on #1117. Review those first; this base retargets as they merge.

Implements Phase 1 of the plan for stacklok/stacklok-enterprise-platform#3060.

What

Documents the components that ship today with no public documentation at all, and removes the two sections whose software is being withdrawn.

New sections

  • AI Gateway policy (7 pages) covering model providers, routing and failover, budgets and pricing, prompt injection screening, PCI/PII controls, and audit log forwarding.
  • Identity and directory (6 pages) covering users and groups, SCIM provisioning, identity providers, managed secrets, and virtual API keys.
  • The console (11 pages) split by role, matching the product's own two experiences.
  • Concepts (2 pages), on install-driven visibility and on the two group models.
  • Setup for each gateway, both of which are off by default.

Removed

Stacklok Desktop (5 pages) and the previous console (7 pages), plus the Desktop policy page. All 13 URLs get permanent redirects and every inbound link is fixed, including one from the ToolHive side. Registry, source, and entry administration redirect to toolhive/guides-registry, which already documents that surface in 18 pages.

Decisions worth reviewing

  • Setup instructions are linked, not reproduced. The console generates per-client instructions with the deployment's real endpoints interpolated. Duplicating them here means drift, and a doc page can only show a placeholder.
  • Two pages I did not write. There is no rate-limits page because the AIGateway CRD has no rate-limit fields, so there is no configuration surface to document. There is no transition page because a migration guide is out of scope and, with the product name unchanged, there is nothing to transition between.
  • Enterprise Manager keeps its name. Renaming it would be 10 more redirects for a label change, on a component that still exists under that name.
  • The two group models get their own page. Connector access keys on directory group slugs; cluster authorization policy keys on OIDC claim groups; nothing links them. A customer will assume they are the same, and the failure is silent.

Assumptions stated for the record

  • The connector id space is unified and connectorGatewayDirectoryConfigMigration is default-on by launch. Group-based connector access is documented as a live feature on that basis.
  • The end-user console pages are public rather than customer-internal. If that call goes the other way, the workspace/ directory comes out and its sidebar entry with it.

Not ready to merge

This site is unversioned, so merging deletes docs for software customers are still running. This should land as one merge on launch day, not before. It is a draft for that reason as well as for review.

Verification

npm run build succeeds, so every internal link resolves. tsc --noEmit, prettier --check, and eslint are clean. The build output confirms enterprise-desktop and enterprise-cloud-ui are gone and the new routes render.

Screenshots are not included yet: they should be taken against the shipped console rather than a dogfood deployment, and cropped so the internal route prefix does not appear.

blkt added 4 commits August 25, 2026 21:50
Documents the components Stacklok Enterprise ships that had no public
documentation at all, and removes the two sections whose software is
being withdrawn.

New: an AI Gateway policy section (providers, routing, budgets and
pricing, prompt injection screening, PCI/PII controls, audit log
forwarding), an Identity and directory section (users and groups, SCIM,
identity providers, managed secrets, virtual API keys), a console
section split by role, and two concepts pages. Two setup pages cover
enabling each gateway, both of which are off by default.

Removed: Stacklok Desktop and the previous console, with permanent
redirects for all 13 URLs and every inbound link fixed. Registry, source,
and entry administration redirect to the ToolHive registry guides, which
already document that surface.

Deliberately not written: a rate-limits page (the AIGateway CRD has no
rate-limit fields, so there is no configuration surface to document) and
a transition page (a migration guide is out of scope, and with the
product name unchanged there is nothing to transition between).
@vercel

vercel Bot commented Aug 25, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs-website Ready Ready Preview Aug 25, 2026 11:01pm

Request Review

@blkt blkt closed this Aug 26, 2026
@blkt
blkt deleted the feat/platform-console-docs branch August 26, 2026 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant