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

BLOG PREVIEW CARD

Isaiah Williams•40
@Zayacode96
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I utilized some CSS variables for the main colors to make implementing the color design easier. Relatively easy project for my beginning skill level, although I drew a blank on some CSS properties like "font-style". I wrote "text-style" instead and was wondering why it didn't work. End up not using it after.

ALL IN ALL, check out my version and code. Would appreciate it. Thank you guys.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • abedzeidan•340
    @Abed001
    Posted over 1 year ago

    Hello good job, I know that there are a lot of comments here but there is also one thing to add which is the active state when the card hovers the shadow should become bigger you can use something like this resource: https://www.freecodecamp.org/news/css-box-shadow-property-with-examples/

    and also this is the code i have used : .cardshadow{ box-shadow: 10px 10px rgba(0,0,0);

    } .cardshadow:hover { box-shadow: 15px 15px rgba(0, 0, 0); /* Increase shadow size and opacity on hover */ } keep going!!

    Marked as helpful
  • Marcos Travaglini•6,210
    @Blackpachamame
    Posted over 1 year ago

    Greetings mate!

    I leave you the following comments that may help you improve your code:

    • Apply display: block to the image to remove that annoying white space
    • To center the content you can use grid in the body, as follows:
    body {
        width: 100vw;
        min-height: 100vh;
        box-sizing: border-box;
        font-family: 'Figtree', sans-serif;
        font-size: 18px;
        background-color: var(--primary);
        display: grid;
        place-content: center;
        gap: 20px; /* Leave a space between your article and your footer */
    }
    
    article {
        background-color: var(--white);
        width: 280px;
        height: 400px;
        /* margin: 110px auto; You don't need this anymore */
        padding: 1.5rem;
        border: 1px solid black;
        border-radius: 15px;
        box-shadow: 7px 8px 1px black;
    }
    
    Marked as helpful
  • P
    Daniel 🛸•44,810
    @danielmrz-dev
    Posted over 1 year ago

    Hello Isaiah!

    Your solution looks great!

    I have two suggestions for improvement:

    • First: For semantic reasons, replace your article with main. The tag article would make more sense if the card was part of a bigger website (and it certainly would in real world), but since it is all we have on the screen, you can use main.

    This tag change may have little or no visual impact but they make your HTML code more semantic and improve SEO optimization as well as the accessibility of your project.

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

    You can apply this to the body (in order to work properly, you can'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
  • Melvin Aguilar 🧑🏻‍💻•61,020
    @MelvinAguilar
    Posted over 1 year ago

    Hello there 👋. Good job on completing the challenge !

    I have other suggestions about your code that might interest you.

    • The <figure> tag should be used only when captions are required with <figcaption>. In this challenge, it is not required.
    • Use min-height: 100vh instead of height. Setting the height to 100vh may result in the component being cut off on smaller screens, such as a mobile phone in landscape orientation.

    • Using width: 100vw generates an unnecessary horizontal scrollbar on some screens. So you can remove it.

    I hope you find it useful! 😄 Above all, the solution you submitted is great!

    Happy coding!

  • turanarican•200
    @turanarican2022
    Posted over 1 year ago

    All the above comments make sense and I wanna add something. There is another value for min-height. It is 100svh instead of 100vh. It helps mobile devices to show all the content even while some of the screen is occupied with top bar of the browser. You can search YouTube for Kevin Powell's video on this.

    Happy coding!

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

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

Oops! 😬

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

Log in with GitHub