Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 3 years ago

Intro Section With Dropdown Navigation (challenging but rewarding)

Nguyen Nguyen•340
@jesuisbienbien
A solution to the Intro section with dropdown navigation challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone,

It's been a while because this challenge was quite difficult for me. I've finally finished (and very proud of myself hehe). Please take some time to review my solution. I'd love to receive as many feedbacks as possible.

One thing I noticed is that, when on a few specific mobile devices (iphone SE, next hub, and galaxy S8+), the overlay effect acted weird. There was a white part at the top of the page. This doesn't happen in other mobile devices though. Any help on this issue would be greatly appreciated.

Any other feedbacks are welcome. Thank you in advance!

Happy coding :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yehan Nilanga•670
    @Yehan20
    Posted about 3 years ago

    Hey Congratulations on Completing the Challenge , I noticed that the nav bar did not expand on my laptop and once i inspected it , it expanded once it exceeds 1400px , i think you could add your break point on around 768 px , and in my laptop there were some side scrolling as well , in addition if your wanted to rotate the arrow near the navlink your could do that using js when you add the click effect for the drop down you can select the image next to it and change the src to the new arrow and when you click it again change the src back.

    For the overlay you could use the help of pseudo selectors to generate it , for an example when your nav is open you could add a class may be opened/toggled and for that add a pseudo selector. i did some testing and found this will make a full size overlay

    div#nav-menu:before {
        content: '';
        position: absolute;
        top: 0;
        width: 79%;
        height: 100%;
        left: 0;
        background: rgba(0,0,0,0.5);
        transform: translateX(-99%);
    
    }
    

    you could try this. I Hope by answer was helpful , good luck for the next challenge

    Marked as helpful
  • Yahya•80
    @yhas14
    Posted about 3 years ago

    Wow you've come a long way, I remember commenting on your first project and I can see the major improvements you've made. Keep up the great work.

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
Frontend Mentor logo

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

Oops! 😬

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

Log in with GitHub