Using the conventional commits
- We stick with React
- We use Typescript to type and reduce the risk of failures when it is necessary to scale the software
- We use viteJS to facilitate building and production, taking webpack from the project, we gained in transpilation speed compared to the WebPack bundle
- Used bootstrap to facilitate responsiveness and faster styling and following a clear and objective pattern for those who will maintain the code in the future
- ReactJS was chosen because it is a widely used framework, with a simple ecosystem, easy maintenance, extensive documentation in the developer community, excellent scalability
- The MVC like design pattern was used due to the ease of implementation, extensive knowledge of the developer community
- Local persistence of data was chosen for the ease of implementation and can be readily replaced by any database, relational/non-relational
- The project is under MIT license (free)
- Feature: A technical documentation in Markdown will be produced for ease of use/improvement by other developers, but, basically you set
yarn installand after thisyarn buildoryarn run build, if is necessary running the code on localhost do you need typingyarn dev.
—————————————————
extra feature
- Added Dark/White mode button (initial attempt to implement accessibility/visual comfort)
—————————————————
Future features (after the end of the course)
- Multi-user login system (social and Sign Up authentication [email registration])
- Database Refactoring
- Color system by Card and Task
- Alert for a number greater than 4 lanes created (in order to alert the user that the process is making the process less agile)
—————————————————
issues
- The tasks type of issues will be opened on demand, during testing or at deployment

