Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Blog Preview Card using CSS Grid

accessibility
JoyObaidu•350
@JoyObaidu
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?

Accessibility

What challenges did you encounter, and how did you overcome them?

None , I have an attempted projects like this before

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

CSS MArgin

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Jacob Stone•130
    @jacob-stone9554
    Posted about 1 year ago

    Hi Joy, you have a great start on your solution, it looks fantastic!

    There are only a handful of small, fine-grained tweaks you could make in order to get your solution a little closer to what the design is asking for as some changes to your HTML for a better overall structure.

    As far as the structure of your HTML goes, you used a <section> to develop your blog card. Generally, this tag should be reserved for designating a section of your webpage. For example, if you were developing a webpage about global wars, you might have a <section> on WWI and a <section> on WWII. To get around this, you could create a .card rule in your CSS file and style that instead, using a <div class='card'> in place of <section>. With that being said, you still got your design really close to the solution, great work :)

    As far as the overall style goes, one very minor thing you could try is adding a border to your card. You can achieve this by adding border-width, border-color, and border-style properties to the rule where you style your card.

    Another very minor change you could try is setting the <p> text of your card to hsl(220, 15%, 55%) so that the color of the description matches that of the design.

    The final piece of feedback I have for your solution is regarding the active state (like hover). You have an error on line 36 of your CSS file. You need to remove the space from the rule such that it reads section h1:hover. Then the hover styles should be applied appropriately.

    Feel free to reach out if you have any questions, happy coding :)

    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