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

vanilla CSS, JS dropdown navbar

Ko Loy Yee•50
@koloyyee
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


How can I write cleaner CSS?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hi Ko Loy Yee, I also just completed this challenge so I thought to give you some feedback. First off, good attempt at putting it together, especially the dropdown navs; I really like the animation on the hamburger menu. Some things to note:

    • In the desktop view, the navigation at the top should be sitting on the same row as the logo, as in, they should be in the same container somehow. Once you rework your HTML, you can add flexbox on the div and that should help align things.

    • Sometimes when I click on the dropdown it doesn't open right away, and I'd need to click it again. There might be something in your JS that you should look into.

    • In the mobile slide navigation, the dropdown navigations don't need any drop shadow

    • I notice that you seem to have started with the desktop view in writing your CSS; you can try using a mobile-first approach, and see whether that is a bit easier.

    About how to write cleaner CSS, I think it helps to just be consistent first and to also keep in mind the nature of CSS, namely inheritance and cascading. That would save you from writing a lot of redundant code. It helps to read others' CSS, as that would give you an idea of what they're doing and how readable their code is; it also helps to know what terms that are commonly used, such as wrapper and container. I often would look at repos of experienced developers and see how they structure their CSS (I highly recommend checking out Kevin Powell's repos). Overall, practice is most essential, as there will be many mistakes made, and over time you'll know what works and what doesn't :) Good luck!

    Marked as helpful

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