Repository navigation
Hide VRF v1 and VRF v2 from nav, search, and Markdown - #4282
Open
thodges-gh wants to merge 1 commit into
Open
thodges-gh wants to merge 1 commit into
thodges-gh wants to merge 1 commit into
Conversation
VRF v2.5 stays the current product. The main VRF nav no longer has the "VRF V2 [DEPRECATED]" block. The v2.5 migration pages stay in that nav. The v1 and v2 tutorial URLs still open. They send noindex. Search and per-page Markdown leave them out. The VRF llms-full dump no longer includes those pages. The legacy left nav stays, so an old URL can still reach the v2.5 migration guides. Three quickstarts now point at the v2.5 subscription docs.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
👋 thodges-gh, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
This branch was successfully deployed
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.
VRF v2.5 stays the current product. This PR hides the old VRF v1 and VRF v2 tutorial trees without deleting the URLs.
The main VRF nav no longer has the "VRF V2 [DEPRECATED]" block. "Migrating from V2" and "Migrating from V1" stay in the v2.5 section.
The six
/vrf/v1pages and the fourteen/vrf/v2pages still open. HTML sends<meta name="robots" content="noindex, follow">andX-Robots-Tag: noindex, follow. Search and per-page Markdown skip these files./vrf/v1/introduction.mdand/vrf/v2/subscription.mdreturn 404./vrf/v2-5pages stay indexable and still serve Markdown. The pages stay in the sitemap whileSUNSET_PAGES_STAY_IN_SITEMAPis true.vrf/v2does not matchvrf/v2-5. The check is an exact root or aroot/prefix.The legacy left nav stays on the old pages. It still has "Migrate to VRF V2.5".
src/content/vrf/llms-full.txtdrops the twenty old pages. The v2.5 pages in that file are unchanged.src/content/vrf/llms.txtalready pointed only at v2.5.Quickstart links:
chainlink-demo-appnow links to/vrf/v2-5/subscription/create-manage.vrf-enabled-lootbox-packnow links to/vrf/v2-5/overview/subscription,/vrf/v2-5/billing#estimate-minimum-subscription-balance, and/vrf/v2-5/overview/subscription#minimum-subscription-balance.vrf-mystery-boxalready says to create a v2.5 subscription. The pending link now goes to/vrf/v2-5/overview/subscription#minimum-subscription-balance.Not in this PR:
vrf-subscription-monitorstill links to VRF v2. Its sample contract is the v2VRFD20contract.VRFConsumerBaseV2code sample./vrf/v2/subscription/supported-networks#fantom-mainnet. The other chain links already point at v2.5.