moving keywords to v2 from v1#1193
Merged
Merged
Conversation
Signed-off-by: Liam Randall <liam@cosmonic.com>
✅ Deploy Preview for dreamy-golick-5f201e ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
🔎 Structured data validation
✅ All checks pass and no authoring warnings to backfill. ⚙️ Generated by |
LiamRandall
commented
Jun 10, 2026
LiamRandall
left a comment
LiamRandall
left a comment
Member
Author
There was a problem hiding this comment.
few SEO pages need to be updated to point at the v2 docs
ericgregory
approved these changes
Jun 10, 2026
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
2 participants
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.
Changes:
Build verification (all passed):
On the noindex cutoff you asked about: the swizzle at src/theme/wasmcloud/community/post-page/index.tsx:31 already uses year >= 2025 (2025 + 2026 indexed; 2024 and earlier get noindex, follow), and the sitemap at docusaurus.config.ts:188
matches (2026 → 0.9, 2025 → 0.8, pre-2025 dropped). Build output confirms: sampled 2025 and 2026 transcript/meeting pages have 0 noindex tags. The TL;DR in your prompt was outdated when it said "pre-2026" — the code already does what you
described, so I didn't change it. Tell me if you want a different cutoff.
Heads-up: the rebase state for keywork-check is still present in .git/rebase-merge/ — your in-progress rebase is intact, just switch back to keywork-check to continue it.