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

update styling "what user says" on home page #877

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Abhishek-Sharma-069
Copy link

@Abhishek-Sharma-069 Abhishek-Sharma-069 commented Oct 25, 2024

##Pull Request for Resum-Resume 💡

##Issue Title: Update Styling for "What User Says" on Home Page
Info about the related issue (Aim of the project): Improve the user experience by enhancing the visual appeal of the testimonial cards on hover.

Name: Abhishek Sharma
GitHub ID: Abhishek-Sharma-069
Email ID: [email protected]
Closes: #876

**Describe the Add-ons or Changes You've Made 📃
I improved the styling of the testimonial cards on the homepage. Now, when users hover over a testimonial card, it lifts slightly with a transform effect and features a subtle #0073b1 box-shadow to make it more visually engaging. This change adds a dynamic feel to the cards, creating a smoother user experience.

**Type of Change ☑️
Code style update (formatting, local variables)
How Has This Been Tested? ⚙️
I tested the updated styling locally across different screen resolutions to ensure that the hover effect is consistent and does not interfere with other homepage elements. The added effects work smoothly and do not generate any new warnings.

**Checklist ☑️
My code follows the guidelines of this project.
I have performed a self-review of my own code.
My changes generate no new warnings.
I have added things that prove my fix is effective or that my feature works.

Summary by CodeRabbit

  • New Features

    • Introduced hover effects for testimonial cards, enhancing visual feedback.
    • Added social media icons to the footer for improved visibility and interaction.
    • Implemented a scroll progress bar to indicate the user's scroll position.
  • Improvements

    • Enhanced styling and structure of features and testimonials sections.
    • Adjusted layout for better responsiveness on smaller screens.
    • Refined tooltip behavior for the chatbot button for a cleaner user experience.

added hover feature in testimonial cards
Copy link

coderabbitai bot commented Oct 25, 2024

Walkthrough

The changes in this pull request primarily involve updates to the index.html file, focusing on the styling and structure of the features and testimonials sections. A new hover effect for testimonial cards has been introduced, along with refined CSS for the chatbot button and tooltip. The footer has been enhanced with social media icons, and the overall layout has been adjusted for improved responsiveness on smaller screens. Additionally, a scroll progress bar functionality has been retained in the script section.

Changes

File Change Summary
index.html - Enhanced styling and structure for features and testimonials sections.
- Added hover effect for .testimonial-card with transformation and shadow.
- Refined CSS for chatbot button and tooltip, ensuring tooltip visibility on hover.
- Improved footer with social media icons for better visibility.
- Adjusted layout for responsiveness, particularly on smaller screens.
- Updated media queries for navbar and card components on mobile devices.
- Retained JavaScript functionality for scroll progress bar.

Assessment against linked issues

Objective Addressed Explanation
Update styling "what user says" on home page (876)

Possibly related PRs

  • Homepage Repeated Content, UI Improvements, and Fixes #813: This PR modifies the same index.html file, specifically enhancing the styling and structure of the features and testimonials sections, which aligns closely with the changes made in the main PR regarding hover effects and layout adjustments.

Suggested labels

hacktoberfest, level1, gssoc-ext, hacktoberfest-accepted

Suggested reviewers

  • GarimaSingh0109

🐇 In the garden where the bunnies play,
New styles bloom, brightening the day.
With hover effects that dance and twirl,
Testimonials shine, giving joy a whirl.
Responsive layouts, oh what a treat,
A scroll bar to guide, making it neat! 🌼


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

@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: 0

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

126-130: LGTM! Consider z-index refinement

The hover effect implementation matches the requirements and creates a consistent experience with the feature cards. However, the z-index value might cause unnecessary stacking context issues since the testimonial cards don't overlap.

 .testimonial-card:hover {
     transform: translateY(-10px) scale(1);
     box-shadow: 0 4px 8px #0073b1; 
-    z-index: 3;
 }

Line range hint 1-1000: Consolidate duplicate CSS rules

There are multiple style blocks with duplicate rules for .features-card, .testimonial-card, and other classes. This makes the CSS harder to maintain and can lead to specificity issues.

Consider:

  1. Consolidating all styles into a single style block
  2. Moving styles to an external CSS file
  3. Using CSS preprocessors like SASS/LESS for better organization

Example of duplicated rules that should be consolidated:

  • .features-card appears multiple times with different styles
  • .testimonial-card styling is repeated
  • Media queries are duplicated

Line range hint 450-460: Enhance accessibility for social media icons

The social media icons lack proper accessibility attributes, which makes them harder to use with screen readers.

Add appropriate aria-labels to the social media links:

-<a href="#"><i class="fab fa-facebook-f"></i></a>
-<a href="#"><i class="fab fa-twitter"></i></a>
-<a href="#"><i class="fab fa-linkedin-in"></i></a>
-<a href="#"><i class="fab fa-instagram"></i></a>
+<a href="#" aria-label="Visit our Facebook page"><i class="fab fa-facebook-f"></i></a>
+<a href="#" aria-label="Follow us on Twitter"><i class="fab fa-twitter"></i></a>
+<a href="#" aria-label="Connect with us on LinkedIn"><i class="fab fa-linkedin-in"></i></a>
+<a href="#" aria-label="Follow us on Instagram"><i class="fab fa-instagram"></i></a>

Line range hint 500-520: Optimize performance of scroll progress bar

The scroll event listener can fire frequently and impact performance. Additionally, multiple versions of Font Awesome are being loaded.

  1. Debounce the scroll event:
+ function debounce(func, wait) {
+   let timeout;
+   return function executedFunction(...args) {
+     const later = () => {
+       clearTimeout(timeout);
+       func(...args);
+     };
+     clearTimeout(timeout);
+     timeout = setTimeout(later, wait);
+   };
+ }
- window.addEventListener('scroll', updateProgressBar);
+ window.addEventListener('scroll', debounce(updateProgressBar, 16));
  1. Remove duplicate Font Awesome imports and use a single version:
-<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css" />
-<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.6.0/css/all.min.css" />
+<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.6.0/css/all.min.css" />

Line range hint 1-50: Fix HTML structure and meta tags

There are several HTML best practices issues that should be addressed:

  1. Add viewport meta tag for proper mobile rendering
  2. Close the chatbot anchor tag
  3. Remove duplicate head tags
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
+   <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>LinkedIn Resume Builder - Home</title>
    <!-- Remove duplicate head tags and consolidate meta tags -->
    <div class="chatbot-container">
        <button class="chatbot-button group">
            <img class="h-20" src="chatbot.gif" alt="chatbot">
            <span class="tooltip-text">
                Welcome to Resum Resume! <br>
                How can I help You? ^_^ 
            </span>
        </button>
    </div>
+   </a>
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 443ceed and 913cfd6.

📒 Files selected for processing (1)
  • index.html (1 hunks)

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.

update styling "what user says" on home page
1 participant