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

Todo List App - Vanilla Javascript, SCSS, Vite

vite
Juan A Lagunas Palomares•430
@dev-jLagunas
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?

Proud of I am proud of the fact that I was actually able to finish this. The project took me longer than I initially expected. In the end it was more straightforward than I expected so the main issues I encountered came from me over complicating everything.

Do different Next time I would probably build this with a framework since that would simplify a lot. I did not implement the bonus "drag and drop" functionality but if I had used Angular material I would have.

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

Issues I encountered issues dealing with broken file paths when I uploaded my project to GH pages using Vite. The issue stemmed from my main.js file where I toggled light/dark mode while changing img.src to their respective icons. In the end I could not solve that issue so I completely removed that functionality from my javascript and changed the icons using CSS. This worked immediately!

If anyone has encountered this issue please let me know because I know sometime in the future I will need to use Javascript to change img.src.

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

Next Steps I would like to make this a full stack project using some free database service instead of using local storage.

Any tips on that would be nice!

Thanks buddies, see ya next time.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Juan A Lagunas Palomares'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.