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

Tic_Tac_Toe_App - NEXTJS13/REACTJS/TS/TAILWINDCSS/ZUSTAND

next, tailwind-css, typescript, zustand, react
Mikhail Lorenzo Aniel•230
@lorenzoaniel
A solution to the Tic Tac Toe game challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Tic Tac Toe game with accompanying algorithm for CPU opponent. Relied heavily on zustand for state management. Not much in terms of complex animations but i still tried to incorporate framer for any animations, some challenges associated especially some initial styling for tailwind and framer conflicting. Initially used tailwind's built in animations for the simple ones but i wanted to separate all animations to framer and all static and conditional styling to tailwindcss. I also now included storybook for building components, actual speeds up development since I can test the individual components in different resolutions as well as how they react to their specific conditional styling. I will try to implement some form of testing for the next project, I think I will also keep using zustand as my go to state management due to its simplicity and robustness, in conjunction with local component state i should be able to cover most bases, I will have to test how well it works with a backend of some sort.

again, any and all criticism apart from profanity is encouraged as I am very much a junior at this still.

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 Mikhail Lorenzo Aniel'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.