How kripanshu-singh/challenge-8--to-do- works
Project type and purpose
• This is a static, client-side “To-Do” single-page application built with vanilla HTML, CSS, and JavaScript. It is designed to run entirely in the browser and persist data using the Web Storage API (localStorage).
File structure
• Top level:
• index.html – the single entry point and UI shell
• script.js – application logic for rendering tasks, handling user events, and managing storage
• style.css – all presentation rules and layout
• No backend, build scripts, or server-side code—everything executes in the client.
README for additional insights
• Confirms that the site is deployed (via GitHub Pages) at the provided URL.
• No extra architecture notes, so we infer standard static-site patterns.
a. Main components
1. Browser / Client
• UI Layer (HTML/CSS)
• Logic Layer (JavaScript)
• Storage Layer (localStorage API)
2. Asset Store (static assets in Asset/ directory)
3. Hosting Platform (GitHub Pages)
b. Relationships and interactions
• User interacts with the HTML UI in the browser.
• script.js listens for events (add, delete, toggle task), manipulates the DOM, and reads/writes to localStorage.
• style.css is loaded by index.html to style the UI.
• The hosting platform serves the static files over HTTP(S).
c. Architectural patterns/design principles
• Single-Page Application (SPA) pattern: all views and logic live client-side.
• Separation of concerns: HTML for structure, CSS for style, JS for behavior.
• Client-side persistence using the Web Storage API.
d. Key technologies
• HTML5, CSS3, vanilla JavaScript (ES6+)
• localStorage API for data persistence
• GitHub Pages (static file hosting)
• Browser DOM & Event loop