If it were possible to alter the generated output pages without editing and rebuilding the application it would be easier for users to install/use the application.
I see two realistic ways to go here:
Update our default theme/templates to allow parameters to be specified
--blog-title="Steve Kemp's Blog"
--blog-subtitle="Debian & Free Software"
--footer-file="/path/to/file"
--css-file="/path/to/blah.css"
etc
Allow a new configuration entry in the top-level ephemeris.json
"theme": "/path/to/directory"
The first one is simpler to implement, but no doubt whatever values I choose to allow the user to override will be inadequate.
The second approach means simplicity for the implementation:
Use the default templates as-is, unless a theme-directory is specified.
In the case where a directory is specified, then use that location to find the theme-file.
skx
commented
3 years ago
If it were possible to alter the generated output pages without editing and rebuilding the application it would be easier for users to install/use the application.
I see two realistic ways to go here:
--blog-title="Steve Kemp's Blog"--blog-subtitle="Debian & Free Software"--footer-file="/path/to/file"--css-file="/path/to/blah.css"ephemeris.json"theme": "/path/to/directory"The first one is simpler to implement, but no doubt whatever values I choose to allow the user to override will be inadequate.
The second approach means simplicity for the implementation:
We'd have to implement a new command-line flag:
That would generate a hierarchy of theme-files using the built-in templates.