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

Blog Preview Card - plain HTML and CSS using flexbox

RickLearnsToCode•20
@RickLearnsToCode
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 feel pretty good about how my 2nd challenge went. There were a few issues with spacing that I was able to figure out without the help of Copilot, and this was good practice with flexbox. I'm still not sure why my fonts don't look like the provided design image, and I am not sure how to adjust the font sizing for smaller screens without using media queries. Looking forward to seeing other solutions to this one.

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

I downloaded Figma so I could view the provided files, but really struggled to figure out how to use that tool. Ultimately I just used the .png files as my guide, but I need to spend a little time getting up to speed on Figma for future challenges.

I also initially struggled with flexbox to get the card elements aligned vertically until I realized I needed to use flex-direction: column. (Facepalm moment but a good learning experience)

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

The width of my card (or possibly my font sizes?) are not matching the example, so my excerpt text only takes up 2 lines instead of 3. I also notice the font weight of my title and the author name don't seem to be as bold/thick as the example. Not sure what I need to do there to fix it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Komal Jatoi•210
    @komaljatoi
    Posted 23 days ago

    Looks really good! One suggestion you could try for the font weight - instead of font-weight: bold, you could try font-weight: 800, which would make the title/author bolder.

    Marked as helpful

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, SASS, 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