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

Simple blog preview using flexbox

elliot•30
@e-liasz
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 am the most proud of using flexbox properly and getting my card to look as close to the original design as possible. I am also getting the hang of rem values rather than px and I want to continue on practicing those. I believe padding is still a bit of a challenge for me as this is not perfect on the project yet (particularly the bottom padding seems too big?).

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

Rounding the corners right on the top image was a bit of a struggle since the padding and border-radius were not working together as I wanted them to, but I overcame that. The top "learning" tag also proved to be a bit tricky, but I figured it out by just getting rid of a small part of the HTML that was actually unhelpful!

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

Tips on getting the padding values as close to the design as possible are very welcome. I also want to work on organizing my code in a neater way, so if anyone has feedback on that I would love to hear!

I would also really like to work on responsiveness and mobile design more.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • JacobKnittle•110
    @JacobKnittle
    Posted about 1 year ago

    Get more familiar with figma using the alt button on the elements and it will tell you the exact padding.

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.

Oops! 😬

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

Log in with GitHub