Skip to content

logo placement #13839

@gordonwoodhull

Description

@gordonwoodhull

I need to unpack and investigate this for 1.9, after merging Pandoc template changes.

I need to file an issue / PR upstream for the page partial. There isn’t anything in Pandoc for logo, so this is otherwise unaffected.

I don’t know if we use the Typst page header or footer elsewhere; not in our .typ but it could be generated. Have to make sure we’re not stomping on something else.

The fact that parent populates a key rather than a value makes me think that validation is the most important part. I haven’t tried it but I imagine the error message if the value is not a key is not something we want to expose to users.

So I’ll create an issue for the validation of the other fields and then add parent.

Originally posted by @gordonwoodhull in #13591 (reply in thread)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions