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

blog-preview-card

P
Nazarii Sabadash•50
@rr0x9
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    finkusuma-dev•130
    @finkusuma-dev
    Posted 8 months ago

    Hi, your solution looks really nice and it almost identical with the design, good job 👍🏻.

    You have main element wrapping the card and footer element wrapping the attribution, which I think these are the correct semantic to use.

    About the figure, I'm myself still not 100% sure of how to use it. My solution here, completely removed figure from the code. I thought that, as this is a component, it won't relate with the main content of the page when the component is inserted to, so I removed it. And I'm still waiting for more expert person to give feedback on this matter.

    Suggestions

    The interactive element is excellent, I can see the hover effect with a transition when I pointed my mouse over the heading. I think you're just missing a very little here. The challenge is also requires the interactive element to be able to receive focus. Which you can check by clicking the page on an empty area and then press tab. And this focus and hover actually can be done by adding an anchor element. You can add anchor inside the heading like this:

    <h1><a href="#">HTML & CSS foundations</a></h1>
    

    Then you can replace your CSS code .card h1 :hover with .card a:hover.

    For the heading, on my solution I use h2 (I know some other person prefers to use h3). The reason is, once again, it is only a card component. And it will be used on the page somewhere where there will be h1. Because there should be only one h1 element, that means we need choose something else.

    I also noticed that you haven't put the code on the GitHub. Or maybe your repository haven't made public. As when I clicked the view code, I got missing page error.

    That's it from me. You can also give me feedback on the same challenge if you want here. I would really appreciate it if you do. 🙂

  • Jacqueline Bento•20
    @jacquebento
    Posted 8 months ago

    The solution includes semantic HTML. The layout look exactly like the design proposed with little changes on the mobile screen. I liked the way you use media query directly on the element, I never seen like this.

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