Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 3 months ago

figma, vscode, chrome.

Monica Nkiri•90
@Luwisky
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • KumaKorin•180
    @KumaKorin
    Posted 3 months ago

    1. Semantic HTML

    • But, did you know there’s no such thing as <h7> in HTML? 🤔 Maybe consider using a <span> or <p> instead and style it with CSS. Using proper semantic tags is super important for accessibility and SEO!

    2. Accessibility

    • Good stuff: Your design is clean and easy to understand, yay! 🎉
    • Improvements:
      1. Alt for images: Don't forget to add alt attributes to your images in HTML! It helps screen readers understand what the image is about.
      2. Focus states: You added a hover effect on .component (which is awesome, by the way 😄), but what about keyboard users? Maybe you could add a similar :focus state for better accessibility!

    3. Responsiveness

    • I love that you added a media query for screens under 500px! It’s so nice to see that .component shrinks to 90% width and the profile image adjusts too. 🌟
    • But, um, what about larger screens (like desktops)? Maybe you could think about adding styles for screens wider than 1200px to make it look even better on big monitors! 🖥️

    4. Code Structure

    • Your CSS looks neat and organized! The class names are super clear, so it’s easy to guess what they’re doing. Nice job! 🥳
    • But… I noticed a few repetitive rules, like margin-left: auto; margin-right: auto;. Maybe you could move those into a reusable class or a parent container? It’ll save you some work later!
    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