FYI, I did the W3C Validation and the main issue that popped up was warnings of no headings (h1-h6 and so forth). I ignored these warnings due to the user story not specifying header use. Other than these warnings, no other errors found :).
The project looks nice. Here are a few suggestions.
Add this code to your CSS:
:root{scroll-behavior: smooth;}
This is a neat trick that makes it so the navigation bar doesnât instantly jump, but rather transitions. If this isnât working, use #navbar instead of :root .
For your anchor tags, try changing the text to black instead of the default blue. Then give it a smooth transition that scales the text with a shadow when you hover over it.
Thank you so much for the feedback! Your suggestions for the navbar definitely added a more aesthetically pleasing affect - I will keep this in mind for future projects.
I would also apply that same scroll bar hiding code to the #navbar ul on line 60 of your CSS when the screen changes. Then edit the media on 139 to prevent it from popping it up again.
The code I mentioned above still allows for scrolling but hides the scrollbar. Double scroll bars on smaller screens may be too much. On smaller screens, the user uses touch screen to navigate and not the scroll bars. You can keep the overall scroll bar for the entire page if youâd like, but avoid double scroll bars. I would hide the overall navigation bar on smaller screens (far right of screen) on smaller screens, (use :root to target this). You can keep it on bigger screens because bigger screens are desktops, where users can use a scroll bar.
You could also add:
box-shadow: 2px 2px 5px black to your #navbar (CSS - 11) in order to make it pop from the rest of the page. This can attract user attention to show it is important. You may need to remove your border-right in order to make this look better with the box shadow.
I personally use box-shadow on all my navigation bars, especially the desktop versions that are attached (fixed) to the top of the page. This adds a nice divide between the content on the main flow of the page and the fixed content in the navbar.
Your page looks good @bbs2527. Some things to revisit;
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>â
There are coding errors you should be aware of and address.
overflow-x: hidden; will completely hide anything that extends outside its container element horizontally. Itâs recommended to not do this, and refactor your CSS to be more responsive - otherwise it is possible for your site to appear to be missing content.
Do not use the <br> element to force line breaks or spacing. Thatâs what CSS is for.
Thanks for the feedback and suggestions! I made sure to clean up my code, adjusted the errors for css (forgot about that part). and I made some design adjustments and hopefully it should be okay :). I also removed the break and it seems to flow okay in the document. I also hid the nav bar for smaller screens and it does seem to flow better.