Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Blog Preview Card By Yasin Zahir

pure-css
Yasin Zahir•40
@YasoJan
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?

I’m proud that I built this entire layout using mostly div tags and basic HTML/CSS without any advanced frameworks. It was a great exercise in layout structure and responsive design. If I were to do it again, I’d likely try to refactor using more semantic tags and maybe explore utility-first styling or component-driven architecture to clean up the structure and improve accessibility.

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

One of the biggest challenges was recreating the box-shadow and depth effect from the original design. The way the image and card cast overlapping shadows was tricky. I managed to overcome it by layering multiple divs using z-index and position: absolute to fake the stacking, which gave me more control over shadow layering. It wasn’t the cleanest solution, but it worked.

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

I’d really appreciate feedback on my use of box-shadowing. I had to manually layer divs and use positioning to achieve the look, and I’m curious if there are cleaner, more efficient ways to replicate that kind of multi-depth shadow styling. Would love tips on how to better approach that kind of design in a scalable or more semantic way.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Yasin Zahir's solution.

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.