First you need to install the systatic server. It's really just a bricksjs+servitude server with a bunch of predefined paths and templates.
npm install systatic -gsystatic new my_projcd my_projsystatic
The last command runs the server, by default port 3000 (like bricks, you can change the port with
/js) change this file.
Since the point is to generate a static site, the next command you run will be
build. This will remove the need for an app server like nodejs, and allow you to just dump the static files somewhere like CloudFront.
Once your static files are built and compressed, you can test out the files output in the
build directory with the
test command. This just runs a static server on the same development port in your
With that generated static content, next you'll want to deploy to some server, git repo, CDN... whatever.
I'm reimplementing the hard-coded actions as sets of discreet stages which can be configured, allowing third-party plugins to add their own stage to the build/render toolchain. Current thoughts:
An example may be if someone wanted to added a function to compress a set of icons used as CSS into sprites, and pass that information into the next action (which would be bound to the compress stage)
Stages (executing a stage executes every stage up to it):
Would clean the output directory, build the html resource, and build the assets.