to-do-list

https://github.com/pielock/to-do-list.git

https://pielock.github.io/to-do-list/

**Technical Functionality

• Users can add new tasks via an input and button. done
• Tasks are dynamically rendered to the DOM upon addition. done
• Tasks are validated (non-empty, and ideally unique) before being added. 1/2done
• Users can delete tasks, and the DOM updates accordingly. done
• (Bonus) Users can edit tasks, update the content, and save changes dynamically.

**JavaScript & DOM Manipulation

• Proper use of event listeners for user interactions (e.g., button clicks, Enter key). done
• Effective use of JavaScript arrays or data structures to manage tasks.
• DOM updates are correctly synchronized with the task array (add/delete/edit).
• Clean, modular JavaScript code with meaningful variable/function names.

**Input Validation & Error Handling

• Prevents adding empty or invalid tasks. done
• Provides clear user feedback for invalid inputs (e.g., warning messages).
• Optional: Prevents duplicate entries or provides visual cues when a task already exists.

**Bonus Feature Implementation

• Edit buttons are available next to each task.
• Clicking edit allows task modification and saving.
• DOM updates and task array updates are in sync.
• UI/UX around editing is intuitive and clean.

**Code Quality & Structure

• Uses semantic HTML and follows best practices.
• JavaScript code is organized, uses functions, and avoids repetition.
• File structure is logical (e.g., index.html, style.css, script.js). done
• Comments and indentation improve readability. done

**Deployment

• Clear repository name and description. done
• Descriptive README.md with challenge details and deployment link. done
• Commits are frequent and meaningful. done
• Files and folders are well-organized and named logically. done