
Solution retrospective
This one is kinda tricky, because I had to search how to do it and then do it my way because I built the html differently than other tutorials.
Next time, I would like to build it myself with my own way of thinking
What challenges did you encounter, and how did you overcome them?i was originaly gonna do everything with js, but that was the hardest way because of the way I built the html, so I did some changes in the UI in css and the dislay changed in JS which was the easiest way to do it
What specific areas of your project would you like help with?It's not perfect so If you have a better way tell me!
Please log in to post a comment
Log in with GitHubCommunity feedback
- @Alex-Archer-I
Hi!
There no need in this work to use
header
andnav
tags. Those tags have a specific semantic meanings - they represent a top part of the site which is the same for all it's pages.nav
in turn should contain navigation menu and nothing else. This project doesn't have all that =)And that is why
header
andmain
should be a sibling tags.The
box-shadow
property have a very wide browser support now - more than 98%. So, you don't have to add vendor prefix for it.Oh, and you have a few extra constants in your code. Guess you planned more complex algorithm initially =)
Overall you've done quite a neat work, keep doing =)
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