pages #

An unofficial sidekick for AngularJS / (and optionally) Node.js applications. _It's a developer's framework._

Pre-reqs ##

Just make it so.

1. OSX
1. Node.js, version 0.10.12.
1. Ruby For Terminal Notifier
1. Java For node-minify
1. Terminal Notifier

Also, because Pages manages Bower assets for you (and thus interacts with the filesystem), you'll probably want to run ulimit -n 10000 or face the error Error: spawn EMFILE.

Install ##

``
sudo npm install -g pages
`

_Note:_ Pages doesn't require any dependency _but itself_ to be installed globally.

Usage (simple) ##

Pages has a CLI; it's how you use it!

What can you do with Pages?

`
pages help
`

_todo_ Add help when finished.

Create a Pages application:

`
pages generate --type=app --name="My Pages App"
`

This generates a non-compiled application from a default or configured skeleton.

_Note:_ The name option is sanitized to my-pages-app.

Run, compile, and watch for changes in a Pages application for development:

`
cd my-pages-app
pages run --port=3000 --browser=chrome
`

This runs the Pages application compiler on port 3000, watching for changes to CoffeeScripts, Jade templates, and dependencies; Google Chrome's first browser tab is automatically refreshed after bundling (compiling/downloading assets).

_Note:_ By default (not specifying the option), Pages runs applications on port 80. If you do not have access to port 80, it will hang.

Compile/concat/minify/run a Pages application for production:

`
cd my-pages-app
pages start --port=3000 --browser=chrome
`

_Note:_ The same default port assignments apply from the CLI command pages run`, but a specified browser will refresh just _once_ after the build is done.

_See the wiki for more!_