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

Blog Preview site using html and css

mayank1405•100
@mayank1405
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?

This would be my second project on frontend mentor. It feels nice to have completed this project and see it be almost the desired output. I would learn a bit of JS and make it more responsive

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

I couldn't figure out how to change the property of a parent element when hovering over a child element with only html and css. I didn't want to use JS as I wanted this to be a pure html css project. I would really appreciate if someone can suggest a way.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dylan de Bruijn•3,220
    @DylandeBruijn
    Posted about 1 year ago

    Hi @mayank1405,

    I'm glad I was able to help you out! Could you mark my comment as helpful when you have the chance? That would help me out a great deal!

    I read the challenge again but couldn't find the specification to increase the box-shadow on the card when hovering the card title. But I must admit I have seen some other people do it. What I think is that they grow the box-shadow when the user hovers on the card and turn the card title yellow when that gets hovered. So there are two separate hover animations.

    Marked as helpful
  • Dylan de Bruijn•3,220
    @DylandeBruijn
    Posted about 1 year ago

    Hi @mayank1405,

    Congratulations on another great solution! It's good that you want to learn a bit of JS an try to make it more responsive.

    I would love to help you out with your challenge, but I'm confused what you are describing:

    I couldn't figure out how to change the property of a parent element when hovering over a child element with only html and css.

    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
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