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

Responsive blog preview card

Kanchana K.•400
@Kanchana-Kaushal
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 that I made the website exactly like the design and responsive.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • jdrodriguez2707•170
    @jdrodriguez2707
    Posted 4 months ago

    Hi @Kanchana-Kaushal,

    Great work, congratulations! You built the website exactly like the design, and the card is responsive, even when I stretch the screen, it resizes perfectly, that's awesome. Plus, you used CSS custom properties, which is a good practice for making styles reusable.

    Here are a few things that, in my opinion, could further improve your website:

    • Use semantic HTML: Instead of using div elements you could use more semantic tags like article for the card. This tag is perfect for independent content, so it's useful in this context. Think of it like the card would be used in a different section of a larger website.

    Also, it's not necessary to wrap text in div. Instead, you can use the p tag to mantain the semantic structure. Try to use div only when you need to group elements for styling purposes.

    • Font Importing Best Practices: There's a better way to import fonts, by linking them in the head of the HTML rather than using @import in CSS. I don't remember the exact technical differences, but I do know that importing fonts via the head is generally faster in terms of performance.

    • Using classes: You're already using some classes in your code, that's great. But consider using them consistently for all elements. This approach makes styling more reusable and scalable, especially in larger projects.

    You might also want to explore methodologies like BEM to structure your CSS more efficiently. It’s worth checking out!

    • Add a bit of documentation: Lastly, I recommend adding some documentation about your project. You could edit the provided Frontend Mentor template to include details about what you practiced and learned during the process. This will not only help others understand your project’s purpose but also showcase your skills and thought process.

    That’s all! I hope this feedback helps. Keep up the great work, and happy coding! 🚀

    Marked as helpful
  • Franco•250
    @Franco-Cipolla
    Posted 4 months ago

    Nice!

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