Design comparison
Solution retrospective
Any tips to improve are welcomed, especially for the mobile version and thanks
Community feedback
- @CodeWithAlaminPosted almost 2 years ago
Hi Yassine Boukhlaπ Great job on completing this challenge! π₯³
I would like to share a few suggestions on this solution if you don't mind.
HTML Suggestions:
- Instead of using a
div
element to wrap the preview cards, you could use a more semantic element such as asection
element to represent a section of the page. - Consider using the
alt
attribute for theimg
elements to provide a text alternative for the images. This is especially important for users with visual impairments who rely on screen readers to access your website.
CSS Suggestions:
- You can use the
font-weight
property in thefont-family
property value to specify the font weight, instead of using a separatefont-weight
property. For example:font-family: "Lexend Deca", sans-serif; font-weight: 400;
can be written asfont-family: "Lexend Deca", sans-serif 400;
. - Consider using CSS variables (also known as "custom properties") to store values that you use repeatedly throughout your styles. This can make it easier to maintain and update your styles. For example, you could define a variable for your primary color and use it throughout your styles like this:
:root { --primary-color: hsl(31, 77%, 52%); } .container-sedans { background-color: var(--primary-color); } .container-btn-sedans { color: var(--primary-color); }
- You can use the
:not
pseudo-class to specify styles for elements that do not match a particular condition. For example, you could usebutton:not(:hover)
to select all buttons that are not being hovered over. This can be useful for writing more concise and maintainable styles.
For more information about these topics, you can check out the following resources:
- HTML
section
element - HTML
alt
attribute - CSS
font-family
property - CSS custom properties
- CSS
:not
pseudo-class
Overall, this is a very well done solution to the challenge. Great job!
I hope this feedback was helpful. π Keep up the good work!π
Marked as helpful0@yassineboukhlaPosted almost 2 years ago@CodePapa360 Hi, Thank you for your answer, really helpful.
0 - Instead of using a
- @VCaramesPosted almost 2 years ago
Hey there! π Here are some suggestions to help improve your code:
Regarding your question,
Implement a "Mobile First" approach π± > π₯
Mobile devices are now the dominant π way in which people browse the web, it is critical that your website/content looks perfect on all mobile devices.
More Info: π
- Your
CSS Reset
is being underutilized. π’ To fully maximize π― it, you will want to add more to it.
Here are some examples that you can freely use:
- For improved accessibility π for your content, it is best practice to use
rem
for yourfont-size
and other property values. Whileem
is best formedia-queries
. Using these units gives users the ability to scale elements up and down, relative to a set value.
- Along with the blank
alt tag
, you also want to include thearia-hidden=βtrueβ
β οΈ to your βcar images/iconsβ to fully remove them from assistive technology.
More Info:π
[MDN Aria-Hidden] (https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-hidden#description)
- 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 anh2
heading β since it is reusable and it will give each heading the same level of importance.
- Your "buttons" were created with the incorrect element β. When the user clicks on the button they should be directed to a different part of you site. The
anchor tag
}will achieve this.
More Info:π
If you have any questions or need further clarification, feel free to reach out to me.
Happy Coding! πππͺ
Marked as helpful0@yassineboukhlaPosted almost 2 years ago@vcarames Thank you for the answer, really appreciate your help.
0 - Your
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