I’d love some feedback on my product landing page project and some help with a few specific things.
When viewed on mobile my nav bar becomes a column, but it extends out of the header.
The centre yellow guitar image is a bit smaller than the other two, which is fine, but it means the price text “£400” isn’t always in line with the other prices on either side depending on your browser size.
The video is sometimes an odd shape. If I give it absolute dimensions, it looks wrong on mobile and falls off the edge of the screen. I’ve given it relative dimensions using vw, but now it seems to stretch to a strange ratio in some instances.
I wanted to use font awesome for some icons - do I need to sign up to get it to work as when I tried, nothing displayed.
There are probably other things that are wrong too or could be improved. It’s passed the test, but I’m not fully happy with it so please give some constructive feedback.
I tried a few things to fix the above problems and I was tempted to grind out another hour trying to fix these issues on my own but realised I need to get used to asking for help more. Any and all feedback is much appreciated.
I don’t have the time to debug all of your issues, but at least issue one:
Simply reduce the padding and font-size of the nav-links in your media query, also reduce the navigation height to 75% in there. That will make your mobile menu look better.
With just three links, you can actually align them in a row on mobile if you reduce the dimensions of the logo. For navigation links in a column hamburger menus are the better way.
Just to clarify here, you actually do need JS to make an accessible hamburger menu since HTML does not offer a native element to do this (the details/summary elements are unfortunately not good enough). These CSS-only menu examples work for people who can see the page, but they aren’t accessible for people who are listening to the page with a screen reader.
Please go ahead and use a CSS-only solution for now since you don’t have JS in your toolbox. I just wanted to let you know that it isn’t a complete accessible solution and you wouldn’t want to use a CSS-only solution in real production code.