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

Responsive blog preview card with CSS flexbox

Marvelous Edwards•70
@Marvyeddy
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Check this out and give your honest comments.. thank you

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marvelous Edwards•70
    @Marvyeddy
    Posted over 1 year ago

    Thanks

  • Pierce Issah•120
    @PJIceskull
    Posted over 1 year ago

    Hey Edward, you did a pretty good job recreating the design! I like that you went out of your way to recreate the header image using SVG. You were very close to nailing it but you missed a few design elements.

    Font

    • First off, the font for your solution should be Figtree as stated in the style guide.
    • The links for these fonts can be found in the source files you downloaded.
    • You can find the files either locally in the assets folder or import them using Google Fonts.

    Learning Button

    • A nitpick but I think you should add more padding in your learning button.

    Paragraph Text

    • Your h1 and .date text seem to have the same fontweight. If you look at the design closely you see that h1 is much more bolder than the rest of the text.

    Box Shadow

    • You were close to getting this but the trick for your box shadow is that the blur value should be zero. For Example:
    .container {
        box-shadow: 10px 10px 0px rgba(0,0,0,1);
    }
    

    The third value holds the blur value and if you set that value to 0, you'll get a flat shape.

    Hover State You were very close to getting the hover state right but you're missing an element. Where you hover over the card, the card's box shadow should increase! The change is simple as you have to add a :hover selector just like you did with your h1.

    .container:hover {
    }
    

    The only values you'll need to change are the x and y values of your box-shadow

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