2021-05-03-ttt-online-bst
The Carpentries Instructor Training workshop. Online, May 2021. Trainers: Anne Fouilloux & Toby Hodges.
Science Score: 41.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
✓Committers with academic emails
21 of 95 committers (22.1%) from academic institutions -
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (13.5%) to scientific vocabulary
Keywords
Keywords from Contributors
Repository
The Carpentries Instructor Training workshop. Online, May 2021. Trainers: Anne Fouilloux & Toby Hodges.
Basic Info
- Host: GitHub
- Owner: tobyhodges
- License: other
- Language: HTML
- Default Branch: gh-pages
- Homepage: https://tobyhodges.github.io/2021-05-03-ttt-online-BST/
- Size: 2.88 MB
Statistics
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
- Releases: 0
Topics
Metadata Files
README.md
training-template
This repository is The Carpentries' template for creating websites for Instructor Training workshops.
Please do not fork this repository directly on GitHub. Instead, please use GitHub's importer following the instructions below to create a website repository for your workshop.
Please do your work in your repository's
gh-pagesbranch, since that is what is automatically published as a website by GitHub.Once you are done, please send your repository's URL to The Carpentries' administrator. We build the list of workshops on our websites from the data included in your
index.mdpage. We can only do that if you customize that page correctly and send us a link to your workshop website.
If you run into problems, or have ideas about how to make this process simpler, please get in touch. The pages on customizing your website, the FAQ, and the design notes have more detail on what we do and why.
Creating a Repository
Log in to GitHub. (If you do not have an account, you can quickly create one for free.) You must be logged in for the remaining steps to work.
Go to GitHub's importer.
Paste the url of this repo as the old repository to clone: https://github.com/carpentries/training-template.
Select the owner for your new repository. (This will probably be you, but may instead be an organization you belong to.)
Choose a name for your workshop website repository. This name should have the form
YYYY-MM-DD-ttt-site, e.g.,2016-12-01-ttt-miskatonic, whereYYYY-MM-DDis the start date of the workshop. for online workshops, chooseonlineassiteMake sure the repository is public.
At this point, you should have a page like this:

You can now click "Begin Import". When the process is done, you will receive a message like "Importing complete! Your new repository gvwilson/2016-12-01-ttt-miskatonic is ready." and you can go to the new repository by clicking on the name.
Note: some people have had intermittent errors during the import process, possibly because of the network timing out. If you experience a problem, please re-try; if the problem persists, please get in touch.
Customizing Your Website
Go into your newly-created repository, which will be at
https://github.com/your_username/YYYY-MM-DD-ttt-site. For example, if your username isgvwilson, the repository's URL will behttps://github.com/gvwilson/2016-12-01-ttt-miskatonic.Edit the header of
index.mdand_config.ymlto customize the list of instructors, workshop venue, etc. You can do this in the browser by clicking on it in the file view on GitHub and then selecting the pencil icon in the menu bar:
Editing hints are embedded in
index.mdand_config.yml, and full instructions are in the customization instructions.Alternatively, if you are already familiar with Git, you can clone the repository to your desktop, edit
index.mdthere, and push your changes back to the repository.~~~ git clone -b gh-pages https://github.com/your_username/YYYY-MM-DD-ttt-site ~~~
You should specify
-b gh-pagesbecause the imported repository doesn't have amasterbranch.In order to view your changes once you are done editing, you must push to your GitHub repository:
~~~ git push origin gh-pages ~~~
Note: please do all of your work in your repository's
gh-pagesbranch, since GitHub automatically publishes that as a website.When you are done editing, go to the GitHub Pages URL for your workshop and preview your changes. In the example above, this is
https://gvwilson.github.io/2016-12-01-ttt-miskatonic.
Note: this template includes some files and directories that most workshops do not need, but which provide a standard place to put extra content if desired. See the design notes for more information about these.
Further instructions are available in the customization instructions. This FAQ includes a few extra tips (additions are always welcome) and these notes on the background and design of this template may help as well.
Checking Your Changes
If you want to preview your changes on your own machine before publishing them on GitHub, you can do so as described below.
Install the software described below. This may require some work, so feel free to preview by pushing to the website.
Run the command:
~~~ $ jekyll serve ~~~
and go to http://0.0.0.0:4000 to preview your site. You can also run this command by typing
make serve(if you have Make installed).Run the command
python bin/workshop_check.py index.mdto check for a few common errors in your workshop's home page. (You must have Python 3 installed to do this.) If you have Make installed, you can also run this command by typingmake workshop-check.
Creating Extra Pages
In rare cases,
you may want to add extra pages to your workshop website.
You can do this by putting either Markdown or HTML pages in the website's root directory
and styling them according to the instructions give in
the lesson template.
If you do this,
you must also edit _config.yml to set these three values:
carpentryis "cp" (for The Carpentries). This determines which logo is loaded.titleis the title of your workshop (typically the venue and date).emailis the contact email address for your workshop, e.g.,gvwilson@miskatonic.edu.
Note: carpentry andemailduplicate information that's inindex.md`,
but there is no way to avoid this
without requiring people to edit both files in the usual case
where no extra pages are created.
Installing Software
If you want to set up Jekyll so that you can preview changes on your own machine before pushing them to GitHub, you must install the software described below. (Note: Julian Thilo has written instructions for installing Jekyll on Windows.)
Ruby. This is included with Linux and Mac OS X; the simplest option on Windows is to use RubyInstaller. You can test your installation by running
ruby --version. For more information, see the Ruby installation guidelines.RubyGems (the package manager for Ruby). You can test your installation by running
gem --version.Jekyll. You can install this by running
gem install jekyll.
You can check the formatting of your header by running bin/workshop_check.py
(which is invoked by make workshop-check).
You must have Python 3 installed in order to do this,
and you will also need the PyYAML module.
Getting and Giving Help
We are committed to offering a pleasant setup experience for our learners, Trainers, Instructors and workshop hosts. If you find bugs in our instructions, or would like to suggest improvements, please file an issue or mail us.
Owner
- Name: Toby Hodges
- Login: tobyhodges
- Kind: user
- Location: Heidelberg, Germany
- Company: @carpentries
- Website: https://tbyhdgs.info
- Twitter: tbyhdgs
- Repositories: 25
- Profile: https://github.com/tobyhodges
Director of Curriculum @carpentries
Citation (CITATION)
Please cite as: Greg Wilson (ed): "Software Carpentry: Workshop Template." Version 2016.06, June 2016, https://github.com/swcarpentry/workshop-template, 10.5281/zenodo.58156.
GitHub Events
Total
Last Year
Committers
Last synced: about 1 year ago
Top Committers
| Name | Commits | |
|---|---|---|
| Greg Wilson | g****n@s****g | 198 |
| W. Trevor King | w****g@t****s | 92 |
| Raniere Silva | r****e@r****m | 87 |
| François Michonneau | f****u@g****m | 78 |
| Raniere Silva | r****7@i****r | 49 |
| Abigail Cabunoc Mayes | a****c@g****m | 25 |
| Maxim Belkin | m****n@g****m | 23 |
| Erin Becker | e****r@g****m | 14 |
| Maneesha Sane | a****m@g****m | 14 |
| Katrin Leinweber | 9****r | 11 |
| Piotr Banaszkiewicz | p****r@b****g | 10 |
| Gabriel A. Devenyi | g****i@g****m | 8 |
| Aleksandra Nenadic | a****c@m****k | 8 |
| James Allen | j****s@s****m | 7 |
| Rémi Emonet | r****t@r****e | 6 |
| Ethan White | e****n@w****g | 5 |
| Jeramia Ory | j****y@g****m | 5 |
| Matt Davis | j****b@g****m | 5 |
| Carol Willing | c****e@w****m | 5 |
| Andrew Walker | a****r@l****k | 5 |
| Lex Nederbragt | l****t@i****o | 5 |
| David LeBauer | d****r@g****m | 4 |
| Damien Irving | d****g@y****u | 4 |
| David Mawdsley | d****y@m****k | 4 |
| Olav Vahtras | v****s@k****e | 4 |
| Pauline Barmby | p****y@u****a | 4 |
| Toby Hodges | t****s@g****m | 4 |
| Andy Boughton | p****t@g****m | 3 |
| Michael R. Crusoe | 1****c | 3 |
| Nick Young | n****g@a****z | 3 |
| and 65 more... | ||
Committer Domains (Top 20 + Academic)
Issues and Pull Requests
Last synced: 9 months ago
All Time
- Total issues: 0
- Total pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Total issue authors: 0
- Total pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0