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

Blog Preview Card Solution

Jon D•190
@jcad57
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


As a newbie i'm sure there are better solutions. I'm really interested in clean code - if you have any suggestions that could clean this code up - or alternative ways to code in general like utilizing grid or flexbox, etc.

Also, I'm not sure how to keep the footer at the bottom when I turn the card into display:absolute. That lifts it off the page and everything below it goes to the top. So I didn't mess with that much.

Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marley Semende•570
    @Marley-Semende
    Posted over 1 year ago

    Hi @jcad57. You can solve the footer issue by using flexbox to layout your page. for exampl if you get rid of the position absolute properties your code would look like this :

    display: flex;
        justify-content: center;
        align-items: center;
        flex-direction: column;
        min-height: 100vh;
    }
    

    I've removed the position: absolute and top, right properties and the 92% width on the card and just stuck to a body width of 100vw;. Margin-right of -50% is also affecting the placement of your card, I'd just stick to the above highlighted display: flex for placement. The transform translate property is also affecting your placement, I'd also get rid of it and stick with just display: flex for the card placement and by removing those properties and using flexbox you will get your desired results. I hope this helps. Let me know if anything is unclear.

    Marked as helpful
  • P
    Daniel 🛸•44,790
    @danielmrz-dev
    Posted over 1 year ago

    Hello @jcad57!

    Your project looks great!

    I noticed that you used position to place the card in the middle of the page. Here's a very efficient (and better) way to center the card:

    • Apply this to the body (in order to work properly, don't use position or margins):
    body {
        min-height: 100vh;
        display: flex;
        justify-content: center;
        align-items: center;
    }
    

    I hope it helps!

    Other than that, great job!

    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

Oops! 😬

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

Log in with GitHub