Workflow development
Build bioinformatics pipelines
Develop, optimise and maintain reproducible workflows for genomic, transcriptomic and other biological data.
Contribute to open-source bioinformatics, develop reproducible workflows, improve scientific resources and collaborate with people who share an interest in computational biology.
Your contribution journey
A collaborative development workflow
Explore a project
Find a workflow or research resource
Fork & develop
Work on your own branch
Test & document
Check your changes and results
Submit a pull request
Share your contribution
Everyone can contribute
Open-source scientific development depends on more than programming. Researchers provide biological insight, developers build tools, students bring fresh perspectives and contributors help make scientific resources more accessible.
Whether you are writing your first documentation page or developing a complex analysis workflow, there are meaningful ways to participate.
Ways to contribute
Explore different contribution areas. You can start with what you already know and gradually develop new skills.
Workflow development
Develop, optimise and maintain reproducible workflows for genomic, transcriptomic and other biological data.
Scientific research
Explore biological datasets, develop computational methods and investigate questions across biomedical research.
Documentation
Write practical guides, explain methods, improve installation instructions and make workflows easier to understand.
Testing & validation
Run workflows with suitable test data, identify bugs, report unexpected results and improve reliability.
Education
Develop tutorials, practical exercises and learning material for people entering computational biology.
Community & design
Help improve website usability, scientific visualisation, accessibility and the overall community experience.
Showing all 6 contribution areas.
Getting started with GitHub
The following is a typical open-source workflow. Explore each step to understand how contributions move from an idea to a proposed improvement.
Visit a GitHub repository and create a fork. This gives you your own copy where you can safely make changes without modifying the original project.
Example command
# Fork the repository using GitHub's Fork buttonContribution guidelines
We aim to make contributions transparent, understandable and maintainable. These principles provide a starting point for participating in Bioxflow projects.
Before making substantial changes, discuss your idea or report a bug so that the work can be coordinated.
Keep each contribution focused on one feature, fix or improvement. Use a descriptive branch name.
Explain what you changed, why it matters and how someone else can reproduce or test it.
Describe your changes clearly and include relevant test results, screenshots or example outputs.
Built for reproducibility
Bioinformatics workflows need clear inputs, defined software environments, documented parameters and reliable outputs. Contributors can help improve each of these components.
Explore pipeline concepts →nextflow.enable.dsl = 2
params.input = 'data/*.fastq.gz'
// Example workflow structure
process FASTQC {
input:
path reads
output:
path '*_fastqc.html'
script:
"""
fastqc ${reads}
"""
}
workflow {
reads = Channel.fromPath(params.input)
FASTQC(reads)
}Illustrative Nextflow code — not a validated production workflow.
Build with Bioxflow
Have an idea, a scientific question or a useful skill to share? We would love to hear from you.