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

Blog preview card - Pure CSS

SMHN•200
@smhnfreelancer
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 used the Figma layout and I tried to do my best to match the result with the design.

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

Several challenges were kind of hard to achieve.

  1. I finally used width:66vw in the mobile screen size to make the whole card responsive in all sizes.
  2. I was pretty busy matching the width in the desktop screen size box-sizing:border-box fixed the issue.
  3. I used the exact font size and font properties, but my result was slightly different, so I set the desc class, font size to 17px; instead of 16px and got a better result.
What specific areas of your project would you like help with?

I think I need some help with the understanding difference between the results, even when you use the exact font and exact font-size and font properties. Also having a fully responsive card in all the mobile sizes made me to use 66vw as width of the card, but I think, there must be a better approach.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vadim Pospelov•40
    @VH135
    Posted over 1 year ago

    Hi there! Good effort on this chalenge.

    I see your desktop design excellent matches with the layout, congrats! Also you've added custom cursor pointer as shown in the layout, that's cool. And I like how you changed your styles to be more readable like this:

        <link
          rel="icon"
          type="image/png"
          sizes="32x32"
          href="./assets/images/favicon-32x32.png"
        />
    

    And there are some points woulbe great to improve:

    • Your mobile version of the card differs from the layout significantly.
    • Yours HTML classes like "tag" and "desc" are not informative. It woulbe be to name it like "card-tag", "card-desc", for example.
    • A couple of your lines of code starts with this symbol: >, it's not good in terms of readability.

    Hope you'll find this helpful.

    Marked as helpful
  • tgodo•50
    @tobiekwe
    Posted over 1 year ago

    What I can say is this is super cool effort as I am still finding my level.

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