Skip to content

Conversation

qbzzt
Copy link
Contributor

@qbzzt qbzzt commented Jan 16, 2025

  • Moved the tutorials in the assets directory (the only tutorials we have right now) to their own directory as requested by @zainbacchus .
  • Moved the explainers in the assets directory into the top interop level.
  • Best practices for Superchain ERC-20 was looking sad and lonely, so I moved it also to the top interop level and killed the assets directory.
  • All changes propagated to public/_redirects.

qbzzt added 2 commits January 16, 2025 13:08
Also, removed the assets directory, it is no longer needed
@qbzzt qbzzt requested a review from a team as a code owner January 16, 2025 19:16
Copy link

netlify bot commented Jan 16, 2025

Deploy Preview for docs-optimism ready!

Name Link
🔨 Latest commit 6209934
🔍 Latest deploy log https://app.netlify.com/sites/docs-optimism/deploys/678aa6d6eebe760008d6d6e4
😎 Deploy Preview https://deploy-preview-1253--docs-optimism.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

Copy link
Contributor

coderabbitai bot commented Jan 16, 2025

📝 Walkthrough

Walkthrough

This pull request involves updates to the documentation metadata and redirect paths within the Optimism/Superchain ecosystem. Key changes include the removal of the "assets" key from the _meta.json file and the addition of new key-value pairs for superchain-weth, superchain-erc20, and tutorials. The _meta.json file related to Superchain ERC20 assets has been deleted, while new tutorial entries have been introduced in the tutorials metadata file. Additionally, a comprehensive set of redirect path modifications has been made to reorganize how resources are categorized and accessed. These updates aim to improve documentation clarity and resource accessibility for developers and users.

Possibly related PRs

  • superchainERC20 #986: The changes in this PR involve adding a new key-value pair for "superchain-erc20" in the _meta.json file, which relates directly to the key added in the main PR.
  • Edit SuperchainERC20 consistency #972: This PR focuses on enhancing consistency in the documentation related to SuperchainERC20, which is directly relevant to the changes made in the main PR regarding the addition of superchain-erc20.
  • Add linked to SuperchainERC20 #1010: This PR adds a link to the SuperchainERC20 documentation in the explainer, which aligns with the changes made in the main PR that introduced new key-value pairs related to superchain-erc20.

Suggested reviewers

  • zainbacchus
  • sbvegan

📜 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 f0cea1a and 6209934.

📒 Files selected for processing (1)
  • pages/stack/interop/superchain-erc20.mdx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • pages/stack/interop/superchain-erc20.mdx

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
🪧 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. (Beta)
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
pages/stack/interop/_meta.json (1)

6-8: Verify naming consistency in Superchain-related entries.

Note the inconsistent casing in superchainerc20-best-practices compared to other Superchain entries. Consider standardizing to match the format used in superchain-erc20 and superchain-weth.

-    "superchainerc20-best-practices": "SuperchainERC20 best practices",
+    "superchain-erc20-best-practices": "SuperchainERC20 best practices",
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between cacf142 and 2ad3f7f.

📒 Files selected for processing (4)
  • pages/stack/interop/_meta.json (1 hunks)
  • pages/stack/interop/assets/_meta.json (0 hunks)
  • pages/stack/interop/tutorials/_meta.json (1 hunks)
  • public/_redirects (1 hunks)
💤 Files with no reviewable changes (1)
  • pages/stack/interop/assets/_meta.json
✅ Files skipped from review due to trivial changes (1)
  • pages/stack/interop/tutorials/_meta.json
🔇 Additional comments (2)
public/_redirects (1)

118-120: Ensure tutorial redirects align with the new directory structure.

The tutorial-related redirects have been consolidated under the /stack/interop/tutorials/ path. This aligns well with the new metadata structure in _meta.json.

pages/stack/interop/_meta.json (1)

10-11: LGTM! Good organization of documentation sections.

The addition of separate sections for tools and tutorials provides a clear structure for different types of content.

@sbvegan
Copy link
Collaborator

sbvegan commented Jan 17, 2025

The assets page still exists, can we delete that? https://deploy-preview-1253--docs-optimism.netlify.app/stack/interop/assets

@qbzzt
Copy link
Contributor Author

qbzzt commented Jan 17, 2025

Done. I should make pages for every directory, but I'll do that when the rest is done.

@zainbacchus
Copy link
Contributor

zainbacchus commented Jan 17, 2025

@qbzzt @bradleycamacho @sbvegan lets just nuke Best practices for managing SuperchainERC20 tokens not sure what its adding.

Re the piece on deterministic addresses we can add back into the SuperchainERC20 explainer or tutorial when we get there

The one relevant best practice moved to the erc20 explainer
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
pages/stack/interop/superchain-erc20.mdx (1)

74-74: Apply sentence case to section header

According to the documentation guidelines, H2 headers should use sentence case. Please update the header to:

-## Consistent addresses across chains
+## Consistent addresses across chains
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1b7cb11 and f0cea1a.

📒 Files selected for processing (3)
  • pages/stack/interop/_meta.json (1 hunks)
  • pages/stack/interop/superchain-erc20.mdx (1 hunks)
  • public/_redirects (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • pages/stack/interop/_meta.json
🧰 Additional context used
📓 Path-based instructions (1)
pages/stack/interop/superchain-erc20.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
  • For H1, H2, and H3 headers:
    1. Use sentence case, capitalizing only the first word.
    2. Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
    3. Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
  • Flag any headers that seem to inconsistently apply these rules for manual review.
  • When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
    "
🪛 LanguageTool
pages/stack/interop/superchain-erc20.mdx

[uncategorized] ~76-~76: The preposition “at” seems more likely in this position.
Context: ...rrespond to the tokens that were burned on source. Consider using `Create2Deploye...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)

⏰ 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 (3)
public/_redirects (3)

115-116: LGTM: Asset paths correctly moved to top level

The redirects properly handle the migration of Superchain assets from the /assets/ subdirectory to the top level of the interop section, aligning with the PR objectives.


117-119: LGTM: Tutorial paths correctly organized

The redirects appropriately move the tutorials to a dedicated /tutorials/ directory, maintaining a clean separation of content types.


120-120: Verify the target path exists

Please ensure that the target path /stack/interop/superchain-erc20 exists to prevent 404 errors.

#!/bin/bash
# Description: Verify the existence of the target path
fd -t f "superchain-erc20\.(md|mdx)$" pages/stack/interop/

@qbzzt
Copy link
Contributor Author

qbzzt commented Jan 17, 2025

@qbzzt @bradleycamacho @sbvegan lets just nuke Best practices for managing SuperchainERC20 tokens not sure what its adding.

Re the piece on deterministic addresses we can add back into the SuperchainERC20 explainer or tutorial when we get there

Consider it done. I still need to go over the ERC20 doc, but that's for a different PR.

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.

4 participants