consistent handling of logo across formats #11310
Closed
gordonwoodhull
started this conversation in
Feature Requests
Replies: 2 comments
-
Partly implemented in #11446 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Websites handle logos at the project level, not the page level, as covered by #11309. I think we'll eventually want to change that. But dashboard and revealjs are consistent with Typst now, so I'll close this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
Thought I'd open a discussion instead of an issue, because this is something that does work, but it works differently across formats.
I think the formats have a path for convergence, but it can happen over time and they may not need to converge completely.
Summary
We have mostly consistent behavior of
brand.logo
across formats, but we haven't revisited the older baselogo
metadata.html
,logo
is ignoreddashboard
andrevealjs
,logo
specifies a path which supercedesbrand.logo
, and objects orbrand.logo
resource names generate 404 errors and broken image icontypst
,logo
can be a path orbrand.logo
resource name, or it can be an object containing any ofpath
,padding
,width
,location
Consequences
I think it's likely that people will ask why they can't use a
brand.logo
resource name for html/dashboard/revealjs, and other features may also bleed out from typst.Right now, the negative consequence is that if you specify e.g.
results will be inconsistent across between formats, with typst using that logo, dashboard/revealjs doing 404 and broken image icon, and html ignoring it.
Likewise the object form
uses that logo in typst, generates 404 and broken image icon in dashboard and revealjs, and has no effect in html.
(brand yaml itself is consistent)
Beta Was this translation helpful? Give feedback.
All reactions