deleting sdk page

[sbvegan]

fixes: #1090
fixes: #1083

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	40cf36e
🔍 Latest deploy log	https://app.netlify.com/sites/docs-optimism/deploys/672d6282bbbc480008c887f3
😎 Deploy Preview	https://deploy-preview-1091--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.

[coderabbitai]

Walkthrough

This pull request involves the removal of references to the Optimism SDK from the documentation. Specifically, the tutorial file on using the SDK has been deleted, and the corresponding entry in the metadata file has been removed. Additionally, a series of redirect paths have been updated to reflect a reorganization of the documentation structure, moving resources to new locations that align with the current categorization scheme.

Changes

File Path	Change Summary
pages/builders/chain-operators/tutorials/_meta.json	Removed key "sdk": "Using the Optimism SDK"
pages/builders/chain-operators/tutorials/sdk.mdx	Deleted the file containing the tutorial on using the Optimism SDK
public/_redirects	Updated multiple redirect paths to reflect new organizational structure and resource locations

Assessment against linked issues

Objective	Addressed	Explanation
Page deleted (related to SDK)	✅
Meta.json updated (removal of SDK reference)	✅
Add a redirect for the removed SDK tutorial	✅
Update/remove using the Optimism SDK page	✅

Possibly related PRs

• Added banner and notice page for SDK deprecation  #928: Discusses the deprecation of the Optimism SDK and transition to the viem library, related to the removal of SDK references.
• Update sdk-deprecation.mdx #1025: Updates the SDK deprecation notice, reinforcing the transition away from the Optimism SDK.
• update audit issue template #1068: Enhances the audit issue template, indirectly related to documentation changes.
• remove wallet & cex section #1081: Removes the "Wallets & CEX" section, relating to the overall restructuring of documentation.
• dropping OPM down #1085: Involves reorganizing documentation structure, aligning with changes affecting SDK references.

Suggested reviewers

• bradleycamacho
• krofax

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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 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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f29e271 and 40cf36e.

📒 Files selected for processing (3)

• pages/builders/chain-operators/tutorials/_meta.json (0 hunks)
• pages/builders/chain-operators/tutorials/sdk.mdx (0 hunks)
• public/_redirects (1 hunks)

💤 Files with no reviewable changes (2)

• pages/builders/chain-operators/tutorials/_meta.json
• pages/builders/chain-operators/tutorials/sdk.mdx

🔇 Additional comments (1)

public/_redirects (1)

118-118: LGTM! Consistent redirect structure.

The redirect maintains consistency with other superchain-related documentation paths.