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

blog-card using css grid

tushar-Ruhela•260
@tushar-Ruhela
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 for made a better blog card and add new desgin in it.make user view better

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

challenges is come like difficulty to give a properties to the blog-card box for looking site better.we learn something new by doing challenges work

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

i would like the box-shadow area .it gives a look better to website

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Journey-Grinder•150
    @Journey-Grinder
    Posted 11 months ago

    Try every time, When you find a problem, or something you re struggling or you re not understanding the source of the problem, Don't ignore it. Try to find how you can fix/add that thing that you want.If you don't even know what you should add like the box shadow or something like that consider seaching for it. Because that s the goal for all of this. Which is filling the empty gaps that we miss with new productive knowledge.

    And my advice especially for you. Is to not ignore your problems.

    Why: What I see is the spacing and positioning of elements is so off. And the boxshadow isn't added (Maybe you didn't see it but you gotta the spacing of the elements). Thank you my friend If you re reading this. And this is just my feedback for you to learn from your mistakes and progress further more.

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