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

Blog preview card using Flexbox

Franklin Gomez•180
@frankgomezdev
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?

The two things I am most proud of are:

  1. I finished this faster than it would usually take me. Practice and repetition are key.
  2. I feel like this is one of my first solutions that is almost 99% identical to what the design file shows.

If I could do anything differently next time... I set most of the colors, font sizes, and styles after I was done getting the layouts and images correct and I would probably do this reverse in my next project.

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

My two biggest challenges were:

  1. Centering the blog card horizontally and vertically (surprise, surprise). I pulled up a blog post by Josh Comeau that wrote about how to center divs with different methods (using margin, flexbox, or CSS grid) and used the method that made the most sense to me.

  2. Getting that yellow box around the category "Learning". I used Google to find some solutions and landed upon one that worked for the blog card.

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

Specific areas I would like help with:

  1. Is my HTML structured properly and semantic? If not, how can I improve it?
  2. What improvements can I make on how I name my classes?
  3. Any improvements I can make to the CSS so that the attribution isn't so low on the page?

All advice and feeback is welcomed. Thanks in advance.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Laila Ben•270
    @Laila-front-dev
    Posted over 1 year ago

    your work is great keep this way, and this energy

  • Shameem•150
    @shameem-dev
    Posted over 1 year ago

    .

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

Oops! 😬

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

Log in with GitHub