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

Responsive Article Preview Component using CSS Grid and CSS Flexbox

pure-css
Muhamad Rukhul Kirom•380
@rukhulkirom
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 how well the design and functionality came together. The layout is clean and responsive, adapting smoothly across different screen sizes. The animation effects on the share button also enhance the user experience by making the transition feel fluid and natural. Additionally, I was able to use semantic HTML and maintain a well-structured CSS file, making the code easy to read and modify.

What I Would Do Differently Next Time

  1. Improve JavaScript Logic: Instead of manipulating classList.value directly, I would use classList.toggle() for better readability and maintainability.

  2. Add More Interactivity: I could enhance the experience by adding a tooltip for the share button or displaying the share options in a more intuitive way.

What challenges did you encounter, and how did you overcome them?
  • Challenge:
  1. The layout looked great on mobile, but on larger screens, the positioning of the share popup was inconsistent.

  2. The slide-in and slide-out animations for the share section weren’t smooth at first, causing flickering or abrupt movements.

  • Solution:
  1. I adjusted the position properties in CSS and used @media queries to ensure the share popup was positioned correctly on different screen sizes.

  2. refined the keyframes, adjusted the easing function, and added opacity transitions to make the animation smoother.

What specific areas of your project would you like help with?
  1. Currently, I’m using a ternary operator to toggle the share popup, but I feel like there might be a cleaner way to handle this. Would using classList.toggle() be a better approach, or is there an even more efficient way to achieve this?

  2. The slide-in and slide-out animations work well, but I’d love feedback on making them even smoother. Are there better easing functions or techniques to create a more polished transition effect?

  3. Are there any improvements I could make in the HTML, CSS, or JavaScript to make my code cleaner and more maintainable?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Annalyza106•190
    @Annalyza106
    Posted 4 months ago

    Great take on the challenge, an area I'd to see better though is the transition. It's a lovely touch, yet can be a little bit more subtle.

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