How should we structure the docs for the UI bundle?
- Are we going to store the UI component's documentation with it?
- These docs would include information for people developing/customizing the UI for their site as well as the documentation for other team members who want to use existing UI bundles.
- I'm proposing storing the docs for UI bundle usage here because it definitely feels ungainly to me to have those files over in the antora repo (I've already had to deal with the UI loading file that I had to spin off while setting up the playbook module. This also pushes us to set up Antora's documentation site.
- For modules, my first thought is role-based, i.e., a module for web/UI devs/maintainers (org or project team members responsible for creating a custom UI for their docs site) and writers (consumers? loaders? users? org or project team members who are mainly interacting with the UI bundle via the playbook, such as loading an existing UI, switching values in the UI key).
After we make a decision, I'll set up the appropriate issues for loading in the previous documentation and probably spawning the initial contributing file at the same time.