Renamed News section to Contact Us #3852

[SURAJ-RATHI]

Title:
Renamed News Section to Contact Us (#3852)

Description:
This PR addresses issue #3852 by renaming the News section to Contact Us as discussed in the issue thread.

Changes Made:

Updated the section title from News to Contact Us. (Footer\footer.tsx)

Ensured consistency in the UI and layout.
Verified that the changes align with the discussion in the issue thread.
Screenshots (if applicable):
Before fix :

after Fix:

Checklist:
Code follows the project’s contributing guidelines.
Tested changes locally to ensure proper display.
Linked the PR with issue #3852.

Summary by CodeRabbit

• New Features
  • Updated the footer heading from "News" to "Contact Us," making it easier for users to locate contact information.

[coderabbitai]

Walkthrough

The update modifies the text content within the Footer component. The heading text has been changed from "News" to "Contact Us." The alteration is limited to updating the display label without impacting the component's structure, functionality, or public interfaces.

Changes

File(s)	Change Summary
components/footer/Footer.tsx	Updated the heading text from "News" to "Contact Us" in the Footer.

Poem

I'm a happy rabbit, hopping with glee,
"News" waved goodbye, now "Contact Us" we see,
A slight twist in the footer's song,
Brings a fresh label to sing along,
Cheers to small changes that make UI bright!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9ceaf84 and 956f611.

📒 Files selected for processing (1)

• components/footer/Footer.tsx (1 hunks)

⏰ Context from checks skipped due to timeout of 180000ms (1)

• GitHub Check: Lighthouse CI

🔇 Additional comments (1)

components/footer/Footer.tsx (1)

58-58: Change looks good!

The label has been appropriately updated from "News" to "Contact Us", which aligns with the PR objective. This change makes the section's purpose clearer since it contains contact information (the "Email Us" link).

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[asyncapi-bot]

We require all PRs to follow Conventional Commits specification.
More details 👇🏼

 No release type found in pull request title "Renamed News section to Contact Us #3852". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	956f611
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/67d02fe27d34510008076da6
😎 Deploy Preview	https://deploy-preview-3866--asyncapi-website.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 site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (9ceaf84) to head (956f611).

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #3866   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines          667       667           
  Branches       113       113           
=========================================
  Hits           667       667           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Mayaleeeee]

Why not add a mail icon to the "Email Us" text?