Design comparison
SolutionDesign
Solution retrospective
What are you most proud of, and what would you do differently next time?
This challenge was more complex than the others but I was proud to think it through and get to a solution faster and with more quality then the other times.
What challenges did you encounter, and how did you overcome them?The design with the image at the top is something that I couldn't find a way to solve it just now. I tried a couple of things but the result was not good.
What specific areas of your project would you like help with?The image at the top for smaller screen sizes.
Community feedback
- @nayan041Posted about 1 month ago
Your design seems perfect to me. Great start to a long journey!
Marked as helpful0 - @grace-snowPosted about 1 month ago
Hey, the html looks good overall but I have a few pointers:
- emphasised text should be in a
strongtag. We don't really usebany more as that has no meaning and non-emphasis text is styled with css anyway. - the header cells in the table must be coded as header cells (
th) not data cells. That's really important. Without it, the table is inaccessible. - Those header cells should ideally also have
scope="row"to make it clear they are row headers and not column headers (which is the default). - it's going to be poorer for performance loading the css reset as a separate stylesheet. If possible, just include it at the start of your main stylesheet so you are only loading one asset.
0 - emphasised text should be in a
Please log in to post a comment
Log in with GitHub
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