quarto-dev / quarto-dev/quarto-cli
Varying the reference position in `quarto-journals` template
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Discussed in https://github.com/quarto-dev/quarto-cli/discussions/2009
@dragonstyle You should read to the bottom of the discussion to see the clearest explanation of what the bug is.
Originally posted by sammo3182 August 19, 2022
Recently I asked a question about varying the reference allocation with Quarto in #1728. Then I find the problem that made the old rmarkdown tricks not work was because I used the article-format-template. The reference was in the right place I want when rendering the plain pdf but then moved to the very end of the document when rendering the aft.
A replicable example:
---
format:
pdf:
number-sections: true
aft-pdf:
keep-tex: true
aft-html: default
bibliography: bio.bib
title: A test
---
content @Hu2020
# Reference
::: {#refs}
:::
# Online Supplementary Materials
See the difference of the reference when choosing the following options respectively:

How could I allow the aft to recognize my reference setting? Any suggestion will be very helpful.
Moreover, a more detailed instruction and examples about how to customize the template than the current brief version under aft repo and Quarto.org will be super welcomed---details like how to arrange the author area, showing the corresponding author, adding the key words and acknowledge, etc.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading discussion #2009 to the end, then render the provided QMD example with the plain PDF and aft formats and compare where the references appear. Done means the aft template honors the requested reference position, with the customization guidance and examples requested in the issue addressed or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100