Make sure you put your code in the correct spot or the Grues will eat your face.
Any documents relevant to developing the website should be put in this folder
This is where the application logic belongs. The controllers that render the website should be as thin as possible with all logic in the files located here. By doing this then all the logic of the application can be unit tested.
Any content placed in this folder will be served as static files.
In the interest of keeping things neat please put all graphics used in the template/theme of the website in this folder
This folder holds the Stylus files which
are used to generate the CSS files. If the filename is
foo.styl then a request
foo.css will cause
foo.styl to be processed and outputed to
which is then served in subsequent requests.
This folder contains the controller code. As noted above, these controllers
should be fairly thin. The
index.js file in this folder has a
that sets up all the routes.
This folder contains all the test items
This folder contains the client side QUnit tests
This folder contains the Nodeunit unit tests for server code
This folder contains the integration tests for the server
This folder contains the views for rendering. The
layout.jade file is the
master template which exposes blocks for the other templates to render.
This is the config file for the application. The file is in the gitignore so
if you wish to commit changes use the
-f option when adding it to your commit.
Make sure that no keys or secrets are stored in this file, all such data should
come from environment variables set on the server.
This is the launching point for the application. Anything that is outside of
configuring the application does not belong here. If it's not configuration then
it can be tested, and testable things should be in the
Grunt file for automation.