A Quarto Manuscript Template
This is a template for generating a repo for a Quarto project for a study that will include
It is based off of a tutorial at: Quarto Manuscripts: RStudio but expanded to include linked posters and talks and with some customizations for our workflow and preferences.
We strongly recommend that you read the following pages from the Quarto website to better understand their manuscript format
If you plan to make slide sets, you can also read docs on making slides in quarto generally and more specifically with the revealjs format
Use this template
drop down and select create new repository
study_template.Rproj
to the same name that you used for your repo (i.e., study_[insert_name]
.Rproj`Github is a good choice to publish your manuscript and associated code from notebooks. Your code is already hosted there so why not keep the manuscript website there as well? There are three different methods available to publish there. We prefer the docs folder method. To use this method:
You need to make sure the repo is public. Go to Settings | Danger Zone and change visibility to public.
You need to configure GitHub to publish the website from the docs folder. Go to Settings | Pages | Build and Deployment | Branch. Set Branch to main
and folder to /docs
and save these settings.
In the terminal, go to the root of the folder and enter touch .nojekyll
(this file should already be in your repo if you started from the template)
Render the manuscript. This can be done from terminal using quarto render
at the root of the quarto project
Add and commit the changes and push to Github. The associated website will update automatically.
A Github repo can only have one website associated with it. If we are using the repo for the manuscript website, we need another location to publish slidesets from talks. We have been using Quarto Pub. You can publish there using quarto publish quarto-pub
[filename.qmd] from the folder that contains the qmd file for the talk. The first time you do this, you will need to verify your account and the page address. Follow the prompts. This info is saved in _publish.yml so that you wont need to update it the next time you publish updates to your project.
More details are here