That's a possible workaround. I didn't want to go that route as I'll
then have to maintain two stylesheets. I was hoping to be able to
demonstrate that Sphinx would lower our maintenance overhead for
documentation, and complicating the stylesheet situation undermines
this, but it's not a deal-breaker.
well, just copy the main theme into a custom one, place it within
your documentation project and add the styling in-place => one file.
then sell it as flexibility ("this way we can later, ahem, harmonize,
ahem, link color, with our external web page -- i hear management
wants it badly", "it makes us independent from changes to the themes
in later sphinx updates" :)
even if not, the 2nd css need not become part of the installation,
just the project. and you'd actually have to maintain neither,
unless you plan to mess with the theme regularly -- and then
solution one is what you'd already have in any case.
--
You received this message because you are subscribed to the Google Groups
"sphinx-dev" group.
To post to this group, send email to sphinx-dev@googlegroups.com.
To unsubscribe from this group, send email to
sphinx-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sphinx-dev?hl=en.
