Refactor Docs toolchain to separate Transforms from Templates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
Currently, the transform engine for the documentation repositories is https:/
I don't understand why both the transform templates for Rackspace Proper and Openstack are in this repository. I shouldn't have to be an OpenStack committer to change the markup templates for Rackspace Documentation.
I'm wondering if there's a way to refactor the tooling to have something more like this:
1) The transformer (I don't know if this is clouddocs-
2) The transform templates. I would expect there would be one of these per property. I.e. api.openstack.org would be one repository, and docs.rackspace.com would be another, each in those companies (or organizations) own github repo.
3) The documentation proper. This could presumably stay as is.
Just trying to get my head around how to have a clearer separation between OS doc and RS doc templates.
Changed in openstack-manuals: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
How do other consumers who brand content with this plugin maintain their branding (transforms)?