- Support for browsers that do not support ES6+ natively (via Babel)
- Render component presentations from regions
- Render component template fragments based on semantic information
- Define Regions from markup in a page template
This toolchain is based on node.js. Ensure that you are using a stable version of node, such as
8.0.0 or higher. Your version of NPM should be at least
5.0.0 or higher.
After ensuring an up-to-date version of node and NPM:
- download/clone the package.
npm installin the client folder
Settings and Configuration
There are a few settings in the client folder:
package.jsondefines the configuration for the entire project. It establishes what dependencies are needed and contains information that NPM can use later on.
gulp/config.jsdefines configuration for Gulp. This helps reduce redundancies between gulp tasks.
assetscontains source files that can be edited. Currently,
assetsonly contains a
jsfolder, but in the future, this is where libraries and frameworks could be added, too
gulpcontains a gulp configuration and individual gulp tasks
buildis the final product that contains what would be added to your website
Gulp is the task runner for this project.
Gulpfile.js is the entry point for Gulp, and it references only the tasks that are in the
gulp/tasks folder. Each task is its own file so that it can be easier to add new tasks and track those changes in a version control system.
Each Gulp task uses
require() to bring in
config.js, which is where common data is stored.
Any of these tasks can be run from the command line by typing
Take the file(s) in the build folder, add them to your page(s).