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

Todo App built with Next

accessibility, tailwind-css, typescript, next
Jenny Eikens•250
@Jenny-Eikens
A solution to the Todo app 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 I managed to find a solution for adding a linear-gradient border to the checkboxes on hovering. This is something I inititally struggled with, as border-image, which would've been the most straightforward solution, wasn't compatible with setting a border-radius.

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

This was my first time implementing a drag-and-drop functionality. I used the dnd-kit library for this, which in itself wasn't hugely challenging, but I didn't find out until I was done that it doesn't automatically work with touch-based devices. So implementing this was a bit of a challenge but the docs were very helpful.

I also encountered some challenges using localStorage and setting the initial theme as there were some conflicts between the server-side rendered content and the client-side. I eventually managed to resolve these issues through a useEffect that uses a state variable to ensure the app is mounted on the client before trying to access localStorage:

const [isClient, setIsClient] = useState(false);

useEffect(() => {
    setIsClient(true);
  }, []);
What specific areas of your project would you like help with?

I can't think of any specific questions right now, but I'm not very experienced at working with Next yet, so if you have any feedback or would like to suggest improvements, I'd love to hear it!

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 Jenny Eikens'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

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.