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

Blog Preview Card - BA

soybrrraian•60
@imbraian
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'm especially proud of having been able to complete the challenge despite the difficulties I faced. However, in hindsight, I believe I have not yet given my 100%. I think I'm capable of doing things better. Next time, I will focus on doing even better than the previous time and so on consecutively to improve every day.

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

I didn't see any other challenges. I didn't have time. But I will do all the ones that come my way.

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

In this project, I would like to receive specific help in:

Accessibility: I would like to make the project more accessible for people with disabilities, ensuring compliance with web accessibility standards. Code improvement: If there are areas in my code that could be improved in terms of clarity, efficiency, or maintainability, I would love to receive suggestions and guidance on that.

Any help or advice in these areas would be greatly appreciated. Thank you in advance for your help and support!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Ruben de Man•830
    @developer-ruben
    Posted over 1 year ago

    Hi!

    Great component, here are my tips:

    • I would not use article in sections, articles are used to have a more independent role rather than sections. More info here: https://www.smashingmagazine.com/2022/07/article-section-elements-accessibility/
    • For timestamps you can use the <time> html tag. More info here: https://www.w3schools.com/tags/tag_time.asp#:~:text=The%20tag%20defines%20a,can%20produce%20smarter%20search%20results
    • card__container--img is an invalid BEM class since you used img as an modifier, to rather change it into card__img to keep the BEM method in place.
    • Try using css variables with for example colors, so you dont have to repeat them in your code

    That's pretty much it! Best, Ruben

    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.

Oops! 😬

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

Log in with GitHub