Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 10 months ago

Blog Preview Card Using BEM CSS Styling and Flexbox

bem
Peter•20
@skipperr254
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 was able to implement the BEM CSS styling method which I have never used before. Hope I implemented it the right way!

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

Probably trying to figure out the rem values for the various px values used in the project.

What specific areas of your project would you like help with?
  1. How was my implementation of BEM? Is that's how it's done or is there a better way I missed?
  2. Is using rem for the various sizes including the text-size, width, and border-radius the best way to scale the elements based on the screen size? Did I use the rem sizing the correct way?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alyfer Jacobsen•450
    @AlyferJT
    Posted 10 months ago

    Well, the view code page is going to 404, you changed the project name. But, congratulations!

    The thing about rem is root-em, he is a size unit based on the root value, since the default root value is 16px in most cases

    .5rem = 8px
    1rem = 16px
    2rem = 32px
    5rem = 80px
    And so on and so forth...
    

    but there is a trick that a lot of users use The 62.5% Font Size Trick I recommend you to search about it

    This trick is about setting the root default size to 62.5%. It's 62.5% of the default (16px) that is equal to 10px. They set then inside the html {}, like this:

    html {
          font-size: 62.5%;
    }
    

    That's how you set it Well, this bring us a lot of benefits, and i personally like to use it This helps us setting responsive fonts on the screen, since not all browsers uses the same font-size by default, and some users grow up the font to better see then, you could say that it brings us a help with the accessibility, actually this is a rem property, but you simplify the use with this 62.5% trick

    Anyway, when you set the 62.5%, this is the way you would use the rem:

    .5rem = 5px
    1rem = 10px
    2rem = 20px
    5rem = 50px
    And so on and so forth...
    

    Cool, right? You can clearly see how much px the rem will give That's a life savier Well, that's not all, this is the main idea about the trick But i recommend you to search about it, there is a lot about

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