Skip to content

Reports page: link out to the ethereumadoption.com community report collection #18347

@konopkja

Description

@konopkja

Context

We recently launched the Reports page. After it shipped, we noticed there is already an established community initiative covering similar ground: ethereumadoption.com (maintained by hanniabu.eth / Ether Alpha), which curates collections of Ethereum reports at /reports/eth/ and /reports/ethereum/.

Rather than let the official page quietly compete with a community resource, we should coexist and point users to it. An outbound, followed link from ethereum.org is the strongest, lowest-cost way to support the community project and avoid cannibalizing it, while giving our own visitors a wider collection to explore.

Proposed change

In the bottom section of /reports/ (currently the "Suggest a report" block):

  1. Rename the heading from "Suggest a report" to "Want to see more reports?" so the section frames both browsing more and contributing.
  2. Add a second button next to the existing "Suggest a report on GitHub" button, linking to https://ethereumadoption.com/reports/eth/.
  3. Update the body copy so it covers both actions (browse the community collection, or suggest a report to add here).

CTA wording

The destination is a community-maintained collection, so the label should name it honestly and read as a parallel to the existing GitHub button.

  • Proposed: Browse more on ethereumadoption.com (parallels "Suggest a report on GitHub", names the external destination plainly)
  • Alternatives considered: "Browse more reports", "See the community collection", "More Ethereum research"

Open to the maintainers' preference on the exact wording and on whether to also reach out to hanniabu.eth as a courtesy before/after merge.

Implementation notes

  • Reuse existing primitives only: wrap the two ButtonLinks in a Flex (flex-wrap gap-4); no new components.
  • One new translatable string (page-reports-more-cta) in src/intl/en/page-reports.json.
  • Both buttons kept as variant="outline" for equal, modest weight; hierarchy is trivially adjustable.

A PR implementing this follows directly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs triage 📥This issue needs triaged before being worked on

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions