search

epiverse-trace / howto

https://epiverse-trace.github.io/howto/
Creative Commons Attribution 4.0 International
1 stars 2 forks source link

add workflow/pipelines summary figures in the "steps in detail" section #44

Open avallecam opened 8 months ago

avallecam commented 8 months ago

originally suggested by @Karim-Mane

the "step in details" is optional to keep the barrier low for contributions.

for stable entries, we can complement or replace the "steps in detail" with visual summaries to quickly wrap multiple package interoperability