Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

Blog card project

Hendrixx•430
@BeeAlmighty
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 happy i get to practice what i've learnt so far.
  • I would try as much as possible to always build something and test my knowledge against challenges and i hope to overcome them.
What challenges did you encounter, and how did you overcome them?
  • Honestly, i was quite a challenge figuring out how to structure my HTML in a way that CSS flexbox can be applied.
  • I had challenges with the mobile-first workflow with CSS media queries but luckily W3schools was there to help.
What specific areas of your project would you like help with?
  • I would really appreciate general review of my code on how to write more concise and clean code.
  • I would like help with my judgements in terms of the responsiveness of my project especially with smaller screens.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nisha Kumari•300
    @technoish
    Posted 9 months ago

    Hi, great work on your code! It’s clean and well-structured. Here are a few suggestions to improve it:

    Semantic HTML: Use semantic elements like <header>, <footer>, or <section> instead of <div> where appropriate. It improves readability and accessibility.

    Font Sizes: Use relative units like em or rem for better scalability on different devices.

    Media Query: Great job with responsiveness! Test on various devices to ensure everything scales properly.

    Code Cleanup: Remove unused styles like /* font-weight: <weight>; */ to keep your code tidy.

    If this helps, feel free to mark it as helpful. Happy coding! 😊

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