How should we organize content

[epage]

Inputs

• Allow evolution
• Don't break CIs
• Simple, naiive case should not lead user to unstable resources
  • If using branches for different versions, someone might naiively grab the URL for a master version of a script and we could end up breaking them
• Testability
• Azure Pipelines: each template repo has to be explicitly added in the resources
• Easy changelog management