Design comparison
Solution retrospective
-
What are you most proud of? I’m proud of creating a clean, responsive layout using Flexbox and integrating Google Fonts for a modern look. The project successfully met its goal of improving my front-end skills.
-
What would you do differently next time? Next time, I’d add subtle animations for interactivity, focus more on accessibility, and possibly use CSS Grid for more complex layouts. I’d also consider using SCSS or CSS variables to make styling more efficient.
Responsive design: Ensuring the layout looked good on different screen sizes required some adjustments.
What specific areas of your project would you like help with?Areas for Help Accessibility: Guidance on improving accessibility with ARIA roles and keyboard navigation.
Animations: Tips on implementing subtle hover effects and transitions.
CSS Optimization: Advice on using SCSS or organizing styles for better scalability.
Community feedback
- @StroudyPosted 2 months ago
Awesome job tackling this challenge! You’re doing amazing, and I wanted to share a couple of suggestions that might help refine your approach…
-
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. -
Having a clear and descriptive
alt
text for images is important because it helps people who use screen readers understand the content, making your site more accessible. It also improves SEO, as search engines usealt
text to understand the image's context, helping your site rank better, Check this out Write helpful Alt Text to describe images, -
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. -
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. -
For future project, You could downloading and host your own fonts using
@font-face
improves website performance by reducing external requests, provides more control over font usage, ensures consistency across browsers, enhances offline availability, and avoids potential issues if third-party font services become unavailable. Place to get .woff2 fonts
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@bonssssPosted 2 months agoOkay Thank you. am starting to develop my skills so if you have any resources that can help me you can share.
1@StroudyPosted 2 months agoHey @bonssss, Some of the links I shared above are some great resources to start with. Take your time it is now a race, You got this bro!
0 -
- @MikDra1Posted 2 months ago
If you want to make your card responsive with ease you can use this technique:
.card { width: 90%; max-width: 37.5rem; }
On the smaller screens card will be 90% of the parent (here body), but as soon as the card will be 37.5rem (600px) it will lock with this size.
Also to put the card in the center I advise you to use this code snippet:
.container { display: grid; place-items: center; }
Hope you found this comment helpful 💗💗💗
Good job and keep going 😁😊😉
Marked as helpful0 - @ronaldyonggiPosted 2 months ago
Looks good! I didn't see the part for mobile view in the CSS file, this can be something to be done as for the next steps.
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