[BUG] [UI Improvement] Update Outdated Navbar Buttons #376

[sahhoArjun097]

Closes: #376

Description

The button in the navbar needs improvement to enhance the overall user experience and match the design aesthetics of the site. The current button design does not align with the modern design style used in other sections of the page.

Navbar Button Update

• The navbar button has been redesigned to improve user experience and responsiveness.
• The button now has modern hover and active states for better interaction.
• The color scheme is updated to maintain consistency with the overall design.
• Responsiveness is enhanced for better display across different screen sizes.
• Accessibility improvements include better contrast and focus states for the button.

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

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
  • Updated project name to "Waste Management" in the README for clarity.
  • Enhanced the "Contributing" section for better guidance.
• Style
  • Introduced a new button style with modern aesthetics and hover effects.
  • Improved layout for the hero section and upload components for better visual presentation.
  • Adjusted media queries for improved responsiveness on mobile devices.

[coderabbitai]

Walkthrough

The changes involve updates to the README.md and styles.css files for the Waste Management project. The README.md file now accurately reflects the project name and purpose, enhancing clarity and guidance for users and contributors. The styles.css file features modifications to button styles, layout adjustments, and improved responsiveness across various sections, including the introduction of new classes and enhancements to existing ones.

Changes

File	Change Summary
README.md	Updated project name to "Waste Management," revised sections for clarity, and improved structure.
styles.css	Introduced new button styles, updated layout for .hero, .upload-card, and .mission-box, and improved responsiveness with media queries.

Assessment against linked issues

Objective	Addressed	Explanation
Update navbar buttons to match modern UI design (#376)	✅

Possibly related PRs

• [Feature]Revamp Homepage CSS & Add Relevant Images for Enhanced UI #352 #375: Enhances documentation for the Waste Management project, aligning with updates made in the main PR regarding project name and contributing guidelines.
• [Feature] No CSS Applied to ecotipes.html #354 #379: Includes structural changes to ecotips.html that improve layout and functionality, relevant to overall enhancements in user experience and design consistency.

Suggested labels

gssoc-ext, hacktoberfest, level2, hacktoberfest-accepted

Suggested reviewers

• GarimaSingh0109

Poem

In a world of waste, we strive to mend,
With buttons bright, our styles we blend.
From "Community-Site" to "Waste Management" we cheer,
A cleaner tomorrow, let’s hold it near!
🐰✨

---

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

[netlify]

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

Name	Link
🔨 Latest commit	d06bafe
🔍 Latest deploy log	https://app.netlify.com/sites/manageyourwaste/deploys/671669377560780008dec362

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (4)

README.md (3)

Line range hint 80-101: LGTM! Contributing guidelines are clear and comprehensive.

The expanded contributing section provides detailed steps for potential contributors, which is excellent. To further improve this section:

Consider adding a link to the CONTRIBUTING.md file for more detailed guidelines. You can add this line after the existing content:

For more detailed guidelines, please refer to our [CONTRIBUTING.md](CONTRIBUTING.md) file.

---

Line range hint 138-151: Great addition of GSSOC 2024 information. Minor typo needs correction.

The inclusion of the GSSOC 2024 section is valuable and aligns well with the project's participation in open source programs.

There's a minor typo on line 151. Please correct "Waste Managment" to "Waste Management".

-                This project is part of GirlScript Summer of Code. We enthusiastically invite community contributions to contribute to Waste Managment.
+                This project is part of GirlScript Summer of Code. We enthusiastically invite community contributions to contribute to Waste Management.

---

Line range hint 153-168: Remove duplicated sections at the end of the file.

The content of the README is good, but there's unnecessary duplication of the Open Source Programs and Code of Conduct sections at the end of the file.

To improve clarity and avoid confusion, please remove the duplicated sections (lines 153-168). The information is already present in the main body of the README.

styles.css (1)

1290-1320: LGTM! Modern and responsive button styles.

The new button styles for the navbar look great and align well with the PR objectives. The transparent background, removal of borders, and addition of hover effects create a modern and interactive design.

Consider adding a transition effect to the text color change on hover for smoother user experience:

 .button a {
   text-decoration: none;
   color: #fff;
   font-weight: bold;
+  transition: color 0.3s ease;
 }

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 84be23f and d06bafe.

📒 Files selected for processing (2)

• README.md (1 hunks)
• styles.css (1 hunks)

🧰 Additional context used

🔇 Additional comments (2)

README.md (2)

Line range hint 1-37: LGTM! The introduction and features are well-defined.

The updated project name and description accurately reflect the focus on waste management. The features section provides a clear and comprehensive overview of the platform's capabilities, aligning well with the project objectives.

---

Line range hint 1-168: Overall, the README updates are positive but require minor adjustments.

The changes to the README file align well with the PR objectives, improving the project description, contributing guidelines, and adding valuable information about GSSOC participation. To finalize these improvements:

1. Add a link to the CONTRIBUTING.md file in the contributing section.
2. Correct the typo in "Waste Management" in the GSSOC section.
3. Remove the duplicated Open Source Programs and Code of Conduct sections at the end of the file.

Once these minor issues are addressed, the README will provide a clear, comprehensive, and well-structured overview of the Waste Management project.