Any suggestions with my Technical Page

I just finished it and it only gives me an error when resizing it from small to large that the NAV does not appear. until update.

here is my work.
https://codepen.io/gabrielrip/pen/xxRapXK

Your page looks good @GabrilRIP. Some things to revisit;

  • Keep the test script when forking the pen (<script src="https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js"></script>)
    • The test script, with all tests passing, should be included when you submit your projects.
    • Your page passes 15/16 user stories. Click the red button to see which test(s) are failing and text to help you correct the issue.
    • Be sure and read more than just the first line of the failing message. The ability to read and comprehend error messages is a skill you’ll need to acquire as a developer. Ask questions on what you don’t understand.
  • Codepen provides the boilerplate for you. It only expects the code you’d put within the body element in the HTML editor. (No need to include the body tags). For anything you want to add to the <head> element click on the ‘Settings’ button, then HTML and add it into the ‘Stuff for <head>’ box.
    • For instance links to fonts go in the box labeled ‘Stuff for <head>’
  • Do not use the <br> element to force line breaks or spacing. That’s what CSS is for.
    • Reference MDN Docs
    • You can nest multi-line <code> snippets in <pre> </pre> tags in HTML to preserve whitespace and line breaks.
      Or skip the pre element and do the following in CSS;
      code {
        white-space: pre-line;
      }

If you’re saying that the test fails when the screen is small it’s not an issue. The instructions say, “On regular sized devices (laptops, desktops), the element with id="navbar" should be shown on the left side of the screen and should always be visible to the user.

A smaller screen is not a regular sized device.

Btw, when you add the test script, this is not the test that is failing. You need to correct the failing test.

On a side note, since you’re asking for feedback I’m moving this to the more appropriate #project-feedback subforum to get more eyes-on.