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

html css

ameera•80
@ameera-abed
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Øystein Håberg•13,260
    @Islandstone89
    Posted 11 months ago

    HTML:

    • Remove .underMain, it is not needed.

    • I would wrap all of the card content in a <div class="card">. Hence, your HTML structure would look like this:

    <main>
      <div class ="card">
         --card content 
      </div>
    </main>
    
    • "Learning" and "Greg Hooper" should be <p>.

    CSS:

    • I like to add 1rem of padding on the body, to ensure the card doesn't touch the edges on small screens.

    • On the body, change height to min-height - this way, the content will not get cut off if it grows beneath the viewport.

    • Remove all widths and heights in px, except for the profile image.

    • Add a max-width of around 20rem on the card, to prevent it from getting too wide on larger screens.

    • font-size must never be in px. This is a big accessibility issue, as it prevents the font size from scaling with the user's default setting in the browser. Use rem instead.

    • Remove all positioning and transform properties.

    • Remove z-index, it is not needed.

    • I'm not sure this needs a media query , as the layout doesn't change. When you do need media queries , they must be in rem or em.

    Marked as helpful
  • larryQuao•130
    @larryQuao
    Posted 11 months ago

    These are my suggestions for your solution:

    • I think you forgot to add the : hover property to your card, try to do so to have the hover effect on the card. And not to forget, make sure you make the cursor: pointer to make the mouse pointer when hovered on the card to change to a pointer.
    • It would be nice if you would have a look at the Figma file, you would have gotten the right properties, sizes, widths and heights for your solution.

    I think these will help. regards

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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