docs: add product and Helm chart name conrefs for the enterprise import - #507
Merged
Merged
Conversation
The enterprise import rebases these pages verbatim into solo-io/docs, so 1.x prose arrived downstream saying "kagent" where it should say "Solo Enterprise for kagent", and the install commands pointed at the OSS chart. Adds four conrefs under assets/kagent-docs/snippets/ and wires them up: - helm-path, helm-kagent and helm-kagent-crds across the 8 chart references in setup/installation, agents/agent-memory, observability/audit-prompts, observability/tracing and operations/operational-considerations. helm-path deliberately carries the whole structural difference between the two registries (/helm vs /charts) so that no literal left at a call site is correct for only one side. Release names and the kagent namespace stay literal, being identical on both sides. - name-product at the first product mention on 24 pages. Component names such as the kagent controller and the kagent CLI, link text, headings, reference/community.md and the generated reference/helm.md are left alone. Rendered output on this site does not change: every conref resolves to the value that was previously inline. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Rachael Graham <rachael.graham@solo.io>
Nadine2016
approved these changes
Sep 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds four conrefs under
docs-site/assets/kagent-docs/snippets/and wires them into the 1.x pages, so the enterprise import can rebrand this prose instead of hand-forking the pages.helm-path.mdoci://ghcr.io/kagent-dev/kagent/helmhelm-kagent.mdkagenthelm-kagent-crds.mdkagent-crdsname-product.mdkagentWhy
solo-io/docs rebases these pages verbatim, so today 1.x prose reaches the enterprise site saying "kagent" where it should say "Solo Enterprise for kagent", and the install commands point at the OSS chart. A conref with an enterprise twin at the same path fixes that per file; one without a twin renders this repo's value silently.
Nothing renders differently on kagent.dev. Every conref resolves to the value that was previously inline — verified against a full
make build-docs.Scope
setup/installation(x2),agents/agent-memory,observability/audit-prompts(x2),observability/tracing(x2) andoperations/operational-considerations.helm-pathdeliberately carries the whole structural difference between the two registries (/helmvs/charts), so nothing left literal at a call site is correct for only one side. Release names and thekagentnamespace stay literal, being identical on both sides.reference/community.md(it describes the open-source project), andreference/helm.md(generated byupdate-ref-docs.yaml, so an edit there would be reverted on the next run).Restraint is the point rather than edit cost: even downstream, "Solo Enterprise for kagent" is a first-mention brand name, so substituting all 833 would read worse, not better.
Merge order
First of three. Then solo-io/enterprise-kagent, then solo-io/docs — the downstream build reads this repo's
mainthrough a git worktree, so these calls must land here before the enterprise halves can do anything.🤖 Generated with Claude Code