Jack Lukic
c642868123
|
11 years ago | |
---|---|---|
.. | ||
node_modules | 11 years ago | |
out | 11 years ago | |
src | 11 years ago | |
.bowerrc | 11 years ago | |
.jshintrc | 11 years ago | |
Gruntfile.js | 11 years ago | |
LICENSE.md | 11 years ago | |
Procfile | 11 years ago | |
README.md | 11 years ago | |
docpad.coffee | 11 years ago | |
grunt-config.json | 11 years ago | |
package.json | 11 years ago |
README.md
HTML5 Boilerplate skeleton for DocPad
Bare essentials for building a modern website with best practices
Why the fork?
This fork adds Grunt to show an example of taking the HTMLBP and minifying and concatenating all the JS and CSS assets into single files and including those in the layout.
What is different?
grunt-config.json
- This file is contains the object passed to
grunt.initConfig
ingrunt.js
. It has been put into its own file since it is used indocpad.coffee
to build file lists for inclusion in the layout and deleting unused files.
grunt.js
- This is the Grunt file. It runs
initConfig
with thegrunt-config.json
object. It also registers adefault
task with all the keys from the config file.
docpad.coffee
- I added the helper functions
getGruntedStyles
andgetGruntedScripts
. These functions will return all the compiled assets that contain.min.(css|js)
with the correct base path. - A
writeAfter
DocPad event. It is based on this gist, with some additional functionality. It will run thedefault
grunt command. Then it will use yourgrunt-config.json
to delete thesrc
files since they are no longer needed. It will also delete any empty directories in the 'out/' directory.
layouts/default.html.eco
- The script and style blocks have been replaced with calls to the helper functions described above.
Getting Started
-
Clone the project and run the server
git clone git://github.com/lukekarrys/html5-boilerplate.docpad.git cd html5-boilerplate.docpad npm install docpad run
``
-
Start hacking away by modifying the
src
directory
License
This skeleton is made "public domain" using the Creative Commons Zero, as such before you publish your website you should place your desired license here and within the LICENSE.md
file.
If you are wanting to open-source your website, we suggest using the Creative Commons Attribution License for content and the MIT License for code. In which case you'd probably want to use the following as your license:
Unless stated otherwise, all content is licensed under the [Creative Commons Attribution License](http://creativecommons.org/licenses/by/3.0/) and code licensed under the [MIT License](http://creativecommons.org/licenses/MIT/), © [Your Name](http://your.website)
If you are wanting to close-source your website, we'd suggest using the following:
Copyright [Your Name](http://your.website). All rights reserved.
Other included things such as themes and libraries are likely already licensed by their own invidual licenses, so be sure to respect their licenses too.
Thanks, the DocPad team loves you.