Restructure pipeline configs to improve discoverability

[edmundmiller]

I think restructuring the configs across the board like this would make it easier for new maintainers to find configs for pipeline for their institutions.

[lpantano]

I support this! At least for me is easy to see now.

[jfy133]

This might be a good Hackathon task thinking about it (just moving stuff around), but we would need to coordinate with @mashehu as will need to update how the website parses this repo

[mashehu]

Yep, please don't move anything without updating the website at the same time. My hope is that surfacing them on the website with the latest website upgrade should solve already a lot of the discoverability.

[mahesh-panchal]

Can I get an overview of what you're doing that improves discoverability?

Each config and related material (docs, pipeline) is put in a folder with the profile name?
I think that's better. It'll allow better dynamic inclusion too.

I think the README should be right next to the config.

What other discoverability issues are there?

• Key words? Hostnames?
• What the config supports in plain language?