Add 'Ethereum Ecosystem' CTA to ethereum.org

[Maxservais]

This PR introduces a Call to Action on https://ethereum.org/en/dapps/, guiding visitors to Ethereum Ecosystem, an unofficial ecosystem page for Ethereum and its L2s.

Description

This addition aims to provide enhanced visibility for a resource that catalogues over 1000 dApps across Ethereum and its Layer 2s, facilitating greater user exploration and engagement within the ecosystem.

Related Issue

https://github.com/ethereum/ethereum-org-website/issues/12372

Summary by CodeRabbit

• New Features
  • Introduced a new section in the Dapps page to explore the ecosystem, featuring a callout banner with a direct link for user engagement.

[netlify[bot]]

✅ Deploy Preview for ethereumorg ready!

Name	Link
🔨 Latest commit	cadad027cfa40fac195fe7400775da81cc0d8015
🔍 Latest deploy log	https://app.netlify.com/sites/ethereumorg/deploys/66421f50e979ca0008aeea2f
😎 Deploy Preview	https://deploy-preview-12373--ethereumorg.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	7 paths audited Performance: 45 (🔴 down 11 from production) Accessibility: 92 (no change from production) Best Practices: 89 (🔴 down 9 from production) SEO: 95 (no change from production) PWA: - View the detailed breakdown and full score reports

---

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

[konopkja]

This is too aggressive ad, it is above the list of curated dapps on the page itself. It is a worthy addition for users who seek an expanded list of dapps or to see the whole ecosystem, but will not be useful to a beginner who needs less options and more curation/guidance, which https://www.ethereum-ecosystem.com/ currently does not offer.

I suggest to rethink the position and how to link to this project on this page.

[Maxservais]

Hi @konopkja ,

Thanks for the constructive feedback on the CTA.

I see your point about its prominence possibly being overwhelming for newcomers. Inspired by the L2Beat CTA on ethereum.org's Layer 2 overview, I was aiming for similar visibility for Ethereum Ecosystem.

Would you be open to placing the CTA lower on the page, where it might be more contextually appropriate for users looking for expanded information? I'm keen to adjust the approach to better fit the community's needs.

Looking forward to your guidance.

[coderabbitai[bot]]

Walkthrough

The update involves adding a new feature to the DappsPage component within the dapps.tsx file. This feature introduces an import for a new image named exploring and adds a section aimed at exploring the ecosystem. The section is highlighted by a callout banner, which includes a button that links users to a specified URL, enhancing the page's interactivity and informational capacity.

Changes

File	Change Summary
src/.../dapps.tsx	Added exploring image import and new section with callout banner and link button.

---

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:

Note: Auto-reply has been disabled for this repository by the repository owner. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[Maxservais]

@konopkja what do you think about this?

[konopkja]

@konopkja what do you think about this?

its better, though this is a very big recognition - using a full width banner like this, there are only few instances when we have done that before and those were open source communities not a closed project so I am still hesitant on this approach. For now lets keep this open and see what others say.

[wackerow]

I do like the idea of linking out to this, but am hesitant on using such a large callout for an initial listing. To me this feels like a good follow-up to the listings shown above, like "Want to browse more?"

^ Referring to this space here, as a regular text callout.

Also, ideally we make it clear to users that they're going to an external resource. "Ethereum.org" "Ethereum" "Ethereum Foundation" "Ethereum Ecosystem"... User's often don't discern the differences well.

[konopkja]

agree with @wackerow and i would suggest changing it to a text based link perhaps

[Maxservais]

Hello @wackerow @konopkja,

Thank you both for your valuable input. Based on your suggestions, I’ve developed a more subdued approach: a button that prompts users who are interested in delving deeper after browsing the listings. This replaces the more assertive banner with a subtler call to action.

Additionally, a 'tooltip' will appear when users hover over the button, alerting them that they are about to visit a third-party site not managed by Ethereum.org.

Here's a preview of the implementation:

I’m eager to hear your thoughts on this update.