I wrote a tutorial for nf-core/eager on how a researcher can use custom config files and profiles to share pipeline parameters for reproducible science (:tada:).
@ewels suggested that this would be suitable for the website, as it isn't EAGER specific. However when I tried 'merging' the text with the current 'configuration' page, this became very difficult because of the style of writing (the tutorial being exactly that, a step by step walkthrough with more detail), and I realised the context was different - infrastructual configs vs pipeline parameters. The former is aimed at bioinfs/sys admins who understand how to configure a scheduler, vs. a user of a pipeline who just wants the pipeline to 'run'.
Therefore I would to propose a new section to the website, which contain pipeline user-focused (or new developer) step-by-step tutorials of various aspects. I think 'tutorials' is actually a good name as well, as this will attract the eye of people explicitly looking for 'introductions' to certain aspects. Thoughts @nf-core/core ?
I wrote a tutorial for nf-core/eager on how a researcher can use custom config files and profiles to share pipeline parameters for reproducible science (:tada:).
@ewels suggested that this would be suitable for the website, as it isn't EAGER specific. However when I tried 'merging' the text with the current 'configuration' page, this became very difficult because of the style of writing (the tutorial being exactly that, a step by step walkthrough with more detail), and I realised the context was different - infrastructual configs vs pipeline parameters. The former is aimed at bioinfs/sys admins who understand how to configure a scheduler, vs. a user of a pipeline who just wants the pipeline to 'run'.
Therefore I would to propose a new section to the website, which contain pipeline user-focused (or new developer) step-by-step tutorials of various aspects. I think 'tutorials' is actually a good name as well, as this will attract the eye of people explicitly looking for 'introductions' to certain aspects. Thoughts @nf-core/core ?