Custom User Templates

[matthewnau]

Feature Outline:

Consider allowing the users to implement their own templates and styling. Could be a simple -t option that takes a template as an argument. The templates should be stored in a directory under templates/custom/ and the default could be moved under templates/default/. Each template directory would then have their own assets directory as a child.

Concerns

1. Since the current command line arguments are mostly tied to the default template, this would require a significant effort to rework the implementation of the package.

Solutions

1. An additional config file could be used to bind custom user options/arguments and flags to user-defined methods. This would require detailed documentation. If the package detects that a custom template is being used, it could switch over to only accepting options and flags from the user's config file and ignore the default ones.