# faqs

category: galaxy
filename: workflows_share
title: Share
area: workflows
box_type: tip
content_hash: e3988e6f4d4053bffeca5ad79d1d3b1e
last_modified: 2026-05-27T09:01:47.471975
contributors_json: ["shiltemann"]
content:
1. Click on {% icon galaxy-workflows-activity %} *Workflows* in the Galaxy activity bar (on the left side of the screen, or in the top menu bar of older Galaxy instances). You will see a list of all your workflows
2. Click on the {% icon history-share %} *Share* button of the workflow you would like to publish

3. Go to **Share Workflow with Individual Users**

4. Enter the email address of the user you want to share the workflow with.

5. They will be able to find and import your workflow under **Workflows shared with me** tab in the **Workflows** section of the Activity bar


category: galaxy
filename: datatypes_fastq_compressed
title: Compressed FASTQ files, (`*.gz`)
area: datatypes
box_type: tip
content_hash: dbc86e56cc1da114fce2e532cc5fa9fe
last_modified: 2026-05-15T22:28:09.570381
contributors_json: ["shiltemann"]
content:
- Files ending in `.gz` are compressed (zipped) files.
  - The `fastq.gz` format is a compressed version of a `fastq` dataset.
  - The `fastqsanger.gz` format is a compressed version of the `fastqsanger` datatype, etc.
- Compression saves space (and therefore your quota).
- Tools can accept the compressed versions of input files
- Make sure the datatype (compressed or uncompressed) is correct for your files, or it may cause tool errors.


category: galaxy
filename: sequencing_nanopore
title: Nanopore sequencing
area: sequencing
box_type: comment
content_hash: 1036fb25440e57a84a9aa25e813278bf
last_modified: 2026-05-15T22:28:09.593884
contributors_json: ["shiltemann"]
content:
Nanopore sequencing has several properties that make it well-suited for our purposes

1. Long-read sequencing technology offers **simplified** and less ambiguous genome **assembly**
2. Long-read sequencing gives the ability to **span repetitive genomic regions**
3. Long-read sequencing makes it possible to **identify large structural variations**

![How nanopore sequencing works]({% link topics/microbiome/images/plasmid-metagenomics-nanopore/nanopore_sequencing.png %} "Using nanopore sequencing, a single molecule of DNA or RNA can be sequenced without the need for PCR amplification or chemical labeling of the sample. (Image from: <a href="https://doi.org/10.7875/togopic.2020.01">Nanopore sequencing: The advantages of long reads for genome assembly</a>)") <br><br>


When using Oxford Nanopore Technologies (ONT) sequencing, the change in electrical current is measured over the membrane of a flow cell. When nucleotides pass the pores in the flow cell the current change is translated (basecalled) to nucleotides by a basecaller. A schematic overview is given in the picture above.

When sequencing using a MinIT or MinION Mk1C, the basecalling software is present on the devices. With basecalling the electrical signals are translated to bases (A,T,G,C) with a quality score per base. The sequenced DNA strand will be basecalled and this will form one read. Multiple reads will be stored in a fastq file.


category: galaxy
filename: workflows_hide_intermediate_steps
title: Hiding intermediate steps
area: workflows
box_type: tip
content_hash: 2a1e6c67ec68253e9114f918cb82dccb
last_modified: 2026-05-27T09:01:47.471248
contributors_json: ["shiltemann", "hexylena"]
content:
When a workflow is executed, the user is usually primarily interested in the final product and not in all intermediate steps.
By default all the outputs of a workflow will be shown, but we can explicitly tell Galaxy which outputs to show and which to hide for a given workflow.
This behaviour is controlled by clicking on the eye icon on for all dataset that should be hidden:

![Asterisk for `out_file1` in the `Cut` tool]({% link shared/images/workflow_editor_hide_output.png %})


category: galaxy
filename: histories_top_control_buttons
title: Top level history controls
area: histories
box_type: tip
content_hash: 5b8a5f08ea4d4763f682747f455295d9
last_modified: 2026-05-15T22:28:09.576276
contributors_json: ["nekrut"]
content:
Above the current history panel are three buttons: 

- The {% icon new-history %} "**Create new history**" button will create an empty history.
- The {% icon switch-histories %} "**Switch to history**" will open a window letting you easily swap to any of your other histories.
- The {% icon galaxy-history-options %} "**History options**" (formerly the {% icon galaxy-gear %} "Gear menu") gives you access to advanced options to work with your history.

![The three history buttons]({% link shared/images/history_top_level_buttons.svg %})

<!-- history_top_level_buttons.svg = editable version = https://docs.google.com/drawings/d/11ZIUNYVHzrieHLVph9lhXgfzrO7MM-N4ehTehMr_eto/edit?usp=sharing -->


category: galaxy
filename: datatypes_Using_compressed_fastq_data
title: Using compressed fastq data as tool inputs
area: datatypes
box_type: tip
content_hash: f7aea70cae45ff13f4717eb1ca2ec9d3
last_modified: 2026-05-15T22:28:09.569536
contributors_json: ["jennaj", "Melkeb"]
content:
- If the tool accepts `fastq` input, then `.gz` compressed data assigned to the datatype `fastq.gz` is appropriate.
- If the tool accepts `fastqsanger` input, then `.gz` compressed data assigned to the datatype `fastqsanger.gz` is appropriate.
- Using uncompressed `fastq` data is still an option with tools. The choice is yours.

**TIP:** Avoid labeling compressed data with an uncompressed datatype, and the reverse. Jobs using mismatched datatype versus actual format will fail with an error.


category: gtn
filename: galaxy_events
title: Are there any upcoming events focused on Galaxy Training?
area: other
box_type: tip
content_hash: 9fb34e8dfc046e68b29fda064b30b9e4
last_modified: 2026-05-15T22:28:09.608561
contributors_json: ["shiltemann"]
content:
Yes, always! Have a look at the [Galaxy Community Events Calendar](https://galaxyproject.org/events/) for what coming up right now.


category: gtn
filename: gtn_tutorial_mode
title: Supporting Tutorial Mode (GTN-in-Galaxy) in a tutorial
area: contributors
box_type: tip
content_hash: ca1d0e72d8c46710355c0e09c6f6624f
last_modified: 2026-05-15T22:28:09.612681
contributors_json: ["shiltemann"]
content:
GTN tutorials can be viewed directly within Galaxy, we call this *Tutorial mode* ([read news post]({% link faqs/galaxy/tutorial_mode.md %}))

In this mode, tool names in hands-on boxes become clickable, directly opening the tool in Galaxy, at the right version.

To enable this feature, a bit of metadata needs to be added to the tool names in hands-on boxes as follows:

{% raw %}
```
{% tool [Name](Toolshed ID) %}
```
{% endraw %}

For example:

{% raw %}
```
{% tool [bedtools intersect intervals](toolshed.g2.bx.psu.edu/repos/iuc/bedtools/bedtools_intersectbed/2.30.0+galaxy1) %}
```
{% endraw %}

To find the toolshed ID of a tool:

1. Open the tool in Galaxy
2. Click on the {% icon dropdown %} options menu (dropdown icon)
3. Select **Copy Tool ID**

  ![screenshot of menu with toolshed link for a tool]({% link faqs/gtn/images/tool_toolshed_link.png %})

Example of a hands-on box using this feature:

{% raw %}
```
> <hands-on-title> Counting SNPs </hands-on-title>
>
> 1. {% tool [Datamash](toolshed.g2.bx.psu.edu/repos/iuc/datamash_ops/datamash_ops/1.8+galaxy0) %} (operations on tabular data):
>
>    - *"Input tabular dataset"*: select the output dataset from **bedtools intersect intervals** {% icon tool %}
>    - *"Group by fields"*: `Column: 4` (the column with the exon IDs)
>
{: .hands_on}
```
{% endraw %}


category: gtn
filename: gtn_audience
title: What audiences are the tutorials for?
area: introduction
box_type: tip
content_hash: 660ea84b7988eb3bf2af57df4a0e90d3
last_modified: 2026-05-15T22:28:09.610285
contributors_json: ["bebatut", "shiltemann"]
content:
There are two distinct audiences for these materials.

1. **Self-paced individual learners.** These tutorials provide everything you need to learn a topic, from explanations of concepts to detailed hands-on exercises.
2. **Instructors.** They are also designed to be used by instructors in teaching/training settings. Slides, and detailed tutorials are provided. Most tutorials also include computational support with the needed tools, data as well as Docker images that can be used to scale the lessons up to many participants.


category: gtn
filename: contributors_git_advanced
title: How can I contribute in "advanced" mode?
area: contributors
box_type: tip
content_hash: bcffd2cfd77bebf1dcc49079ed02636c
last_modified: 2026-05-15T22:28:09.605971
contributors_json: ["shiltemann", "hexylena"]
content:
Most of the content is written in [GitHub Flavored Markdown](https://guides.github.com/features/mastering-markdown/) with some metadata (or variables) found in [YAML](http://yaml.org/) files. Everything is stored on our [GitHub repository]({{ site.github_repository }}). Each training material is related to a topic. All training materials (slides, tutorials, etc) related to a topic are found in a dedicated directory (*e.g.* `transcriptomics` directory contains the material related to transcriptomic analysis). Each topic has the following structure:

![Structure of the repository]({% link shared/images/repo_organization.png %}){: width="400px"}

- a metadata file in YAML format
- a directory with the topic introduction slide deck in Markdown with introductions to the topic
- a directory with the tutorials:

    Inside the tutorials directory, each tutorial related to the topic has its own subdirectory with several files:
    - a tutorial file written in Markdown with hands-on
    - an optional slides file in Markdown with slides to support the tutorial
    - a directory with Galaxy Interactive Tours to reproduce the tutorial
    - a directory with workflows extracted from the tutorial
    - a YAML file with the links to the input data needed for the tutorial
    - a YAML file with the description of needed tools to run the tutorial

- a directory with the Dockerfile describing the details to build a container for the topic (self-study environments).

To manage changes, we use [GitHub flow](https://guides.github.com/introduction/flow/) based on Pull Requests (check our [tutorial]({% link topics/contributing/tutorials/create-new-tutorial-content/tutorial.md %})):

1. [Create a fork](https://help.github.com/articles/fork-a-repo/) of this repository on GitHub
2. Clone your fork of this repository to create a local copy on your computer and initialize the required submodules (`git submodule init` and `git submodule update`)
3. Create a new branch in your local copy for each significant change
4. Commit the changes in that branch
5. Push that branch to your fork on GitHub
6. Submit a pull request from that branch to the [original repository]({{ site.github_repository }})
7. If you receive feedback, make changes in your local clone and push them to your branch on GitHub: the pull request will update automatically
8. Pull requests will be merged by the training team members after at least one other person has reviewed the Pull request and approved it.

Globally, the process of development of new content is open and transparent:

1. Creation of a branch derived from the main branch of the GitHub repository
2. Initialization of a new directory for the tutorial
3. Filling of the metadata with title, questions, learning objectives, etc
4. Generation of the input dataset for the tutorial
5. Filling of the tutorial content
6. Extraction of the workflows of the tutorial
7. Automatic extraction of the required tools to populate the tool file
8. Automatic annotation of the public Galaxy servers
9. Generation of an interactive tour for the tutorial with the [Tourbuilder](https://tailordev.fr/blog/2017/07/19/the-galaxy-tour-builder-extension/) web-browser extension
10. Upload of the datasets to Zenodo and addition of the links in the data library file.
11. Once ready, opening a Pull Request
12. Automatic checks of the changes are automatically checked for the right format and working links using continuous integration testing on Travis CI
13. Review of the content by several other instructors via discussions
14. After the review process, merge of the content into the main branch, starting a series of automatic steps triggered by Travis CI
15. Regeneration of the website and publication on [{{ site.url }}{{ site.baseurl }}/]({{ site.baseurl }}/)
16. Generation of PDF artifacts of the tutorials and slides and upload on the FTP server
18. Population of [TeSS](https://tess.elixir-europe.org/), the ELIXIR’s Training Portal, via the metadata

![Development process]({% link shared/images/development_process.png %})

To learn how to add new content, check out our [series of tutorials on creating new content]({% link topics/contributing/index.md %}):

{% assign topic = site.data["contributing"] %}
<ol>
{% assign topic_material = site | topic_filter:'contributing' %}
{% for material in topic_material %}
 {% if material.enable != "false" %}
  {% if material.type == "introduction" %}
<li><a href="{{ site.baseurl }}/topics/{{ topic.name }}/slides/{{ material.tutorial_name }}.html">{{ material.title }}</a></li>
 {% elsif material.type == "tutorial" %}
  {% if material.hands_on %}
<li><a href="{{ site.baseurl }}/topics/{{ topic.name  }}/tutorials/{{ material.tutorial_name }}/tutorial.html">{{ material.title }}</a></li>
  {% elsif material.slides %}
<li><a href="{{ site.baseurl }}/topics/{{ topic.name }}/tutorials/{{ material.tutorial_name }}/slides.html">{{ material.title }}</a></li>
   {% endif %}
  {% endif %}
 {% endif %}
{% endfor %}
 </ol>

We also strongly recommend you read and follow [The Carpentries](https://carpentries.org/) recommendations on [lesson design](https://carpentries.github.io/lesson-example/01-design/) and [lesson writing](https://carpentries.github.io/instructor-training/15-lesson-study/) if you plan to add or change some training materials, and also to check the structure of the training material above.


category: gtn
filename: learners_using_materials
title: How do I use this material?
area: learners
box_type: tip
content_hash: e8c50c2c4d166e4f2e3acd49f11901a3
last_modified: 2026-05-15T22:28:09.634552
contributors_json: ["bebatut", "shiltemann"]
content:
Many topics include slide decks and if the topic you are interested in has slides then start there.  These will introduce the topic and important concepts.

Most of your learning will happen in the next step - the hands-on tutorials.  This is where you'll become familiar with using the Galaxy interface and experiment with different ways to use Galaxy and the tools in Galaxy.


category: gtn
filename: contributors_appreciated
title: Thanks!
area: contributors
box_type: tip
content_hash: 88bccfe593d3479874c52f04ab6e50e3
last_modified: 2026-05-15T22:28:09.604783
contributors_json: ["bebatut", "shiltemann"]
content:
First off, thanks for your interest in contributing to the Galaxy training materials!

Individual learners and instructors can make these training more effective by contributing back to them. You can report mistakes and errors, create more content, etc. Whatever is your background, there is a way to contribute: via the GitHub website, via command-line or even without dealing with GitHub.

We will address your issues and/or assess your change proposal as promptly as we can, and help you become a member of our community. You can also check our [tutorials]({% link topics/contributing/index.md %}) for more details.


category: gtn
filename: galaxy_tested_with
title: Compatible Versions of Galaxy
area: other
box_type: warning
content_hash: b132c97c03c21c6f94e2b40b24c30667
last_modified: 2026-05-15T22:28:09.608647
contributors_json: ["hexylena"]
content:
{% if include.version %}
This tutorial has been tested to work with {{ include.version }}
{% else %}
This tutorial may not be updated for the latest version of Galaxy.
{% endif %}

- Galaxy's Interface **may** be different to the Galaxy where you are following this tutorial.
- ✅ All tutorial steps will still be able to be followed (potentially with minor differences for moved buttons or changed icons.)
- ✅ Tools will all still work


category: gtn
filename: gtn_advertise
title: How can I advertise the training materials on my posters?
area: introduction
box_type: tip
content_hash: 4f059f087a625729c07dda27b299fb84
last_modified: 2026-05-15T22:28:09.609941
contributors_json: ["bebatut", "shiltemann"]
content:
We provide some QR codes and logos in the [images folder]({{ site.github_repository }}/tree/{{ site.github_repository_branch }}/assets/images).


category: gtn
filename: galaxy_what_is_it
title: What is Galaxy?
area: introduction
box_type: tip
content_hash: f86abb204129c980322e627bec316a12
last_modified: 2026-05-15T22:28:09.608830
contributors_json: ["bebatut", "shiltemann"]
content:
[Galaxy](https://galaxyproject.org/) is an open data integration and analysis platform for the life sciences, and it is particularly well-suited for data analysis training in life science research.


category: gtn
filename: contributors_reporting_issues
title: How can I report mistakes or errors?
area: contributors
box_type: tip
content_hash: 1b81c9e8d9ba3f8346bb4e9031270b83
last_modified: 2026-05-15T22:28:09.606476
contributors_json: ["shiltemann"]
content:
The easiest way to start contributing is to [file an issue]({{ site.github_repository }}/issues/new) to tell us about a problem such as a typo, spelling mistake, or a factual error. You can then introduce yourself and meet some of our community members.


category: gtn
filename: contributors_without_git
title: How can I create new content without dealing with git?
area: contributors
box_type: tip
content_hash: dab29fa7fa83192787c61f78db380b62
last_modified: 2026-05-15T22:28:09.607539
contributors_json: ["shiltemann"]
content:
If you feel uncomfortable with using the git and the [GitHub flow](https://guides.github.com/introduction/flow/), you can write a new tutorial with any text editor and then contact us (via [Gitter]({{ site.gitter_url }}) or [email](mailto:{{ site.email }})). We will work together to integrate the new content.


category: gtn
filename: get_data_upload
title: How can I load data?
area: introduction
box_type: tip
content_hash: 2838e1069714dd8818224611f7972885
last_modified: 2026-05-15T22:28:09.608930
contributors_json: ["jennaj", "bernandez"]
content:
- Load by "browsing" for a local file. Some servers will support load data that is 2 GB or larger. If you are having problems with this method, try FTP.
- Load using an **HTTP URL** or **FTP URL**.
- Load a few lines of plain text.
- Load using FTP. Either line command or with a desktop client.


category: gtn
filename: contributors_giving_feedback
title: How can I give feedback?
area: contributors
box_type: tip
content_hash: 2f942a6b430a188ddff4f1fa76b6e39b
last_modified: 2026-05-15T22:28:09.606306
contributors_json: ["shiltemann"]
content:
At the end of each tutorial, there is a link to [a feedback form](https://docs.google.com/forms/d/1BILuBp8bPv42odpZ55Kcf2rqzR-k0Czx46agVVSRgm4/edit). We use this information to improve our tutorials.

For global feedbacks, you can open an [issue on GitHub]({{ site.github_repository }}/issues/new), write us on [Gitter]({{ site.gitter_url }}) or send us an [email](mailto:{{ site.email }}).


category: gtn
filename: contributors_getting_started
title: How can I get started with contributing?
area: contributors
box_type: tip
content_hash: 2a18f7c793bc7d1cd0f341c9a97bc92b
last_modified: 2026-05-15T22:28:09.605465
contributors_json: ["bebatut", "shiltemann"]
content:
If you would like to get involved in the project but are unsure where to start, there are some easy ways to contribute which will also help you familiarize yourself with the project!

A great way to help out the project is to test/edit existing tutorials. Pick a tutorial and check the contents. Does everything work as expected? Are there things that could be improved?

Below is a checklist of things to look out for to help you get started. If you feel confident in making changes yourself, please open a pull request, otherwise please file an issue with any problems you run into or suggestions for improvements.

Basic:

- **Test** the tutorial on a running Galaxy instance
   - For example {% assign servers = nil | list_usegalaxy_servers_shuffle %}{% for server in servers %}[{{ server.name }}]({{ server.url }}){% if forloop.last %}{% else %}, {% endif %}{% endfor %}
   - Report any issues you run into
- **Language** editing
  - Fix spelling and grammar mistakes
  - Simplify the English (to make it more accessible)

Intermediate:

- **Metadata**
  - Are the objectives, keypoints and time estimate filled in?
  - Do they fit with the contents of the tutorial?
- **Content**
  - Is there enough background information provided in the introduction section and throughout the tutorial?
  - **Question boxes**
    - Add questions or question boxes where you think they might be useful (make people think about results they got, test their understanding, etc)
    - Check that answers are still up-to-date
  - **Screenshots and Videos**
    - Make sure there is also a textual description of the image/video contents
    - Does the screenshot add value to the tutorial or can it be removed?

Advanced:

- **Workflows**
  - Add a workflow definition file `.ga` if none is present
  - Check that the existing workflow is up-to-date with the tutorial contents
  - Enable [workflow testing](https://github.com/usegalaxy-eu/workflow-testing)
- **Tours**
  - Add a tour if none exists
  - Run the existing tour and check that it is up-to-date with the tutorial contents
- **Datasets**
  - Check that all datasets used in the tutorial are present in Zenodo
  - Add a data-library.yaml file if none exists


Another great way to help out the project is by reviewing [open pull requests]({{ site.github_repository }}/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc). You can use the above checklist as a guide for your review. Some documentation about how to add your review in the GitHub interface can be found [in GitHub's PR Reviewing Documentation](https://help.github.com/articles/about-pull-request-reviews/)


category: gtn
filename: gtn_stats
title: GTN Stats
area: other
box_type: none
content_hash: ba300c8cd596d49db1486adf13153a70
last_modified: 2026-05-27T09:01:47.472327
contributors_json: ["hexylena"]
content:
<!-- tutorial stats -->
{% assign tutorials = site.pages | where:"layout", "tutorial_hands_on" | where_exp:"item","item.draft != true" %}
{% assign faqs = site.pages | where:"layout", "faq" %}
{% assign topics = site | list_topics_by_category: "science-technical" | to_keys %}
{% assign contributors = site.data['contributors'] | where_exp: "item", "item.gtn-halloffame != 'no'" | sort: "joined" %}
{% assign learning_pathways = site.pages | where:"layout", "learning-pathway" | where_exp:"item","item.draft != true"  %}
{% assign news = site.posts | where:"layout", "news" %}
{% assign events = site.pages | where:"layout", "event" %}
{% assign events_ext = site.pages | where:"layout", "event-external" %}
{% assign events_s = events | size %}
{% assign events_ext_s = events_ext | size %}
{% assign videos = site | list_videos  %}
{% assign editors = site | list_editors_flat %}
{% assign workflow_count = site | count_workflows %}
{% assign orgs = site.data['organisations'] %}


{% if include.compact %}
<div class="row" style="color: var(--text-color-boxtitle)">

<div class="col-md-3 col-sm-6 col-6">
 <div class="gtn-card color-comment">
   <div class="card-title-small">{{ contributors | size }}</div>
   <div class="card-text-small">Contributors</div>
 </div>
</div>

<div class="col-md-3 col-sm-6 col-6">
 <div class="gtn-card color-agenda">
   <div class="card-title-small">{{ topics | size }}</div>
   <div class="card-text-small">Topics</div>
 </div>
</div>

<div class="col-md-3 col-sm-6 col-6">
 <div class="gtn-card color-tip">
   <div class="card-title-small">{{ tutorials | size }}</div>
   <div class="card-text-small">Tutorials</div>
 </div>
</div>

<div class="col-md-3 col-sm-6 col-6">
 <div class="gtn-card color-handson">
   <div class="card-title-small">{{ site.age | round: 1}}</div>
   <div class="card-text-small">Years</div>
 </div>
</div>

</div>

{% else %}

<div class="row" style="color: var(--text-color-boxtitle)">

<!-- Row 1; High Level Metrics -->

<div class="col-md-3">
 <div class="gtn-card color-rainbow-orangered">
   <div class="card-title">{{ tutorials | size }}</div>
   <div class="card-text">Tutorials</div>
 </div>
</div>

<div class="col-md-3">
 <div class="gtn-card color-rainbow-orange">
   <div class="card-title">{{ topics | size }}</div>
   <div class="card-text">Topics</div>
 </div>
</div>

<div class="col-md-3">
 <div class="gtn-card color-rainbow-orangeyellow">
   <div class="card-title">{{ learning_pathways | size }}</div>
   <div class="card-text">Learning Paths</div>
 </div>
</div>

<div class="col-md-3">
 <div class="gtn-card color-rainbow-green">
   <div class="card-title">{{ faqs | size }}</div>
   <div class="card-text"><abbr title="Frequently Asked Questions">FAQs</abbr></div>
 </div>
</div>


<!-- row 2 -->

<div class="col-md-3">
 <div class="gtn-card color-rainbow-blue">
   <div class="card-title">{{ workflow_count }}</div>
   <div class="card-text">Workflows</div>
 </div>
</div>

<div class="col-md-3">
 <div class="gtn-card color-rainbow-purple">
   <div class="card-title">{{ videos | size }}</div>
   <div class="card-text">Videos ({{ site | list_videos_total_time | round:1}}h)</div>
 </div>
</div>

<div class="col-md-3">
 <div class="gtn-card color-rainbow-violet">
   <div class="card-title">{{ news | size }}</div>
   <div class="card-text">News Posts</div>
 </div>
</div>

<div class="col-md-3">
 <div class="gtn-card color-rainbow-pink">
   <div class="card-title">{{ site.age | round: 1}}</div>
   <div class="card-text">Years</div>
 </div>
</div>


</div>

<!-- Row 3: People & Project -->

<h2> Community Stats </h2>
<div class="row" style="color: var(--text-color-boxtitle)">

<div class="col-md-3">
 <div class="gtn-card color-rainbow-orangeyellow h-100">
   <div class="card-title">{{ contributors | size }}</div>
   <div class="card-text">Contributors</div>
 </div>
</div>

<div class="col-md-3">
 <div class="gtn-card color-rainbow-green h-100">
   <div class="card-title">{{ editors | size }}</div>
   <div class="card-text">Editorial Board Members</div>
 </div>
</div>

<div class="col-md-3">
 <div class="gtn-card color-rainbow-blue h-100">
   <div class="card-title">{{ events_s | plus: events_ext_s }}</div>
   <div class="card-text">Events</div>
 </div>
</div>

<div class="col-md-3">
 <div class="gtn-card color-rainbow-violet h-100">
   <div class="card-title">{{ orgs | where_exp: "org", "org.gtn-halloffame != 'no'" | size }}</div>
   <div class="card-text">Supporting Organisations</div>
 </div>
</div>

</div>
{% endif %}


category: gtn
filename: recordings_create
title: Recording a video tutorial
area: contributors
box_type: tip
content_hash: c1ce185dd3c79c187e035f762134ab7b
last_modified: 2026-05-27T09:01:47.478082
contributors_json: ["shiltemann", "hexylena"]
content:
This FAQ describes some **general guidelines** for recording your video

**Anybody is welcome to record one of the GTN tutorials**, even if another recording already exists!
Both the GTN tutorial and Galaxy itself change significantly over time, and having regular and/or multiple recordings of tutorials is great!

**Done with your recording?** Check out the instructions for adding it to the GTN:

[Submitting Recordings to the GTN]({% link faqs/gtn/recordings_add.md %}){: .btn.btn-info}


#### Video content

1. **Start of video**
  - **Introduce yourself**
  - Discuss the **questions and learning objectives** of the tutorial
  - Give a **basic introducion about the topic**, many participants will be novices

2. **Guide the learners through the tutorial step by step**
   - Explain the scientific background of the analysis
   - Explain where you are clicking in Galaxy
   - Explain what tool parameters mean
   - Explain what the tool does
   - Discuss the output files
   - Discuss how to interpret the results
   - Discuss question boxes from the tutorial

3. **Speak slowly and clearly**
  - Take your time, we are not in a hurry
  - It is often a lot of new information for participants, give them a chance to process all of it
  - Speaking slowly and clearly will improve the quality of the auto-generated captions, and will be less work for you to fix captions.

4. **If things go wrong that is OK!**
  - It's a great teaching moment!
  - Explain the steps you are taking to determine what went wrong, and how you are fixing it.
  - It makes participants feel less bad if things go wrong for them

5. **If your tutorial is long**
  - Indicate good places for people to take a break
  - e.g. when a tool takes a while to run

6. **End of video**
  - Go over some of the **take-home messages (key-points)** of the tutorial
  - Remind viewers about the **feedback form** embedded at the end of the tutorial
  - Share your recommendations for **follow-up tutorials**
  - Share any other tips for where to learn more about the topic
  - Share **how to connect with the community** (e.g. Matrix, Help Forum, social media, etc)

7. If you are doing both a lecture and a hands-on training, please create 2 separate videos


#### Technical Guidelines

1. Start a [Zoom](https://zoom.us/) call with yourself, record that.
   - For Mac users, QuickTime Player is also a nice option.
   - Have another preference like OBS? Totally OK too!
   - We recommend zoom to folks new to video production as it is the easiest to get started and produces quite small file sizes.

2. Do a short **test recording** first
   - Is the **audio quality** good enough?
     - Wearing a headset often improves the audio quality.
   - **Screen sharing:** is your screen readable?
     - Make sure you **zoom in** enough for it to be clearly visible what you are doing in Galaxy.
     - Test watching the video in a non-maximised window. Is it still legible?
     - If the participant is using 50% of their screen for the video, 50% for Galaxy, will it be legible?

3. Need to edit your video after recording?
  - For example to merge multiple videos together?
  - Software like [KDEnlive](https://kdenlive.org/en/) can help here.
  - Command line option to merge videos (ubuntu) `for f in *.mp4 ; do echo file \'$f\' >> list.txt; done && ffmpeg -f concat -safe 0 -i list.txt -c copy stitched-video.mp4 && rm list.txt`
  - Great way to simply remove background noise and clicks `ffmpeg -i stitched-video.mp4 -af "adeclick" output.mp4`
  - Feel free to ask us for help if you need!


#### Standards

1. **Zoom in**, in every interface you're covering! Many people will be watching the video while they're doing the activity, and won't have significant monitor space. Which video below would you rather be trying to follow?

   Bad | Good 😍
   --- | ---
   ![default size screenshot of usegalaxy.eu]({% link faqs/gtn/images/bad.png %}) | ![zoomed in screenshot of usegalaxy.eu, now much more legible]({% link faqs/gtn/images/good.png %})

   Bad | Good 🤩
   --- | ---
   ![green text on black background console with tiny font]({% link faqs/gtn/images/bad-console.png %}) | ![zoomed in screenshot of a console with high contrast black and white content]({% link faqs/gtn/images/good-console.png %})

2. (Especially for introductory videos!) Clearly call out what you're doing, especially on the first occurrence

   Bad | Good
   --- | ---
   "Re-run the job" | "We need to re-run the job which we can do by first clicking to expand the dataset, and then using the re-run job button which looks like a refresh icon."

   Bad | Good
   --- | ---
   "As you can see here the report says X" | "I'm going to view the output of this tool, click on the eyeball icon, and as you can see the report says X."

   But the same goes for terminal aliases, please disable all of your favourite terminal aliases and quick shortcuts that you're used to using, disable your bashrc, etc. These are all things students will try and type, and will fail in doing so. We need to be very clear and explicit because people will type exactly what is on the screen, and their environment should at minimum match yours.

   Bad | Good
   --- | ---
   `lg file`| `ls -al | grep file`
   `z galaxy`| `cd path/to/the/galaxy`

3. Consider using a pointer that is more visually highlighted.

   ![mouse pointer with circle around it that follows it around]({% link faqs/gtn/images/mouse.png %})

   There are themes available for your mouse pointer that you can temporarily use while recording that can make it easier for watchers to see what you're doing.

   - [Windows](https://www.microsoft.com/en-us/p/mouse-pointer-highlight/9p7sb9s4rq7z?activetab=pivot:overviewtab)
   - [Linux](https://askubuntu.com/questions/777896/how-do-i-highlight-my-mouse-pointer-while-screen-recording/917587#917587)


category: gtn
filename: fair_training
title: How does the GTN ensure our training materials are FAIR?
area: contributors
box_type: tip
content_hash: 3fe5108254fda257a9dd20498e12ceaf
last_modified: 2026-05-15T22:28:09.608321
contributors_json: ["hexylena"]
content:
This infrastructure has been developed in accordance with the FAIR (Findable, Accessible, Interoperable, Reusable) principles for training materials {% cite Garcia2020 %}. Following these principles enables trainers and trainees to find, reuse, adapt, and improve the available tutorials.

The GTN receives a 100% score on the [FAIR Checker](https://fair-checker.france-bioinformatique.fr/check), as noted in our recent [news post]({{ site.baseurl }}/news/2024/05/13/fair.html)


10 Simple Rules                                                            | Implementation in GTN framework
---------------                                                            | -------------------------------
Plan to share your training materials online                               | Online [training material portfolio](https://training.galaxyproject.org/), managed via [a public GitHub repository](https://github.com/galaxyproject/training-material)
Improve findability of your training materials by properly describing them | Rich metadata associated with each tutorial that are visible and accessible via schema.org on each tutorial webpage.
Give your training materials a unique identity                             | URL persistency with redirection in case of renaming of tutorials. Data used for tutorials stored on Zenodo and associated with a Digital Object Identifiers (DOI)
Register your training materials online                                    | Tutorials automatically registered on TeSS, the [ELIXIR's Training e-Support System](https://tess.elixir-europe.org/)
If appropriate, define access rules for your training materials            | Online and free to use without registration
Use an interoperable format for your training materials                    | Content of the tutorials and slides written in Markdown. Metadata associated with tutorials stored in YAML, and workflows in JSON. All of this metadata is available [from the GTN's API]({% link api/index.html %})
Make your training materials (re-)usable for trainers                      | Online. Rich metadata associated with each tutorial: title, contributor details, license, description, learning outcomes, audience, requirements, tags/keywords, duration, date of last revision. Strong technical support for each tutorial: workflow, data on Zenodo and also available as data libraries on UseGalaxy.\*, tools installable via the Galaxy Tool Shed, list of possible Galaxy instances with the needed tools.
Make your training materials (re-)usable for trainees                      | Online and easy to follow hands-on tutorials. Rich metadata with "Specific, Measurable, Attainable, Realistic and Time bound" (SMART) learning outcomes following Bloom's taxonomy. Requirements and follow-up tutorials to build learning path. List of Galaxy instances offering needed tools, data on Zenodo and also available as data libraries on UseGalaxy.\*. Support chat embedded in tutorial pages.
Make your training materials contribution friendly and citable             | Open and collaborative infrastructure with contribution guidelines, a CONTRIBUTING file and a chat. Details to cite tutorials and give credit to contributors available at the end of each tutorial.
Keep your training materials up-to-date                                    | Open, collaborative and transparent peer-review and curation process. Short time between updates.


category: gtn
filename: what-is-a-learning-pathway
title: What is a Learning Pathway?
area: introduction
box_type: comment
content_hash: 7dfd89cbfb71b30d27e9408d4a37635f
last_modified: 2026-05-15T22:28:09.635438
contributors_json: ["shiltemann"]
content:
<div style="display:inline-block;vertical-align:top;width:10%">
<img src="{{site.baseurl}}/assets/images/learning-pathway.png" alt="A graphic depicting a winding path from a start symbol to a trophy, with tutorials along the way" class="invert-safe" />
</div>
<div  style="display:inline-block; margin-left: 2em; width:70%">
We recommend you follow the tutorials in the order presented on this page. They have been selected to fit together and build up your knowledge step by step. If a lesson has both slides and a tutorial, we recommend you start with the slides, then proceed with the tutorial.
</div>


category: gtn
filename: learners_running_tutorials
title: Where can I run the hands-on tutorials?
area: learners
box_type: tip
content_hash: 718dafec9e1941a2529016240d9648bb
last_modified: 2026-05-15T22:28:09.634164
contributors_json: ["bebatut", "shiltemann"]
content:
To run the hands-on tutorials you need a Galaxy server to run them on.

Each tutorial is annotated with information about which [public Galaxy servers](https://galaxyproject.org/public-galaxy-servers/) it can be run on. These servers are available to anyone on the world wide web and some may have all the tools that are needed by a specific tutorial.

If your organization/consortia/community has its own Galaxy server, then you may  want to run tutorials on that. You will need to confirm that all necessary tools and reference genomes are available on your server and possible install missing tools and data. To learn how to do that, you can follow our [dedicated tutorial]({% link topics/teaching/tutorials/setup-galaxy-for-training/tutorial.md %}).

Some topics have a [Docker](https://www.docker.com/) image that can be installed and run on participants' laptops.  These Docker images contain Galaxy instances that include all tools and datasets used in a tutorial, as well as saved analyses and repeatable workflows that are relevant. You will need to [install Docker](https://docs.docker.com/install/).

Finally, you can also run your tutorials on cloud-based infrastructures.  Galaxy is [available on many national research infrastructures](https://galaxyproject.org/galaxy-services/) such as [Jetstream](https://galaxyproject.org/cloud/jetstream/) (United States), [GenAP](https://www.genap.ca/) (Canada), [GVL](https://www.gvl.org.au/) (Australia), [CLIMB](http://www.climb.ac.uk/) (United Kingdom), and more.  These instances are typically easy to launch, and easy to shut down when you are done.

If you are already familiar with, and have an account on [Amazon Web Services](https://aws.amazon.com/) then you can also launch a Galaxy server there using [CloudLaunch](https://launch.usegalaxy.org/).


category: gtn
filename: gtn_licenses
title: What licenses are used in the GTN?
area: introduction
box_type: tip
content_hash: 1115746dfa9472c583d7684e2708109c
last_modified: 2026-05-15T22:28:09.611011
contributors_json: ["hexylena"]
content:
We provide a listing of all licenses for code and things displayed to you in the GTN in [the licenses page]({% link licenses.md %})


category: gtn
filename: gtn_news_create_post
title: Creating a GTN News post
area: contributors
box_type: tip
content_hash: 93bae0732d22a54f14f3bdabb5c1bead
last_modified: 2026-05-15T22:28:09.611971
contributors_json: ["shiltemann"]
content:
If you have created a new tutorial, running an event, published a paper around training, or have anything else interesting to share with the GTN community, we encourage you to write a **News item** about it!

News items will show up on the [GTN homepage]({% link index.md %}) and in the [GTN news feed]({% link news.md %}).

**Creating the news post: The Easy Way**

[Fill out this Google Form](https://forms.gle/6SRAVcppzieef7Zz9). Every day our bot will import the news posts submitted via this Google Form, and we will process them, perhaps requesting small changes, so we recommend that you have a GitHub account already.

**For Advanced Users**

Have a look at the existing news items in the [`news/_posts/` folder](https://github.com/galaxyproject/training-material/tree/main/news/_posts) of the GTN repository for some examples.

A news post is a markdown file that looks as follows:


```markdown
---
layout: news

title: "New Tutorial: My tutorial title"
tags:
  - new tutorial
  - transcriptomics
contributors:
  - shiltemann
  - hexylena

tutorial: "topics/introduction/tutorials/data-manipulation-olympics/tutorial.html"
cover: "path/to/cover-image.jpg"  # usually an image from your tutorial
coveralt: "description of the cover image"

---

A bit of text containing your news, this is all markdown formatted,
so you can do **bold** and *italic* text like this, and links look
like [this](https://example.com) etc.

Describe everything you want to convey here, can be as long as you
need.
```

Make sure the filename is structured as follows: `year-month-day-title.md`, so for example: `2022-10-28-my-new-tutorial.md`


category: gtn
filename: recordings_add
title: Adding your recording to a tutorial or slide deck
area: contributors
box_type: tip
content_hash: 5a1df76c9e70a789ca17dbdbe32ddb81
last_modified: 2026-05-15T22:28:09.634875
contributors_json: ["shiltemann"]
content:
**We welcome anybody to submit their recordings!** Your videos can be used in (online) training events, or for self-study by learners on the GTN.

For some tips and tricks about recording the video itself, please ensure your recording conforms to our recommendations:

[Recording Tips & Tricks]({% link faqs/gtn/recordings_create.md %}){: .btn.btn-info}
[Submit a Recording](https://forms.gle/qNG8FkTN1yRZPNZY6){: .btn.btn-info}

#### Submission process

The process of adding recordings to the GTN is as follows:

1. **Instructor:** Record video ([tips & tricks]({% link faqs/gtn/recordings_create.md %}))
2. **Instructor:** Submit your video using this [Google Form](https://forms.gle/qNG8FkTN1yRZPNZY6)
3. **GTN:** A [GTN GitHub pull request (PR)](https://github.com/galaxyproject/training-material/pulls) will be made by our bot based on the form.
4. **GTN:**: We will upload your video to the [GalaxyProject YouTube channel](https://www.youtube.com/c/galaxyproject)
5. **GTN:**: We will put the auto-generated captions from YouTube into a Google Doc
6. **Instructor:**: Check and fix the auto-generated captions
7. **GTN:** Upload the fixed captions to YouTube
8. **GTN:** Merge the Pull Request on GitHub
9. Done! Your recording will now show up on the tutorial for anybody to use and re-use


**Note:** If you are submitting a video to use in an event, please submit your recording **2 weeks before the start of your course** to allow ample time to complete the submission process.

#### Recordings Metadata

Our bot will add some metadata about your recording to the tutorial or slide deck in question, and looks as follows:

```
recordings:
  - speakers:       # speakers must be defined in the CONTRIBUTORS.yaml file
    - shiltemann
    - hexylena
    captioners:     # captioners must also be present in the CONTRIBUTORS.yaml file
    - bebatut
    type:           # optional, will default to Tutorial or Lecture, but if you do something different, set it here (e.g. Demo, Lecture & Tutorial, Background, Webinar)
    date: '2024-06-12'         # date on which you recorded the video
    galaxy_version: '24.0'     # version of Galaxy you used during the recording, can be found under 'Help->About' in Galaxy
    length: 1H17M              # length of your video, in format: 17M or 2H34M  etc
    youtube_id: "dQw4w9WgXcQ"  # the bit of the YouTube URL after youtube.com/watch?v=

  - speakers:
    - shiltemann
    captioners:
    - hexylena
    - bebatut
    date: '2020-06-12'
    galaxy_version: '20.05'
    length: 51M
    youtube_id: "oAVjF_7ensg"

```

#### Misc

**Note:** If your videos are already uploaded to YouTube, for example as part of a different project's account, you can add this metadata to the tutorial or slides manually, without using our submission form.
Note that we do require all videos to have good-quality English captions, and we will not be able to help you configure these on other YouTube accounts.


category: gtn
filename: gtn_citing
title: How can I cite the GTN?
area: introduction
box_type: tip
content_hash: 34f41077629ecb15e5bd1da92f29b88e
last_modified: 2026-05-15T22:28:09.610370
contributors_json: ["bebatut", "shiltemann"]
content:
We wrote two articles about our efforts:

- [Batut, Bérénice, et al. "Community-driven data analysis training for biology." Cell systems 6.6 (2018): 752-758](https://doi.org/10.1016/j.cels.2018.05.012)
- [Hiltemann, Saskia, Rasche, Helena et al. "Galaxy Training: A Powerful Framework for Teaching!." PLOS Computational Biology (2023) 19(1): e1010752](https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1010752)

To cite individual tutorials, please find citation information at the end of the tutorial.

Here is the BibTeX formatted version of those citations:

```
@article{Hiltemann_2023,
	title        = {Galaxy Training: A powerful framework for teaching!},
	author       = {Hiltemann, Saskia and Rasche, Helena and Gladman, Simon and Hotz, Hans-Rudolf and Larivi\`{e}re, Delphine and Blankenberg, Daniel and Jagtap, Pratik D. and Wollmann, Thomas and Bretaudeau, Anthony and Gou\'{e}, Nadia and Griffin, Timothy J. and Royaux, Coline and Le Bras, Yvan and Mehta, Subina and Syme, Anna and Coppens, Frederik and Droesbeke, Bert and Soranzo, Nicola and Bacon, Wendi and Psomopoulos, Fotis and Gallardo-Alba, Crist\'{o}bal and Davis, John and F\"{o}ll, Melanie Christine and Fahrner, Matthias and Doyle, Maria A. and Serrano-Solano, Beatriz and Fouilloux, Anne Claire and van Heusden, Peter and Maier, Wolfgang and Clements, Dave and Heyl, Florian and Gr\"{u}ning, Bj\"{o}rn and Batut, B\'{e}r\'{e}nice},
	year         = 2023,
	month        = jan,
	journal      = {PLOS Computational Biology},
	publisher    = {Public Library of Science (PLoS)},
	volume       = 19,
	number       = 1,
	pages        = {e1010752},
	doi          = {10.1371/journal.pcbi.1010752},
	issn         = {1553-7358},
	url          = {http://dx.doi.org/10.1371/journal.pcbi.1010752},
	editor       = {Ouellette, Francis},
}
@article{Batut_2018,
	title        = {Community-Driven Data Analysis Training for Biology},
	author       = {Batut, B\'{e}r\'{e}nice and Hiltemann, Saskia and Bagnacani, Andrea and Baker, Dannon and Bhardwaj, Vivek and Blank, Clemens and Bretaudeau, Anthony and Brillet-Gu\'{e}guen, Loraine and \v{C}ech, Martin and Chilton, John and Clements, Dave and Doppelt-Azeroual, Olivia and Erxleben, Anika and Freeberg, Mallory Ann and Gladman, Simon and Hoogstrate, Youri and Hotz, Hans-Rudolf and Houwaart, Torsten and Jagtap, Pratik and Larivi\`{e}re, Delphine and Le Corguill\'{e}, Gildas and Manke, Thomas and Mareuil, Fabien and Ram\'{\i}rez, Fidel and Ryan, Devon and Sigloch, Florian Christoph and Soranzo, Nicola and Wolff, Joachim and Videm, Pavankumar and Wolfien, Markus and Wubuli, Aisanjiang and Yusuf, Dilmurat and Taylor, James and Backofen, Rolf and Nekrutenko, Anton and Gr\"{u}ning, Bj\"{o}rn},
	year         = 2018,
	month        = jun,
	journal      = {Cell Systems},
	publisher    = {Elsevier BV},
	volume       = 6,
	number       = 6,
	pages        = {752--758.e1},
	doi          = {10.1016/j.cels.2018.05.012},
	issn         = {2405-4712},
	url          = {http://dx.doi.org/10.1016/j.cels.2018.05.012},
}
```


category: gtn
filename: a11y
title: How does the GTN ensure accessibility?
area: contributors
box_type: tip
content_hash: 63861c79d409dc3689c990fa3f11ccfe
last_modified: 2026-05-15T22:28:09.604303
contributors_json: ["hexylena"]
content:
We are committed to an accessible training experience regardless of disability. Please see our [accessibility page]({% link accessibility.md %}) for more information.


category: gtn
filename: collaborative_development
title: How does the GTN implement the "Ten simple rules for collaborative lesson development"
area: contributors
box_type: tip
content_hash: 3ec3c6e32c9f9a9fcefb1bcb06f75e7b
last_modified: 2026-05-15T22:28:09.604458
contributors_json: ["hexylena"]
content:
The GTN framework is inherently collaborative and community-driven, and comprises a growing number of contributors with expertise in a wide range of scientific and technical domains. Given this highly collaborative nature of a community with very different skill sets, the GTN framework has evolved over the years to facilitate the contribution and maintenance of the tutorials. We aim to adhere to best-practice guidelines for collaborative lesson development described in {% cite Devenyi_2018 %}. The structure of the tutorials and repository has been made modular with unified syntax and use of snippets enabling easy access for authors to add common tips and tricks new users might need to know. This system allows for easy updating of all tutorials, if there is a change in tools or interface. More generally, we continually strive to lower contribution barriers for content creators by providing a framework that is easy to use for training developers regardless of their level of knowledge of the underlying technical framework.

Implementation of the "Ten simple rules for collaborative lesson development" ({% cite Devenyi_2018 %}) in the training material:

Rules                                            | Implementation in the GTN framework
----                                             | ---
Clarify audience                                 | Tutorial metadata includes level indicators (introductory, intermediate, advanced) and a list of prerequisite tutorials as recommended prior knowledge. This information is rendered at the top of each tutorial.
Make lessons modular                             | Development of small tutorials linked together via learning paths
Teach best practice lesson development           | We maintain the topic [*Contributing to the Galaxy Training Material*]({% link topics/contributing/index.md %}) including numerous tutorials describing how to create new content. Furthermore, quarterly online collaboration fest (CoFests) are organized, where contributors can get direct support. Development of a Train the Trainer program and a mentoring program for instructors, in which lesson development is taught
Encourage and empower contributors               | Involve them in reviews. Mentor them. Encourage them to become maintainers.
Build community around lessons                   | Quarterly online collaboration fest (CoFests) and Community calls. Chat on our Gitter/Matrix channel.
Publish periodically and recognize contributions | Author listed on tutorials. Hall of fame listing all contributors. Full tutorial citation at the end of the tutorial. Tweet about new or updated tutorials. List of new or updated tutorials in Galaxy Community newsletter. Soon: publication of tutorials via article
Evaluate lessons at several scales               | Tutorial change (Pull Request) review. Embedded feedback form in tutorials for trainee feedback. Instructor feedback. Automatic workflow testing
Reduce, re-use, recycle                          | Sharing content between tutorials, specially using snippets. Development of small modular tutorials linked by learning paths
Link to other resources                          | Links to original paper, documentation, external tutorials and other material
You can't please everyone                        | but we can try (several different Galaxy introduction tutorials for different audience). Aim to clearly state what the tutorial does and does not cover, at the start.


category: gtn
filename: instructors_choosing_server
title: What Galaxy instance should I use for my training?
area: instructors
box_type: tip
content_hash: 22588ddb9b9486aa4ef6b7f42212e153
last_modified: 2026-05-15T22:28:09.631557
contributors_json: ["bebatut", "shiltemann"]
content:
To teach the hands-on tutorials you need a Galaxy server to run the examples on.

Each tutorial is annotated with the information on which [public Galaxy servers](https://galaxyproject.org/public-galaxy-servers/) it can be run. These servers are available to anyone on the world wide web and some may have all the tools that are needed by a specific tutorial. If you choose this option then you should work with that server's admins to confirm that the server can handle the workload for a workshop. For example, the [usegalaxy.eu](https://usegalaxy.eu/)

If your organization/consortia/community has its own Galaxy server, then you may want to run tutorials on that. This can be ideal because then the instance you are teaching on is the same as your participants will be using after the training. They'll also be able to revisit any analysis they did during the training. If you pursue this option you'll need to work with your organization's Galaxy Admins to confirm that

- the server can support a room full of people all doing the same analysis at the same time.
- all tools and reference datasets needed in the tutorial are locally installed.  To learn how to setup a Galaxy instance for a tutorial, you can follow our [dedicated tutorial]({% link topics/teaching/tutorials/setup-galaxy-for-training/tutorial.md %}).
- all participants will be able to create/use accounts on the system.

Some training topics have a Docker image that can be installed and run on all participants' laptops.  These images contain Galaxy instances that include all tools and datasets used in a tutorial, as well as saved analyses and repeatable workflows that are relevant.

Finally, you can also run your tutorials on cloud-based infrastructures.  Galaxy is [available on many national research infrastructures](https://galaxyproject.org/galaxy-services/) such as [Jetstream](https://galaxyproject.org/cloud/jetstream/) (United States), [GenAP](https://www.genap.ca/) (Canada), [GVL](https://launch.genome.edu.au/launch) (Australia), [CLIMB](http://www.climb.ac.uk/) (United Kingdom), and more.


category: gtn
filename: learners_getting_help
title: How can I get help?
area: learners
box_type: tip
content_hash: 6706420150c74d911b3b55f723ad9b2d
last_modified: 2026-05-15T22:28:09.633286
contributors_json: ["bebatut", "shiltemann"]
content:
If you have questions about this training material, you can reach us using the [Gitter chat]({{ site.gitter_url }}).  You'll need a [GitHub](https://github.com/) or [Twitter](https://twitter.com/) account to post questions.  If you have questions about Galaxy outside the context of training, see the [Galaxy Support page](https://galaxyproject.org/support/).


category: gtn
filename: gtn_tutorials
title: What are the tutorials for?
area: introduction
box_type: tip
content_hash: 25203210ee68dd5cec0c1d2c8d74fd0c
last_modified: 2026-05-15T22:28:09.612785
contributors_json: ["bebatut", "shiltemann"]
content:
These tutorials can be used for learning and teaching how to use Galaxy for general data analysis, and for learning/teaching specific domains such as assembly and differential gene expression analysis with RNA-Seq data.


category: gtn
filename: short-url
title: Finding a material's PURL or Short URL
area: instructors
box_type: tip
content_hash: 6a8eecf664c61a76c919c63e663a2ebc
last_modified: 2026-05-15T22:28:09.635268
contributors_json: ["hexylena"]
content:
Every material in the GTN is automatically assigned two short URLs:

- a [PURL]({{site.baseurl}}/news/2023/04/19/shortlinks.html) which will always point to the material, and looks like `https://gxy.io/GTN:T00001`
- a tutorial ID based short URL like `https://gxy.io/GTN:admin/ansible-galaxy`, which will redirect to topics/admin/tutorials/ansible-galaxy/tutorial.md

The PURLs, when available, are listed in the Metadata box of a given material, or on the first slide of a slide deck. Additionally any page with a PURL lists it in the footer of the page. PURLs are generated every monday, so it can take up to a week for your PURL to be available. If you need it sooner, please let us know.

The second short URL is not currently displayed anywhere but can be constructed manually based on the URL of the page.


category: gtn
filename: instructors_getting_help
title: How do I get help?
area: instructors
box_type: tip
content_hash: 9810ffd64b8a5fdae651f2e739988582
last_modified: 2026-05-15T22:28:09.632200
contributors_json: ["bebatut", "shiltemann"]
content:
The support channel for instructors is the same as for individual learners.  We suggest you start by posting a question to the Galaxy Training Network [Gitter chat]({{ site.gitter_url }}). Anyone can view the discussion, but you'll need to login (using your GitHub or Twitter account) to add to the discussion.

If you have questions about Galaxy in general (that are not training-centric) then there are [several support options](https://galaxyproject.org/support/).


category: gtn
filename: instructors_best_practices
title: What are the best practices for teaching with Galaxy?
area: instructors
box_type: tip
content_hash: 658aeaf135ca2f349174e1faf75cd94b
last_modified: 2026-05-15T22:28:09.631287
contributors_json: ["bebatut", "shiltemann"]
content:
We started to collect some best practices for instructors inside our [Good practices slides]({% link topics/teaching/index.md %})


category: gtn
filename: contributors_helping_project
title: What can I do to help the project?
area: contributors
box_type: tip
content_hash: 3291bbfee20f7b91595e371ad713b311
last_modified: 2026-05-15T22:28:09.606391
contributors_json: ["shiltemann"]
content:
In [issues](https://github.com/galaxyproject/training-material/issues), you will find lists of issues to fix and features to implement (with the ["newcomer-friendly"]({{ site.github_repository }}/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Anewcomer-friendly) label for example). Feel free to work on them!


category: gtn
filename: why-the-gtn
title: Why host your materials with the GTN?
area: introduction
box_type: tip
content_hash: e9c78c68bd49b9d9476ac7a39b1c328b
last_modified: 2026-05-15T22:28:09.635927
contributors_json: ["hexylena"]
content:
The short version is we're a popular, FAIR training materials platform, and we want to be a home for your training materials.

### Your content in front of the world

As of June 2023 the GTN sees around 60k visitors per month. Please see [our public page view monitoring](https://plausible.galaxyproject.eu/training.galaxyproject.org?period=30d) for more details.

### FAIR

We go to great lengths to make sure our training platform is completely FAIR. See [this FAQ for the details on how we achieve that.]({% link faqs/gtn/fair_training.md %}). All of our materials have extensive [BioSchemas](https://bioschemas.org) markup ensuring they're easily accessible to search engines.
Our materials are automatically indexed by [TeSS](https://tess.elixir-europe.org/materials?content_provider=Galaxy+Training), and we are working on a WorkflowHub integration.

### Accessible

We regularly test our pages with a thorough suite of accessibility tools, as well as via screen reader.

### Not Just Galaxy

Our name can be a bit misleading! While a lot of our tutorials are focused on Galaxy, we have multiple growing topics which are unrelated to Galaxy.

- [ai4life]({% link topics/ai4life/index.md %})
- [FAIR]({% link topics/fair/index.md %})
- [Data Science]({% link topics/data-science/index.md %})

All of these topics are using the GTN as a platform to disseminate their materials far and wide.

### Features

Do you need

- Choose your own adventure tutorials
- Automatic videos from your slides

Then choose the GTN.


category: gtn
filename: galaxy_usage
title: Ways to use Galaxy
area: introduction
box_type: tip
content_hash: 0e62dceb23352aaad91aeee2ce11ce88
last_modified: 2026-05-15T22:28:09.608745
contributors_json: ["jennaj", "garimavs"]
content:
All ways to use Galaxy are included in the [Galaxy Directory listing](https://galaxyproject.org/use).

Having one account at several public Galaxy servers expands your access to distinct data storage and computational resources, plus common and domain-specific analysis tools. 

When running your own private Galaxy server for routine analysis, publishing results at a public Galaxy server allows for worldwide access by others when you share your data: Histories, Workflows, and related assets.

Tips:
- **Teaching with Galaxy** We strongly recommend using Galaxy’s Training Infrastructure as a Service ([TIaaS](https://usegalaxy-eu.github.io/tiaas)) for synchronous class work.
- **Public Galaxy** servers are appropriate for many analysis projects or for when sharing data or results publicly is a goal. These are also a great choice when learning on your own with [GTN](https://training.galaxyproject.org/) tutorials.
- **Private Galaxy** servers are more appropriate when working with very large data, time sensitive projects, and ongoing research projects that require more resources than the public Galaxy servers can support. These two options are scientist friendly as they require very little to no server administration.
    - [GVL Cloudman](https://galaxyproject.org/use/aws/) is a single or multi-user choice and AWS [offers grants](https://aws.amazon.com/grants/). 
    - [AnVIL](https://galaxyproject.org/use/anvil/) is a single-user choice sponsored by NHGRI and is a pay-for-use Google Cloud platform.


category: gtn
filename: gtn_event_create
title: Creating a GTN Event
area: contributors
box_type: tip
content_hash: d47e6f7babc599976ce291424a713179
last_modified: 2026-05-15T22:28:09.610457
contributors_json: ["shiltemann"]
content:
To add your event to the GTN, you will need to supply your course information (dates, location, program, etc). You will then get [an event page like this]({% link events/2024-04-01-example-event.md %}) which you can use during your training. This page includes a course overview, course handbook (full program with links to tutorials) and setup instructions for participants.

Your event will also be shown on the [GTN event horizon]({% link events/index.md %}) and on the homepage. We are also happy to advertise your event on social media and Matrix channels.


**Already have your own event page?** No problem! You can add your event as an external event (see below) and we will simply link to your page!

To add your event to the GTN:

1. Create a page in the `events/` folder of the [GTN repository](https://github.com/galaxyproject/training-material)
2. Have a look at example event definitions in this folder:
   - [2024-04-01-example-event.md](https://github.com/galaxyproject/training-material/blob/main/events/2024-04-01-example-event.md)
   - or [2024-04-01-example-event-external.md](https://github.com/galaxyproject/training-material/blob/main/events/2024-04-01-example-event-external.md) if you already have an event page elsewhere
3. Adapt one of these example pages to fit your event
4. Create a pull request on the GTN

**We are also happy to help you** to add your event, please [contact us on Matrix](https://matrix.to/#/#Galaxy-Training-Network_Lobby:gitter.im) to discuss the details of your course with us.

For a full list of metadata fields for events, please have a look at our [schema documentation page](https://github.com/galaxyproject/training-material/blob/main/_layouts/event.html)

Please also feel free to contact us with ideas for improvements! We know that training comes in many different forms, so if something in your event is not yet supported, let us know and we are happy to add it!


### External events

Already have a course webpage? Great! In this case, you only have to provide the most basic information about your course (title, desciption, dates, location).

The easiest method is to fill in our Google Form:

[Events Google Form!](https://forms.gle/4KjCKKrZ6kamg81o7){: .btn.btn-success}

Or you can create the event file manually. See also [2024-04-01-example-event-external.md](https://github.com/galaxyproject/training-material/blob/main/events/2024-04-01-example-event-external.md) for an example definition.

```
---
layout: event-external
title: My External Training Event Title

external: "https://galaxyproject.org/events/"
description:

date_start:
date_end:  # optional, for multi-day events

location:
  name:
  city:
  country:

contributions:
  organisers:
    - name1
    - name2
```


category: gtn
filename: gtn_sustainability
title: Sustainability of the training-material and metadata
area: other
box_type: tip
content_hash: 2663f5d15a0e55569530c3e0f473a16c
last_modified: 2026-05-15T22:28:09.612565
contributors_json: ["bebatut", "shiltemann"]
content:
This repository is hosted on [GitHub](https://github.com/) using git as a [DVCS](https://en.wikipedia.org/wiki/Distributed_version_control). Therefore the community is hosting backups of this
repository in a decentralised way. The repository is self-contained and contains all needed content and all metadata.
In addition we mirror snapshops of this repo on [Zenodo](http://zenodo.org).


category: gtn
filename: gtn_license
title: How is the content licensed?
area: introduction
box_type: tip
content_hash: a22e36b544e9f83d939a955c121029b2
last_modified: 2026-05-15T22:28:09.610910
contributors_json: ["bebatut", "shiltemann"]
content:
The content of this website is licensed under the [Creative Commons Attribution 4.0 License](https://creativecommons.org/licenses/by/4.0/).


category: gtn
filename: gtn_minor_correction
title: Making a minor correction to any training material
area: contributors
box_type: tip
content_hash: e3227f14b87e3a6596a74c46655616a2
last_modified: 2026-05-27T09:01:47.472212
contributors_json: ["PhilReedData", "nomadscientist"]
content:
If you find a minor mistake in any GTN training material, we encourage you to propose a correction. For small changes such as typos, this can be done from the browser. If you can implement the corrections yourself, in the context of where they happen, this saves a lot of time for the editors.  When you submit your suggestion, it will be carefully checked by an expert, so do not worry about breaking anything!

Outline of the steps:

1. Start from the page with the minor mistake.  
2. Open the page in the GitHub editor.  
3. Make the correction.  
4. Save the changes with a description of what you did.  
5. Send the proposal to the GTN team to check, then apply the change.

In this example, we will show how to correct a typo in the metadata of a learning pathway. Note, this specific typo has now been corrected.

### 1. Start from the page with the minor mistake

![Learning pathways page]({% link faqs/gtn/images/minor-fix-01.png %} "Example of a page with a typo, this time in the page metadata")

![A training material page]({% link faqs/gtn/images/minor-fix-02.png %} "At the top a training material, click Settings then Propose a change or correction")

1. From the [learning pathways page]({% link learning-pathways/ %}), you can see the tags below each pathway. Here, one of the pathways has a tag 'introcuction', which should be 'introduction'.
2. Click to open the page.
3. At the top-right of the page, click **Settings** then **Propose a change or correction**. This will open the page in edit mode. The training material is stored in GitHub, an external site, but we will walk you through how to navigate it.

### 2. Open the page in the GitHub editor  

![Create a fork]({% link faqs/gtn/images/minor-fix-04.png %} "You need to create a 'fork' of the training material")

1. You may be asked to sign into GitHub. If you have never used GitHub before, please [register for a free GitHub account](https://docs.github.com/en/get-started/start-your-journey/creating-an-account-on-github).
2. You may be asked to create a fork of the GTN training materials repository. A fork is a linked copy of the training materials in your personal GitHub account. Click **Fork this repository**.

### 3. Make the correction  

![GitHub edit page]({% link faqs/gtn/images/minor-fix-06.png %} "Make your changes in the editor")

1. You will see the text that makes up the training material (it uses a language called Markdown).
2. In this example, we need to correct a line of the metadata at the top of the file (this is called the frontmatter). Type your correction.

### 4. Save the changes with a description of what you did

![Commit changes]({% link faqs/gtn/images/minor-fix-07.png %} "Give a summary and 'commit' them")

1. When you have finished making corrections, click the **Commit changes...** button.
2. You will be asked to provide a brief summary of the changes you have made. In the box labeled **Commit message**, type a summary.
3. You do not need to give an extended description here.
4. Click the **Propose changes** button.

### 5. Send the proposal to the GTN team to check, then apply the change

![Compare your changes]({% link faqs/gtn/images/minor-fix-08.png %} "Compare your changes")

![Make a pull request]({% link faqs/gtn/images/minor-fix-11.png %} "Send the proposal in a 'pull request'")

1. You are taken to a page titled **Comparing changes**. You will see a list of the changes you have made. This appears as lines removed (beginning with a minus sign, in red) and lines added (beginning with a plus sign, in green).
2. Click the **Create pull request** button. This will open a pull request; this is a submission of your proposal that contains all the essential information for the editors and the platform to implement and apply the correction.
3. The **title** will be the same as the commit message you typed earlier.
4. Add a **description** which describes your changes. You can include links as required.
5. Click the **Create pull request** button. Your change has now been submitted, or, in GitHub terms, you have now opened a pull request.
6. The pull request will need to be reviewed by a human. There are also some automated checks that will be run. After all this is completed, if your request is approved, it will be applied (or 'merged' in GitHub terms).

{% icon congratulations %} Thank you for helping improve our training materials.


category: gtn
filename: gtn_faq_create
title: Creating a GTN FAQ
area: contributors
box_type: tip
content_hash: d0d19bf64220406e81d276833c9697b1
last_modified: 2026-05-15T22:28:09.610805
contributors_json: ["hexylena"]
content:
If you have a snippet of knowledge that is reusable, we recommend you to share with the GTN community, and we encourage you to create an FAQ for it!

**Creating the FAQ: The Easy Way**

[Fill out this Google Form](https://forms.gle/2JVMfd1AgtenZPvv9). Every day our bot will import the FAQs submitted via this Google Form, and we will process them, perhaps requesting small changes, so we recommend that you have a GitHub account already.

**For Advanced Users**

Have a look at the existing FAQs in the [`faqs/galaxy/` folder](https://github.com/galaxyproject/training-material/tree/main/faqs/galaxy) of the GTN repository for some examples.

A news post is a markdown file that looks as follows:

{% raw %}
```markdown
---
title: Finding Datasets
area: datasets
box_type: tip
layout: faq
contributors: [jennaj, Melkeb]
---


- To review all active Datasets in your account, go to **User > Datasets**.

Notes:
- Logging out of Galaxy while the Upload tool is still loading data can cause uploads to abort. This is most likely to occur when a dataset is loaded by browsing local files.
- If you have more than one browser window open, each with a different Galaxy History loaded, the Upload tool will load data into the most recently used history.
- Click on refresh icon {% icon galaxy-refresh %} at the top of the History panel to display the current active History with the datasets.
```
{% endraw %}


category: gtn
filename: my-galaxy-training
title: What is my.galaxy.training
area: introduction
box_type: tip
content_hash: e14e38ae69aabcd4c8e16da6333ade57
last_modified: 2026-05-15T22:28:09.634641
contributors_json: ["hexylena"]
content:
The [`my.galaxy.training`](https://my.galaxy.training) is part of the GTN. We found that often need to direct our learners to specific pages within Galaxy, but which Galaxy? Should we add three links, one for each of the current bigger UseGalaxy.* servers? That would be really annoying for users who aren't using one of those servers.

E.g. how do we link to [/user](https://my.galaxy.training/?path=/user), the user preferences page which is available on every Galaxy Instance? This service handles that in a private and user-friendly manner.

### (Learners) How to Use It

When you access a my.galaxy.training page you'll be prompted to select a server, simply select one and you're good to go!

If you want to enter a private Galaxy instance, perhaps, behind a firewall, that's also an option! Just select the 'other' option and provide your domain. Since the redirection happens in your browser with no servers involved, as long as *you* can access the server, you'll get redirected to the right location.

### (Tutorial Authors) How to use it

If you want to link to a specific page within Galaxy, simple construct the URL: `https://my.galaxy.training/?path=/user` where everything after `?path` is the location they should be redirected to on Galaxy. That example link will eventually redirect the learner to something like `https://usegalaxy.eu/user`.

### Technical Background

So we took inspiration from [Home Assistant](https://my.home-assistant.io/) which had the same problem, how to redirect users to pages on their own servers. The `my.galaxy.training` service is a very simple static page which looks in the user's [`localStorage`](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage) for their preferred server.
If it's not set, the user can click one of the common domains, and be redirected. When they access another link, they'll be prompted to use a button that remembers which server they chose.

### Data Privacy

Any domain selected is not tracked nor communicated to any third party. Your preferred server is stored in your browser, and never transmitted to the GTN. That's why we use localStorage instead of cookies.


category: gtn
filename: gtn_workflow_testing
title: Adding workflow tests with Planemo
area: contributors
box_type: tip
content_hash: 1f04e695c567fc46dd757362d8eaae27
last_modified: 2026-05-27T09:01:47.472637
contributors_json: ["hexylena"]
content:
### Ensuring a Tutorial has a Workflow

1. Find a tutorial that you're interested in, that **doesn't currently have tests.**

   This tutorial has a workflow (`.ga`) and a test, notice the `-tests.yml` that has the same name as the workflow `.ga` file.

   ```
   machinelearning/workflows/machine_learning.ga
   machinelearning/workflows/machine_learning-tests.yml
   ```

   You want to find tutorials without the `-tests.yml` file. The workflow file might also be missing.

2. Check if it has a workflow (if it does, skip to step 5.)
3. Follow the tutorial
4. Extract a workflow from the history
5. Run that workflow in a new history to test

### Extract Tests (Online Version)

If you are on UseGalaxy.org or another server running 24.2 or later, you can use [PWDK](https://pwdk.apps.galaxyproject.eu/), a version of planemo running online to generate the workflow tests.

However if you are on an older version of Galaxy, or a private Galaxy server, then you'll need to do the following:

### Extract Tests (Manual Version)

6. Obtain the workflow invocation ID, and your API key (User → Preferences → Manage API Key)

   ![screenshot of the workflow invocation page. The user drop down shows where to find this page, and a red box circles a field named "Invocation ID"]({% link faqs/gtn/images/invocation.png %})

7. Install the latest version of `planemo`

   ```
   # In a virtualenv
   pip install planemo
   ```

8. Run the command to initialise a workflow test from the `workflows/` subdirectory - if it doesn't exist, you might need to create it first.

   ```
   planemo workflow_test_init --from_invocation <INVOCATION ID> --galaxy_url <GALAXY SERVER URL> --galaxy_user_key <GALAXY API KEY>
   ```

   This will produce a folder of files, for example from a testing workflow:

   ```
   $ tree
   .
   ├── test-data
   │   ├── input dataset(s).shapefile.shp
   │   └── shapefile.shp
   ├── testing-openlayer.ga
   └── testing-openlayer-tests.yml
   ```

### Adding Your Tests to the GTN

9. You will need to check the `-tests.yml` file, it has some automatically generated comparisons. Namely it tests that output data matches the test-data exactly, however, you might want to replace that with assertions that check for e.g. correct file size, or specific text content you expect to see.

10. If the files in test-data are already uploaded to Zenodo, to save disk space, you should delete them from the `test-data` dir and use their URL in the `-tests.yml` file, as in this example:

    ```yaml
    - doc: Test the M. Tuberculosis Variant Analysis workflow
      job:
         'Read 1':
            location: https://zenodo.org/record/3960260/files/004-2_1.fastq.gz
            class: File
            filetype: fastqsanger.gz
    ```

11. Add tests on the outputs! Check the [planemo reference if you need more detail](https://planemo.readthedocs.io/en/latest/test_format.html).

    ```yaml
    - doc: Test the M. Tuberculosis Variant Analysis workflow
      job:
         # Simple explicit Inputs
         'Read 1':
            location: https://zenodo.org/record/3960260/files/004-2_1.fastq.gz
            class: File
            filetype: fastqsanger.gz
      outputs:
        jbrowse_html:
          asserts:
            has_text:
              text: "JBrowseDefaultMainPage"
        snippy_fasta:
          asserts:
            has_line:
              line: '>Wildtype Staphylococcus aureus strain WT.'
        snippy_tabular:
          asserts:
            has_n_columns:
              n: 2
    ```

12. Contribute all of those files to the GTN in a PR, adding them to the `workflows/` folder of your tutorial.


category: gtn
filename: learners_getting_started
title: Where do I start?
area: learners
box_type: tip
content_hash: eaef69755381423134c60f1198ed6b84
last_modified: 2026-05-15T22:28:09.633405
contributors_json: ["bebatut", "shiltemann"]
content:
If you are new to Galaxy then start with one of the introductory topics.  These introduce you to concepts that are useful in Galaxy, no matter what domain you are doing analysis in.

If you are already familiar with Galaxy basics and want to learn how to use it in a particular domain (for example, ChIP-Seq), then start with one of those topics.

If you are already well informed about bioinformatics data analysis and you just want to get a feel for how it works in Galaxy, then many tutorials include *Instructions for the impatient* sections.


category: gtn
filename: gtn_example_histories
title: Using Answer Key Histories
area: introduction
box_type: tip
content_hash: 5d717b1c3371f8375f244f1616271964
last_modified: 2026-05-27T09:01:47.472099
contributors_json: ["nomadscientist"]
content:
If you get stuck, you can first check your history against an {% icon galaxy-history-answer %} Answer Key history found in the header of (some) tutorials.

First, import the target history.

{% snippet faqs/galaxy/histories_import.md %}

Next, compare the answer key history with your own history.

{% snippet faqs/galaxy/histories_side_by_side_view.md %}

You can compare there, or if you're really stuck, you can also click and drag a given dataset to your history to continue the tutorial from there.

{% snippet faqs/galaxy/histories_copy_dataset.md %}

You can also use our handy troubleshooting guide.

{% snippet faqs/galaxy/analysis_troubleshooting.md %}


category: gtn
filename: gtn-what-is-it
title: What is this website?
area: introduction
box_type: tip
content_hash: 1fd9766bcad0026bdc569d45f288b9d6
last_modified: 2026-05-15T22:28:09.609514
contributors_json: ["bebatut", "shiltemann"]
content:
<!-- GTN:IGNORE:004 -->

This website is a collection of hands-on tutorials that are designed to be interactive and are built around Galaxy:

![Interactive training]({{site.baseurl}}/shared/images/interactive_training.png "The hands-on nature of our training material. It can be used with two web browser windows open side-by-side, one pointed at the current tutorial and the other at a Galaxy instance")

This material is developed and maintained by the [worldwide Galaxy community](https://galaxyproject.org/). You can learn more about this effort by reading our [first](https://doi.org/10.1016/j.cels.2018.05.012) and [second articles](https://doi.org/10.1371/journal.pcbi.1010752)


category: gtn
filename: translations
title: Translations within the GTN
area: other
box_type: tip
content_hash: ee8d02488c7a9955936fefd4737972c9
last_modified: 2026-05-15T22:28:09.635349
contributors_json: ["hexylena"]
content:
The GTN currently supports two forms of translation:

- Manual (`tutorial_ES.md` and `slides_ES.html` for example)
- Automated (via linking through to Google Translate)

We accept manual translations if and only if there is a team that is able to commit to their maintenance. We need to ensure the trainings are kept up to date and high quality, but that requires native speakers of that language to maintain those translations.

Please contact us if you have any questions regarding translations.


category: gtn
filename: instructors_getting_started
title: Where do I start?
area: instructors
box_type: tip
content_hash: d46b5a73442616e4fe1c1f0a47868303
last_modified: 2026-05-15T22:28:09.632864
contributors_json: ["bebatut", "shiltemann"]
content:
Spend some time exploring the different tutorials and the different resources that are available. Become familiar with the structure of the tutorials and think about how you might use them in your teaching.


category: gtn
filename: contributors_tours
title: How can I test an Interactive Tour?
area: contributors
box_type: tip
content_hash: 256939ff78ed23f69ebc5f95dd2f19f0
last_modified: 2026-05-15T22:28:09.607084
contributors_json: ["shiltemann"]
content:
Perhaps you've been asked to review an interactive tour, or maybe you just want to try one out. The easiest way to run an interactive tour is to use the [Tour builder](https://tailordev.fr/blog/2017/07/19/the-galaxy-tour-builder-extension/) browser extension.

1. Install the Tour Builder extension to your browser ([Chrome Web Store](https://chrome.google.com/webstore/detail/galaxy-tour-builder/mdfbapknmcpnbmggahhaegehbbbmhmgg), [Firefox add-on](https://addons.mozilla.org/en-US/firefox/addon/galaxy-tour-builder/)).
2. Navigate to a Galaxy instance supporting the tutorial. To find which Galaxy instances support each tutorial, please see the dropdown menu next to the tutorial on the training website. Using one of the usegalaxy.\* instances ({% assign servers = nil | list_usegalaxy_servers_shuffle %}{% for server in servers %}[{{ server.name }}]({{ server.url }}){% if forloop.last %}{% else %}, {% endif %}{% endfor %})
) is usually a good bet.
3. Start the Tour Builder plugin by clicking on the icon in your browser menu bar
4. Copy the contents of the `tour.yaml` file into the Tour builder editor window
5. Click `Save` and then `Run`


