docs(seo): hub umbrella content + front-matter parity#654
Open
rain-Brian wants to merge 2 commits into
Open
Conversation
Additive content for the cluster hub (homepage repositioning intentionally NOT touched; see PR notes for the Biodiversity-vs-Pytorch-Wildlife positioning flag): - New docs/ecosystem.md: the ecosystem directory + a "which project should I use?" decision guide, with topic-specific anchors linking out to each project's documentation site (cluster cohesion). - New docs/ecosystem-standards.md: the shared documentation standards every ecosystem repo follows (structure, metadata, structured data, cross-linking, topic ownership) so new repos replicate the pattern. - Add both to nav; surface the ecosystem + collaborators from the homepage. - Add title front-matter to 10 hand-written pages; remove stale "SPARROW Studio" naming and em-dashes from touched pages. Part of the cluster SEO-parity work (ADO Epic 506340).
…RL is stable Per SEO review: the hub should not link to Acoustic's canonical URL while it 301-redirects (repo private, Pages on a randomized URL). Name it as 'documentation coming soon' without the live link in the ecosystem directory and the topic-ownership table; re-add the link once the repo is public and the URL returns 200.
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.
What
Additive content layer for the Biodiversity hub (stacked on the infra/schema PR #653; base will retarget to main when #653 merges).
New pages
docs/ecosystem.md— the ecosystem directory + a "which project should I use?" decision guide, with topic-specific anchors linking out to each project's documentation site (MegaDetector, MegaDetector-Acoustic, SPARROW, PyTorch-Wildlife). Targets the hub's umbrella keywords (Microsoft biodiversity AI, open source conservation AI). Cluster-cohesion win.docs/ecosystem-standards.md— the shared documentation standards every ecosystem repo follows (site structure, metadata, structured data, cross-linking, topic ownership), so new repos replicate the gold-standard pattern.Other
title:front-matter added to 10 hand-written pages (front-matter parity).Verification
mkdocs buildsucceeds; both new pages render with correct titles, interior BreadcrumbList, and resolving lane links.The hub repo (microsoft/Biodiversity) hosts the PytorchWildlife package + setup.py and its homepage is titled "Welcome to PyTorch-Wildlife", while a separate microsoft/Pytorch-Wildlife repo also embodies the framework. This creates a hub-vs-sub-repo identity overlap and "PyTorch Wildlife" keyword cannibalization. Reframing the hub homepage as a pure umbrella is deferred pending a team decision on which repo owns the framework identity. This PR is additive only and does not touch that positioning.
Part of the cluster SEO-parity work (ADO Epic 506340).