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

blog preview card with css and html

Luka•180
@zmora2622
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What specific areas of your project would you like help with?

Any advice on responsiveness and the code itself and how to improve it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted 11 months ago

    Hi,

    Well done on remembering to include the link in this, so many people forget that!

    Here are a few suggestions from your code:

    • Really the link should be inside the heading, not the other way around.
    • This would never act as a page title once the component is used on a real web page, so it shouldn't have a h1. Use a lower importance heading level like h2.
    • According to the design, the whole card should be clickable. One way to do that easily is by making the card position relative, then adding a pseudo-element to the link (e.g. :after) and setting that to be absolutely positioned and covering the card. Now the link will effectively cover the whole card.
    • On hover of that link (or pseudo or card), the shadow is meant to change a little.
    • The main image is decorative in my opinion. That means it should have an empty alt value (alt="").
    • Do you need a div for the card body? That's not really adding anything.
    • Alt text shouldn't include words like "image". If you consider it meaningful it should describe what the image looks like, or if decorative the alt should be blank.
    • As a general rule, don't put text in divs or spans alone, as they are meaningless elements only intended to be used for layout purposes. I'd make that learning category into a paragraph.
    • The card doesn't need a min-height.
  • tomblack9452•60
    @tomblack9452
    Posted 12 months ago

    This design is basically exact to the original design. The weight of the text on the main heading is slightly lighter - maybe not the same number specified on the style spec? Other than that, perfect.

  • P
    MikDra1•7,470
    @MikDra1
    Posted 12 months ago

    Responsiveness Improvements:

    • Use Media Queries: Implement media queries in style.css to ensure the card layout adapts well to different screen sizes.
    • Flexbox/Grid Layout: Consider using Flexbox or CSS Grid for more flexible and responsive design.

    Code Quality Enhancements:

    • Semantic HTML: Ensure proper use of HTML5 semantic elements like <article> or <section> for better accessibility.
    • CSS Optimization: Minimize CSS by combining similar styles and removing unused code.
    • **Consistency: **Maintain consistent indentation and naming conventions across the project.

    Hope you found this comment helpful 💗

    Good job and keep going 😁😊😉

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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