feat(gsoc): Update GSoC landing page for 2025 with modern design and …

[Ashutoshx7]

fixes #227

Uploading Screen Recording 2025-03-23 123645.mp4…

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The change significantly updates the gsoc_landing_page.html file by adding new sections to the landing page. These additions include an "Alpha One Labs x GSoC: First-Time Participation" section with a highlights grid, a "GSoC 2025 Timeline" listing key program events with descriptions, and a "FAQs" section addressing common questions regarding GSoC and Alpha One Labs. No modifications were made to the declarations of any exported or public entities.

Changes

File(s)	Change Summary
web/templates/gsoc_landing_page.html	Added three new sections: "Alpha One Labs x GSoC: First-Time Participation" (with highlights for "What to Expect", "Mentorship", and "Community"), "GSoC 2025 Timeline" (detailing key program events), and "FAQs" (answering common questions).

Possibly related PRs

• GSoC 2025 Landing Page: Alpha One Labs Rebrand, Sections & GitHub API  #157: Involves similar content updates to the landing page, focusing on the "First-Time Participation," "Timeline," and "FAQs" sections.

Suggested labels

d:21, d:22

Suggested reviewers

• A1L13N

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 22f682c and 1e651e4.

📒 Files selected for processing (1)

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

---

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

[github-actions]

🚨 Missing Issue Link

This pull request appears to not reference any GitHub issue.

As per our workflow requirements, all PRs should address an existing issue. This ensures:

• Changes are properly tracked
• Work is discussed before implementation
• Code reviews are more focused

How to Fix This

Please link this PR to an existing issue using one of these methods:

1. Reference the issue in your PR description: "Fixes darkmode/about #123" or "Addresses darkmode/about #123"
2. Use GitHub's interface to link the PR to an issue in the Development section
   • Look for the section that says "Development" on the right side of your PR
   • Click "Link an issue" or "Link issues"
   • Select the relevant issue(s)
3. If no issue exists yet, please create one first

Exceptions

PRs with these labels don't require linked issues:

• documentation
• dependencies
• typo
• ci
• chore

Or with titles starting with:

• docs:
• chore:
• deps:
• ci:

This PR will be automatically closed. Feel free to reopen it once you've linked it to an issue or added appropriate labels.

Thank you for your contribution!

[github-actions]

🚨 Missing Issue Link

This pull request appears to not reference any GitHub issue.

As per our workflow requirements, all PRs should address an existing issue. This ensures:

• Changes are properly tracked
• Work is discussed before implementation
• Code reviews are more focused

How to Fix This

Please link this PR to an existing issue using one of these methods:

1. Reference the issue in your PR description: "Fixes darkmode/about #123" or "Addresses darkmode/about #123"
2. Use GitHub's interface to link the PR to an issue in the Development section
   • Look for the section that says "Development" on the right side of your PR
   • Click "Link an issue" or "Link issues"
   • Select the relevant issue(s)
3. If no issue exists yet, please create one first

Exceptions

PRs with these labels don't require linked issues:

• documentation
• dependencies
• typo
• ci
• chore

Or with titles starting with:

• docs:
• chore:
• deps:
• ci:

This PR will be automatically closed. Feel free to reopen it once you've linked it to an issue or added appropriate labels.

Thank you for your contribution!