Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

news homepage

Raphael Nnadi•300
@raphaelnnadi
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I cannot seem to get my nav-toggle to work. Please help me

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Obiora Emmanuel•350
    @Emmanuel-obiora
    Posted over 2 years ago

    Good day. For your toggle button you can create a function that reveals or hides the navigation using pre-defined CSS property. First you will need to change the flow of your nav menu to vertical and adjust it to the right using CSS. second set the display of the nav className to

    nav{
    display: none;
    }
    

    then create a class element within your style sheet, i.e

    .reveal-nav{
    display: flex; **depending on what you used**
    }
    

    Once the above is completed, you will move over to JavaScript. you can use the code as follow.

    const Navigation = () => {
    const show = document.getElementById('input-the-html-tag-you-set-to-none-here');
    
    show.classList.add('reveal-nav');
    }
    

    Then to hide the nav bar you use the reversal of what was written above

    const HideNav = () => {
    const show = document.getElementById('input-the-html-tag-you-set-to-none-here');
    
    show.classList.remove('reveal-nav');
    }
    

    Finally add the onClick={HideNav} as the case maybe to the elements performing the functions. once the above is implemented your code should be working fine. But you will also need to create a background modal. add a div tag to your code and give it an id, then add the following CSS properties

    .modal{
    display: block;
    width: 100%;
    height: 100vh;
    top: 0;
    left: 0;
    right: 0;
    bottom: 0;
    }
    

    However, you will need to call up the modal when showing and hiding the navigation bar. Just add the following to the functions above.

    const Navigation = () => {
    const show = document.getElementById('input-the-html-tag-you-set-to-none-here');
    const modal = document.getElementById('add-modal-id-here');
    
    show.classList.add('reveal-nav');
    modal.classList.add('modal');
    }
    

    And on close add the new lines.

    const HideNav = () => {
    const show = document.getElementById('input-the-html-tag-you-set-to-none-here');
    const modal = document.getElementById('add-modal-id-here');
    
    show.classList.remove('reveal-nav');
    modal.classList.remove('modal');
    }
    

    This is a basic JavaScript function, I hope this helps in resolving your bug

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub