Fix Grammatical Errors and Improve Mobile Responsiveness on GSoC Landing Page

[Satyamkumarnavneet]

This pull request addresses the following updates:

1. Grammatical Fixes:

   • Corrected minor grammatical errors on the GSoC landing page.

2. Mobile Responsiveness:

   • Updated the "Get Started with GSoC" section to ensure better mobile responsiveness, especially for smaller screen sizes.

These changes improve the overall user experience and accessibility on both desktop and mobile devices.

Summary by CodeRabbit

• Style
  • Updated the formatting in the "Connect with Mentors" section to enhance text clarity.
  • Modified the announcement link styling in the Google Summer of Code section to ensure it displays on all screen sizes.

[coderabbitai]

Walkthrough

The changes update the HTML templates for the GSoC landing and announcement pages. In the “gsoc_landing_page.html”, the “Connect with Mentors” section has been reformatted so that the “Slack community” text now appears as a standalone sentence outside the closing anchor tag. In the “index.html”, the anchor element for the GSoC announcement has been updated by removing the hidden class from its class list, which makes the link visible on all screen sizes.

Changes

File(s)	Change Summary
web/templates/gsoc_landing_page.html	Reformatted the “Connect with Mentors” section by splitting the text so that “Slack community” is rendered as a standalone sentence before the closing anchor tag.
web/templates/index.html	Modified the class attribute in the GSoC announcement anchor element by removing the hidden class, ensuring the link is displayed on all screen sizes while preserving styling.

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

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

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

web/templates/gsoc_landing_page.html (1)

66-67: Refined Grammar in the "Connect with Mentors" Section
Moving the "Slack community." text into its own line helps clarify the call-to-action and improves readability. Please verify that the punctuation (the period) placement aligns with the overall design and content guidelines—if the design intends the period to be outside the link, a minor adjustment may be needed.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2967ff5 and 15e059a.

📒 Files selected for processing (2)

• web/templates/gsoc_landing_page.html (1 hunks)
• web/templates/index.html (1 hunks)

🔇 Additional comments (1)

web/templates/index.html (1)

240-244: Improved Mobile Visibility for the GSoC Announcement Button
Removing the hidden class from the anchor element ensures that the "Get Started with GSoC" button is visible on all screen sizes, which meets the mobile responsiveness objective described in the PR. Please double-check on various devices that the adjusted styling (e.g., use of inline-flex with the other utility classes) maintains consistency with the rest of the layout.