Skip to content

Scope solution onboarding CTAs via docset.yml paths#7555

Closed
bmorelli25 wants to merge 1 commit into
mainfrom
cta-solution-paths
Closed

Scope solution onboarding CTAs via docset.yml paths#7555
bmorelli25 wants to merge 1 commit into
mainfrom
cta-solution-paths

Conversation

@bmorelli25

Copy link
Copy Markdown
Member

What

Adds three CTA templates to docset.yml and scopes each to its solution subtree, so the "Get started free" sidebar CTA deep-links into the matching Serverless onboarding flow:

Token Scoped paths
onboarding_token=observability solutions/observability
onboarding_token=security solutions/security
onboarding_token=search solutions/search, solutions/elasticsearch-solution-project

This uses the new cta.<name>.paths key added in elastic/docs-builder#3716. Every page under a scoped prefix gets the right CTA with no per-page frontmatter, and new pages inherit it automatically.

Implements elastic/docs-content-internal#1475.

Exclusions handled for free

The issue asks to exclude the pages already updated in #635 (the monitor-kubernetes / monitor-aws pages from #7135 / #7191). Those pages set an explicit cta id in frontmatter, which always wins over a path scope, so they keep their more specific CTA without any exclusion list. The azure-native-isv-service page lives under deploy-manage/, outside these scopes, and is unaffected.

⚠️ Merge order

This depends on elastic/docs-builder#3716. The current docs-builder does not recognize the paths key, so this must merge after #3716 is released into the docs-builder version docs-content builds with. Do not merge before then.

Open question

ziv's comment on #1475 gave the search scope as solutions/elasticsearch-solution-project, but the published search solution content lives under solutions/search (49 pages vs. 13). I scoped both to onboarding_token=search to be safe. Confirm whether both should carry the search token, or only one.

Test plan

  • After Fix typo #3716 is released, build docs-content and confirm pages under each scope render the correct token in the sidebar CTA URL
  • Confirm the monitor-kubernetes / monitor-aws pages still render their own CTA

Made with Cursor

Adds observability, security, and search CTA templates that deep-link the
"Get started free" sidebar CTA into the matching Serverless onboarding flow
(onboarding_token=observability|security|search). Each template is scoped to
its solution subtree via the new cta.<name>.paths key, so every page under
solutions/observability, solutions/security, and the search solution folders
gets the right CTA without per-page frontmatter.

Pages that already set an explicit cta id (the monitor-kubernetes / monitor-aws
pages) keep their more specific CTA, since frontmatter wins over a path scope.

Depends on and must merge after elastic/docs-builder#3716 is released.
Implements elastic/docs-content-internal#1475.

Co-authored-by: Cursor <cursoragent@cursor.com>
@bmorelli25
bmorelli25 requested a review from a team as a code owner July 23, 2026 22:46
@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@bmorelli25 bmorelli25 closed this Jul 23, 2026
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