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

Improve Footer and Navbar Styling on About Page #833

Merged
merged 1 commit into from
Oct 25, 2024

Conversation

Mohitranag18
Copy link
Contributor

@Mohitranag18 Mohitranag18 commented Oct 22, 2024

Description:

This pull request addresses issue #810, which focuses on improving the styling of the footer and navbar on the About page. The current styling was inconsistent, and this update ensures the design is clean, responsive, and aligned with the overall project theme.

Changes Implemented:

Navbar Styling:

  • Improved the overall alignment and spacing of navbar elements to enhance readability and navigation.
  • Updated the color scheme, hover effects, and transitions to match the project’s design guidelines.
  • Ensured the navbar is fully responsive across different screen sizes and devices.

Footer Styling:

  • Redesigned the footer layout for better organization and visual appeal.
  • Adjusted margins, padding, and alignment to fix inconsistencies in the previous design.
  • Ensured the footer content is responsive and adjusts properly on mobile devices.

Screenshot:

Screenshot 2024-10-22 at 08-44-09 About Us - LinkedIn Resume Builder

Testing:

  • Verified that the navbar and footer look clean and professional on both desktop and mobile views.
  • Ensured the updated styles maintain consistency with the overall design of the About page.
  • Tested hover effects and transitions for smooth user interaction.

Summary by CodeRabbit

  • New Features

    • Introduced a new "About" section detailing the LinkedIn Resume Builder's purpose, mission, and advantages.
    • Added a progress bar that reflects the user's scroll position.
  • Enhancements

    • Restructured the navbar for better organization and improved styling.
    • Updated footer layout for enhanced visual hierarchy and alignment.
    • Enhanced overall styling with new CSS rules for improved layout and readability.

Copy link

coderabbitai bot commented Oct 22, 2024

Walkthrough

The changes in this pull request involve significant updates to the about.html file, including a restructured navbar, enhanced CSS styles, and new JavaScript functionality. The navbar is now encapsulated in a single <nav> element, and a new "About" section has been added to the main content area, featuring three informative cards. Additional styling improvements include updated CSS variables, footer layout adjustments, and the introduction of a scroll progress bar.

Changes

File Change Summary
about.html Restructured navbar, added "About" section with three cards, enhanced CSS styles, and JavaScript for scroll progress bar.

Possibly related issues

Possibly related PRs

Suggested labels

hacktoberfest, level2, gssoc-ext, hacktoberfest-accepted

Suggested reviewers

  • GarimaSingh0109

Poem

🐰 In the land of code where bunnies play,
The navbar shines in a stylish way.
Cards tell tales of a builder's might,
With colors bright and a scroll bar's light.
Hopping through changes, oh what a sight!
Let's celebrate this coding delight! 🎉


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: 3

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between fdc4db8 and bc9cd57.

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

Comment on lines +418 to 425
<img src="images/logo.png" alt="logo">
<a class="tab" href="index.html">Home</a>
<a class="tab" href="about.html">About</a>
<a class="tab" href="resume.html">Build Resume</a>
<a class="tab" href="resume_tips.html">Resume Tips</a>
<a class="tab" href="signup.html">Sign Up</a>
<a class="tab" href="login.html">Login</a>
<a class="tab" href="privacypolicy.html">Privacy Policy</a>
</div>
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix the mismatched HTML tags in the navbar

There's an unmatched closing </div> tag within the nav element starting at line 418, which may cause rendering issues. Ensure that all HTML tags are properly opened and closed.

Apply this diff to correct the HTML structure:

 <nav class="navbar">
     <img src="images/logo.png" alt="logo">
     <a class="tab" href="index.html">Home</a>
     <a class="tab" href="about.html">About</a>
     <a class="tab" href="resume.html">Build Resume</a>
     <a class="tab" href="resume_tips.html">Resume Tips</a>
     <a class="tab" href="signup.html">Sign Up</a>
     <a class="tab" href="login.html">Login</a>
-    </div>
 </nav>
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<img src="images/logo.png" alt="logo">
<a class="tab" href="index.html">Home</a>
<a class="tab" href="about.html">About</a>
<a class="tab" href="resume.html">Build Resume</a>
<a class="tab" href="resume_tips.html">Resume Tips</a>
<a class="tab" href="signup.html">Sign Up</a>
<a class="tab" href="login.html">Login</a>
<a class="tab" href="privacypolicy.html">Privacy Policy</a>
</div>
<img src="images/logo.png" alt="logo">
<a class="tab" href="index.html">Home</a>
<a class="tab" href="about.html">About</a>
<a class="tab" href="resume.html">Build Resume</a>
<a class="tab" href="resume_tips.html">Resume Tips</a>
<a class="tab" href="signup.html">Sign Up</a>
<a class="tab" href="login.html">Login</a>

Comment on lines +534 to +554
<style>
.footer-section{
display: flex;
justify-content: left;
flex-direction: column;
}
.ul{
display: flex;
flex-direction: column;
justify-content: left;
}
li{
text-align: left;
}
.footer a{
color: white;
}
.footer p{
margin-top: 2rem;
}
</style>
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Move footer styles to the <head> section or external stylesheet

Defining CSS within <style> tags inside the body is not recommended. For better maintainability and consistency, consider moving these footer styles to the <head> section or an external stylesheet. Additionally, consider using more descriptive class names instead of .ul, since ul is an HTML tag, to avoid confusion.

Apply this diff to move the footer styles to the <head> section and rename the .ul class:

 <!-- Remove the inline footer styles from the body -->
-<style>
-    .footer-section{
-        display: flex;
-        justify-content: left;
-        flex-direction: column;
-    }
-    .ul{
-        display: flex;
-        flex-direction: column;
-        justify-content: left;
-    }
-    li{
-        text-align: left;
-    }
-    .footer a{
-        color: white;
-    }
-    .footer p{
-        margin-top: 2rem;
-    }
-</style>

Add these styles to the existing <style> section in the <head>:

+/* Add to your existing CSS in the <head> */
+.footer-section {
+    display: flex;
+    justify-content: left;
+    flex-direction: column;
+}
+.footer-list {
+    display: flex;
+    flex-direction: column;
+    justify-content: left;
+}
+li {
+    text-align: left;
+}
+.footer a {
+    color: white;
+}
+.footer p {
+    margin-top: 2rem;
+}

Update the HTML to use the new class name:

-<ul class="ul">
+<ul class="footer-list">

Committable suggestion was skipped due to low confidence.

about.html Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants