-
Notifications
You must be signed in to change notification settings - Fork 1
Getting started
victorkane edited this page Jul 11, 2011
·
16 revisions
##Intro
For the very initial As a writer i can work on my texts we wanted simple user actor text object CRUD functionality with content shunted to a simple auth protected /textstream, as dealt with in User Story issue #7.
##Screens
An outline of the screens:
- / (login/join/splash)
- /textview (on successful login)
- /text/:id
- /text/:id/edit
- /user/:id
- /user/:id/edit
- /text/:id/edit
- /text/new
- /text/:id
- /join
- /textview (on successful login)
##Analysis & Design
- biz objects
- user
- session (express example)
- text
- textview (list of texts)
- user
In this initial implementation we thought to base ourselves on 3 express examples, just as a first KISS
- auth
- session
- route-separation
But the express blog example is much better!!! So we move onto that!
##Implementation See commits for incremental implementation