A community effort to collect a curated set of analysis pipelines built using Nextflow.

nf-core

&gt; Question 1
I don't really understand the question to be honest. MultiQC was written specifically for the use case of parsing outputs from tools where the codebase can't be changed. So.. basically every module is an example. If you're feeling masochistic then just take a look at the <https://github.com/ewels/MultiQC/blob/623e0a1b086788c605905904eaa30f95852796e0/multiqc/modules/bowtie2/bowtie2.py#L58-L60|bowtie2 module>...

Ah, sorry, I had heard about tools having "multiqc support" and incorrectly assumed it was implemented in the tools themselves. This makes it clear how it works.

In some cases I guess it could be people doing the `_mqc` custom content thing. And tool authors often come to MultiQC to write a module to support their own tools these days.

You can also create <https://multiqc.info/docs/development/plugins/|MultiQC plugins> to have a custom module to support a tool outside of the main codebase, but that's a bit of a hassle as it doesn't play nicely with using the general-use docker containers

So yeah, likely that people just mean that there is a MultiQC module for that tool's output..