Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 10 days ago

Blog Preview Card - semantic HTML, modern CSS layout techniques.

Oscar Echenique D.•80
@OscarE2D
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

’m most proud of how I implemented a fully responsive design using Flexbox and CSS Grid, which allowed the blog preview card to adapt seamlessly across different screen sizes and devices. I also took care to use semantic HTML5 elements to improve accessibility and maintain a clean structure. Additionally, I’m happy with how I used CSS transitions and pseudo-classes like :hover and :focus to create smooth interactive effects that enhance the user experience.

If I were to do this project again, I would spend more time organizing my CSS code to follow best practices and improve maintainability. Also, I’d like to deepen my understanding of CSS animations, transformations, and pseudo-classes to create even more engaging interactions.

What challenges did you encounter, and how did you overcome them?

One challenge was mastering the clamp() function to create fluid and scalable typography and element sizing. I overcame this by breaking down the calculations and adapting existing formulas to fit the project’s needs, which helped me gain a better grasp of fluid design techniques.

Another challenge was ensuring fonts were imported correctly from local sources instead of relying on external links. This required me to learn the correct CSS structure for font imports, which ultimately improved the project’s independence and performance

What specific areas of your project would you like help with?

I would appreciate help or resources on best practices for organizing CSS code more efficiently. Also, guidance on advanced CSS pseudo-classes, animations, and transformations would be very valuable as I aim to deepen my skills and create more dynamic UI interactions.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•3,270
    @thisisharsh7
    Posted 10 days ago

    Great job! Here’s some feedback to help you improve:

    What’s Working Well:

    • ✅ Excellent use of Flexbox and CSS Grid for responsiveness.
    • ✅ Semantic HTML structure enhances accessibility.
    • ✅ Smart use of clamp() for fluid typography – very modern!

    Suggestions for Improvement:

    • 🔄 Consider grouping your CSS logically using sections or comments like /* Typography */, /* Layout */, etc. for better maintainability.
    • 🧱 The CSS file is robust but could benefit from utility classes or even a CSS methodology like BEM for scalability.
    • 🎯 The main is height: 100vh, which could cause issues on smaller screens. Maybe switch to min-height: 100vh.
    • 🎨 Add cursor: pointer to interactive elements like .card-container to indicate interactivity.
    • 🎥 Explore transform, scale(), and keyframe @animations to enhance interactions further.

    💡 Tip: To level up your CSS skills, check out CSS TRICKS.

    Overall, you’ve built a solid foundation — with a few tweaks and deeper animation skills, this project could shine even more!

  • Javeria-kanwal•20
    @Javeria-kanwal
    Posted 10 days ago

    I'm really impressed with how you’ve approached responsiveness using Flexbox and Grid — it’s clear you’re building a strong foundation. Your use of semantic HTML and attention to accessibility is also commendable, as it shows long-term thinking.

    I like that you experimented with clamp() and local font imports — both can be tricky at first, but you handled them well and learned from the process.

    For next time, organizing your CSS and diving deeper into animations/pseudo-classes is a great focus. I’d suggest looking into methodologies like BEM or using tools like Sass for structure, and maybe checking out resources like CSS Tricks or MDN Web Docs for more advanced styling techniques.

Join 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
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub