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

flexbox, grid, media query

accessibility
Hamid Abdalla (HA)•250
@hamid-abdallah-mohammed
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


hello, world... I got through the hardest time of my life while I was working on the sidebar menu but I did it . for me sidebar was like nightmare but enough is enough . hope to see more perfect way to create nice design

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Harm Intemann•590
    @ghintema
    Posted almost 3 years ago

    Hi Hamid-Abdallah-Mohammed,

    I've reviewed your code and I'd like to give you some comments that may be useful to improve yourself. First of all I am wondering, why you've build to different navigations in the html-structure. You have one for the desktop-version nested into <nav></nav> (wich is good, of course) and a second navigation nested into <div class="mobile-nav"></div>. This irritated me a lot! :) You really could (and should) have done mobil and desktop with the one nested in the <nav></nav>. Secondly I would advice you to always build your menu-structure in list-elements like this: <ul><li></li></ul>. You can even do that with two or more layers of menu-structure by nesting a <ul><li></li></ul> INSIDE A <li></li>. It really is more semantical and (much) easier to layout one single <nav></nav> for mobile and desktop. One last (miner) thing that rose my curiosity is this (from line148): grid-template-columns: repeat(1, max(200px, 350px)); What sense does it have to max(250px, 350px)? The max of 250 and 350 is always and forever 350px.

    If you have further questions on my coment, don't hesitate to get back on me! I hope I could help you a bit. Really mean to do that... Cheers, Harm

    Marked as helpful
  • umar453•130
    @umar453
    Posted almost 3 years ago

    Nice overall. for good user experience try to add cursor pointer on dropdown links and at the moment user click on the dropdown link the icon would be changed downward.

    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

Oops! 😬

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

Log in with GitHub