Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 15 days ago

Article preview component using HTML, CSS Flexbox, and JavaScript

P
JiaHe35354•140
@JiaHe35354
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?

Implementing different interactions for desktop and mobile screens using JavaScript and window.innerWidth.

How to adapt behavior conditionally depending on screen size, such as hiding and showing specific elements (e.g., showing the mobile share icon or hiding the desktop button on smaller screens).

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

I spent a lot of time figuring out how to display the popup when clicking the share button, especially getting its style and position right. It wasn’t easy for me at first. I used absolute positioning for the popup and had to test different width and height values multiple times to make it look correct on both desktop and mobile screens. To make the popup show and hide properly, I also experimented with JavaScript and had to debug it through trial and error until I got the desired result.

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

I'm having trouble changing the color of the share icon. I used filter: brightness() to make it look white, but the result doesn’t match the design in the Figma file. I’d like to learn a better or more accurate way to style the icon so it looks the same as the design.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•5,520
    @thisisharsh7
    Posted 15 days ago

    Hey, fantastic work adding transitions enhances UX! Your live webpage looks good and the popup logic and positioning are clean and functional across devices.

    For icon color styling: Instead of filter: brightness() for making icons white, try using: - An SVG icon with fill="currentColor" and toggle the parent button’s color property. - OR, use a white version of the icon if provided by the design.

    For next projects:

    • Try adding aria-expanded and aria-controls to buttons for better screen reader support.
    • Try reusing component and style it responsively.

    Overall a good solution - happy coding!

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