xet7 is also current maintainer of Wekan. This KanRule is a fork of another MIT licensed Open Source Kanban board, just to see can it be made usable enough. You can send pull requests to this project. There is no CLA required for contributing.

I do React consulting and this is a showcase product I've built in my spare time. It's a very good example of modern, real-world React codebase.

There are many showcase/example React projects out there but most of them are way too simple. I like to think that this codebase contains enough complexity to offer valuable insights to React developers of all skill levels while still being relatively easy to understand.

• Proven, scalable, and easy to understand project structure
• Written in modern React, only functional components with hooks
• A variety of custom light-weight UI components such as datepicker, modal, various form elements etc
• Simple local React state management, without redux, mobx, or similar
• Custom webpack setup, without create-react-app or similar
• Client written in Babel powered JavaScript
• API written in TypeScript and using TypeORM

• Install postgreSQL if you don't have it already and create a database named kanrule_development.
• git clone https://github.com/KanRule/KanRule.git
• Create an empty .env file in /api, copy /api/.env.example contents into it, and fill in your database username and password.
• npm run install-dependencies
• cd api && npm start
• cd client && npm start in another terminal tab
• App should now be running on http://localhost:8080/

• Set up development environment
• Create a database named kanrule_test and start the api with cd api && npm run start:test
• cd client && npm run test:cypress

There are features missing from this showcase product which should exist in a real product:

We're currently using TypeORM's synchronize feature which auto creates the database schema on every application launch. It's fine to do this in a showcase product or during early development while the product is not used by anyone, but before going live with a real product, we should introduce migrations.

We currently auto create an auth token and seed a project with issues and users for anyone who visits the API without valid credentials. In a real product we'd want to implement a proper email and password authentication system.

Not all components have properly defined aria attributes, visual focus indicators etc. Most early stage companies tend to ignore this aspect of their product but in many cases they shouldn't, especially once their userbase starts growing.

Both Client and API are currently tested through end-to-end Cypress tests. That's good enough for a relatively simple application such as this, even if it was a real product. However, as the app grows in complexity, it might be wise to start writing additional unit/integration tests.

• Website: https://kanrule.com/
• Email: [email protected]

1. Original Author: Ivor Reic ✍️

• Repo: https://github.com/oldboyxx/jira_clone
• Website: https://getivor.com/
• Skype handle: ivor.reic 💬

2. https://github.com/FauxJira/FauxJira

MIT