Landing Page

[Damini2004]

Related Issue

#89 #88

Description

As i designed this with the help of HTML,CSS

Type of PR

• Bug fix
• Feature enhancement
• Documentation update
• Other (specify): _______________

Screenshots / videos (if applicable)

Checklist:

• I have performed a self-review of my code
• I have read and followed the Contribution Guidelines.
• I have tested the changes thoroughly before submitting this pull request.
• I have provided relevant issue numbers, screenshots, and videos after making the changes.
• I have commented my code, particularly in hard-to-understand areas.

Additional context:

[Include any additional information or context that might be helpful for reviewers.]

Summary by CodeRabbit

• New Features

  • Introduced a new web page layout for "Web Design Mastery | Fitclub" showcasing InfraBoard's features.
  • Added a class booking section for users to easily book classes.
  • Included a footer with social media links for better connectivity.

• Style

  • Defined custom styles including CSS variables, layout, typography, colors, and responsive design rules for enhanced user experience across devices.

[netlify]

✅ Deploy Preview for infraboard ready!

Name	Link
🔨 Latest commit	f8bb31e
🔍 Latest deploy log	https://app.netlify.com/sites/infraboard/deploys/66539aecd34a0100080c1508
😎 Deploy Preview	https://deploy-preview-104--infraboard.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.

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

Commits

Files that changed from the base of the PR and between 611716f and f8bb31e.

Files selected for processing (2)

• src/pages/index.html (1 hunks)
• src/styles/style.css (1 hunks)

 ______________________________________________________
< Multiplying to perform multi-threaded bug detection. >
 ------------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

---

Tip

Early Access Features

• gpt-4o model for chat

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.

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 full the 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 help to get help.

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

CodeRabbit Configration 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 611716f and f8bb31e.

Files selected for processing (2)

• src/pages/index.html (1 hunks)
• src/styles/style.css (1 hunks)

Files skipped from review due to trivial changes (1)

• src/styles/style.css

Additional comments not posted (8)

src/pages/index.html (8)

1-11: Ensure the HTML document structure is correctly set up.

The document type, language, meta tags, and stylesheet links are correctly defined.

---

14-24: Review the navigation bar implementation.

The navigation bar is well-structured with appropriate links and a call-to-action button. However, consider adding alt attributes to icons for accessibility.

---

26-36: Check the header section for content and styling.

The header section is visually appealing and contains a clear call-to-action. The use of background blurs adds a nice touch. Ensure that the text remains legible on all backgrounds.

---

38-83: Evaluate the 'Explore' section for functionality and design.

The 'Explore' section is interactive with navigation arrows and cards for different features. Ensure that the links are correctly set up and that the hover effects on the cards are consistent.

---

85-93: Assess the 'Class Booking' section.

The section is straightforward and promotes a specific service with a booking button. Check that the button links to the correct booking system.

---

95-126: Inspect the 'Join' section for user engagement elements.

This section effectively uses cards to highlight different aspects of the service. Consider adding more interactive elements like modals or tooltips for a better user experience.

---

128-160: Review the 'Pricing' section for clarity and information presentation.

The pricing section is clear and informative. The use of cards for different plans is effective. Ensure that all images have alt attributes for accessibility.

---

162-188: Examine the footer for completeness and functionality.

The footer includes contact information, social media links, and additional navigation. Ensure that all links are up-to-date and that the social media icons link to the correct pages.

[aryasoni98]

@Damini2004 Have you check the issue or read the issue #89 . Please read the issue and what framework use to build the landing page .