Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 24 days ago

w3schools

Akinloye3264•20
@Akinloye3264
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

  • gok786•50
    @gok786
    Posted 21 days ago

    Overall Feedback:

    You've created a clean and visually structured blog preview card with a solid understanding of layout and basic styling. The use of Flexbox is appropriate and your font choices are on brand for a modern UI.

    What’s Good:

    Semantic structure is mostly clear and easy to follow.

    Nice use of Google Fonts and Flexbox for layout.

    Card styling (border, shadow, radius) looks visually engaging.

    Good use of class naming and image handling for the avatar.

    Suggestions for Improvement:

    Accessibility & Semantics:

    Use meaningful tags like <article>, <section>, and <time> instead of <h2> for date.

    Consider adding alt attributes to all <img> tags for accessibility.

    Image Styling:

    img { width: 50; } is missing a unit (px). Should be width: 50px;.

    Content Spacing:

    Add some spacing (e.g. margin-top) between elements like h3 and the paragraph for better readability.

    Responsive Widths:

    Avoid hardcoded widths like width: 400px on h3; this can break responsiveness. Use relative units or let it adjust naturally.

    CSS Cleanup:

    Remove unused or commented code for better readability.

    Fix the empty font-weight: in .udo.

    External Link:

    Your attribution link to Gmail might not be appropriate — consider using a personal portfolio or GitHub instead.

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