Tiny Trello is a very light-weight version of the popular project management software Trello. In Tiny Trello, there is only one "Board", with many lists. This board is loaded by default each time you load the app, without any authentication or persistence.
If you're familiar with Trello, most of this should be pretty obvious. This is a very dumbed-down version, and the requirements are listed out below. There are also example wireframes in docs/wires.pdf which you might find helpful.
IMPORTANT You should implement this as an Ember.js app. If you haven't used Ember before, you may find it helpful to read through the Getting Started, and maybe work through the tutorial as well, available in the Ember Guides.
- The default state of the app should be a board with one, empty list named "Default List"
- There is no authentication necessary, anyone visiting this app should automatically see the "Default List"
- There is no persistence. Reloading the app should reset to the default state
- A user can add an item to the list by clicking the "Add an item" link at the bottom of the list (see the examples in docs/wires.pdf).
- A user can add a list by clicking the "Add a list" link to the right of the last board (see the examples in docs/wires.pdf).
- Clicking an item in a list opens a modal window with a "detail" view of the item that was clicked. This includes the title and a description. (see docs/wires.pdf)
- An item's Title and Description are editable in-line in the detail view described earlier
- Clicking "Close" from the detail view closes the detail view (see docs/wires.pdf)
- Clicking "Delete" from the detail view asks for confirmation and, if approved, deletes the item.
- It is not required to implement drag/drop for reordering items or lists.
It is completely acceptable to use plain old Ember.Objects and a default state consisting of a 1-element Array. Or, you can use Ember Data with ember-cli-mirage to stub out an actual API endpoint. If you're really feeling ambitious, you can implement the actual api in whatever language you'd like -- just make sure to include instructions on how we can run this locally when testing it out.
As for styling, this can look however you'd like. We're looking at how you are able to approach a new problem with a new technology, given a fairly stable base of JavaScript knowledge. That said, you have the freedom to apply any styling that you'd like -- have fun with it!
Feel free to reach out to us with any questions you might have. If you feel stuck and want some help, send us a note and we'll share a skeleton of a solution for this that you can use for inspiration.