Hi folks! It may have flown under people's radars,...
# pipeline-maintainers
p
Hi folks! It may have flown under people's radars, but Nextflow config now has a new
manifest.icon
scope that can accept a path to a custom pipeline logo 👀 (absolute or relative, for us relative is preferred as that'll be better for forks etc). These will then show up in Seqera Platform launchpads - we could probably look into rendering them on the nf-core pipelines page if set too. I know many of you have put effort into lovely custom pipeline icons, so here's your chance to show them off!
j
Do you have an example?
It's basically a one-line change in
nextflow.config
within
manifest
scope:
Copy code
icon = './docs/images/<pipeline-icon>.png'
j
I meant rendering it it e.g. on platform
p
CleanShot 2025-05-28 at 13.09.16@2x.png
CleanShot 2025-05-28 at 13.09.41@2x.png
🤣 1
j
Nice! I wonder if we can exploit that ourselves somehow too
p
Yeah I was thinking the same, that's what my vague trail-off here was about:
we could probably look into rendering them on the nf-core pipelines page if set too.
👍 1
j
MultiQC reports?
f
Can we point to the raw github link from the icon repo?!
p
I guess! Not sure we even need to have pipeline logos in there then tbh. Could just grab them from the pipeline repos on the website and use the same logic to auto-populate a table of links on the logos repo readme or something.
f
Just want to avoid having lots of duplicates flying around, makes it painful to find everything after. I like having all stickers and logos in one repo, that makes it easiest to find for presentations etc. But to be fair, probably need a copy in the actual pipeline repo as well 🫠
👍🏻 1
p
Oh I see, I interpreted you meaning it the other way. Yeah I think that if we have to pick one, the pipeline repo is the place they should be (not logos)