Usecases for --stylesheet vs. --css handling in the HTML template

Initially, the HTML template received the path for the stylesheet (either the default one, or a custom one provided with the --stylesheet option):

https://github.com/danburzo/percollate/blob/7c43aec36d94476fcaa31d136fcebd053d70f87e/templates/default.html#L3-L7

With the introduction of the --css option, I changed it to:

https://github.com/danburzo/percollate/blob/cecd11e0c290d0bd0b653047c53e2f82bfb31fca/templates/default.html#L7-L9

And deprecated the passing of the stylesheet property to the template.

However, I think I might have missed a valid use-case for an external stylesheet, namely being able to reference outside resources (images, web fonts) in the custom CSS.

This issue outline some use-cases, to make sure the final solution covers all of them elegantly:

• Override just the page size, margins, font sizes
• Override the default stylesheet with a custom one
• Use local web fonts in the custom stylesheet

(Adding to this list as more use-cases arise)

[danburzo]

Oops, missed your comment here. Yes, you can set it on the html element. Also, I’ll add in the docs how to use the CSS variables --body-font and --alt-font.

[danburzo]

Override just the page size, margins, font sizes

This works well with the --css option.

Override the default stylesheet with a custom one.

This works via the --style option.

Use local web fonts.

For PDFs and HTMLs you can either reference fonts by name with local(), or use their absolute path on disk. EPUBs currently don’t fetch these fonts to bundle them, but that’s okay.

I think we can close the issue for now.