Bioinformatics Field Guide is a practical, reproducible learning resource for bioinformatics. It is built for readers who want to move from setup and command-line confidence into real sequencing files, public data, and analysis decisions without getting lost in scattered tutorials.
Read the published site · Open the content folder · Use the resources
Bioinformatics is full of invisible failure points: mismatched genome builds, confusing file formats, missing metadata, fragile environments, and tools that work only when every prerequisite is just right.
This project turns those rough edges into guided, testable lessons:
- short articles with plain-language explanations
- runnable commands with expected outputs
- tiny datasets for safe practice
- reproducible Conda, Docker, notebook, and script resources
- GitHub Discussions for reader questions and corrections
| No. | Guide | What readers practice | Resources |
|---|---|---|---|
| 01 | Set Up Your Laptop For Bioinformatics | Conda, Docker, JupyterLab, VS Code, Ollama, BioChatter | Week 1 resources |
| 02 | What Programming Languages Should A Bioinformatician Know? | Bash, Python, R, SQL, notebooks, AI-assisted learning | Week 2 resources |
| 03 | The Bioinformatics File Types You Must Know | FASTQ, SAM/BAM/CRAM, VCF, GTF/GFF, BED, bedGraph, bigWig, metadata | Week 3 resources |
Only published guides are listed here. Draft and future articles are intentionally hidden from this landing page until they are ready.
If you are new to bioinformatics:
- Start with Week 1 to set up a working environment.
- Use Week 2 to understand when to use Bash, Python, R, and SQL.
- Spend extra time on Week 3 because file literacy is where many real projects succeed or fail.
If you already work in bioinformatics, jump directly to Week 3 and run the file-format lab.
content/
posts/ Published article source files and drafts
resources/ Conda files, notebooks, scripts, tiny datasets, and tutorial assets
assets/ Site CSS and JavaScript
templates/ Shared article template
Each article supports GitHub-powered discussion through giscus. If something is unclear, incorrect, or missing, open a discussion from the article footer or suggest an edit through GitHub.
Published through Week 3. Future guides will be added only after review, testing, and cleanup.