Fixes various redirects

[bradleycamacho]

This pull request includes multiple changes to the public/_redirects file to update and add new redirect rules. The changes are primarily focused on improving navigation and organization within the documentation.

Fixes various broken links caused by our re-nav and not fixed in #1354

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	4179c1d
🔍 Latest deploy log	https://app.netlify.com/sites/docs-optimism/deploys/67db397dc3024f0008bd318f
😎 Deploy Preview	https://deploy-preview-1518--docs-optimism.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sbvegan]

lgtm, but I personally didn't verify the src redirects for 404s

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the public/_redirects file by introducing several new redirect rules. The changes include mapping various legacy or outdated paths to their current destinations. For example, paths related to audit reports, stack overviews, and beta features are now redirected to updated sections such as /stack/security/audits-report and /stack/getting-started. Additionally, modifications are made for transaction fees and Superchain documentation, alongside updates for chain operators and app developer resources. The file also sees the renaming of a section from “Tool and Resource Migrations” to “App Developers and tools” and the introduction of a new “General redirects” section. Each redirect rule has been explicitly declared, ensuring that users and automated processes are seamlessly guided to the appropriate new endpoints.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant WebServer
    User->>WebServer: Request original URL (e.g., /audit-reports/1)
    WebServer->>WebServer: Lookup matching rule in _redirects
    WebServer-->>User: HTTP Redirect to /stack/security/audits-report
    User->>WebServer: Request new redirected URL (/stack/security/audits-report)

Loading

Possibly related PRs

• remove profile page + fix internal links #685: Modifies the public/_redirects file with additions and alterations to redirect paths.
• relocate crosschain directory #1361: Updates the redirect structure for cross-chain documentation and tutorials, aligning with similar routing changes.
• fixing redirect to superchain explainer #1502: Involves a direct modification to the redirect for /stack/explainer, which contrasts with the updated mapping in this PR.

Suggested reviewers

• krofax
• sbvegan

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d24349f and 4179c1d.

📒 Files selected for processing (1)

• public/_redirects (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Redirect rules - docs-optimism
• GitHub Check: Header rules - docs-optimism
• GitHub Check: Pages changed - docs-optimism

🔇 Additional comments (6)

public/_redirects (6)

109-116: New "Others" section addresses critical redirects

These new redirects properly map audit reports, stack overview pages, and the custom gas token feature to their current destinations. This helps fix broken links from the previous navigation restructuring mentioned in the PR description.

---

119-119: Good addition for Superchain content consistency

This redirect from /stack/components to /superchain/superchain-explainer maintains consistency with the similar redirect on line 118, ensuring users find the right content regardless of which legacy URL they might be using.

---

137-137: Proper handling of deprecated custom gas token feature

This redirect correctly points users from the operators path to the same deprecation notice used in line 114, maintaining consistency across the documentation.

---

145-145: Section renamed to reflect current information architecture

Renaming from "Tool and Resource Migrations" to "App Developers and tools" better aligns with the current documentation structure where "builders" has been replaced with "app-developers".

---

151-154: Fixed duplicate path nesting issues

These redirects correctly resolve the erroneous duplicate nesting (/app-developers/app-developers/) that likely occurred during the previous restructuring, ensuring users are properly directed to the correct single-nested paths.

---

166-171: New "General redirects" section provides important basic redirects

The new section includes helpful redirects for design principles content and the index page. The index redirect is particularly important for ensuring users landing on /index are properly directed to the homepage.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.