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

Blog preview card

Lyna•260
@lynaIFR
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'm pretty proud of how the project came out, if you have any feedback, please feel free to share.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Roberts P•120
    @indaqoo
    Posted about 1 year ago

    Hi @lynaIFR,

    Looking at the HTML, I noticed you are styling elements using IDs ( # ). This is not ideal.

    IDs have a higher specificity compared to classes. This can make it harder to override styles later, as you would need to use even more specific selectors.

    IDs are often used in JavaScript for element selection and manipulation.

    Classes are reusable across multiple elements, whereas an ID is supposed to be unique within a document.

    Using height: 100vh on .container might not be the best approach. It is best to set height of html and body tag:

    html,
    body {
        height: 100%;
    }
    

    The .container class is intended to wrap your main content, centering it both vertically and/or horizontally within the viewport. Here’s an example of how to use it correctly ( based on mobile first approach).

    .container {
        max-width: 90%;
        margin-inline: auto;
    }
    
    @media only screen and (min-width: 425px) {
        .container {
            max-width: 100%;
            margin-inline: unset;
        }
    }
    
    <body>
        <main class="container">
            <article class="article">crazy content</article>
        </main>
    </body>
    
    

    At the moment there are no media queries to handle different screen sizes, which makes the design less adaptable to various devices.

    Project looks good on desktop size but that cannot be said about mobile versions - view images

    You should consider a "mobile-first" approach. You can also check out my project on article cards where I implemented this approach.

    Have a look at Kevin Powell's responsive web design video: youtube

    Overall great job, keep it up.

    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