updated libre chat to selenium slack

[rpallavisharma]

User description

Thanks for contributing to the Selenium site and documentation!
A PR well described will help maintainers to review and merge it quickly

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, and help reviewers by making them as simple and short as possible.

updated information in about section to selenium slack channel from libre chat

Description

updated information in about section to selenium slack channel from libre chat

Motivation and Context

latest information

Types of changes

• Change to the site (I have double-checked the Netlify deployment, and my changes look good)
• Code example added (and I also added the example to all translated languages)
• Improved translation
• Added new translation (and I also added a notice to each document missing translation)

Checklist

• I have read the contributing document.
• I have used hugo to render the site/docs locally and I am sure it works.

---

PR Type

Documentation

---

Description

• Updated community communication channel reference

• Changed from Libera Chat to Selenium Slack Group

• Updated channel name from #selenium to #selenium-docs

• Modified documentation link to Slack inviter

---

Diagram Walkthrough

flowchart LR
  A["Libera Chat #selenium"] -- "migrate to" --> B["Selenium Slack #selenium-docs"]
  B -- "inviter link" --> C["inviter.co/seleniumhq"]

Loading

File Walkthrough

	Relevant files
Documentation	_index.en.md Update community chat platform and channel reference          website_and_docs/content/documentation/about/_index.en.md Replaced Libera Chat reference with Selenium Slack Group Updated channel name from #selenium to #selenium-docs Changed documentation link from libera.chat to Slack inviter URL Maintains same context about community support availability +2/-2

---

[netlify]

👷 Deploy request for selenium-dev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	1c47f8d

[qodo-merge-pro]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Not Applicable: The PR only updates documentation text and does not add or modify runtime code that could implement or affect audit logging. Referred Code Many members of the community are present at the #selenium-docs channel of [Selenium Slack Group](https://inviter.co/seleniumhq).
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Not Code Change: Changes are prose in Markdown, not code identifiers or functions, so this naming convention check is not applicable to the diff. Referred Code Many members of the community are present at the #selenium-docs channel of [Selenium Slack Group](https://inviter.co/seleniumhq).
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Not Applicable: Documentation-only changes do not introduce executable paths or error handling logic to evaluate. Referred Code Many members of the community are present at the #selenium-docs channel of [Selenium Slack Group](https://inviter.co/seleniumhq).
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: External Link Risk: The new Slack inviter URL is an external link; while acceptable for docs, security validation of external inputs is not applicable in code but the link’s safety cannot be verified from the diff. Referred Code channel of [Selenium Slack Group](https://inviter.co/seleniumhq). Feel free to drop in and ask questions

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Use the official support page link Replace the third-party Slack invitation redirect link with a link to the official Selenium support page to ensure long-term stability and avoid potential broken links. website_and_docs/content/documentation/about/_index.en.md [27] -channel of [Selenium Slack Group](https://inviter.co/seleniumhq). +channel on Slack. You can find an invitation on the [Selenium support page](https://www.selenium.dev/support/). Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly points out the risk of using a third-party redirector and proposes a more robust solution by linking to the official support page, which improves the long-term maintainability of the documentation.	Low
More