Move glossary to correct location and format#495
Conversation
Thank you!Thank you for your pull request 😃 🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}. If you have files that automatically render output (e.g. R Markdown), then you should check for the following:
Rendered Changes🔍 Inspect the changes: https://github.com/carpentries-incubator/hpc-intro/compare/md-outputs..md-outputs-PR-495 The following changes were observed in the rendered markdown documents: What does this mean?If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible. This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation. ⏱️ Updated at 2026-05-21 11:20:37 +0000 |
| title: Glossary | ||
| permalink: /guide/ |
There was a problem hiding this comment.
These are hangovers from the old format I think
| ```bash | ||
| {{ site.local.prompt }} rsync —progress my_precious_data.txt {{ site.remote.user }}@{{ site.remote.login }} | ||
| rsync: link_stat "/home/{{ site.local.user }}/—progress" failed: | ||
| $ rsync —progress my_precious_data.txt user@host |
There was a problem hiding this comment.
Getting the templating to work in this file is hard, as the location of the configuration files is no longer the same
Follow up to #493 to put the glossary in the place where it is found by the heading. Looks like the current best practice is to use glosario...but I just spent 2 hours doing this and we need a fix