Docs:Add hyperlinks to community resources and Eventyay

[Diksha-MukherjeeAgarwal]

Issue no: #910
Documentation:

• Link FOSSASIA references on GitHub, mailing list, newsletter, social media, chat, and repositories directly from the participation guidance text.

Summary by Sourcery

Update participation guidance documentation with direct links to FOSSASIA community channels and Eventyay.

Documentation:

• Add hyperlinks to FOSSASIA GitHub, mailing list, newsletter, social media, chat, and repositories in the participation section.
• Refresh wording around social media posts and Eventyay meetups in the participation and FAQ sections.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds concrete hyperlinks to FOSSASIA community resources (GitHub, mailing list, newsletter, social media, chat, repositories, Eventyay) and slightly modernizes related participation copy in labs/index.html.

File-Level Changes

Change	Details	Files
Link community participation bullet list items directly to relevant FOSSASIA resources.	Wraps GitHub reference in an anchor tag to the FOSSASIA GitHub organization page. Adds mailto/newsletter-style links for the FOSSASIA mailing list and newsletter from the guidance text. Links social media mention to the FOSSASIA contact/social page. Links chat channel reference to the FOSSASIA Gitter room. Links repository reference to the FOSSASIA GitHub organization repositories view. Updates the tweet/blog bullet to instead mention posting on X or writing a blog article. Links Eventyay mention to the Eventyay homepage in the meetup bullet.	labs/index.html
Tweak Eventyay FAQ copy to be clearer and better aligned with current social media terminology.	Fixes duplicated word in sentence describing organizing a FOSSASIA developers event. Updates guidance to share events on social media and tag @fossasia, instead of the older tweet-only wording, keeping existing Eventyay link intact.	labs/index.html

Possibly linked issues

• [Docs] Hyperlink external resources and update "Twitter" terminology #910: The PR implements the issue’s requested links and text updates in the “Before you apply” section.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• The mailing list anchor uses href="fossasia@googlegroups.com"; this should likely be a mailto: link (e.g. href="mailto:fossasia@googlegroups.com") so it behaves correctly in browsers.
• In the social media list item, the wording changed from "Follow FOSSASIA on social media channels" to "Follow on ... social media channels", which drops the organization name; consider keeping "Follow FOSSASIA on" to maintain clarity and consistency with the other bullets.
• You updated one reference from "Tweet" to "Post on X" but left other mentions of "Twitter" (e.g., @fossasia in Twitter); consider making the terminology for Twitter/X consistent throughout the updated text.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The mailing list anchor uses `href="fossasia@googlegroups.com"`; this should likely be a `mailto:` link (e.g. `href="mailto:fossasia@googlegroups.com"`) so it behaves correctly in browsers.
- In the social media list item, the wording changed from "Follow FOSSASIA on social media channels" to "Follow on ... social media channels", which drops the organization name; consider keeping "Follow FOSSASIA on" to maintain clarity and consistency with the other bullets.
- You updated one reference from "Tweet" to "Post on X" but left other mentions of "Twitter" (e.g., `@fossasia in Twitter`); consider making the terminology for Twitter/X consistent throughout the updated text.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}