Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Blog Preview Card with Media Query

Alex Blue•70
@fake-alex-blue
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 of how close I got to the original design. Next time I would have really liked to notice that the instructions ask you not to use a media query for mobiles. Oops. 🤦‍♀️

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

Probably the most challenging aspect of this was deciding on a semantic structure that could be re-used. You have to imagine that this is a template for other cards that will go next to it on a larger site. If that's the case, how do you make this code easy to reuse, for different articles etc.

Without another card to compare to, I think you sort of just have to make a best guess at what might change and what will stay the same, and that's all I've done here.

There's a school of thought that suggests you shouldn't do extra work before it's needed; so before you actually know what the requirements will be for a whole set of cards- don't spend too much time building out all the hooks and connection points. For all I know, the client might decide that all the other cards are rounded triangles, or that they all have an edge-to-edge video etc. 😋

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

To get a pixel perfect result, I think technically the 1px black border needs to be on the inside of the card element's width:384px and height:522px.

But, as the height of the element isn't set (to allow for user font sizes), I couldn't account for the line border thickness properly; so I'm ~2px too tall at default 100% zoom font-size:16px. What's the best way to overcome that?

Also, how would you refactor this to use a smaller font-size on mobile without using a media query. I reckon I could do it in JS, but I'm not 100% sure what the best practice would be for CSS alone. 🤔

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 Alex Blue'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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.