├── .DS_Store ├── .github ├── ISSUE_TEMPLATE │ ├── bug.yml │ ├── documentation.yml │ ├── feature_request.yml │ └── styles.yml ├── PULL_REQUEST_TEMPLATE.md ├── pr-title-checker.json └── workflows │ ├── codeql.yml │ ├── greetings.yml │ └── pr-title-checker.yml ├── .vscode └── settings.json ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── Roboto_Slab.zip ├── images ├── to-do-list.png └── todoWhite.png ├── index.html ├── index.js ├── package-lock.json ├── scroll.js ├── scroll_img.svg └── style.css /.DS_Store: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Kritika30032002/To-Do-List-Application/d7f1ffa5d3346f2de6adab81eea5161b99b9735c/.DS_Store -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug.yml: -------------------------------------------------------------------------------- 1 | name: ​🐞 Bug 2 | description: Report an issue to help us improve the project. 3 | title: "[BUG] " 4 | labels: ["bug", "goal: fix"] 5 | body: 6 | - type: textarea 7 | attributes: 8 | label: Description 9 | description: A brief description of the issue or bug you are facing, also include what you tried and what didn't work. 10 | validations: 11 | required: false 12 | - type: textarea 13 | attributes: 14 | label: Screenshots 15 | description: Please add screenshots if applicable 16 | validations: 17 | required: false 18 | - type: textarea 19 | attributes: 20 | label: Any additional information? 21 | description: Any additional information or Is there anything we should know about this bug? 22 | validations: 23 | required: false 24 | - type: dropdown 25 | id: browsers 26 | attributes: 27 | label: What browser are you seeing the problem on? 28 | multiple: true 29 | options: 30 | - Firefox 31 | - Chrome 32 | - Safari 33 | - Microsoft Edge 34 | - type: checkboxes 35 | id: no-duplicate-issues 36 | attributes: 37 | label: "Checklist" 38 | options: 39 | - label: "I have starred the repository" 40 | required: true 41 | 42 | - label: "I have checked the existing issues" 43 | required: true 44 | 45 | - label: "I have read the discussion tab thoroughly and got the project idea" 46 | required: true 47 | 48 | - label: "I am willing to work on this issue (optional)" 49 | required: false 50 | 51 | 52 | 53 | 54 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/documentation.yml: -------------------------------------------------------------------------------- 1 | --- 2 | name: Documentation Issue 3 | about: Report an issue with the project documentation 4 | title: "[Documentation] " 5 | 6 | --- 7 | 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: | 12 | 15 | 16 | ### Issue Summary 17 | 18 | **Description:** 19 | A clear and concise description of the problem with the documentation or the improvement you'd like to suggest. 20 | 21 | **Severity:** 22 | [ ] Low 23 | [ ] Medium 24 | [ ] High 25 | [ ] Critical 26 | 27 | **Affected Documentation Section:** 28 | Specify the relevant section(s) or page(s) of the documentation where you encountered the issue. 29 | 30 | ### Expected Documentation 31 | 32 | **Describe the expected content:** 33 | If applicable, describe how you expected the documentation to be or provide examples of how it could be improved. 34 | 35 | **Proposed Solution:** 36 | Share your ideas for improving the documentation or propose a solution if you have one. 37 | 38 | ### Reproduction Steps 39 | 40 | **Steps to Reproduce:** 41 | If the issue is related to inaccuracies or unclear instructions, provide the steps to reproduce the problem. 42 | 43 | **Screenshots or Code Snippets:** 44 | Attach any relevant screenshots or code snippets that illustrate the problem. 45 | 46 | ### Environment Information 47 | 48 | **Your Environment:** 49 | - OS: [e.g., Windows, macOS, Linux] 50 | - Browser: [e.g., Chrome, Firefox, Safari] 51 | - Version: [e.g., 1.0.0] 52 | 53 | **Additional Context:** 54 | Add any other context or details that might be helpful for understanding the issue. 55 | 56 | ### Related Documentation URLs 57 | 58 | **Links:** 59 | If relevant, provide any specific URLs or links to the documentation in question. 60 | 61 | ### Contributor Checklist 62 | 63 | Please make sure that you have considered the following before submitting this documentation issue: 64 | 65 | - [ ] I have checked the project's existing documentation issues to ensure there are no duplicates. 66 | - [ ] I have reviewed the project's CONTRIBUTING guidelines. 67 | - [ ] I understand that submitting a documentation issue does not guarantee immediate updates. 68 | 69 | ### Additional Notes 70 | 71 | **Notes:** 72 | Add any other notes or comments related to this documentation issue. 73 | 74 | 78 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.yml: -------------------------------------------------------------------------------- 1 | name: Feature Request 💡 2 | description: Have any new idea or new feature ? Please suggest! 3 | title: "[Feature] " 4 | labels: ["enhancement", "goal: addition"] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description 10 | description: A clear and concise description of any alternative solution or features you've considered. 11 | validations: 12 | required: true 13 | - type: textarea 14 | id: screenshots 15 | attributes: 16 | label: Screenshots 17 | description: Please add screenshots if applicable 18 | validations: 19 | required: false 20 | - type: checkboxes 21 | id: no-duplicate-issues 22 | attributes: 23 | label: "Checklist" 24 | options: 25 | - label: "I have starred the repository" 26 | required: true 27 | 28 | - label: "I have checked the existing issues" 29 | required: true 30 | 31 | - label: "I have read the discussion tab thoroughly and got the project idea " 32 | required: true 33 | 34 | - label: "I am willing to work on this issue (optional)" 35 | required: false 36 | 37 | 38 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/styles.yml: -------------------------------------------------------------------------------- 1 | --- 2 | name: Style Changing Request 3 | description: Suggest a style designs 4 | title: '[style]: ' 5 | labels: ['enhancement'] 6 | 7 | --- 8 | 9 | body: 10 | - type: markdown 11 | attributes: 12 | value: | 13 | Thanks for taking the time to fill out this template! 14 | - type: textarea 15 | id: style-idea 16 | attributes: 17 | label: What's the style idea? 18 | placeholder: Add descriptions 19 | value: 'We need to improve ' 20 | validations: 21 | required: true 22 | - type: textarea 23 | id: screenshots 24 | attributes: 25 | label: Add screenshots 26 | description: Add screenshots to see the demo 27 | placeholder: Add screenshots 28 | value: 'Add screenshots' 29 | - type: checkboxes 30 | id: terms 31 | attributes: 32 | label: Code of Conduct 33 | description: By submitting this issue, you agree to follow our Code of Conduct 34 | options: 35 | - label: I agree to follow this project's Code of Conduct 36 | required: true 37 | 38 | - label: I want to work on this issue 39 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Related Issue 4 | 5 | Closes #issue_number 6 | 7 | 8 | 9 | ## Description 10 | 11 | 13 | 14 | ## Screenshots (if applicable) 15 | 16 | | Original | Updated | 17 | | :-----------------: | :----------------: | 18 | | original screenshot | updated screenshot | 19 | 20 | ## Checklist 21 | 22 | 23 | 24 | 25 | - [ ] My code adheres to the established style guidelines of the project. 26 | - [ ] I have included comments in areas that may be difficult to understand. 27 | - [ ] My changes have not introduced any new warnings. 28 | - [ ] I have conducted a self-review of my code. -------------------------------------------------------------------------------- /.github/pr-title-checker.json: -------------------------------------------------------------------------------- 1 | { 2 | "LABEL": { 3 | "name": "title needs formatting", 4 | "color": "F9D0C4" 5 | }, 6 | "CHECKS": { 7 | "prefixes": [ 8 | "build: ", 9 | "chore: ", 10 | "docs: ", 11 | "feat: ", 12 | "fix: ", 13 | "perf: ", 14 | "refactor: ", 15 | "revert: ", 16 | "style: ", 17 | "test: " 18 | ] 19 | }, 20 | "MESSAGES": { 21 | "success": "Everything is great. Status: 200", 22 | "failure": "PR title does not confirm to the required format. Please use one of the specified prefixes followed by a colon and a space. Status: 400", 23 | "notice": "" 24 | } 25 | } 26 | -------------------------------------------------------------------------------- /.github/workflows/codeql.yml: -------------------------------------------------------------------------------- 1 | name: 'CodeQL' 2 | 3 | on: 4 | push: 5 | branches: ['main'] 6 | pull_request: 7 | branches: ['main'] 8 | schedule: 9 | - cron: '19 19 * * 0' 10 | 11 | jobs: 12 | analyze: 13 | name: Analyze 14 | runs-on: ${{ (matrix.language == 'swift' && 'macos-latest') || 'ubuntu-latest' }} 15 | timeout-minutes: ${{ (matrix.language == 'swift' && 120) || 360 }} 16 | permissions: 17 | actions: read 18 | contents: read 19 | security-events: write 20 | 21 | strategy: 22 | fail-fast: false 23 | matrix: 24 | language: ['javascript-typescript'] 25 | 26 | steps: 27 | - name: Checkout repository 28 | uses: actions/checkout@v4 29 | 30 | # Initializes the CodeQL tools for scanning. 31 | - name: Initialize CodeQL 32 | uses: github/codeql-action/init@v3 33 | with: 34 | languages: ${{ matrix.language }} 35 | 36 | - name: Autobuild 37 | uses: github/codeql-action/autobuild@v3 38 | 39 | - name: Perform CodeQL Analysis 40 | uses: github/codeql-action/analyze@v3 41 | with: 42 | category: '/language:${{matrix.language}}' 43 | -------------------------------------------------------------------------------- /.github/workflows/greetings.yml: -------------------------------------------------------------------------------- 1 | name: Greetings 2 | 3 | on: [pull_request, issues] 4 | 5 | jobs: 6 | greeting: 7 | runs-on: ubuntu-latest 8 | permissions: 9 | issues: write 10 | pull-requests: write 11 | steps: 12 | - uses: actions/first-interaction@v1 13 | with: 14 | repo-token: ${{ secrets.GITHUB_TOKEN }} 15 | issue-message: 'Hey, @${{ github.actor }} welcome to To-Do-List-Application repository.🎊 Thank you so much for taking the time to point this out.🙌' 16 | pr-message: 'Hey, @${{ github.actor }} welcome to To-Do-List-Application repository.🎊 Thank you so much for taking the effort to make our project better! 🙌 Keep making such awesome contributions!' -------------------------------------------------------------------------------- /.github/workflows/pr-title-checker.yml: -------------------------------------------------------------------------------- 1 | name: 'PR Title Checker' 2 | on: 3 | pull_request_target: 4 | types: 5 | - opened 6 | - edited 7 | - synchronize 8 | - labeled 9 | - unlabeled 10 | 11 | jobs: 12 | check: 13 | runs-on: ubuntu-latest 14 | steps: 15 | - uses: thehanimo/pr-title-checker@v1.3.7 16 | with: 17 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} 18 | pass_on_octokit_error: false 19 | configuration_path: '.github/pr-title-checker.json' 20 | -------------------------------------------------------------------------------- /.vscode/settings.json: -------------------------------------------------------------------------------- 1 | { 2 | "liveServer.settings.port": 5503 3 | 4 | } -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | kritikagupta3003@gmail.com. 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series 86 | of actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or 93 | permanent ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within 113 | the community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.0, available at 119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 120 | 121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 122 | enforcement ladder](https://github.com/mozilla/diversity). 123 | 124 | [homepage]: https://www.contributor-covenant.org 125 | 126 | For answers to common questions about this code of conduct, see the FAQ at 127 | https://www.contributor-covenant.org/faq. Translations are available at 128 | https://www.contributor-covenant.org/translations. 129 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | 2 | ```markdown 3 | # Contributing to the TODO List App 4 | 5 | Thank you for considering contributing to our TODO List App. Your help is greatly appreciated! This guide will help you get started and ensure that your contributions are effective. 6 | 7 | ## Table of Contents 8 | 9 | - [Getting Started](#getting-started) 10 | - [Prerequisites](#prerequisites) 11 | - [Setting up the Development Environment](#setting-up-the-development-environment) 12 | - [Making Changes](#making-changes) 13 | - [Coding Guidelines](#coding-guidelines) 14 | - [Commit Messages](#commit-messages) 15 | - [Testing](#testing) 16 | - [Submitting Changes](#submitting-changes) 17 | - [Review Process](#review-process) 18 | - [Code of Conduct](#code-of-conduct) 19 | - [License](#license) 20 | 21 | ## Getting Started 22 | 23 | ### Prerequisites 24 | 25 | Before you start contributing, ensure you have the following: 26 | 27 | - **Git**: Make sure you have Git installed. [Download Git](https://git-scm.com/). 28 | 29 | - **GitHub Account**: You'll need a GitHub account to make contributions. 30 | 31 | ### Setting up the Development Environment 32 | 33 | 1. **Fork the Repository**: Click the "Fork" button on the top right of the GitHub repository page. This creates a copy of the repository in your GitHub account. 34 | 35 | 2. **Clone Your Fork**: Clone the forked repository to your local machine: 36 | 37 | ```bash 38 | git clone https://github.com/your-username/To-Do-List-Application.git 39 | ``` 40 | 41 | 3. **Navigate to the Project Directory**: 42 | 43 | ```bash 44 | cd To-Do-List-Application 45 | ``` 46 | 47 | 4. **Start the Development Server**: 48 | 49 | ```bash 50 | Click on index.html file in your web browser to start using the application. 51 | ``` 52 | 53 | Now, you have the TODO List App running locally. 54 | 55 | ## Making Changes 56 | 57 | ### Coding Guidelines 58 | 59 | - Follow our coding guidelines to maintain a consistent codebase (link to your coding guidelines document or style guide). 60 | 61 | - Use clear and meaningful variable and function names. 62 | 63 | - Write comments to explain complex sections of code. 64 | 65 | ### Commit Messages 66 | 67 | - Write clear and concise commit messages that describe your changes. 68 | 69 | - Follow the conventional commit format (e.g., "feat: add new feature," "fix: resolve bug"). Learn more about it [here](https://www.conventionalcommits.org/en/v1.0.0/). 70 | 71 | - Use the imperative mood (e.g., "fix," "add," "update") in commit messages. 72 | 73 | 74 | ## Submitting Changes 75 | 76 | 1. **Create a New Branch**: Create a new branch for your changes: 77 | 78 | ```bash 79 | git checkout -b feature/my-feature 80 | ``` 81 | 82 | 2. **Make and Commit Changes**: Make your changes and commit them with descriptive messages. 83 | 84 | 3. **Push Changes**: Push your changes to your GitHub fork: 85 | 86 | ```bash 87 | git push origin feature/my-feature 88 | ``` 89 | 90 | 4. **Open a Pull Request**: Open a pull request on the [main repository](https://github.com/main-repo/todo-list-app) with a clear title and description of your changes. 91 | 92 | ## Review Process 93 | 94 | - The maintainers will review your pull request and may request changes or provide feedback. 95 | 96 | - Once your changes are approved, they will be merged into the main branch. 97 | 98 | ## Code of Conduct 99 | 100 | Please review and follow our [Code of Conduct](CODE_OF_CONDUCT.md) to ensure a respectful and inclusive environment for everyone. 101 | 102 | ## License 103 | 104 | By contributing to this project, you agree that your contributions will be licensed under the [MIT License](LICENSE). 105 | ``` 106 | 107 | This revised CONTRIBUTING.md file provides more detailed explanations and clear steps for potential contributors. Remember to replace placeholders like `your-username`, `your-branch-name`, and `main-repo` with the actual values relevant to your project. 108 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2023 Kritika Gupta 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | 2 | ![image](https://user-images.githubusercontent.com/83400697/207388229-b6463c21-39cb-4926-98b1-b77f3c2790a1.png) 3 | 4 | ![image](https://user-images.githubusercontent.com/83400697/202429157-a953dc00-f32d-4312-862a-1902a628b6ba.png) 5 | 6 | 7 | Join the [discord server](https://discord.gg/JdFsJPrayj) for more discussion: 8 | 9 | # To-Do List Application 10 | 11 | This is a simple yet effective To-Do List Application built with HTML, CSS, and JavaScript. It allows you to manage your tasks and stay organized. You can add, edit, mark as completed, and delete tasks effortlessly. 12 | 13 | ## Tech Stack 14 | 15 | - HTML 16 | - CSS 17 | - JavaScript 18 | 19 | ## Installation 20 | 21 | Clone the repository to your local machine: 22 | 23 | ```bash 24 | git clone https://github.com/Kritika30032002/To-Do-List-Application.git 25 | ``` 26 | Open the index.html file in your web browser to start using the application. 27 | 28 | 29 | ## Usage 30 | 1. Add tasks with a simple click. 31 | 2. Edit task names by double-clicking on them. 32 | 3. Mark tasks as completed by clicking on the checkbox. 33 | 4. Delete tasks by clicking on the trash icon. 34 | 5. Using voice command feature to add, edit and delete task 35 | 36 | Our to-do list application supports voice command for adding tasks effortlessly. Here's how you can use it : 37 | 1. Click on the "Start Voice Command" button 38 | 2. Wait for the application to start listening 39 | 3. Clearly state your task, due date and priority. 40 | 41 | Example prompt for adding task using voice command : 42 | "Add asignment due date 16th Nov priority High" 43 | Example prompt for editing tasks : 44 | "Edit task assignment to a" (will change the task title from assignment to a " 45 | Example prompt for deketing a task : 46 | "Delete task assignment" 47 | 48 | Watch our video for detailed demonstration. 49 | 50 | https://github.com/AishaAgarwal/To-Do-List-Application/assets/107138192/832814c7-cd21-4c85-81ed-e7192c720710 51 | 52 | ## Contributing 53 | Feel free to contribute to this project by creating a pull request. We welcome any improvements, bug fixes, or new features. 54 | 55 | ## Why & How to contribute? 56 | - If you find any bugs then please report them by creating an issue. 57 | - If you can make a website look good by modifying then go ahead and describe it in issue and create pull request. 58 | - If you can add more functionality, then create an issue and contribute by making pull request. 59 | 60 | 61 | 62 | 63 | ## Thanks to all Contributors 💪 64 | 65 | 66 | 67 |
68 | Thanks a lot for spending your time.
69 | Keep rocking 🍻
70 | Also Give it a Star 🌟, If you loved contributing to the project. 71 | 72 | ## [MIT Licensed](https://github.com/Kritika30032002/To-Do-List-Application/blob/main/LICENSE) 73 | -------------------------------------------------------------------------------- /Roboto_Slab.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Kritika30032002/To-Do-List-Application/d7f1ffa5d3346f2de6adab81eea5161b99b9735c/Roboto_Slab.zip -------------------------------------------------------------------------------- /images/to-do-list.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Kritika30032002/To-Do-List-Application/d7f1ffa5d3346f2de6adab81eea5161b99b9735c/images/to-do-list.png -------------------------------------------------------------------------------- /images/todoWhite.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Kritika30032002/To-Do-List-Application/d7f1ffa5d3346f2de6adab81eea5161b99b9735c/images/todoWhite.png -------------------------------------------------------------------------------- /index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 15 | 16 | 19 | 20 | 21 | 22 | To-Do List 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 |
32 | 33 |
34 |
35 | 36 | 37 |
38 | 39 |
40 |
41 |

42 |
43 | 44 | 45 | 46 | 47 |
48 | 66 |
67 | 68 | 69 | 70 |
71 | 72 | 73 | 74 |
75 | 76 | 77 | 78 |
79 |
80 |
81 | 82 |
83 |

Confirmation

84 |
Are you sure you want to delete this task?
85 | 86 | 87 |
88 |
89 | 90 | 91 |
92 |
93 |
94 | 95 |
96 |

Alert

97 |
This task is already present
98 | 99 |
100 |
101 | 102 | 103 | 104 |
105 |
106 |
107 | 108 |
109 |

Confirmation

110 |
Are you sure you want to delete this task?
111 | 112 | 113 |
114 |
115 | 116 | 117 | 118 |
120 |
121 | 122 |

123 |

Simply add 124 | your tasks here

125 |
126 |

Add your tasks below :

127 | 128 | 129 |
130 | 131 | 132 | 134 | 135 | 136 | 138 | 139 | 140 | 149 | 150 | 151 | 152 | 154 | 157 |
158 | 159 | 160 |
161 | 162 | 195 |
196 |
197 |
198 | 199 |
200 | 201 |
202 |

203 | Why Simply Tasked?

204 |

206 | 207 | Simply, because it is a SIMPLE To-Do List Tool to organize your tasks 208 | efficiently. 209 |

210 |
212 |
    213 |
  • Intuitive task management
  • 214 |
  • Seamless due date tracking
  • 215 |
  • Beautiful and user-friendly design
  • 216 |
217 |
218 |
219 |
220 |
221 | 222 | 223 | 224 | 225 | 227 | 228 | 244 | 277 | 278 | 279 | 280 | 281 | 288 | 289 | 290 |