Work in process...
This is a single page application.
The technical plan is showed below
Used for Backend and Frontend Models
General layout
ID_user ID_post ID_comment ID_image ID_tag userName FK_user FK_post FK_post FK_tagList pwd FK_user FK_post email accessLvl
Likes ? post or comments ? Brand surveys ?
How are we gonna handle the tags list ? Can your ruby plugin take care of creating dynamic tags that are not doubled and with an Identifier ?
Build upon backbone MV* structure Possibility of adding Backbone plugins
- PageView
a) HeaderView
i) MenuView
ii) LoginView
b) BrandView
i) GraphView
ii) Surveys/Contest Views
c) HomeView
i) PostViews
- SearchView ii) InfiniteScrollView d) DashBoardView i) CRUD view e) FooterView
Each table represent a model with their attributes They are nested that is
- User Model a) Collection of Post models i) Collection of tag models ii) Collection of Comment models iii) Collection of Image models
Those are models groupment
- User collection
- Post collection
- Tag Collection
- Image Collection
For the main sub-apps
- #home
- #dashboard
- #brand
For the RestFul API Design
POST-PUT-DELETE-GET
- user/:id
- post/:id
- comment/:id
- image/:id
- tag/:id
Each view also will have events attached Those views will also listen to the model changes
Each view requires a design
...