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

Blog card with hover effect

arpan62825•60
@arpan62825
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?

Happy that I made it look almost like the original one.

  • took less time than the previous one
  • Did all by myself

Things I would like to improve:

  • Use of unnecessary margins
  • Unprofessional work/Bad Practices
What challenges did you encounter, and how did you overcome them?

There was not much of any challenge, everything went smoothly. Used flex to align all the items

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

Okay, so I did this without any help (like chat GPT, google, stack overflow, etc) I am pretty sure that I did some unnecessary things.

And did some Bad practices

I would really appreciate anyone pointing out the mistakes/bad practices that I did. And would greatly benefit from any suggestions to make the code DRY

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Antoine Delalande•170
    @Hamsolovski
    Posted 12 months ago

    Hello ! Very nice work, you're near pixel perfect :)

    You wanted tips on bad practices you might have, here's what i've noticed :

    • css : don't use values when naming your variables (yellow, etc.), but instead, use a term describing the role of the variable (main-color, bg-color, title-font) etc. That way, if someday, you have to change the value of your variables, you don't have to rename it and avoid having a variable "yellow" containing an hex code for red.
    • html : avoid div if you can, there are a lot of other tags you can use : article, section, header, footer, etc. divs are not very good from a SEO point of view.
    • try to store your svg data into a dedicated file : it makes your code cleaner. Good habit to have : if you have one element or function you might want to use elsewhere : put it in a separate file.

    Some other tips :

    • you can put other values than colors in your variables : font, size, etc.
    • try to avoid fixed height and width for element whose size might change : your element will better adapt to its content.
    • you can use numeric values in font-weight : 100, 200, etc. It allows you to be more precise than using values like bold, etc.

    Hope it helps :)

    Very nice work on the transition btw !

    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