OpenStack Manuals supplies its own CSS which looks similar if not identical to openstackdocstheme
Bug #1751795 reported by
Rob Cresswell
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| openstack-manuals |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
https:/
Does anyone have any insight into this? It seems redundant for manuals to supply that CSS.
Revision history for this message
| Andreas Jaeger (jaegerandi) wrote | #1 |
| Changed in openstack-manuals: | |
| importance: | Undecided → Wishlist |
| Changed in openstack-manuals: | |
| status: | New → Triaged |
| Changed in openstack-manuals: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
we developed those in different steps - and nobody had time to merge it.
In theory we could use one set of these for all of docs.openstack.org. So, remove from openstackdocstheme and only have it in openstack-manuals.
We haven't done that yet so that openstackdocstheme can be build and tested offline without changes in another repo.
I'm aware of these requirements:
1) building of standalone html pages that can be viewed offline
2) easy revieweing changes on review.
3) Offline testing for both openstackdocstheme and openstack-manuals
If you want to give it a try, please provide a short design summary, perhaps a spec.
Note: I really would like to find a solution that we need to store CSS only at a single place on the website (or single per release) instead of right now with each document and the index pages.