Allow multiple start paths to be specified per content source in the playbook
Antora strives to allow you to organize your content as you want. One of those layouts is to use folders to organize different components or component versions inside the same branch of a repository. While Antora can already handle this scenario just fine, doing so requires using multiple content source entries in the playbook, one per start path.
Like with branches, it would be convenient to be able to specify multiple start paths (possibly a start path pattern) under a single content source entry.
content: sources: - url: https://github.com/org/docs-repo.git branches: master start_path: core, api, extensions
(We could also consider introducing the start_paths key, which would take precedence over the start_path key).
If multiple references are specified in addition to multiple start paths, the aggregator will look for those start paths in each of those references. So there will be some caveats to watch out for. Regardless, this syntax would drastically cut down on the number of entries in the playbook.