Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Intro section with dropdown navigation

sumaira10041•210
@sumaira10041
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


Can anyone plzz tell me how to make it responsive .....i give two days to this page but still cant make it responsive...can someone tell me where i did mistake

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mr. Ryt•200
    @MrRyt247
    Posted over 1 year ago

    To achieve responsiveness, you must:

    • get familiar with flex & grid
    • media queries
    • learn to use other units (i.e. vw, %, vh, dvh, dvw, rem, etc.)

    Flex and Grid can easily adjust when the window is resized. With the use of min-width / min-height and min() function, you can adjust the size the item can expand to or shrink to. Media queries enables you to redesign the page for different sets of screen sizes and even orientation (very useful for mobile devices). You can create the perfect webpage for each phone. 'px', 'in', 'ch', 'mm', 'cm', etc. is fixed. The properties defined for an element with such units never change for different screen sizes. But for units like '%', 'vw', 'dvh', they adjust when the window is resized which is great for responsiveness.

    Marked as helpful
  • Anis Bacha•630
    @AnisBacha
    Posted over 1 year ago

    Hey, Good job for getting the desktop design done ! I noticed in the 'style.css' file that you started with the desktop design and then used media queries to adjust it for mobile, but it is recommended to first start your work with the mobile design and then try to adjust it to be a desktop design. This will save a lot of time in projects like this. You can look up 'mobile first design' for more information.

    Also, like Johan mentioned, you'll need two separate navbars – one for the desktop view and one for the mobile view. To get it right, you might want to use some JavaScript to detect the window width and switch between the mobile and desktop navbars accordingly. Keep up the good work!

    Marked as helpful
  • Johan•200
    @CallensJ
    Posted over 1 year ago

    Hello, adding a global container at the beginning will prevent to manipulate the <body> directly. As for the responsive navbar you only wrote one navbar. this is not a responsive navbar who goes at the right side on mobile. this is two differents navbars. one for desktop one for mobile. you have to make some part disappear depending on what layout you are. im guessing its possible make one entirely responsive but....wow... As for the main content... Grid is life.. grid is absolute.. grid is everything ^_^

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

Oops! 😬

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

Log in with GitHub