quarto-dev / quarto-dev/quarto-cli

logo placement

Open
#13,839 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement typst
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

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 https://github.com/quarto-dev/quarto-cli/discussions/13591#discussioncomment-14797372

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the pending Pandoc template changes and the page partial referenced in the discussion; inspect the .typ file and whether Typst headers or footers are generated elsewhere. Check how the other fields are validated, including parent, and confirm that logo placement and validation work without overwriting existing header or footer content.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.