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

Blog preview card with cursor interactability

emeraldknytt•90
@emeraldknytt
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 am quite content with how close my solution is to the design and if I had to do something differently, then it would be making sure that properties that are the same across different tags are given their own tags i.e

h1, p, .card {
   color: blue;
}
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Teodor Jenkler•4,040
    @TedJenkler
    Posted 11 months ago

    Hi @emeraldknytt,

    Nice project! I noticed a couple of things that could be improved:

    Semantic HTML: Instead of using multiple <div> elements, you should consider using semantic HTML. For instance, your card could be wrapped in a <main> tag, and you could purge most of the unnecessary <div>s. Using Flexbox with flex-direction: column inside the card would give you a cleaner design and improve readability, SEO, and accessibility.

    Heading Usage: The <h1> tag is meant for page titles and should be used only once per page. While you’ve correctly used it just once here, in smaller projects or components like this, you can skip using <h1> and go with an <h2> instead. If you had multiple cards on the same page, using several <h1> tags would violate the one <h1> rule.

    Use of <time>: When displaying a time element, consider using the <time> tag to further improve accessibility and readability.

    Keep up the great work!

    Best, Teodor

    Marked as helpful
  • Mateusz•440
    @MatPawluk
    Posted 11 months ago

    Great job! 😊 Here are a few suggestions to improve your code:

    The settings width: auto and height: 960px are generally correct, but it's worth considering responsiveness. You might want to use relative units (e.g., vh for height) or media queries to adjust the height for different screen sizes.

    The styling of the element with an id in CSS (#description) is valid, but it's worth noting that id selectors have higher specificity than classes. This means that if you need to override the style for this element in the future, styling with id may be harder to modify. Instead of using id, consider using a class.

    The HTML structure is correct and well-organized. However, it’s advisable to add alt attributes to all images to enhance accessibility.

    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

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