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

Responive animated solution to Hangman

P
Justin Green•2,940
@jgreen721
A solution to the Hangman game 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?

Some of the shadow/layering details to enhance a more cartoon-y effect on the UI was good practice/something worth remembering

The styling got a little mess, between Tailwind, custom CSS and some framer-motion, it'd be worth tidying that up/maybe improving.

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

Again, the styling got a little away from me as far as clean organized setup. Intro/exit animations on the different could be done better, in that there aren't any exit animations as I found Next to operate differently enough to not really accommodate framer-motions easy setup with plain React.

The audio btn has a bug to where first click doesn't toggle the audio off but after that its on track. Again, will probably go back and clean that up.

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

It could just benefit with a good code cleanup between the styling and also the components folder structure. Still haven't quite clicked into a natural rhythm with Next, for whatever reason. lol. Feedback and suggestions definitely all welcomed and appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex 🤸🏻‍♂️•1,710
    @sksksk2024
    Posted 7 months ago

    🔥 Great job on creating a responsive and animated solution for Hangman! The animations are modern and engaging, which makes the game feel fresh and exciting. I also love how your website has a playful, game-like aesthetic—it's inviting and fun!

    One thing to note: after finishing a round, the solution is visible for a moment, which makes it easy to cheat if someone is paying attention. It might be worth tweaking this to prevent players from getting an unfair advantage.

    Keep up the fantastic work! 🎮✨

    Marked as helpful
  • Tsotne Meladze•1,120
    @tsotneforester
    Posted 3 months ago

    Really liked background image loop! Bravo, if you don't mind I will steal this idea to add to my project ;)

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

Oops! 😬

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

Log in with GitHub