Design comparison
Solution retrospective
I am proud of my semantic html, involving researching the different elements and how they should be used, such as the section tags and also the article tag for the recipe.
I am also proud of my ability to make the design responsive, where it switches from the desktop/mobile view with the use of media queries.
I believe the end result is pretty good and matches the figma design.
What challenges did you encounter, and how did you overcome them?I encountered challenges with the various padding and spacing within elements, such as between the bullet point on the lists and the list item, having to add classes in order to achieve the right spacing as per the figma file.
What specific areas of your project would you like help with?I would like some feedback on both my semantic HTML and also the responsive element of my design. Should I be using pixels for media queries and have I done it in the right way? What other changes should I make to have this as responsive as possible?
Community feedback
- @kaamiikPosted about 1 month ago
Hi good job. I have noticed some points I wanna mention:
- On the mobile view add a margin-top, left and right to have a space from the edge of the page.
- This page does not need any
header
and header should not be inside themain
. We haveheader
,main
andfooter
and these are siblings. - You can simply put your text inside
li
. There is no need to usespan
unless there is a styled text. - On CSS try to use a better CSS reset. Andy Bell's good.
- Never ever use
px
for font-size. Only userem
s. https://fedmentor.dev/posts/font-size-px/ - Also for width and heigh also use rems and for spacing you can use
em
too. - You don't need and you should not use width and height to limit your card. It's not good for the page if your content change. On height you only need
min-height: 100vh;
most of the time andmax-width:[...]rem
0@marcus-hillPosted about 1 month agoHi @kaamiik, thanks for taking the time to review my work.
- The design files do not show any space from the edge of the page on a mobile view, so I deliberately left none and started designing it for mobile first, before later adding the margin for desktop and tablets.
- Thanks for the feedback on the header, I didn't realise this had to be separate to the
main
element so I have removed it and replaced it with adiv
instead. - The reason I used
span
was because I was struggling to apply the margin-left to theli
, and several websites suggested nesting aspan
inside theli
in order to achieve this, as I was trying to match the figma design spacing. Would this have been possible without thespan
as it was not working for me? - Thanks for suggesting a different reset.css, I've made the necessary changes to Andy Bell's.
- I've changed all
px
's torem
's for font sizes. Thanks for linking to the article, I can see how this will impact accessibility now. - Noted
- I've checked over my code and I don't think I am using width or height to limit the card, I was already using
min-height: 100vh
andmax-width: 42rem
on the card inside the media query, so I will assume this has been done the correct way. I was using width on the banner and also a few other elements inside the card.
Thanks so much again for your feedback, it is much appreciated and helping me to improve!
0@kaamiikPosted about 1 month ago-
Yes you are right but still on the size between 600px to 678px needs a margin inline to have some little space from the edges.
-
Yes you are right.
-
Yes. It's ok completely. I thought that your .banner class is a text wrapper. @marcus-hill
0@marcus-hillPosted about 1 month agoHi @kaamiik, thanks for this feedback. I know what you mean now with the requirement for a margin between 600px and 678px so I have added one with a size of
2rem
.I appreciate your help!
1 - @AndresLamarPosted about 1 month ago
Hey, everything seems good in terms of HTML semantic and responsiveness of your solution
0
Please log in to post a comment
Log in with GitHubJoin 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