diff --git a/.eslintignore b/.eslintignore
index d8b83df9..483a9c42 100644
--- a/.eslintignore
+++ b/.eslintignore
@@ -1 +1 @@
-package-lock.json
+package-lock.json
\ No newline at end of file
diff --git a/.husky/.gitignore b/.husky/.gitignore
new file mode 100644
index 00000000..31354ec1
--- /dev/null
+++ b/.husky/.gitignore
@@ -0,0 +1 @@
+_
diff --git a/README.md b/README.md
index b8108178..16b08df1 100644
--- a/README.md
+++ b/README.md
@@ -1,380 +1,52 @@
-`#react.js` `#master-in-software-engineering`
-
+# React To Do List
+Basic to do list with friendly UI, using react, local storage
+and bootstrap.
-[](#contributors-)
+## Appendix
-
+Any additional information goes here
-# Assembler School: React.js Todo List
-
-In this project you will learn how to create a React.js todo list.
-
-## Table of Contents
-
-- [Getting Started](#getting-started)
-- [The Project](#the-project)
-- [Project requirements](#project-requirements)
-- [Project delivery](#project-delivery)
+- [Documentation](#documentation)
+- [Lessons Learned](#lessons-learned)
- [Resources](#resources)
+- [Links](#links)
+## Documentation
-## Getting Started
-
-These instructions will get you a copy of the project up and running on your
-local machine for development and testing purposes.
-
-See deployment for notes on how to deploy the project on a live system.
-
-### The repository
-
-First, you will need to `clone` or `fork` the repository into your Github
-account:
-
-
-
-```
-$ git clone https://github.com/assembler-school/reactjs-todo-list.git
-```
-
-## Contents and Branches Naming Strategy
-
-The repository is made up of several branches that include the contents of each
-section.
-
-The branches follow a naming strategy like the following:
-
-- `main`: includes the main contents and the instructions
-- `assembler-solution`: includes the solution
-
-### Fetching All the Branches
-
-In order to fetch all the remote branches in the repository, you can use the
-following command:
-
-```sh
-$ git fetch --all
-```
-
-### List Both Remote Tracking Branches and Local Branches
-
-```sh
-$ git branch --all
-```
-
-Then, you can create a local branch based on a remote branch with the following
-command:
-
-```sh
-$ git checkout -b
-```
-
-### Installing
-
-First, you will need to install the dependencies with: `npm install`.
-
-Run the following command in your terminal after cloning the main repo:
-
-```sh
-$ npm install
-```
-
-### Running the Tests
-
-The tests that validate your solution can be executed by runing the following
-commands:
-
-#### 1. Run the development server
-
-```
-$ npm run start
-```
-
-#### 2. Run the Cypress tests with the graphical test runner
-
-```
-$ npm run cy:open
-```
-
-#### 3. Or you can run the Cypress tests from the terminal
-
-```
-$ npm run cy:run
-```
-
-Both need the Create React App development server to be running.
-
-### Git `precommit` and `prepush` Hooks
-
-In the `assembler-solution` branch you can see an implementation of these tools
-if you'd like to use them.
-
-## Deployment
-
-In this pill we won't deploy the app.
-
-## Technologies used
-
-- `React.js`
-- `@testing-library/react`
-- `eslint`
-- `prettier`
-- `lint-staged`
-- `husky`
-
-## The Project
-
-In this project you will build a todo app similar to the following screenshot.
-
-
-
-## Project requirements
-
-This is an overview of the main requirements of this project. The exact ones are
-found in the doc that the academic team will provide you.
-
-- You must follow all the instructions of the project step-by-step
-- You should always try to solve them by yourself before asking for help
-- You should always help your team members and fellow students of the master so
- that you can all learn together and become better software developers and team
- members
-- You must finish all the steps that are marked as `Required`
-- **You must use semantic HTML5 elements for all the markup of the application**
-- Once you are done, you can move on to the optional ones that are marked as
- `Extra 💯`
-
-### 1. Styles and Layout
-
-For this step you have to think of a layout for the app.
-
-1. You **must** use `SCSS` for all the styles of the app and the
- [classnames](https://github.com/JedWatson/classnames#readme) npm package to
- handle any conditionally set classes
-2. The overall layout must be a pixel perfect copy of the design we provide
-3. The layout must be responsive so that it works in all device sizes
-
-### 2. Show All the Todos
-
-In this step you must implement the logic to render all the todos of the app.
-This means that all the todos are rendered without taking into account if they
-are completed or not.
+-[Original repo]( https://github.com/assembler-school/reactjs-todo-list )
-1. **The todos must be created in the `App` component and passed as props to the
- page components**
-2. **All the methods that modify the `` state must also be passed as
- props**
-3. If there are no todos created you must render a message telling the user that
- they can create their first todo to get started
-4. You can also render an illustration that indicates users that they can create
- a todo to get started
- 1. Feel free to create your own or use one from the internet, this is a great
- resource: [undraw.co](https://undraw.co/illustrations)
- 2. For this step, you will need to add a `data-testid="no-todos"` property on
- the html component that is rendered as the illustration or the
- illustration wrapper.
+
+## Lessons Learned
-### 3. Creating Todos
+- Use React
+ -to use props and states
+ -to organice and structure components 😭
-#### Step 1
+- To work in peer coding
-Users must be able to create a new todo using the form in the app header
+- Use SASS with React
-1. To test the todo creation requirement you will need to add a
- `data-testid="create-todo-input"` property on the input element
-2. If the user presses enter without entering a value in the todo form, an
- error message should be rendered. The message needs to have a
- `data-testid="create-todo-error-message"` property with the following error
- message: `"Please enter at least one character"`
-3. Users must be able to press the `enter` key on their keyboard to create the
- todo (if you implement it using semantic html5 this comes for free)
-
-#### Step 2
-
-Once the todo is created it must be rendered in the list bellow the form.
-
-1. By default the list should be empty.
-2. The list must be implemented using `ul` and `li` elements.
-3. To test the todo creation requirement you will need to:
- 1. add a `data-testid="todos-list"` property on the `ul` list element.
- 2. add a `data-testid="todo-item"` property on the `li` list element.
- 3. the `li` list element should have a text content of the todo that was
- created and the `checkbox` value set to `checked` or not depending on if
- the todo was marked as completed.
-
-#### Step 3
-
-Render the total number of todos in the app footer.
-
-The footer should have a property of: `data-testid="app-footer"` and be
-implemented using an html5 `footer` element.
-
-1. To test this requirement you will need to render the total number of todos
- that the app has, that is both completed and incomplete todos.
-2. The text rendered should be:
- 1. `0 todos left`: if there are no todos
- 2. `1 todos left`: if there is only 1 todo
- 3. `12 todos left`: if there are 12 todos in the app
- 4. etc
-
-### 4. Editing Todos
-
-Users must be able to edit the todos once they are created.
-
-1. Clicking the todo name should open a form that allows users to edit the todo
- name.
- 1. This can be implemented either in line or by filling out the new todo form
- with the details of the todo that was clicked
- 2. The todo item should have a property of `data-testid="todo-item-input"`
- 3. We recommend that you implement a solution that allows users to edit the
- todo in line. This means that clicking the todo name replaces the todo
- with a form that has a value of the todo's name
- 4. Then, by clicking on the done button or by pressing enter, the todo is
- edited and saved
-2. Users should be able to delete todos by clicking the `X` button that is
- rendered when users hover over the todo name
- 1. the `X` button should have a property of
- `data-testid="todo-item-delete-button"`
-3. Users must be able to mark a todo as completed when they press the `Done`
- button that is rendered when the user hovers over the todo name
- 1. the `X` button should have a property of
- `data-testid="todo-item-checkbox"`
-
-### 5. Filtering Todos
-
-In this step you will create a page for each todo type.
-
-In order to allow users to navigate to a page you will need to complete the
-footer of the app that you can see in the screenshot above.
-
-You will have to render the following in the footer:
-
-1. The total count of all the `active` todos
-2. A link to the home page that renders `all` the todos, **both active and
- completed**
-3. A link to the active todos page that renders the `active` todos
-4. A link to the completed todos page that renders the `completed` todos
-
-#### 5.1 All Todos
-
-- Route: `/`
-- Page Component: `Home`
-
-In this page you will render all the todos, both completed or not.
-
-#### 5.2 Completed Todos
-
-- Route: `/completed`
-- Page Component: `Completed`
-
-In this page you will render all the **completed** todos.
-
-You will need to think of a way to store or filter the todos that are completed.
-
-A possible solution is to use `[].filter` or to store the todos in a different
-`this.state` property.
-
-Feel free to think of a solution for this requirement.
-
-#### 5.3 Active Todos
-
-- Route: `/active`
-- Page Component: `Active`
-
-In this page you will render all the **active** todos, that is, all the todos
-that are not completed.
-
-You will need to think of a way to store or filter the todos that are active.
-
-A possible solution is to use `[].filter` or to store the todos in a different
-`this.state` property.
-
-Feel free to think of a solution for this requirement.
-
-### 💯 Extras
-
-#### 1. Store the todos in `localStorage`
-
-All the todos are stored in `localStorage` so that users can refresh the app and
-their previous todos are not lost.
-
-You must store the todos in a single local storage entry named:
-`"reactjs-todo-list"`.
-
-The todos should be stored using the following shape (you can add other
-properties but these are required):
-
-- `id`: the id of the todo
-- `text`: the text content of the todo
-- `done`: boolean that indicates wether the todo is completed or not
-- `isEditing`: boolean that indicates wether the todo is currently being edited
-
-```js
-[
- {
- id: "9c34e805-7bfc-401a-b386-468c25315e46",
- text: "todo 01",
- done: false,
- isEditing: false,
- },
- {
- id: "d733a37e-cc4e-4cde-916f-935b3e915bb3",
- text: "todo 02",
- done: false,
- isEditing: false,
- },
-];
-```
-
-#### 2. Clear all the Completed Todos
-
-Users must be able to clear all the todos that are completed. You can implement
-a button in the app footer that allows users to clear the completed todos.
-
-The clear completed todos button should have a property of
-`data-testid="clear-completed-todos"`.
-
-#### 3: Light & Dark Mode Switch
-
-You can implement a light & dark mode switch that can be toggled using the moon
-icon in the app header.
-
-The light & dark mode switch button should have a property of
-`data-testid="toggle-theme"`.
-
-## Project delivery
-
-To deliver this project you must follow the steps indicated in the document:
-
-- [Submitting a solution](https://www.notion.so/Submitting-a-solution-524dab1a71dd4b96903f26385e24cdb6)
+- To design friendly UI with bootstrap
+
## Resources
-- [react-testing-library](https://testing-library.com/docs/react-testing-library/intro/)
-- [reactjs.org](https://reactjs.org/)
-
-## License
-
-This project is licensed under the MIT License - see the [LICENSE](LICENSE) file
-for details
-
-## Contributors ✨
+- [WEBPACK](https://webpack.js.org/concepts/)
+- [SASS](https://sass-lang.com/guide)
+- [REACT](https://es.reactjs.org/)
+- [BOOTSTRAP](https://getbootstrap.com/docs/4.6)
-Thanks goes to these wonderful people
-([emoji key](https://allcontributors.org/docs/en/emoji-key)):
+## Authors
-
-
-
-