-
Notifications
You must be signed in to change notification settings - Fork 1
Project guidelines
This project will be a "boilerplate" for node.js web applications.
choose modules to use and do the work to set it all up.
a good set of tools in place to help start a project
It will be pre-configured and documented so that people can learn from it. organize and show examples of how middleware will be used.
javascript and coffeescript are welcome
other boilerplate and modular examples
Here is a skeleton application that is preconfigured for a particular stack: https://github.com/datapimp/backbone-express-mongoose-socketio
also drumkit plugin example
other "non-framework"
derby
Design decisions
architecture for a general app/framework driven by our own application requirements and typical nodejs uses
use an existing framework quick and complete, lots of problems solved, many still to solve
Good applications for Node.js soft real-time aka DIRT, events, streams, websockets loosely coupled clients, servers, and services
vs best of breed 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)
API first based on APIkit, including model sync by push publish API docs clients use our public API
proxy to web APIs, one among many treat storage as a service API accounts are just APIs
move processing to client while server coordinates share code on server and client, browserify, jsdom
apps are loosely coupled CORS site served from github, js request from atlantanodejs.org offline local store, sync
multiple hosts (even as mesh) vps and git push sevaa no.de (inode) vps (anode) aws
multiple clients mobile and desktop web clients We'll create some basic models, views, etc.
backbone browserify (you just told me about this)
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.