StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<h2>Re: Build vs Source</h2> <p>It sounds like you're already familiar with grunt. You may want to consider looking into the <a href="https://github.com/h5bp/node-build-script" rel="nofollow">grunt node-build-script plugin</a>.</p> <p>It adds a number of new tasks, notably <code>grunt mkdirs</code> and <code>grunt copy</code> which duplicates your project directory into a separate staging folder and then copies your optimised project into a publish folder. If I'm not mistaken, this is what you mean by keeping an 'untouched' version of your source files?</p> <p>Running <code>grunt server</code> will then serve up the contents of your publish files on localhost. You could always point your web server to your initial project directory if you want to examine your application in its unoptimised state.</p> <p><code>node-build-script</code> adds a bunch of other super convenient tasks, such as image optimisation, automatic file revving and substitution. It's incredibly easy to use and super customisable.</p> <p>I have a <a href="https://github.com/robinpyon/h5bp-grunt-project" rel="nofollow">basic single page template</a> which uses <code>node-build-script</code> which also may be of interest.</p> <h2>Re: App Cache Manifest generation</h2> <p>I believe this used to be part of <code>node-build-script</code> but was since removed, see <a href="https://github.com/h5bp/node-build-script/issues/32" rel="nofollow">1</a>, <a href="https://github.com/h5bp/ant-build-script/issues/59" rel="nofollow">2</a></p> <p>There would be nothing stopping you from creating a custom grunt task that utilised something like <a href="https://github.com/jamesgpearce/confess" rel="nofollow">confess.js</a> however.</p> <p>Finally, it looks like Google's upcoming <a href="http://yeoman.io/" rel="nofollow">Yeoman</a> might be worth keeping an eye on if you're not already!</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload