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

intro-section-with-dropdown-navigation-main

manarbooo•540
@manarbooo
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

  • P
    Andrey•4,640
    @dar-ju
    Posted 5 months ago

    Hi manarbooo!

    Great job! I like your responsive layout and it's as close to the mockup as possible.

    There are a few things that could be fixed:

    • check the layout on a screen smaller than 840px, it looks good, but there is a horizontal scroll and you can see the mobile menu on the right. You can use display: none for it, but in this case the animation won't work. The best option is to add the line overflow-x: hidden; for body and everything will be ok
    • it would be cool if the "Features" and "Company" menu appeared not only by clicking on the arrows, but also on the text. It would be even cooler if the menu didn't have to be closed by clicking again, but, for example, by clicking anywhere outside this block.
    • when you click on the burger, it would be better if only the menu moved up, and the gray background just appeared. To do this, you need to separate the background and menu blocks, make the background block opacity
    • you used the <figure> tag for the image, but you connected the image itself via css background-image, this makes no sense. In general, this is a content image and it is better to use the <img> tag with a filled alt. You did the right thing for the logos below, but you need to add the alt attribute to them. For the burger menu and menu closing images, there should also be alt, since these are non-content images, the alt should be empty alt="", otherwise it will be an error.

    Otherwise, everything is great, good luck with your development!

    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

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