Skip to content

[DOCS-14086] Centralize site-support banners for 9 integrations#36672

Merged
hestonhoffman merged 2 commits into
masterfrom
heston/DOCS-14086-site-support
May 14, 2026
Merged

[DOCS-14086] Centralize site-support banners for 9 integrations#36672
hestonhoffman merged 2 commits into
masterfrom
heston/DOCS-14086-site-support

Conversation

@hestonhoffman
Copy link
Copy Markdown
Contributor

@hestonhoffman hestonhoffman commented May 13, 2026

Moves site-support banners from inline integration README blocks to centralized unsupported_sites entries in params.yaml. The docs build system renders the banner automatically at build time, so inline blocks in integration source repos are redundant.

Companion PRs (remove inline banners from source repos)

Merge instructions

This should be merged just before we merge the integrations PRs to make sure there isn't a large lag where the pages have double banners.

Move site-support banners from inline integration README blocks to
centralized unsupported_sites entries in params.yaml. The docs build
system renders the banner automatically via path-segment matching
when the integration slug is listed as a key.

New unsupported_sites entries (all [gov,gov2]):
  alibaba-cloud, amazon-compute-optimizer, amazon-xray, confluence,
  confluent_cloud_integration, gitlab-source-code, launchdarkly,
  oracle-cloud-infrastructure, pagerduty

For confluent-cloud, uses a targeted cascade in integrations/_index.md
to set site_support_id: confluent_cloud_integration, avoiding a
path-segment collision with the api/v2/confluent-cloud/ API reference.

Companion PRs that remove the inline banners from integration READMEs:
  - DataDog/integrations-internal-core#3218
  - DataDog/integrations-extras#2992

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added the Architecture Everything related to the Doc backend label May 13, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Preview links (active after the build_preview check completes)

Modified Files

These integrations have nuanced warnings (commercial-only for X-Ray,
limited support for PagerDuty) that belong in the README source, not
in centralized site-support. The inline blocks have been reinstated
in integrations-internal-core with gov,gov2 targeting.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@hestonhoffman hestonhoffman marked this pull request as ready for review May 13, 2026 21:40
@hestonhoffman hestonhoffman requested review from a team as code owners May 13, 2026 21:40
Copy link
Copy Markdown
Contributor

@janine-c janine-c left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@hestonhoffman hestonhoffman merged commit 8c2845f into master May 14, 2026
21 of 24 checks passed
@hestonhoffman hestonhoffman deleted the heston/DOCS-14086-site-support branch May 14, 2026 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Architecture Everything related to the Doc backend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants