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

Blog Preview card main

Pixel-Caje•70
@Pixel-Caje
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

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

    This has quite a lot of foundational issues. This makes me think you've not sought out or read feedback on earlier challenges?

    I'll try to list out some of the issues but you may need to go back and get feedback on earlier challenges first.

    • All content should be contained within landmarks. This is a single component demo that should sit within a main landmark. You shouldn't be changing any roles anywhere or placing a main inside the component. The attribution belongs in a footer landmark under the main.
    • Always include a full modern CSS reset like this at the start of the styles in every project you do. Amongst other things this will stop the image overflowing.
    • Never limit the height of elements that contain text. Almost the only time you'll ever set height and width is on small images or icons. It's the browser's job to decide how tall elements need to be based on the content and spacings inside them.
    • You don't need the container div in this.
    • All the component needs for it's size is a single max-width in rem.
    • The body is only as tall as its content by default. To center something in the viewport you'll need to make the body at least as tall as that viewport with min-height: 100svh and use flex column properties to center it's children.
    • Why have you used h3 for the heading? Is that intentional? (it's not necessarily wrong, I'm just checking you understand why heading levels matter. See https://fedmentor.dev/posts/heading-order/
    • This is missing the most important element in the whole component. This is a blog card. It has an important function of signposting (linking) to a blog, but you've not included a link! That needs to wrap the blog title text inside the heading.
    • To make the whole card clickable, add a pseudo element to that link. The card will need to be position relative and the pseudo will need to be positioned absolutely and cover the card so it's all clickable.
    • I think you're getting confused between padding and margin. The body/main and card in this should have padding on all sides. The child elements within the card should have vertical margins. See https://fedmentor.dev/posts/padding-margin/
    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.

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