Add beta shortcode and standardize beta status notes#3350
Draft
matthewhelmke wants to merge 1 commit into
Draft
Conversation
Introduce layouts/shortcodes/beta.html as the standard for beta-status callouts. Parameters: feature, enroll, access, feedback. Replace seven distinct phrasings across eight pages with the shortcode. For Private APK Repositories (GA but evolving), combine beta status with access scope in one sentence per legal guidance to retain the word "beta." Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
layouts/shortcodes/beta.htmlas the standard callout for beta-status features. Parameters:feature,enroll,access,feedback.An audit of the
content/directory found 21 mentions of "beta" across 9 pages using 7 different phrasings. None used a shortcode. This PR collapses that variation to one source of truth.Usage
Pages migrated
content/chainguard/administration/policy-gates/index.mdcontent/chainguard/api/api-v2-tutorial.mdcontent/chainguard/chainguard-images/about/catalog-starter.mdcontent/chainguard/chainguard-images/features/packages/private-apk-repos/index.mdcontent/chainguard/chainguard-images/features/request-resources/index.mdcontent/chainguard/chainguard-images/how-to-use/use-chainguard-notifications/index.mdcontent/chainguard/chainguard-os/chainguard-os-packages.mdcontent/chainguard/migration/the-guardener.mdItems deliberately left alone
api-v2-tutorial.md— these describe operational implications, not status.the-guardener.md("While The Guardener is in beta…" waitlist, "joined the beta program" FAQ).software-security/learning-labs/ll202511.md.Test plan
noteshortcode pattern🤖 Generated with Claude Code