How gauravxsharma/doneit-todo works
Project type and purpose
• This is a single-page, front-end To-Do application.
• Purpose: let users add/edit/delete tasks, track progress via a bar, and trigger a confetti effect when all tasks are done.
• It uses only HTML, CSS, Vanilla JavaScript, the browser’s LocalStorage API, and the tsParticles confetti library.
File structure
• Top level files:
• index.html – the main UI entry point
• style.css – styling for layout and effects
• app.js – all application logic, DOM manipulation, LocalStorage reads/writes, and integration with tsParticles
• img/ – static assets used in the UI
• No backend, build scripts, or external services beyond the confetti library.
Additional insights from README
• Tasks persist in LocalStorage, so there’s a client-side store only.
• A dynamic progress bar recalculates percentages on each change.
• The tsParticles library is used for the confetti celebration.
a. Main components to show
• Browser (as the container)
• UI Layer: HTML (structure) + CSS (styles)
• Application Logic: app.js – handles event listeners, task CRUD, progress calculation
• Data Store: LocalStorage API
• External Library: tsParticles Confetti
• Static Assets: img folder
b. Relationships and interactions
• User → UI Layer: clicks “Add”, “Complete”, “Delete”, “Edit”
• UI Layer ↔ Application Logic: events flow into app.js; DOM updates flow back out
• Application Logic ↔ LocalStorage: read/write on every CRUD operation and on page load
• Application Logic → tsParticles: triggers confetti when progress hits 100%
• UI Layer loads static img assets
c. Architectural patterns/Design principles
• Separation of concerns:
– HTML/CSS for presentation
– JavaScript for behavior and state management
– LocalStorage as persistent client-side store
• Event-driven updates: user actions trigger JS logic, which updates both the DOM and LocalStorage
• Single responsibility: each module (DOM manipulation, storage management, confetti effect) is clearly delineated
d. Key technologies/frameworks/libraries
• HTML5, CSS3 – static UI
• Vanilla JavaScript – core logic (no frameworks)
• LocalStorage API – persistence
• tsParticles Confetti – celebratory animation
Detailing and coverage
• Don’t omit any piece: show img assets loading, the static files being served by the browser, the single HTML entrypoint.
• Event triggers (add/edit/delete), data persistence, progress bar recalculation, and confetti trigger.