e.g.
https://github.com/maxfordham/document-issue/blob/main/packages/document-issue-quarto/_extensions/document-issue-note/logo.png
ideally this package should be generic and can be configured to a given branding setup in some way.
(currently it makes a maxfordham branded document so it probs shouldn't be a public repo).
ideally we would use brand-yml.
though it currently doesn't support latex generation out-the-box (posit-dev/brand-yml#43), though does support typst so it might be a good nudge to look at that more seriously.
that said we could probs use the python pkg to get the data and add an env var to document-issue where a user can add brand requirements.
https://posit-dev.github.io/brand-yml/pkg/py/
there is also some info missing:
posit-dev/brand-yml#86
e.g.
https://github.com/maxfordham/document-issue/blob/main/packages/document-issue-quarto/_extensions/document-issue-note/logo.png
ideally this package should be generic and can be configured to a given branding setup in some way.
(currently it makes a maxfordham branded document so it probs shouldn't be a public repo).
ideally we would use brand-yml.
though it currently doesn't support latex generation out-the-box (posit-dev/brand-yml#43), though does support typst so it might be a good nudge to look at that more seriously.
that said we could probs use the python pkg to get the data and add an env var to document-issue where a user can add brand requirements.
https://posit-dev.github.io/brand-yml/pkg/py/
there is also some info missing:
posit-dev/brand-yml#86