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

changing text align centre #391

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

Conversation

ambrishgoswami
Copy link

@ambrishgoswami ambrishgoswami commented Oct 22, 2024

Issues Identification

Closes: #(issue number) #390

Description

Summary

Provide a brief description of what this pull request does and why it is needed.

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

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 title and header to "Waste Product Management."
    • Enhanced hero section with new text: "Embrace a Sustainable Future."
    • Added additional footer links for improved navigation: "Upload Waste," "Features," "Feedback," and "About Us."
  • Improvements

    • Adjusted styling for eco-blogs section for better presentation and alignment.

Copy link
Contributor

coderabbitai bot commented Oct 22, 2024

Walkthrough

The changes in this pull request primarily involve updates to the ecotips.html file, including content modifications, structural adjustments, and styling changes. Key updates include a new title and header, revised hero section text, centered titles for the eco-blogs section, and the addition of new footer links to enhance navigation. The eco-tips slider functionality remains unchanged, while the overall clarity and presentation of the content have been improved.

Changes

File Change Summary
ecotips.html - Title updated from "WasteManagement" to "Waste Product Management".
- Header updated from "WasteManagement" to "Waste Product Management".
- Hero text changed from "Reduce. Reuse. Revolutionize." to "Embrace a Sustainable Future".
- Eco-blogs section title centered and updated styling.
- Eco-blogs container centered.
- Footer expanded with links for "Upload Waste," "Features," "Feedback," and "About Us."

Possibly related PRs

Suggested labels

gssoc-ext, hacktoberfest, level2, hacktoberfest-accepted

Suggested reviewers

  • GarimaSingh0109

Poem

🐰 In the land of eco-tips bright,
Waste Product Management takes flight.
With links to explore and a hero so bold,
A sustainable future, a story retold.
Embrace the change, let’s hop along,
Together we’ll make our world strong! 🌍✨


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

netlify bot commented Oct 22, 2024

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

Name Link
🔨 Latest commit c05b78a
🔍 Latest deploy log https://app.netlify.com/sites/manageyourwaste/deploys/6717f56e6769390008982153

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, ambrishgoswami, 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! 😀

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Outside diff range and nitpick comments (5)
ecotips.html (5)

Line range hint 1-452: Critical: Remove duplicate HTML structure

The file contains two complete HTML documents merged together, with duplicate <head> and <body> sections. This is invalid HTML and will cause rendering issues.

Keep only one complete HTML structure. Remove the duplicate sections (lines 453-857) and merge any unique content from the second section into the first.

Also applies to: 453-857


Line range hint 33-37: Improve navigation menu accessibility

The navigation menu lacks ARIA labels and mobile responsiveness indicators.

Enhance the navigation menu:

- <nav>
+ <nav aria-label="Main navigation">
   <ul>
     <li>
-      <a href="#eco-tips-container">
+      <a href="#eco-tips-container" aria-label="View eco tips">
         <i class="fa-brands fa-pagelines"></i> Tips
       </a>
     </li>

Line range hint 36-36: Fix HTML formatting inconsistencies

There are inconsistent spacing and formatting issues in multiple sections.

Apply consistent formatting:

  1. Remove extra spaces between attributes
  2. Maintain consistent indentation
  3. Ensure proper tag closing positions

Example fix:

- <h2 class="blogs-section-title"style="text-align: center;">
+ <h2 class="blogs-section-title">
  Essential Eco Blogs: Your Guide to a Greener Tomorrow!
</h2>

Also applies to: 216-216, 217-217, 218-218


Line range hint 348-391: Enhance slider script performance and accessibility

The slider implementation could be improved for better performance and accessibility.

  1. Add keyboard navigation support
  2. Implement touch events for mobile
  3. Add ARIA labels for screen readers
  4. Use requestAnimationFrame for smooth animations
+ const KEYS = {
+   LEFT: 'ArrowLeft',
+   RIGHT: 'ArrowRight'
+ };

const updateSlider = () => {
+ requestAnimationFrame(() => {
    const slideWidth = slides[0].clientWidth;
    tipsSlider.style.transform = `translateX(-${
      currentIndex * slideWidth
    }px)`;
+ });
};

+ // Add keyboard navigation
+ document.addEventListener('keydown', (e) => {
+   if (e.key === KEYS.LEFT) prevSlide.click();
+   if (e.key === KEYS.RIGHT) nextSlide.click();
+ });

Line range hint 391-452: Enhance form security and validation

The newsletter form lacks proper security measures and validation.

Add proper form validation and security measures:

- <form id="newsletter-form">
+ <form id="newsletter-form" 
+   onsubmit="return validateForm(event)" 
+   autocomplete="off"
+   novalidate>
    <input 
+     type="email" 
+     pattern="[a-z0-9._%+-]+@[a-z0-9.-]+\.[a-z]{2,}$"
+     name="email"
      placeholder="Your Email" 
      required />
    <button type="submit">Subscribe</button>
+   <div class="error-message" aria-live="polite"></div>
  </form>
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 7880a0f and c05b78a.

📒 Files selected for processing (1)
  • ecotips.html (2 hunks)
🧰 Additional context used

Comment on lines +211 to +214
<h2 class="blogs-section-title"style="text-align: center;">
Essential Eco Blogs: Your Guide to a Greener Tomorrow!
</h2>
<div class="eco-blogs-container">
<div class="eco-blogs-container" style="text-align: center;">
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Avoid inline styles for layout and positioning

Using inline styles (style="text-align: center;") for layout is not recommended as it:

  1. Reduces maintainability
  2. Makes it harder to maintain consistent styling across the site
  3. Mixes presentation with content

Move the styling to your CSS file:

.blogs-section-title,
.eco-blogs-container {
  text-align: center;
}

Then remove the inline styles:

- <h2 class="blogs-section-title"style="text-align: center;">
+ <h2 class="blogs-section-title">
  Essential Eco Blogs: Your Guide to a Greener Tomorrow!
</h2>
- <div class="eco-blogs-container" style="text-align: center;">
+ <div class="eco-blogs-container">

@@ -18,7 +18,7 @@
<body>

<header>
<h1>WasteManagement</h1>
<h1>Waste Product Management</h1>
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Codebase verification

Title inconsistency detected - "Waste Product Management" appears only once

Based on the search results, the title "Waste Product Management" appears only once in ecotips.html as an h1 heading, while everywhere else in the codebase (including other parts of the same file) consistently uses "Waste Management". This creates an inconsistency in branding and user experience.

  • ecotips.html: Line containing <h1>Waste Product Management</h1> should be changed to <h1>Waste Management</h1> to maintain consistency with:
    • Page titles across all HTML files
    • Navigation headers
    • Footer text
    • Alt text in images
    • Company references in content
🔗 Analysis chain

Verify the title change impact

The heading has been changed to "Waste Product Management", but this change needs to be consistent across the site.

Let's verify the title consistency:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for inconsistent titles across the site
echo "Searching for title variations..."
rg -i "waste.*management" --type html

Length of output: 4539

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