Order summary component

Solution retrospective
What I have learned / practised in this project:
- box shadow
- the solution is sometimes not that hard (I've first set the background-picture with pseudo-elements, but it was just a simply background image...)
What was difficult?
- I find it sometimes difficult to know what html element that i could use, for example: The price and type of the plan (annual plan/$59.99 ) I was in doubt about using a p or an ul.
Please log in to post a comment
Log in with GitHubCommunity feedback
- @grace-snow
Hi, I hope this feedback helps
- There should be some space aroubd the card at all times. This is hitting my screen edges. You could add a little margin to the component or a little padding to its wrapper
- This is one component, meaning it is only one chunk of meaningful content. It cannot have a header element (that is a banner landmark on a page that should sit outside of main and it's purpose if for content that repeats on every page). And it should not have a section inside. This whole card could be one section if you wanted but there is no semantic benefits to doing that
- not necessarily a problem but can you explain why you've chosen the interactive elements you have done for change, proceed and cancel? What do you expect to happen on click of each of these? Do you understand the key differences between anchors and buttons, and when each should be used?
- you don't need a paragraph inside a button (I'm not even sure that would be valid html tbh)
- CSS looks good to me. The only things if consider changing are the inline-margins in the plan box. Id recommend using gap there and flex-grow on the middle item. I'd also consider adding in flex wrap as a defensive style for if/when text sizes are enlarged and the content may not fit on one line'.
- consider setting the max width in rem instead of pixels on the component
- consider making the top image width 100% instead of setting explicit px width in a media query
Marked as helpful - @faisalahmed11
@Thewatcher13, your submission is greatly appreciated, and you are right on the learning progress, that reduces the difficulty level. and finally, I would say <p> tag is the clear winner and an easy way to go in this situation.
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