Implement the page generator component
Implement the page generator component as defined in #33 (closed). The page generator component should be self-contained, which means no logic or configuration (e.g., globs) should exist outside the component except for configuration that comes from user input. The implementation should go in the packages/page-generator/lib
directory.
Write tests to verify each behavior of the component. Specifically, the tests should verify that the page generator compiles the layout templates, populates the UI model, applies the UI model to the compiled layout template, and updates the contents
property on the vinyl file with the result. The tests should be placed in the packages/page-generator/test
directory.
This implementation issue can be worked on in concert with the architecture issue using an agile process. Any discoveries or decisions made that relate to the architecture should be posted back to the architecture issue. The early implementation prototypes may drive the architecture in return.