Make it even more clear that the `update_dist_directory.sh`
is intended for Travis¹, and not for the user to run it.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
¹ http://docs.travis-ci.com/
Configure Travis to automatically update the content from the `dist`
directory by executing a script¹ that will regenerate the content from
the `dist` directory and commit any new changes to the `master` branch.
This change will help in the development process by:
* ensuring that the content from the `dist` directory is always
in sync with the rest of the content
* removing the need to execute the build step locally everytime
a change is made (especially in the case of trivial changes,
such as, typos)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
¹ The script (`bin/update_dist_directory.sh`) will only be executed
if the tests pass, and will only run if the changes are made in the
`master` branch.
See also: http://docs.travis-ci.com/user/encryption-keys/Closeh5bp/html5-boilerplate#1593
* Move all the H5BP source files into the `src/` directory and remove
all external components that can be fetch via `npm`, namely: the
Apache Server Configs, jQuery, and Normalize.css.
* Add `package.json`, and move to using `npm` for managing dependencies
(for more information about `npm`, see: https://www.npmjs.org/doc/).
* Add `gulp` based build script to allows us to automatically create
the distribution files as well as an archive that can then be attached
to the release - https://github.com/blog/1547-release-your-software
(for more information about gulp, see: http://gulpjs.com/).
* Add other miscellaneous files to help us in our development process:
* `.editorconfig` - to define and maintain consistent coding styles
http://editorconfig.org/
* `.jshintrc` - to specify JSHint configuration options
http://www.jshint.com/docs/
* `.travis.yml` - to specify Travis CI configuration options
http://docs.travis-ci.com/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
These changes:
* automate some of the tedious work (e.g.: updating the external
components, updating some of the inline content such as version
numbers, etc.)
* will allow us to experiment more (e.g.: allow us to create different
builds of H5BP, builds that can contain different components)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Ref h5bp/html5-boilerplate#1563Closeh5bp/html5-boilerplate#1563
