Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 6 months ago

Intro section with dropdown navigation with HTML, CSS and JS

Savvas Chrysostomidis•920
@savchrisostomidhs
A solution to the Intro section with dropdown navigation challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jay Khatri•4,230
    @khatri2002
    Posted 6 months ago

    Hi! The developed solution looks great and is very well implemented! A few suggestions to make it even better:

    1. Hover Behavior Issue:

    On desktop, when hovering over the Learn more button, there’s a slight layout shift. The paragraph above the button moves slightly upward, which disrupts the user experience.

    Initially, the button has no border, but on hover, a 2px border is applied, causing the layout shift.

    Current CSS:

    main .text button {
        border: none;
    }
    main .text button:hover {
        border: 2px solid hsl(0, 0%, 8%);
    }
    

    In order to fix it, add a transparent border initially and only change its color on hover.

    main .text button {
        border: 2px solid transparent;
    }
    main .text button:hover {
        border-color: hsl(0, 0%, 8%);
    }
    

    This way, the border width remains consistent, preventing any layout shifts.

    2. Responsiveness Improvements:

    1. Hero Image:
      Currently, the desktop hero image (image-hero-desktop) is being used across all resolutions. However, a separate image for mobile resolution is provided (image-hero-mobile). Using the appropriate image for mobile devices will enhance the viewing experience.

    2. Client Images Overflow:
      On mobile resolutions, the client images (inside the client div) overflow, taking up excessive space. Reducing their size for mobile will fix this issue and make the layout more compact.

    3. Navigation Drawer Behavior:
      When the navigation drawer appears upon clicking the menu icon, the page is still scrollable. This allows the navbar to scroll out of view, which isn’t the expected behavior.
      Fix: When the drawer is displayed, make the body non-scrollable using:

      body {
          overflow: hidden;
      }
      

      Once the drawer is closed, revert it back to auto:

      body {
          overflow: auto;
      }
      

    These small refinements will make the solution even more polished and user-friendly! Great work so far! Keep it up! 🚀

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub