The main directory is where work usually takes place to update presentations for a new tutorial. When the content is ready, PDFs are generated, renamed (to reflect the sequence of presentation) and moved to the appropriate
subdirectory of the final-presentations
folder. Then, the repository it tagged with the tutorial's event label, and a zip of the presentation PDFs is uploaded as part of defining a GitHub release in the repository.
Important note: On 2021-05-21, the template for the presentations was updated. If you want to add slides from presentations before that date, make sure you use the Use destination theme option when you paste the slides in.
We tag the repository when the final-presentations
folder has been populated for a given tutorial (including PDFs). By convention, the tags use exactly the same format as the directory names in final-presentations
: YYYY-MM-DD-venue
. If the nominally final slides need to be updated (i.e., to correct an error), the tag should be moved to the new version. A zip of the PDFs (only) should be added as the release files associated with the tag.
The names of the presentation files are important with respect to the scripting we're trying to develop. File names here need to match those used in the tutorial web site. That includes the presentation.yml
and agenda.csv
data files and the files in the presentation-resources
directories. Everything in the web site is per-event, so presentation file names can be changed between events.
The presentation.yml
flle in this repository should be kept current as presentations are added or titles change. This file is used in the bssw-tutorial website.
Each presentation may have a supplementary -extras
file. The purpose of this file is to hold extra slides and variants not being used in a particular event, but which we want to keep for possible future use.
-extra
file should always follow the naming of the “parent” file. If the parent name changes, the -extra file name should change. Examples: intro.pptx
and intro-extra.pptx
; overview.pptx
and overview-extra.pptx
; etc.-extra
file.
On the title page of each presentation, we list the presenter's name (underlined), pronouns, and affiliation. We also separately list all of the contributors to the presentation (with short affiliations). Every past presenter is assumed to have contributed, and others may have as well. Contributors are listed in alphabetical order. The current presenter is also listed as a contributor.
The following are the general steps to follow for the production of presentations for a new tutorial event. Some adaptation may be required for special circumstances.
<event-label>
for the tutorial.overview
presentation. It is easiest to start from the agenda table as it appears on the tutorial website to create the Powerpoint version.Some institutions have requirements for review prior to release for slide decks being presented by their employees. In some cases, "R&R numbers" must be added to the slide deck as visible confirmation that they have been reviewed. Where required, our convention is to place the R&R number in the lower right corner of the title slide of the deck, just above the colored band with the logos. We use 12pt Arial.
final-presentations/<event-label>
directory.doi.txt
file which contains the reserved DOI URL.git add
and git commit
the doi.txt
file.license-master.pptx
file with the appropriate citation and any other changes that might be required. We prefer to use the same slide in all presentations unless there are good reasons for something special.agenda-master.pptx
file. The agenda table on the web page can be copied and pasted into the Powerpoint table. It works best if you create a Powerpoint table first in order to get the style from the slide template.intro.pptx
license-master.pptx
. This is easily done by copy and pasting in the left-hand thumbnail view, then deleting the old license slide.head-shots
folder.intro-extras.pptx
. Copy the current slide to -extras
before changing it.intro.pptx
). Update contributor list if necessary. Remove unneeded R&R numbers that may be present.license-master.pptx
overview.pptx
presentation, also replace the agenda slides at the end with the new one(s) from agenda-master.pptx
.presentations.yml
file to reflect any new presentations or changed titles. This file is used in the website.Once the presentations have been updated, it is always a good idea to review the slides for quality. Slides should be viewed in presentation mode to be sure you're seeing what the audience will see.
Note that the bssw-tutorial website is capable of generating bash script commands that cover all but the first step in this process (though at the moment they may require a bit of adjustment here and there to match below). They are generated by the <event-label>/utilities.md
file and can be accessed at the URL https://bssw-tutorial.github.io/<event-label>/utilities.html
in the generated site.
presentations.yml
to the final-presentations/<event-label>
directoryModule
column of the agenda table). For example intro.pdf
to 00-intro.pdf
and overview.pdf
to 01-overview.pdf
.final-presentation/<event-label>
folder.git add
and git commit
the contents of the event directory.zip --update <event-label>.zip *.pdf
git tag -a <event-label> -m "<title> at <venue>"; git push origin --tags
gh
scripting tool:
gh release create <event-label> --title "<event-date> <title> @ <venue>"; gh release upload <event-label> <event-label.zip>
If you update any of the presentations after the release, you should update the release by moving the tag and replacing the zip file on GitHub.