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

Blog Card Using Html and Css

Shahzaib Ur Rehman•370
@Shahzaib-ur-Rehman
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?

I now feel confident in my ability to manipulate various types of images and text using HTML and CSS. Additionally, I believe it's important for me to optimize my CSS code for efficiency.

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

In this challenge, SVG is utilized, and initially, I wasn't sure how to round it. After some research, I decided to use an image tag and rounded it using a CSS property."

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

This challenge will be beneficial for me in the future, especially when I encounter situations where I need to style cards, text, or images.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Øystein Håberg•13,280
    @Islandstone89
    Posted over 1 year ago

    HTML:

    • The main image is mostly illustrative, so give it an empty alt text so screen readers will ignore it:alt="".

    • "Learning" is not a <button>, but a <p>. Buttons are used to trigger an action.

    • Use the <time> element for the date, like this:<p>Published <time datetime="2023-12-21">21 Dec 2023</time></p>. Read more about the <time> tag here.

    • As this is a blog card, the heading should have a link inside.

    • The alt text should be written naturally, without using - between the words. Write something short and descriptive, without including words like "image" or "photo". Screen readers start announcing images with "image", so an alt text of "image avatar" would be read like this: "image, image avatar". I would write something like "Headshot of Gary Hooper".

    • .attribution should be a <footer>, and you should use <p> for the text inside.

    CSS:

    • Add around 1rem of padding on the body, so the card doesn't touch the edges on small screens.

    • Add display: inline-block on .blog-bedge, so it doesn't stretch the full width.

    • Remove the width and height on the top image.

    • Remove max-width on .blog-desc.

    • 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.

    Marked as helpful
  • Marija Paunović•50
    @MarijaPaunovic
    Posted over 1 year ago

    Great job!

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