A digital Kanban board made with React
"The Kanban technique emerged in the late 1940s as Toyota’s reimagined approach to manufacturing and engineering. ... The system’s highly visual nature allowed teams to communicate more easily on what work needed to be done and when. It also standardized cues and refined processes, which helped to reduce waste and maximize value." - via LeanKit.com
Build a Digital Kanban board using:
- React for building the front-end User-Interface (UI)
- HTML and CSS (via sass)
- Express as the Server
- Bookshelf.js as your ORM for the Postgresql Datastore.
Cards contain information about a task.
A Card has 6 properties:
- A unique identifier, e.g. "1", "2", "313".
- A Title
- A Body (task details)
- A priority selection (Low, Medium, High, Blocker)
- A status, the status of a card. Should match the column the card can be found in. Columns: "Queue", "In Progress", or "Done".
- A "Created by" field. This should display name of the person who created the task.
- An "Assigned to field". This should display the name of the person who is currently working on the task.
There should be a form which is used to create a new Card. When a card is first created we need minimal information, the information needed is:
- Title (String)
- Priority (Low, Medium, High, Blocker)
- Created By (Full Name)
- Assigned To (Full Name)
All other fields are not needed when creating a new Card. The other fields: "Unique Identifier", and "Status" fields will be automatically added by the application.
When a Card appears in a column there should be a way (something clickable?) to move that card to either the next or previous column.
Columns contain Cards and each column is a collection of Cards that share the same status.
The board you will building will have 3 columns:
- Queue
- A card will automatically appear in this column after creation.
- In Progress
- When a card is being worked on it should be displayed in this column.
- Done
- When work has finished on a card it should be displayed in this column.
caveat: do not try to implement click-and-drag just yet, save it as a stretch goal!
A Kanban board contains multiple Columns (and Columns contain Cards). This is the main application component. It is responsible for retrieving data and passing it down to other child components.
| Property | Type | Options |
|---|---|---|
| id(Pk) | number | serial, not null, unique |
| title | string(255) | not null |
| body | string(1024) | not null |
| priority_id(Fk) | number | not null |
| status_id(Fk) | number | not null |
| created_by(Fk) | number | not null |
| assigned_to(Fk) | number | nullable |
| created_at | TS w/ TZ | not null |
| updated_at | TS w/ TZ | not null |
| Property | Type | Options |
|---|---|---|
| id(Pk) | number | serial, not null, unique |
| first_name | string | not null |
| last_name | string | not null |
| string | not null, unique | |
| created_at | TS w/ TZ | not null |
| updated_at | TS w/ TZ | not null |
| Property | Type | Options |
|---|---|---|
| id(Pk) | number | serial, not null, unique |
| name | string | not null |
| rank | number | not null |
| created_at | TS w/ TZ | not null |
| updated_at | TS w/ TZ | not null |
| Property | Type | Options |
|---|---|---|
| id(Pk) | number | serial, not null, unique |
| name | string | not null |
| rank | number | not null |
| created_at | TS w/ TZ | not null |
| updated_at | TS w/ TZ | not null |
- Rank determines the position of the Priorities and Statutes when display in either a drop down input or when displaying columns by Statuses.
Build an Express server which will serve your routes, index.html, and static assets.
PostgreSQL and Bookshelf ORM. Create a UML Schema for your database, consider LucidChart. Add these diagrams to your project.
Make It Pretty!™
Your server will have these routes:
- RESTful API endpoints to create, read, update, and delete kanban cards for your application.
- RESTful API endpoint to retrieve and update users to be shown when choosing an assignee while creating a new kanban card.
- Remember to use MVC architecture: Models, Views, Controllers!
- You will use
react-routerto add FE routes to the application.
| route | action |
|---|---|
| / | Show the kanban board |
- Figure out how to use
react-routerto add FE routes to the application.
| route | action |
|---|---|
| /admin/users | Show a listing of users of the board |
| /admin/users/:id | User account page |
| /admin/users/:id/edit | Show form to let user update information |
| /admin/priorities/ | Show list of current priorities |
| /admin/priorities/new | Show form to add new Priority |
| /admin/priorities/:id/edit | Show form to update selected Priority |
| /admin/statuses/ | Show list of current statuses |
| /admin/statuses/new | Show form to add new Status |
| /admin/statuses/:id/edit | Show form to update selected Status |
-
Add drag and drop functionality
-
Full Authentication System on Frontend and Backend
-
Users creation using a register page and route.
-
User can delete their account from their our user account page. Users can only delete their own account and deleting an account must update any cards assigned to them.
- create a desktop and mobile view. Tablet view is not needed (possible stretch goal).
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify