docs: Update headings and texts for community engagement sections

[freya-docs]

Description

This PR updates headings and texts for community engagement sections to make them them more action related and welcoming.

Related Issues

Closes: #352

Summary by CodeRabbit

• Documentation
  • Updated homepage copy for three sections to improve clarity and engagement:
    • Community section heading/text changed to “Join the conversation and help move ideas forward”.
    • Repositories section heading/text changed to “Explore the codebase - your contributions shape what we build”.
    • Contribution/Issues section heading/text changed to “Explore where your voice and work have real influence”.
  • Messaging revisions only; existing lists and links remain unchanged.

[netlify]

✅ Deploy Preview for hiero-open-source ready!

Name	Link
🔨 Latest commit	bfad303
🔍 Latest deploy log	https://app.netlify.com/projects/hiero-open-source/deploys/69db4b2ae723eb0008699c7e
😎 Deploy Preview	https://deploy-preview-372--hiero-open-source.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[lfdt-bot]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

Warning

Rate limit exceeded

@freya-docs has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 13 minutes and 49 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 13 minutes and 49 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1a6dbad0-7989-4094-bef8-247b8d821540

📥 Commits

Reviewing files that changed from the base of the PR and between 2c11d2c and bfad303.

📒 Files selected for processing (1)

• src/app/page.tsx

📝 Walkthrough

Walkthrough

Updated copy for three homepage sections in src/app/page.tsx: replaced meetData, reposData, and issueJumpData heading and text strings; underlying lists, links, and queries remain unchanged. (47 words)

Changes

Cohort / File(s)	Summary
Homepage Section Copy src/app/page.tsx	Rewrote heading and text for meetData, reposData, and issueJumpData (new headings: "Join the conversation and help move ideas forward", "Explore the codebase - your contributions shape what we build", "Explore where your voice and work have real influence"). No edits to lists, links, queries, or exports.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: shorten Join Calls subtext for consistency #361 — Modifies the same meetData.text in src/app/page.tsx, overlapping copy-change area.

Suggested reviewers

• exploreriii
• aceppaluni
• danielmarv

Poem

🐇 I hopped up to the homepage, nibbling lines of text,
I swapped a few words — gentle, not complex,
"Join the chat," "Explore the code," I set the signright,
A tiny hop, a brighter path — come linger and align.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is minimal and lacks detail. While it mentions the purpose and related issue, it omits changes made, testing, and deployment notes from the template.	Expand the description to include details under 'Changes Made', 'Screenshots', and 'Checklist' sections to fully align with the template.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: updating headings and texts for community engagement sections to be more action-oriented and welcoming.
Linked Issues check	✅ Passed	All code changes align with issue #352 objectives: headings and texts for three sections were updated to be more action-oriented and welcoming, replacing practical/literal titles with engaging alternatives.
Out of Scope Changes check	✅ Passed	All changes are within scope—only heading and text content updates to three community engagement sections were modified; no extraneous changes were introduced.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}

[exploreriii]

I really like your approach, but I have a doubt if it is the correct approach in this context for Hiero.

The terms you are using:
explore to contribute, join the discussion, dive into codebase

While very welcoming, to me signify 'light' or surface level, perpetuating a light separation between existing contributors that are central and new contributors that are poking around. While core contributors will realistically be creating the majority of the code, ideally we can frame things like the community could play a major role, and has the ability to

The current phrasing does subtly position newcomers as observers or agents in things that cause them enjoyment, rather than active or meaningful participants that we need.

There are two competing goals here:

1.Reduce intimidation (make it easy to start)
2.Signal legitimacy and ownership (contributors matter)

Right now, your language leans heavily toward (1), at the expense of (2)
i.e. it frames new contribution as optional, peripheral, or exploratory, rather than, you can shape the system and be core to parts.

e.g.
Have a look at the issues... get 'started'
Join the discussion ... stay in the background, maybe say some things here and there, but not participate much
Dive into codebase ... have a look, tinker around.

I think shifting to something where participation is still invited but with more consequence would be ideal, yet we cannot be unrealistic (some repos are more open, contributors will take long periods of time etc to qualify for core responsibilities)

So a shift towards harder active verbs with clearer, more practical pathways would be more brand consitent, in my view.

e.g.
Contribute to Hiero?
Participate in the conversations?
Study the codebase?

So in summary i wonder your thoughts on e.g. less of a jump in / dive around and more of a meaningfully contribute, we want to build more relationships with the community?

e.g.
Contribute to Hiero

Contributors at all levels can influence the direction of Hiero—through code, documentation, and design.

Work on issues, propose improvements, and contribute to systems that are actively used across the ecosystem.?
?

Sorry I am not very creative to offer many ideas in this sense.

[freya-docs]

@exploreriii I get you point. I've tried to rephrase to add "legitimacy and ownership" but it became too long...
Another try - I rephrased it again. I think it's a matter of interpretation as well... To me, "dive in" sounds more engaging (like "deep dive") than for example "study our code" (sounds like "be a student only")...