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

Responsive Article Preview Component with BEM & Flexbo

bem, sass/scss
P
Mars - Martiniano Leguizamon•275
@martinianol
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 proud of how I implemented BEM (Block Element Modifier) correctly, making my CSS more structured, reusable, and easier to maintain. I’m also particularly happy with how the tooltip smoothly follows the button when resizing the window, ensuring a seamless user experience. This project helped me strengthen my JavaScript event handling, especially for managing responsive interactions.

Next time, I would focus on optimizing event listeners further to improve performance on resize events. I’d also explore using CSS animations to enhance the tooltip’s appearance and transitions for a more polished UI.

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

One of the biggest challenges I faced was dealing with window.innerWidth behaving inconsistently near the breakpoint range. When resizing the window pixel by pixel, I noticed that innerWidth sometimes jumped unpredictably, especially between 418px and 496px (break point is set at 31rem=496px) This caused the tooltip to not transition correctly to the bottom position, and the user-info didn’t always hide as expected.

Sometimes in the dev tools the width was 470px but when I console.log innerWidth, it printed 510px...

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

One area I’d like to improve is handling window.innerWidth inconsistencies near breakpoints.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Anamay•470
    @anamaydev
    Posted 4 months ago

    Hey @martinianol, I went through your code and really liked it! I noticed you've used SASS/SCSS, and I've been looking for good resources to learn it. Could you recommend some?

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.

Oops! 😬

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

Log in with GitHub