The flow for using a template with boil use need to be reworked to allow for dynamic alterations to the template compilation (e.g. adding or removing template files to parse). This would allow for more complex field types (see #5).
All relevant project data should be held in a Project class that gets through the flow and can be altered at different points. The class should encapsulate everything about the project template. This would also allow for multiple templates to be used at once or "sub-templates" (See #7).
The flow for using a template with
boil use
need to be reworked to allow for dynamic alterations to the template compilation (e.g. adding or removing template files to parse). This would allow for more complex field types (see #5).All relevant project data should be held in a
Project
class that gets through the flow and can be altered at different points. The class should encapsulate everything about the project template. This would also allow for multiple templates to be used at once or "sub-templates" (See #7).