-
Notifications
You must be signed in to change notification settings - Fork 10k
[Docs Site] New schema value for Support AI #22794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
|
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryEnhanced the documentation for the Cloudflare Firewall Rules by introducing a new schema value to improve the handling of deprecated features in chatbot responses.
Modified Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add |
|
Preview URL: https://13114dd6.preview.developers.cloudflare.com |
|
/windsurf-review |
* [Docs Site] New schema value for Support AI * Test value * Update framing of frontmatter + logic to render in index.md * Add whole product option like noindex * Add tags to .md as well
Summary
In addition to
noindexbehavior used in places like #22758, we need a bit more nuance / flexibility for de-emphasizing certain pages.This should still be applied cautiously, b/c the deprioritization needs to be assumed in whatever context someone might be asking questions to the chatbot.
A good, current example of this would be
/firewall/, where the feature is deprecated but we don't want it fully hidden from Google / our search. A bad example would be something like/pages/, where we're trying to recommend folks use Workers Assets but Pages is still a valid way of accomplishing your actions.Part of the rollout (and testing) related to #22754.
PCX-17631