NodeJS => running a server
npm => managing packages installed on server
bower => managing client-side frameworks
git => version control
github => version control
browser => get familiar with Developer Tools on you browser
git pull <remote> <branch-name>
npm install
bower install
npm start or node[mon] ./bin/www
bin
| - www => starting point
node-modules => a list of the modules is in package.json, under dependencies
public
| - css => css stylesheets live here
| - | - style.css => general style, used by all pages
| - | - page-style.css => only used by 'page'
| - img => images live here
| - js => javascripts live here (this excludes angular stuff)
| - lib => bower installed stuff live here
| - modules => angular modules live here
| - | - module-name
| - | - | - controllers => all controllers of this module live here
| - | - | - services => all services or factories of this module go here
| - | - | - app.js => where module and routes are defined
| - partials => partial html files needed by angular view live here
routes => each root url route would ideally have its own .js file defined here
views => the html files rendered by the server (using HoganJS)
.bowerrc => configuration file for bower
app.js => this is where the server puts most of the ish together
bower.json => file for managing bower installed components
config.js => this is where we define variables or values we want available to everyone
events.json => randomly generated info about events, for demo purposes. Should move ASAP
package.json => file for managing npm installed modules