Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

Blog preview card component

Micah Sells•100
@Micahtron
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 mostly proud of how I was able to figure out more "recent" CSS stylings such as drop shadows, transformations, etc. on my own. I also wanted to get as close as I could to the design from eyeballing the visual image only, not extracting the numerical values from the Figma file.

I'm also pleased at how much faster I was able to complete this compared to previous micro projects / components.

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

The question was whether to nest the anchor tags inside their relative DOM elements, or place the DOM elements inside anchor tags. I decided to go with the latter because if this were a full-site design system or theme, there could easily be a case where h3 elements are NOT meant to also be hyperlinks and I didn't want the stylings to be tag-nesting dependent.

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

I used a fixed size since this is a card component. When it comes to responsive designs I'm good with full site and section layouts, but any micro changes to smaller in-page components are not as intuitive to me for some reason.

I would like to know if there's a way to make this (especially the text) slightly responsive without using a hard break point for elements other than the card body itself

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 Micah Sells'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.