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

👾 Animated Interactive Comments | React | Dark Mode | Switch Users 👾

animation, fetch, framer-motion, react, axios
P
visualdennis•8,395
@visualdenniss
A solution to the Interactive comments section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


🔥 Here is my 30th Challenge! This was fun and tricky! 🔥

  • Built in React and made use of Context API for state management.
  • App is fully responsive for all devices.
  • As usual the data JSON is being hosted online on npoint.io so i fetch using axios. Sometimes the server is overloaded, you might need to refresh couple times.

I've added some more features to the challenge:

  • You can switch between logged in users by clicking avatars top-right. So you can create comments, replies from perspective of different users.
  • I've developed a VOTE system (was the trickiest part for me), so multiple users can vote, change their votes and when switched users, the vote scores and the users vote are persisted between user switches. (Votes are stored as an object)
  • Added some cute loader animation on initial load.
  • You can toggle Dark/Light modes.

This is still a work-in-progress, next i plan to refactor my code using useReducer and tidy up the function, improve accessibility/semantic stuff, localStorage implementation, perhaps a notification system for users when they are being replied to, a function for real/dynamic timestamps.

If anyone interested in how i've built this step by step, i recommend checking MY WORKFLOW

Hope you guys like the final result ♥️

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mohamed Abdellahi haibelty•120
    @mohamed-abdelahi-haibelty
    Posted about 2 years ago

    Hey, you've did great work there. It would be a great idea to add a form validation so user can't send an empty message

    Marked as helpful
  • P
    Darionas•400
    @Darionas
    Posted about 2 years ago

    Hey. I like it. One think especially 'desktop-design-breakdown.jpg'. Could I borrow this method from you?

    Thanks in advance. Happy coding ;)

  • ahsan1280khan•80
    @ahsan1280khan
    Posted about 2 years ago

    Super nice Love it

  • davidpagebyte•30
    @davidpagebyte
    Posted almost 2 years ago

    I really like how you switch users! I was looking for ideas for it

  • Kehinde•680
    @jonathan401
    Posted about 2 years ago

    A wonderful solution 🎊🎊. This is my first time hearing about npoint.io. I'll try using it in my solution to this challenge. Love the extra features ❤️❤️

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.

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

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

Oops! 😬

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

Log in with GitHub