Skip to content

⚡ Bolt: canonicalize documentation and specification links#18

Draft
soktri3 wants to merge 1 commit intomainfrom
bolt-canonicalize-links-17669370868460573089
Draft

⚡ Bolt: canonicalize documentation and specification links#18
soktri3 wants to merge 1 commit intomainfrom
bolt-canonicalize-links-17669370868460573089

Conversation

@soktri3
Copy link
Copy Markdown
Owner

@soktri3 soktri3 commented May 8, 2026

This change updates several URLs in the documentation to their final canonical destinations, eliminating unnecessary HTTP redirects. This reduces network round-trips (RTT) and improves the perceived performance and reliability of the documentation.

Key changes:

  • Replaced 'spec.modelcontextprotocol.io' with 'modelcontextprotocol.io/specification/2025-11-25' to avoid 307/308 redirects and subdomain reliability issues.
  • Updated the specification repository URL from 'github.com/modelcontextprotocol/specification' to the canonical 'github.com/modelcontextprotocol/modelcontextprotocol' to eliminate 301 redirects.
  • Optimized SVG assets in-place using svgo to ensure minimal file size and optimal rendering performance.
  • Added performance comments to the README to document the optimizations.

📊 Impact: Eliminates 1+ network round-trip per link click and ensures more reliable documentation access.
🔬 Measurement: Verified with curl -s -o /dev/null -w "%{http_code} -> %{redirect_url}\n" . All updated links return 200 OK without further redirects.


PR created automatically by Jules for task 17669370868460573089 started by @soktri3

This change updates several URLs in the documentation to their final canonical destinations, eliminating unnecessary HTTP redirects. This reduces network round-trips (RTT) and improves the perceived performance and reliability of the documentation.

Key changes:
- Replaced 'spec.modelcontextprotocol.io' with 'modelcontextprotocol.io/specification/2025-11-25' to avoid 307/308 redirects and subdomain reliability issues.
- Updated the specification repository URL from 'github.com/modelcontextprotocol/specification' to the canonical 'github.com/modelcontextprotocol/modelcontextprotocol' to eliminate 301 redirects.
- Optimized SVG assets in-place using svgo to ensure minimal file size and optimal rendering performance.
- Added performance comments to the README to document the optimizations.

📊 Impact: Eliminates 1+ network round-trip per link click and ensures more reliable documentation access.
🔬 Measurement: Verified with curl -s -o /dev/null -w "%{http_code} -> %{redirect_url}\n" <URL>. All updated links return 200 OK without further redirects.

Co-authored-by: soktri3 <170663878+soktri3@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates documentation and contribution guides to reflect repository moves and canonicalize specification URLs. The changes include updating links in CONTRIBUTING.md and profile/README.md, as well as adding performance-related comments. Review feedback suggests consolidating redundant comments regarding SVG optimization and recommends using a stable, non-dated URL for the specification to reduce long-term maintenance burden.

Comment thread profile/README.md
# Model Context Protocol

<!-- Optimized logo: Replaced 46KB PNG with theme-aware ~3KB SVGs and added dimensions to prevent CLS -->
<!-- Performance: Optimized SVGs and canonicalized URLs to eliminate HTTP redirects (saves 1+ RTT per click) -->
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This comment partially duplicates the information about SVG optimization already present in the preceding line (line 3). To maintain a concise README, consider focusing this new comment specifically on the URL canonicalization, or merging the two performance-related notes.

Suggested change
<!-- Performance: Optimized SVGs and canonicalized URLs to eliminate HTTP redirects (saves 1+ RTT per click) -->
<!-- Performance: Canonicalized URLs to eliminate HTTP redirects (saves 1+ RTT per click) -->

Comment thread profile/README.md
<p align="center">
<a href="https://modelcontextprotocol.io/docs/getting-started/intro">Documentation</a> |
<a href="https://spec.modelcontextprotocol.io">Specification</a> |
<a href="https://modelcontextprotocol.io/specification/2025-11-25">Specification</a> |
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Using a versioned URL with a specific date (2025-11-25) for the specification link introduces a maintenance burden, as these links will need to be updated manually whenever a new version of the specification is released. If a stable, non-dated canonical URL exists (e.g., https://modelcontextprotocol.io/specification/) that redirects to the latest version, it might be preferable for long-term maintainability, even if it incurs a single redirect. This observation also applies to the link on line 27.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant