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

Responsive Article Preview Component HTML / CSS / JS

P
Kyle Mulqueen•400
@kmulqueen
A solution to the Article preview component 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'm most proud of creating a component that works well across different screen sizes with distinct behaviors appropriate to each. The way the share functionality adapts between mobile and desktop demonstrates good responsive design thinking.

Next time, I would:

  • Plan my HTML structure more carefully to avoid issues with overflow and positioning.
  • Create a more modular CSS approach to handle the speech bubble styling.
  • Consider using CSS custom properties for values like the mobile breakpoint to maintain consistency.
  • Implement proper focus management from the beginning rather than adding it later.
What challenges did you encounter, and how did you overcome them?
  1. Maintaining accessibility while toggling visibility - I initially struggled with properly updating aria-hidden attributes. I solved this by consistently checking the element's hidden state and setting the aria attribute accordingly.

  2. Different behaviors across screen sizes - The mobile vs. desktop layout required different behaviors for the same components. I implemented conditional logic based on screen width to handle these differences.

  3. Positioning issues with the toast component - I had challenges with the toast being cut off by overflow settings. I had to carefully balance maintaining border-radius on images while allowing the toast to be fully visible. Because I had overflow: hidden set on the article initially, the toast pop-up on larger devices was getting cut off. When I updated my stylesheet to have overflow: visible at larger devices, my border-radius on the image disappeared. I solved that by manually adding the border-radius to both the top-left and bottom-left corners of the image. This allowed me to have the toast visible while maintaining the border-radius on the image.

  4. Focus management - The button staying in focus state after closing the toast was confusing. I learned to use the blur() method to programmatically remove focus when appropriate.

What specific areas of your project would you like help with?
  1. Creating a more elegant solution for the speech bubble styling that works well across all screen sizes

  2. Improving my CSS Grid implementation to better handle complex layouts

  3. Implementing smooth transitions/animations when toggling the visibility of elements

  4. Developing a more comprehensive focus management system for better keyboard accessibility

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Kyle Mulqueen's solution.

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, SASS, 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.