Design comparison
Solution retrospective
Hi everyone.. I just submitted my 1st solution of 3-column-preview-card.
Any suggestions on how I can improve and optimise my skills are highly appreciated.
Thank you in Advance..
Community feedback
- @correlucasPosted about 2 years ago
👾Hello @rdghostmann, Congratulations on completing this challenge!
Great code and great solution! I’ve few suggestions for you that you can consider adding to your code:
- The html structure entirely with
div blocks
but these div doesn't any semantic meaning, for this reason is better you use a better html markup improving your code, for example for each vehicle card you use<article>
instead of the<div>
. - The icon doesn’t have an important role when you think about semantics and the html structure. So you can add
aria-hidden=“true”
to avoid it being found and read in the accessibility mode/screen readers. These are only decorative items. - Use
max-width: 100%
for the cards in the mobile version to allow the cards grow 100% of the width considering the paddings and avoid to have a lateral gap (limited by a fixed width). - Think about using relative units as
rem
orem
instead ofpx
to improve your performance by resizing fonts between different screens and devices. Anyhow, if we want a more accessible website, then we should use rem instead of px. REM does not just apply to font size, but to all sizes as well.
✌️ I hope this helps you and happy coding!
Marked as helpful1 - The html structure entirely with
- @VCaramesPosted about 2 years ago
Hey there!👋 Here are some suggestions to help improve your code:
-
The headings in your component are being used incorrectly. Since the <h1> Heading can only be used once, it is always given to the heading with the highest level of importance. This component has three headings of equal importance, so the best option would be to use an <h2> Heading, since it is reusable and it will give each heading the same level of importance.
-
Adjust the
padding
andfont-size
of the component as the screen size decrease to better accommodate the smaller screen size. -
At 375px, your component disappears. You will want to fix this.
If you have any questions or need further clarification, let me know.
Happy Coding! 👻🎃
Marked as helpful0 -
- @rdghostmannPosted about 2 years ago
Thank you @correlucas👾...@vcarames 😈 I have been distracted lately to submit my solution especially when am out of 🔋 . I was reviewing an article to understand min(), max() and clamp with KP and how to better use rem for my lenght value.
I have been educating myself to continue with other challenges
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