Added developer tools & language guide

[rocstersolos]

🧠 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 🙏

Summary by CodeRabbit

• Documentation
  • Added section detailing programming languages and tools for building on Morph, including Solidity, TypeScript/JavaScript, React, Hardhat, and Foundry
  • Clarified EVM compatibility with Ethereum ecosystem tools

[coderabbitai]

Walkthrough

Appends a new section to an HTML docs page describing programming languages, frameworks, and toolchains for building on Morph (Solidity, TypeScript/JavaScript, React, Hardhat/Foundry) and notes EVM compatibility; also adds a tiny test file containing the single line "testing".

Changes

Cohort / File(s)	Change Summary
Documentation build/docs/how-morph-works/intro/index.html	Added a new "What Programming Languages Do You Need?" section listing Solidity, TypeScript/JavaScript, React (optional), Hardhat/Foundry, EVM compatibility, and a starter kit link placeholder.
Misc / Test file Rocster testing	Added a new file containing the single line: "testing".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Focus review on the new HTML content for copy/links and the added tiny test file.

Poem

I’m a rabbit in the code-lined glen,
Hopping through docs again and again.
Solidity seeds and TypeScript blooms,
Hardhat tunes and React costumes.
EVM friends, come take your kit—let’s begin! 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: adding a new section about programming languages and developer tools needed to build on Morph.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

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

📒 Files selected for processing (1)

• Rocster testing (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• Rocster testing

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

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)

[coderabbitai]

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