All files from the /src/ directory are compiled into /dest/. You never update anything in /dest/ directly, but build and serve up its contents from /src/ using the scripts in /build/.

There are five main tasks that Grunt accomplishes:

• Content files are read from /src/content/ and templated by the files in /src/templates/. This just lets you have one common template for the site header, for example, and reuse it across multiple content files. Content is also templated a second time into the tmp folder as JSON instead of HTML. This is concatenated into /dest/projects.json and used to build an index instead of a simple, manually-curated list.
• Styles LESS files are processed from /src/styles/ into /tmp/. The results are then appended onto any other *.css files in /src/styles/ into /dest/prod.css. That file is then run through postCSS. Lastly, the results are minified into /dest/prod.min.css.
• Scripts Any javascript files in /src/scripts/ are concatenated into a single file in /dest/prod.js. That file is then uglified into /dest/prod.min.js.
• Assets Any supporting images, libraries, fonts, or other files are copied verbatim from /src/assets/ into /dest/assets/.

Additionaly, build scripts in /build/grunt/ are used by Gruntfile.js to configure all those tasks. Most notably, /build/grunt/grunt-template.js will likely need updates per project to identify the variable names for the various templates.

You can serve up the site compiled by grunt using Express. Running either node main or npm start will run an express server on port 3000 (by default, using an environmental value for potential Hotel use). The express server serves up files from /dest/ using express.static().

The subtree syntax and prefix is a little tedious and error-prone to type out every time, so you can npm run deploy to git subtree push --prefix dest origin master.