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

Blog preview card using html and css

razanabbas•150
@razanabbas
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 am proud that i could solve it quicker than my previous project.

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

This is my first time dealing with an svg so I was not very familiar with them.

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

I want tips on how to make it more semantic and accessible.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Gwenaël Magnenat•1,540
    @gmagnenat
    Posted about 1 year ago

    Hi congrats on completing the challenge!

    I noticed a few things here that you can use to improve this solution and your future challenges.

    Does the solution include semantic HTML?

    • a <main> landmark is missing. The main element represents the main content of the body of a document or application. -w3c
    • The image is missing an alt. It is a blog preview and I think this image is meaningful.
    • you can try the <time> element and datetime attribute for the published date.
    • the avatar should have a more meaningful name.

    Is it accessible, and what improvements could be made?

    • Currently the layout breakes in case of a reflow test. It isn't accessible for users who change the default font-size of their browser. You need to use relative units for everything related to fonts and sizes. Don't add a height to the card, you want the card to stretch correctly with the content if the size of the content increases. Why font-size must NEVER be in pixels
    • You should add hover and focus style to indicate the interaction and the link. The active state is only visible when the link is pressed.

    Does the layout look good on a range of screen sizes?

    • yep

    Is the code well-structured, readable, and reusable?

    • you should use a modern CSS reset at the beginning of your stylesheet in every of your projects. Check out Andy Bell and Josh Comeau, both are great.
    • The CSS is hard to read. You should use one of the linter suggested here Set up your dev environment
    • Try to focus on the lowest specificity in your CSS and only increase specificity when needed. You will avoid complexity targetting elements on larger project and your code will be easier to understand and debug by other developers.

    Does the solution differ considerably from the design? It looks good and respects the design intention.

    I hope you find something useful in these comments. Let me know on discord 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

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub