feat: use typeform for join us

[andostronaut]

This is an automated pull request for branch develop

Summary by CodeRabbit

• New Features

  • Enhanced the HeroSection layout for improved visibility and interactivity.
  • Added a button that directs users to a specified URL upon clicking.
  • Updated visual indicators for interactive elements to enhance user engagement.

• Bug Fixes

  • Adjusted stacking context for better layering of visual components within the HeroSection.

• Chores

  • Restructured the DATA object for improved organization of URLs and color schemes.

[coderabbitai]

Walkthrough

This update refines the HeroSection component, enhancing visibility and user interaction by modifying its layout and button functionality. The DATA object is restructured for better accessibility, introducing a top-level typeform URL while simplifying the overall data organization. These changes collectively aim to improve user experience and maintain cleaner code architecture.

Changes

Files	Change Summary
components/layout/sections/hero.tsx	Updated HeroSection with z-50 for stacking context, added onClick for Button, and modified Particles class to z-0 for better layering.
data/index.ts	Restructured DATA object, moving URLs and colors to top level and removing nested objects, while maintaining the partners array.

Poem

In the hero's vibrant crest,
A button beckons, come, invest!
With colors bright and layers high,
New paths to click, so come and try!
Data dances, restructured neat,
Join the fun, hop to the beat! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b918b4a and e0775c9.

Files selected for processing (2)

• components/layout/sections/hero.tsx (3 hunks)
• data/index.ts (2 hunks)

Additional comments not posted (4)

data/index.ts (1)

12-27: LGTM! Verify the usage of the new DATA structure in the codebase.

The changes improve the organization and accessibility of the DATA properties.

Ensure that all parts of the codebase that interact with the DATA object are updated to reflect the new structure.

Verification successful

---

LGTM! The new DATA structure is correctly utilized across the codebase.

The changes improve the organization and accessibility of the DATA properties.

• components/layout/navbar.tsx
• components/layout/sections/hero.tsx
• components/layout/sections/parteners.tsx
• components/layout/sections/sponsors.tsx
• components/layout/sections/footer.tsx

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of the restructured `DATA` object in the codebase.

# Test: Search for the usage of `DATA` properties. Expect: Only occurances of the new structure.
rg --type typescript -A 5 $'DATA'

Length of output: 67

---

Script:

#!/bin/bash
# Description: Verify the usage of the restructured `DATA` object in the codebase.

# Test: Search for the usage of `DATA` properties. Expect: Only occurrences of the new structure.
rg --type ts -A 5 'DATA'

Length of output: 6151

components/layout/sections/hero.tsx (3)

22-22: LGTM!

The addition of the z-50 class improves the stacking context, ensuring better visibility and interaction with the content.

---

38-41: LGTM!

The update to the Button component enhances user engagement by providing a direct call to action and visually indicating interactivity.

---

50-50: LGTM!

The modification to the Particles component's className ensures proper layering of visual effects.