Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create 404.html #413

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

vishantrathi
Copy link

@vishantrathi vishantrathi commented Nov 7, 2024

Issues Identification

Closes: #413

Description

Summary

Main Heading: “404” displayed prominently in a large, bold font.
Subheading: “Page Not Found” in a smaller, yet bold font.
Message: A brief explanation stating “The page you are looking for doesn’t exist or has been moved,” styled in grey.
Button: A green button labeled “GO HOME” to redirect users back to the homepage.
Footer: A link to your GitHub profile, styled to match the overall design.

Details

Include any detailed information about the changes in this pull request.

Types of Changes

Please check the boxes that apply

  • Bugfix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update (Documentation content changed)
  • Other (please describe):

Checklist

Please check the boxes that apply

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • My changes do not break the current system and pass all existing test cases
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Screenshots

image

If applicable, please attach screenshots of the changes made to the user interface.

Additional Information

Please provide any other information that is relevant to this pull request.

Summary by CodeRabbit

  • New Features
    • Introduced a custom 404 error page for improved user experience.
    • Enhanced styling for error messages and a call-to-action button.

Copy link
Contributor

coderabbitai bot commented Nov 7, 2024

Walkthrough

A new HTML file named 404.html has been added to the project. This file serves as a custom 404 error page, featuring a structured layout that includes a title, styled messages, and a call-to-action button. The page is designed with responsive elements and appropriate CSS classes to enhance user experience when a page is not found.

Changes

File Change Summary
404.html Introduced a custom 404 error page with HTML5 structure, responsive design, CSS styling for messages, and a call-to-action button.

Poem

In the land of lost links, where the bunnies roam,
A 404 page now welcomes them home.
With colors so bright and a message so clear,
It guides every traveler, dispelling all fear.
So hop on along, don’t you fret or despair,
For even in error, we show that we care! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between d5e4053 and 6bffcd0.

📒 Files selected for processing (1)
  • 404.html (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • 404.html

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

Copy link

github-actions bot commented Nov 7, 2024

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. 😊

1 similar comment
Copy link

github-actions bot commented Nov 7, 2024

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. 😊

Copy link

netlify bot commented Nov 7, 2024

Deploy Preview for manageyourwaste failed. Why did it fail? →

Name Link
🔨 Latest commit 6bffcd0
🔍 Latest deploy log https://app.netlify.com/sites/manageyourwaste/deploys/672cdb5c0bbc0000085d7c13

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, vishantrathi, for creating this pull request and contributing to WasteManagement! 💗

The maintainers will review this Pull Request and provide feedback as soon as possible! 😇
We appreciate your patience and contribution, Keep up the great work! 😀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant