-
Task
-
Resolution: Done
-
Undefined
-
None
-
None
Goal:
- Add documentation for the Content Template Experience
- Explain to users:
- What use cases content templates help to solve
- How to create content templates
- Include mentioning pre-requisites of defining custom repositories.
- How to associate registered systems to content templates
- Link to a guide on how to register systems to console dot
- How to have updates to a template reflect on a system:
- Changes to date happen on next yum action
- Adding/removing a repository will be reflected after next checkin, or by running subscription-manager refresh
- mentioned on