Repository navigation
Connect RageLayer documentation and authorship to portfolio - #34
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2c28579866
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| pageData.frontmatter.head ??= []; | ||
| pageData.frontmatter.head.push([ | ||
| "link", | ||
| { rel: "canonical", href: `https://www.parthjadhav.com/products/ragelayer/docs/${slug}` }, |
There was a problem hiding this comment.
Exclude migrated pages from the legacy sitemap
When the GitHub Pages build runs, the existing sitemap configuration still emits https://parthjadhav.github.io/RageLayer/<slug> for every migrated page while this new tag declares the portfolio URL canonical. These conflicting indexing signals can keep the legacy copies indexed or cause crawlers to disregard the intended canonical migration. Filter the migrated slugs out of the GitHub Pages sitemap, while retaining entries for the unmigrated pages.
Useful? React with 👍 / 👎.
RageLayer currently sends readers and package consumers to its older GitHub Pages documentation. Point the README documentation links and package homepage to the maintained portfolio site, and link the existing author credit to Parth Jadhav.
Add canonical URLs for the 13 documentation pages mirrored on the portfolio. Keep the distinct live demo and unmigrated documentation available on GitHub Pages. Package metadata will be picked up by the next normal release.
Validation: frozen dependency install, Biome checks on changed configuration, complete documentation/package build, and HTTP 200 checks for all 13 canonical destinations.