Skip to content

Conversation

@rocstersolos
Copy link

@rocstersolos rocstersolos commented Jun 23, 2025

🧠 Developer Docs Contribution

File edited:
docs/build-on-morph/0-developer-navigation-page.md

What I added:
A new section listing the programming languages and tools required to build on Morph, including Solidity, JavaScript/TypeScript, Hardhat, and Foundry. This is meant to help new developers onboard faster.

Thanks 🙏

@rocstersolos rocstersolos requested a review from a team as a code owner June 23, 2025 12:31
@rocstersolos rocstersolos requested a review from twcctop June 23, 2025 12:32
@coderabbitai
Copy link

coderabbitai bot commented Jun 23, 2025

Walkthrough

A new section has been appended to an HTML documentation page, outlining the programming languages and tools relevant for building on Morph. This section highlights key languages, frameworks, and toolchains, emphasizes EVM compatibility, and provides a link to a Morph Starter Kit for quick onboarding.

Changes

File(s) Change Summary
build/docs/how-morph-works/intro/index.html Added a section detailing required languages, tools, EVM compatibility, and a starter kit link.

Poem

In Morph’s bright digital glade,
New languages and tools are displayed.
Solidity and TypeScript hop into view,
With React and Hardhat joining too.
EVM friends are welcome here—
The Starter Kit brings learning near!
🐇✨


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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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

@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

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 585c260 and 92a82db.

📒 Files selected for processing (1)
  • build/docs/how-morph-works/intro/index.html (1 hunks)
🧰 Additional context used
🪛 HTMLHint (1.5.0)
build/docs/how-morph-works/intro/index.html

[error] 29-29: Special characters must be escaped : [ > ].

(spec-char-escape)

Comment on lines +18 to +29
## 🧠 What Programming Languages Do You Need?

To build on Morph, you'll mainly use:

- **Solidity** – for writing smart contracts compatible with Ethereum and Morph.
- **TypeScript / JavaScript** – for frontend integrations, SDK usage, and dApp interfaces.
- **React** (optional but recommended) – for building modern UI with Morph’s components.
- **Hardhat or Foundry** – for compiling, testing, and deploying smart contracts.

Morph is EVM-compatible, meaning any tooling and language used in the Ethereum ecosystem will generally work with minimal changes.

> 🚀 You can get started even faster with our [Morph Starter Kit](#).
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

❓ Verification inconclusive

Move content into the source markdown and use proper HTML tags
The PR edits the generated HTML with raw Markdown syntax (##, -, >), which won’t render correctly and will be overwritten on rebuild. Please migrate these additions into the documentation source (e.g., docs/how-morph-works/intro.md) and wrap them with valid HTML/MD:

@@ docs/how-morph-works/intro.md
+ ## 🧠 What Programming Languages Do You Need?
+ To build on Morph, you'll mainly use:
+ - **Solidity** – for writing smart contracts compatible with Ethereum and Morph.
+ - **TypeScript / JavaScript** – for frontend integrations, SDK usage, and dApp interfaces.
+ - **React** (optional but recommended) – for building modern UI with Morph’s components.
+ - **Hardhat or Foundry** – for compiling, testing, and deploying smart contracts.
+ 
+ Morph is EVM-compatible, meaning any tooling and language used in the Ethereum ecosystem will generally work with minimal changes.
+ 
+ > 🚀 You can get started even faster with our [Morph Starter Kit](#).

Once merged, rebuild the site to update the HTML.


Move content into the source markdown and use proper HTML tags
The PR edits the generated HTML with raw Markdown syntax (##, -, >), which won’t render correctly and will be overwritten on rebuild. Please migrate these additions into the documentation source (e.g., docs/how-morph-works/intro.md) and wrap them with valid HTML/MD:

@@ docs/how-morph-works/intro.md
+ ## 🧠 What Programming Languages Do You Need?
+ To build on Morph, you'll mainly use:
+ - **Solidity** – for writing smart contracts compatible with Ethereum and Morph.
+ - **TypeScript / JavaScript** – for frontend integrations, SDK usage, and dApp interfaces.
+ - **React** (optional but recommended) – for building modern UI with Morph’s components.
+ - **Hardhat or Foundry** – for compiling, testing, and deploying smart contracts.
+ 
+ Morph is EVM-compatible, meaning any tooling and language used in the Ethereum ecosystem will generally work with minimal changes.
+ 
+ > 🚀 You can get started even faster with our [Morph Starter Kit](#).

Once merged, rebuild the site to update the HTML.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## 🧠 What Programming Languages Do You Need?
To build on Morph, you'll mainly use:
- **Solidity** – for writing smart contracts compatible with Ethereum and Morph.
- **TypeScript / JavaScript** – for frontend integrations, SDK usage, and dApp interfaces.
- **React** (optional but recommended) – for building modern UI with Morph’s components.
- **Hardhat or Foundry** – for compiling, testing, and deploying smart contracts.
Morph is EVM-compatible, meaning any tooling and language used in the Ethereum ecosystem will generally work with minimal changes.
> 🚀 You can get started even faster with our [Morph Starter Kit](#).
## 🧠 What Programming Languages Do You Need?
To build on Morph, you'll mainly use:
- **Solidity** – for writing smart contracts compatible with Ethereum and Morph.
- **TypeScript / JavaScript** – for frontend integrations, SDK usage, and dApp interfaces.
- **React** (optional but recommended) – for building modern UI with Morph’s components.
- **Hardhat or Foundry** – for compiling, testing, and deploying smart contracts.
Morph is EVM-compatible, meaning any tooling and language used in the Ethereum ecosystem will generally work with minimal changes.
> 🚀 You can get started even faster with our [Morph Starter Kit](#).
🧰 Tools
🪛 HTMLHint (1.5.0)

[error] 29-29: Special characters must be escaped : [ > ].

(spec-char-escape)

🤖 Prompt for AI Agents
In build/docs/how-morph-works/intro/index.html lines 18 to 29, the content is
added using raw Markdown syntax inside an HTML file, which will not render
correctly and will be overwritten on rebuild. Move this content into the source
markdown file, likely docs/how-morph-works/intro.md, using proper Markdown or
HTML tags as appropriate. After updating the source markdown, rebuild the
documentation site to regenerate the HTML with the correct formatting.

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