Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

17th task: To-do list๐Ÿฅต Works GREAT!

Rodrigoโ€ข480
@RodrigoHLC
A solution to the Todo app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


The layout and styling were very straightforward, though figuring out which color corresponded to which element when setting up the variables was annoying as hell. The javascript for this was also pretty straightforward (I already knew a couple of ways of creating to-do lists). The most difficult part of course was making the items/tasks draggable and sortable; had to learn from a couple of videos and then I experimented with what I learned to see what else I could do or if there were any other ways to achieve the desired functionality, so that ate up a few hours of my time.

I also made sure to write what I think is very clear code, at least for the JS part, so that anyone who looks at it can quickly understand what everything does. There are comments all throughout the file. Hope someone finds it useful!

PS: because the default items on the list are intended to guide the user into testing out the functionality, I did not add a localStorage feature to the JS, as any changes the users make to the list could result in deleting the original items. Therefore, changes to the list are not saved.

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 Rodrigo'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.