-
Notifications
You must be signed in to change notification settings - Fork 1
Design guidelines
Architecture for a general app/framework, driven by our own application requirements and typical nodejs uses.
(whatever those may be)
soft real-time aka DIRT, events, streams, websockets
loosely coupled clients, servers, and services
learn, use, decide, know the options
architecture thinking for solutions the framework doesn't handle
an un-framework, loosely coupled, tuned to each application
keep alternatives open, opinions loosely held
popular module choice with good reasons
weight to readable quality code, supports various approaches (or small single purposed, swappable)
An existing framework is quick and complete if there is a good fit. For a variety of applications, we need the flexibility of a component approach.
based on APIkit, including model sync by push
publish API docs
clients use our public API
treat storage as a service API
accounts are just APIs
move processing to client while server coordinates
browserify, jsdom
CORS site served from github, js request from atlantanodejs.org
offline local store, sync
vps - sevaa, aws
git push - no.de, ...
mobile and desktop web clients
backbone
We'll create some basic models, views, etc. I want to go a step further and create some simple views with some basic css that people can build off of. A big part of Node is going to be with mobile web and desktop web. We should make that core to this project.
We'll use a nice grid css and boiler plate html 5 so it's not that difficult. We are building off of other people.
##Other examples of boilerplate and modular frameworks
https://github.com/datapimp/backbone-express-mongoose-socketio
drumkit plugin approach
other "non-framework"
derby