This repo provides a template for a wiki-like lab group handbook built as a Quarto book. A lab group handbook is a document that conveys a lab's ethos, policies, and procedures to group members (Tendler et al., 2023). Some of the content is University of Arizona specific (e.g. links in the code of conduct), but it is intended for use by anyone with any kind of lab group (or other group) to adopt!
I ran a workshop on using this template at University of Arizona. You can watch the video or check out the slides.
Zipkin lab policies: https://github.com/zipkinlab/Policies/tree/master
Bahlai lab policies: https://github.com/BahlaiLab/Policies
Tendler, B.C., Welland, M., Miller, K.L., The WIN Handbook Team, 2023. Why every lab needs a handbook. eLife 12, e88853. https://doi.org/10.7554/eLife.88853
There is a growing list of open lab group handbooks that you can get inspiration from (with proper credit of course!)
quarto preview
in the terminal_quarto.yml
configuration file to customize it to your group (see below).qmd
files to customize it to your group (see below)README.md
(and please credit this template!)quarto publish gh-pages
(see below)See Get started with Quarto and the Quarto book documentation for more on customizing this template.
In README.md
In _quarto.yml
book: title:
book: repo-url:
should point to the GitHub repo of your copy of this template on your GitHub organization or account
book: author:
Edit the authors information in _quarto.yml
(e.g. name and ORCID) and potentially add authors
Potentially add, remove, or re-order chapters by editing the chapters:
key in _quarto.yml
In the various .qmd
files
Do a find and replace everywhere (cmd + shift + F in RStudio) for the following: "GROUP_NAME", "PI_NAME", and "PI_EMAIL".
Red callout boxes titled "Group Edit" hold suggestions for what content to include on that page/section. These should be deleted once the edits happen.
All text in the .qmd
documents is boilerplate or example text and intended to be edited to some extent to customize it for your group.
In the terminal run quarto preview
and it should open a live preview of your book in a browser window.
When you make changes and save them, this preview will update.
You only have to do this once.
In the terminal, stop the quarto preview
process if it is running, run quarto render
and then quarto publish gh-pages
.
When this is successful it should open up your book in your web browser.
After this, the GitHub action included in .github/
should automatically re-render and deploy your book when changes are pushed to the main branch on GitHub.