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

Responsive Blog Preview Card – Modern UI with Flexbox & Accessibility

accessibility, semantic-ui
P
Ethan John Paguntalan•260
@dev-ethanjohn
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?

Experience doing more custom styling using custom properties. Studied style scoping when dealing with custom properties. New styling properties and user-action pseudo classes such as :hover and :focus.Additionality, I took the opportunity to learn how to use local fonts (@font-face). For now, I should continue to be comfortable detailing about my css system, so I will be prepared if I go into frameworks on CSS.

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

The one that boggled me is the hover effect of the card. I used box-sizing: border-box for all elements but somehow adding a filter drop shadow causes the width content to shrink. Well since border-box is the overall width consisting of the content+padding+border, adding a negative margin on hover won't solve it. Instead, a simple fix like using box-shadow is enough. Having fun dealing with CSS!

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

I am thinking since that the card's behavior has a hover effect triggered by itself. Meaning not its children inside. Wrapping the card to an anchor tag will make the entire view a link. But, it is not recommended as per my research (not semantically appropriate). Is JavaScript the way to do this?

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Hossana Monday•40
    @hossygifty
    Posted 6 months ago

    the solution includes semantic tags and it is accessible the code is well structured and readable

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.