This example simply looks at an alternative approach to organising an Ampersand application. I personally dislike having all of the application views, models, etc organised into single folders. I prefer instead to structure applications into small modules based on functionality e.g. login
, home
, etc. An interesting post by @hij1nx demonstates that Node's require algorithm can applied to any directory called node_modules
, not just the one at the root of your project, led me to re-structure an Ampersand application (based on the Ampersand examples). Thanks to @simmelj and his blog post for the inspiration.
- All modules are organised into
src/node_modules
. - Each module contains a directory for it's
templates
. - Each module contains a directory for it's
styles
. - Each module contains a
package.json
(see here for explanation). moonbootsConfig.js
contains updated templatizer logic to process templates stored in different module locations (globbing would be nice :P).- Global Stylus styles are organised into
src/styles
. - Static assets are organised into
src/assets
.
cd folder-name
npm install
npm start