Repository navigation
fix(website): trailing-slash URLs, MCP in the title, no report request in the replay - #140
Merged
Merged
Conversation
Netlify serves each page from its directory and answers the bare path with a 301, so the canonical URLs, the sitemap and every internal link pointed at a redirect. They now carry the trailing slash: SitePage.href for the navigation, the pager, the table of contents and the canonical URL, a sed over the sitemap Jaspr writes, and the hard-coded links in the pages, the README and docs/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The old landing page's title started with "Marionette MCP", the name the package is searched by. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The session writes report.md on its own when reports are on, so no prompt on the site asks for one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ Deploy Preview for marionette-landing ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.
BSD sed on macOS reads the argument after -i as a backup suffix, so `sed -i -E` ran the pattern as a basic regex, failed on \1 and stopped tool/build.sh under set -e. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
KrzysztofMamak
approved these changes
Oct 23, 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
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
Follow-ups to the site launch (#136), found while checking it against search engines.
/docs/conceptswith a 301 to/docs/concepts/, so canonical URLs, sitemap entries and internal links all pointed at a redirect.SitePage.hrefadds the slash for the navigation, pager, table of contents and canonical URL;tool/build.shrewrites the sitemap Jaspr writes; hard-coded links in the pages,README.mdanddocs/*.mdfollow. Route paths are unchanged.report.mdon its own.Evidence
On the production build:
id.sitemap.xml:/,/docs/,/docs/concepts/,/docs/configure/,/docs/drive/,/docs/reports/.dart analyze --fatal-infos: no issues ·dart format: 0 changed ·dart test: 8/8Merge Danger
Door: two-way. Revert, or publish the previous deploy in Netlify.
Blast Radius: marionette.leancode.co
Old links without the slash keep working through Netlify's 301. Search engines pick up the new canonical URLs and sitemap on their next crawl.
🤖 Generated with Claude Code