Design comparison
Solution retrospective
I’m most proud of completing this project and creating a clean, responsive blog preview card using HTML and CSS. The design closely follows the Frontend Mentor challenge specifications, and I implemented a well-structured layout with great attention to detail in terms of spacing, typography, and responsiveness across different devices. The component-based structure is easy to maintain and update.
Next time, I would focus more on optimizing the CSS by exploring CSS Grid more thoroughly to handle layout control better.
What challenges did you encounter, and how did you overcome them?Challenges encountered:
One of the main challenges I encountered was ensuring the blog preview card remained fully responsive across different screen sizes. Balancing the layout and typography to look good on both small mobile screens and larger desktops required careful use of CSS Flexbox. Another challenge was working with the design's spacing and alignment to ensure it matched the Frontend Mentor specifications precisely, which sometimes meant fine-tuning padding and margin values.
How I overcame them:
To overcome the responsiveness issue, I leveraged CSS media queries and Flexbox properties to adjust the layout dynamically for different devices. Testing the design on various screen sizes helped refine the responsiveness. For alignment and spacing, I broke down the layout into smaller components and used browser developer tools to inspect and adjust the design iteratively. These tools allowed me to fine-tune elements until they aligned perfectly with the challenge's requirements.
What specific areas of your project would you like help with?I would like help with further optimizing the layout, particularly in refining the CSS to ensure a smoother, more consistent design across all screen sizes. I’d also appreciate guidance on how to improve the project’s overall performance, such as using best practices for image optimization and lazy loading. Additionally, I’m interested in learning how to incorporate more advanced CSS techniques, such as animations or transitions, to enhance user interaction and engagement. Feedback on making the codebase more modular and maintainable would also be valuable.
Community feedback
- @AdrianoEscarabotePosted about 1 month ago
Hi Manuel, hope you're doing well! I loved how your project turned out, but I’ve got a few suggestions that could be useful:
images must have alt text unless it is a decorative image, for any decorative image each IMG tag must have empty alt="" and add aria-hidden="true" attributes to make all the assistive technologies of the Web, as screen reader.
A tip for when the challenge is just one component and the page needs an
h1
, you can add the class:sr-only
:<h1 class="sr-only">Blog Post Overview</h1>
class:
.sr-only { position: absolute; width: 1px; height: 1px; padding: 0; margin: -1px; overflow: hidden; clip: rect(0, 0, 0, 0); white-space: nowrap; border-width: 0; }
By doing this you will have an h1 visible only to page readers!
Learn the differences between decorative/meaningless images vs important content.
The rest is fantastic.
Hopefully, you'll find it helpful. 👍
Marked as helpful0@Manuel7070Posted about 1 month agoThanks @AdrianoEscarabote for the helpful suggestions; let me implement them now.
0@Manuel7070Posted about 1 month ago@AdrianoEscarabote I wanted to confirm whether I should convert the width, height, and margin from pixels (px) to rem units. I plan to do this by dividing each pixel value by 16 to calculate the equivalent rem value accurately.
This is because all my values are in rem instead of px.
0 - @Ejiro-FrancesPosted about 1 month ago
The code is well structured, readable and reusable.
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