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

Responsive Article Preview Card with Share Feature using Flexbox

accessibility, pure-css
Michael Okorie•150
@Michael-Okorie
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 clean and responsive the layout turned out. Implementing the share icon interaction with pure CSS and making sure the component looks great on all screen sizes felt like a real win. If I were to do it again, I’d take it a step further by building a React version with state management to practice component-based structure and interactivity.

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

One key challenge was properly positioning and styling the share icon tooltip across different screen sizes. It required careful use of position: absolute, media queries, and some creative problem-solving to keep it responsive and user-friendly. I iterated through several versions and tested frequently to make sure the layout held up on mobile and desktop.

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

I’d love feedback on accessibility improvements, especially regarding ARIA usage and tab navigation. Also open to suggestions on refining the transition effects for the share tooltip and optimizing the CSS structure further for reusability.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Atif Iqbal•3,320
    @atif-dev
    Posted 27 days ago

    Congrats🎉 Michael Okorie on completing the challenge.

    You can further improve your solution by considering following points:

    • In share options(tooltip),small pointing arrow is missing. If you don't know how to make that arrow you can see this code and customize according to FEM design.
    • Active state color on share icon(your #shareIcon) is missing for mobile and desktop view.
    • For mobile view, make "SHARE" and social icons centered and bigger(see design and your solution).

    Hope the feedback is valuable for you.

    Marked as helpful

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