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

Blog Preview with only css hover effects

Gabriel Romme Reyes•110
@Gabriel-Romme-Reyes
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 learned about the difference of inline and block elements in this one because i had a problem when adding the background color yellow on the span at first it was an h4 element but upon adding the background color it took up the whole horizontal margin that is where i learned that h4 is a block element and that is when i switch it to span instead. i also learnt a bit more about css such as box-shadow and indentation.

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

A bit of a challenge with adding the background color of the learning tag because at first it was an h4 element but when i add the background color it takes up the whole horizontal space that is when i go and checked the internet about the difference of inline and block elements that is why i just used span

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

Are there any ways to change the box-shadow of the ".content" class only when hovering on the h1 element without using js?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kira Tantari•180
    @KirativeWD
    Posted about 1 year ago

    Hi there!

    Great job on completing this challenge.

    "Are there any ways to change the box-shadow of the ".content" class only when hovering on the h1 element without using js?"

    Technically, yes.

    .content {
      pointer-events: none;
    }
    
    .content:hover {
      box-shadow: 1rem 1rem black;
    }
    
    h1 {
      pointer-events: auto;
    }
    
    h1:hover {
      color: hsl(47, 88%, 63%);
    }
    

    However, that is overly complicated and what you could do instead is apply the color change to the h1 when .content is hovered. As a user, this makes more sense because I expect the entire card to be clickable and not just the h1.

    .content:hover h1 {
      color: hsl(47, 88%, 63%)
    }
    

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub