James Brundage

It's a point of strong coupling. Let a view handle that.

As the culling #7 is completed, what remains should be organized into subfolders.

Many high performance sites are built with a serverless backend and a semi-static frontend. Pipeworks should support this scenario very well.

And module should be able to become an AWS Lambda or Azure Function.

Hugo and Jekyll come to mind.

Many portions of Pipeworks do not make sense together. To the degree that it is logically possible, Pipeworks should be partitioned into many modules.

Now that PipeScript exists, Pipeworks works well as a sister brand. PipeScript also takes off a lot of the long term technical burden of Pipeworks. Pipeworks should be reworked within...

Splatter is a sweet little module that could use a little more love in the demo/publicity department: * [ ] #25 * [ ] #26