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

Blog Preview Card using HTML and CSS

Priyanka Roy Choudhury•100
@PriyankaRC16
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello

Any feedback is appreciated!

Thank you

Priyanka

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Andrés Gutiérrez Ramírez•2,470
    @AGutierrezR
    Posted over 1 year ago

    Hello there @PriyankaRC16 👋. Good job on completing the challenge!

    I have some suggestions about your code that might interest you.

    General Structure and HTML:

    • Wrap the primary content within the <main> tag instead of using it as a standalone component like a <div>.
    • All the content should be contained within landmarks. Every page minimally needs a <main> element.
    • Consider using <span> or <time> instead of paragraphs for elements that are not actual paragraphs like "Learning" and "Published...".

    CSS and Styling:

    • Instead of fixed widths, employ max-width and min-width for flexible and responsive design. Replace the width: 20em from the .card for a max-width: 20em.
    • Let the content decide the height of the elements. Use padding and margins strategically for this purpose.

    Accessibility and Semantic HTML:

    • The icons/illustration images are decorative, so their alt text must be empty: alt="".
    • Profile image could benefit from a more descriptive alt text, like alt="Headshot of Greg Hooper".

    I hope you find this helpful 😁. Most importantly, your submitted solution is fantastic!

    Happy coding!

    Marked as helpful
  • Marcos Travaglini•6,210
    @Blackpachamame
    Posted over 1 year ago

    Greetings @PriyankaRC16! you have done an incredible job.

    I leave you some comments in case they help you:

    • Reset the margin in the universal selector * with margin: 0. This will eliminate those annoying scrolls
    • Add a gap: 8px to your card-text class to fix the change above
    • You can adjust the width of the avatar image so that it is correct:
    .avatar-and-text > img {
        width: 35px;
        height: auto;
    }
    
    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub