The GitHub Actions job "Deploy" on wayang-website.git/main has succeeded.
Run started by GitHub user juripetersen (triggered by juripetersen).

Head commit for run:
180ae937ef2fef08182939ed6e6b91d79a64fc27 / Zoi Kaoudi 
<[email protected]>
add "Join community" page (#133)

* docs: add Join the Community page

Adds a community landing page (docs/community/join) with the project's
communication channels, a step-by-step path to a first contribution,
ways to contribute beyond code, and how to become a committer/PMC member.
Links it from the Community navbar dropdown and the footer, and adds a
/community redirect so the link in apache/wayang's CONTRIBUTING.md works.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015EbsXcrjsNeGmb5zxooUan

* docs: make non-code contributions explicit on Join page

State up front that contributions need not be code, move the ways to
contribute ahead of the pull-request steps, and give documentation,
social media, talks and blog posts their own cards. Clarify that
committership recognises non-code contributions too.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015EbsXcrjsNeGmb5zxooUan

* docs: mention Slack invitations on Join page

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015EbsXcrjsNeGmb5zxooUan

* docs: name the #wayang channel on the ASF Slack

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015EbsXcrjsNeGmb5zxooUan

* docs: align Join page with simplified Community navigation

Drop the navbar dropdown entry (the page is first in the community
sidebar) and stop linking to the removed Community Resources page.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015EbsXcrjsNeGmb5zxooUan

---------

Co-authored-by: Claude Opus 5.5 <[email protected]>

Report URL: https://github.com/apache/wayang-website/actions/runs/41870163111

With regards,
GitHub Actions via GitBox

Reply via email to