Design comparison
Solution retrospective
I'm proud to have found a good solution that looks similar to the original. Next time I want to finish a little bit earlier. Due to all new things I have to read and learn about Git, GitHub and so on it took a lot of time.
Next time I think I will also create a .css file.
What challenges did you encounter, and how did you overcome them?Centering the Component was really difficult to me. First I set the height wrong (in "%" than in "vH" ). As I found the solution by looking some other solutions, I was satisfied. Also the display: flex is really nice to center elements.
What specific areas of your project would you like help with?I am not sure how to move the words/ paragraph into the correct position without using a tag and reduce the font-size.
Community feedback
- @StroudyPosted 2 months ago
Amazing job with this! You’re making fantastic progress. Here are some small tweaks that might take your solution to the next level…
-
Using legible font sizes is important because text smaller than 12px can be hard to read, especially on mobile devices, forcing users to zoom in. Aim for more than 60% of your text to be at least 12px or larger. This improves readability, user experience, and accessibility for all visitors.
-
This does not matter that much at this stage but something to be mindful of for SEO(Search Engine Optimisation),
<meta>
description tag missing. -
Using a
<main>
tag inside the<body>
of your HTML is a best practice because it clearly identifies the main content of your page. This helps with accessibility and improves how search engines understand your content. -
Using
max-width: 100%
ormin-width: 100%
is more responsive than justwidth: 100%
because they allow elements to adjust better to different screen sizes. To learn more, check out this article: responsive-meaning. -
Developers should avoid using pixels (
px
) because they are a fixed size and don't scale well on different devices. Instead, userem
orem
, which are relative units that adjust based on user settings, making your design more flexible, responsive, and accessible. For more information check out this, Why font-size must NEVER be in pixels or this video by Kevin Powell CSS em and rem explained.- Another great resource for px to rem converter. -
Avoid using
id
selectors for styling in CSS because they are too specific and hard to override, making your styles less flexible and maintainable. Instead, use class selectors (.
), which are reusable and more manageable, allowing for better control over your styles and easier updates.
You’re doing fantastic! I hope these tips help you as you continue your coding journey. Stay curious and keep experimenting—every challenge is an opportunity to learn. Have fun, and keep coding with confidence! 🌟
Marked as helpful0@47tropfenPosted 2 months ago@Stroudy
Thanks for your tips. They are very well explained and in detail so I can understand them easily :-)
I will try to use them soon.
1@StroudyPosted 2 months ago@47tropfen, I’m thrilled you’re finding this advice helpful! You’re doing an amazing job, so keep up the hard work. Remember, every line of code is a step closer to mastery. Stay motivated and keep coding! 🎉
Marked as helpful0 -
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