Now lets look through the contents of your site directory:
| build | Output directory. Stark will create it if it is missing. |
| bower_components | Bower components. Optional. Used when finding components. |
| lib | Local components. Optional. Used when finding components. |
| node_modules | Node components. Optional. Used when finding components. |
| pages | Pages. Optional. |
| static | Static files. Optional. |
You will find the compiled pages, scripts, styles and other files here. Directory contents should look like this:
| index.html | Home page created from index.mpc |
| static/ | Files copied over from static/ |
| static/ style.css | CSS style built from requirements of index.mpc |
| static/ script.js | JavaScript modules build from requirements of index.mpc |
| somepage/ index.html | Page created from pages/somepage.mpc |
These directories are added to include path. Stark will search for requirements in these directories.
You should put your own templates, widgets, JS modules into lib. You should try installing third party libraries with bower and npm when available.
Directory for your page components. pages/yourpage.mpc will be used to generate build/yourpage/index.html .
The contents of this directory are recursively copied to build/static/.