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

Responsive Blog Card

bem
Bailey Frye•90
@baileyfrye1
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 completed this challenge as apart of the introductory learning path and had a lot of fun with it. I feel very confident in the accuracy of the sizing, and responsiveness of both the font-sizes and the width of the card itself.

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

I had no challenges with this, the area I spent the most time on was making sure the padding and margins lined up with the design.

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

I would be interested to hear everyone's ideas on how I went about the usage of CSS variables and my padding, margin, and gaps. Specifically how I went about spacing the body section of the card, although the layout doesn't change I used grid to be able to control the gap in between all of the elements to prevent myself from having to type margin-top: 0.75rem every time and as an alternate to using the :not(:last-child) selector. Not sure if this is a great practice or not. Thanks everyone!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Darkstar•1,420
    @DarkstarXDD
    Posted about 1 year ago
    • You don't need the layout to change in order to use flex or grid. It's common practice to use flex or grid in order to use the gap property. What you have done is correct and gives a clean result.
    • You should change the card width to be max-width. It won't be a deal breaker in this case but get into the practice of using max-width instead of the fixed width.

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

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.

Oops! 😬

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

Log in with GitHub