Convert :personas: metadata to product-design-approved ADP vocabulary#31
Merged
Conversation
Replace the prior 7-slug list (app_developer, agent_developer, ai_agent_developer, platform_admin, evaluator, streaming_developer, data_engineer) across every .adoc page with 5 role-based slugs sourced from the ADP product persona set: * security_compliance_lead * platform_engineer * agent_builder * domain_evaluator * pilot_lead Add docs-data/personas.yaml as the canonical registry, matching the schema used in cloud-docs, rp-connect-docs, and redpanda-labs. Slugs are descriptive role names; no character names appear in the registry or in page metadata. Each page's :personas: line was chosen by reading the page (intro, topic type, learning objectives) and picking the 1-3 personas that genuinely match its audience. :personas: is also added to 45 pages that previously lacked it (index pages, reference pages, stubs). Pure include fragments (no document title or description) are intentionally left untagged; they inherit personas from the including page. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for redpanda-agentic-data-plane ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Per follow-up review, this PR should only update pages that already carried :personas:. Pages that did not have the attribute before (index pages, reference pages, stubs) should not gain it as part of this vocabulary swap. Drops the :personas: line from 45 files that this branch had newly tagged. No other changes; the 93 pages with pre-existing :personas: metadata keep their newly-assigned slugs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
app_developer,agent_developer,ai_agent_developer,platform_admin,evaluator,streaming_developer,data_engineer) with 5 role-based slugs sourced from the ADP product persona set:security_compliance_lead,platform_engineer,agent_builder,domain_evaluator,pilot_lead.docs-data/personas.yamlas the canonical registry for the slugs, matching the schema used in cloud-docs, rp-connect-docs, and redpanda-labs. Slugs are descriptive role names — no character names appear anywhere in the registry or in page metadata.:personas:line. Pages that previously lacked the attribute remain untagged in this PR.Why
The previous persona vocabulary was undefined and inconsistent — 7 slugs in use, no central registry, no agreed semantics, and a clear duplicate (
agent_developervsai_agent_developer). Product design recently produced 7 named personas for the ADP product; this PR aligns the documentation persona vocabulary to that set (using the 5 personas that have an actual doc-reading audience — skipping Tom, who "will not read documentation," and David, an exec-narrative consumer).Each updated page's
:personas:line was chosen by reading the page (intro paragraph, topic type, learning objectives, tasks documented) and picking the 1–3 personas that genuinely match its audience — not a mechanical slug-to-slug rewrite.Persona distribution across 93 updated pages
platform_engineeragent_buildersecurity_compliance_leadpilot_leaddomain_evaluatorThe shape matches the doc surface: platform/build are the bulk; governance, rollout, and verification are appropriately narrow. (Pages can list multiple personas, so totals exceed the page count.)
Preview pages
This PR touches ~90 page files with one-line metadata changes;
:personas:is not user-visible in the rendered HTML, so a single entry-point preview is enough.Test plan
npm run buildsucceeds; only pre-existing warnings (CSV data, attribute-validation forAgentic AI/AIcategories, unlisted-pages) — none persona-relatedgrepwith word boundaries returns nothing)// TODO: confirm persona vocabularycomments remain in governance pagesgovernance/permissions-overview,agents/monitor,ai-gateway/configure-provider,observability/transcriptsFollow-ups (out of scope for this PR)
:personas:slugs in cloud-docs, rp-connect-docs, and redpanda-labs should also be reconciled to the ADP-product vocabulary. Today each repo is sovereign and overlapping slugs (agent_developer,platform_admin) have slightly different meanings across repos.:personas:values againstdocs-data/personas.yamlat build time (none of the repos enforce this today).🤖 Generated with Claude Code