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

article preview component next-js

jquery, next, react, tailwind-css, accessibility
EmicJoykiller•270
@EmicJoykiller
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 the project came together visually and functionally. The UI is clean, responsive, and closely aligns with modern design principles. The interactive elements, like the share button and hover effects, work smoothly, enhancing the user experience.

If I were to do it again, I would focus more on accessibility and performance optimizations from the start. While the current implementation follows best practices, ensuring full compliance with accessibility standards (such as better keyboard navigation and ARIA roles) would improve usability. Additionally, optimizing image loading and minimizing unnecessary re-renders could make the project even more efficient.

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

One major challenge was handling dynamic UI elements, specifically the share button toggle. Initially, positioning and responsiveness caused layout shifts and overflow issues on smaller screens. To resolve this, I adjusted the absolute positioning of the share container, ensuring it remained within the article card without overlapping critical content.

Another challenge was ensuring smooth state management. Since Next.js is a React-based framework, I used the useState hook for toggling elements, but at times, unnecessary re-renders affected performance. Refactoring event handlers and using memoization techniques helped streamline the interactions.

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

I’d love feedback on improving the accessibility of the interactive elements, especially the share button. Are there any best practices I might have overlooked in terms of keyboard navigation and ARIA attributes?

Additionally, any suggestions on optimizing performance further, such as lazy loading images or minimizing unnecessary component re-renders, would be greatly appreciated. If anyone has insights into further improving responsiveness for various screen sizes, that would be helpful as well!

Looking forward to your feedback! 🚀

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on EmicJoykiller'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 1st-party linked stylesheets, and styles within <style> tags.

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.