<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">One of the primary goals of the new documentation was that maintenance of docs be as streamlined as possible, i.e. through a single API/language/interface. A new dev should have to learn the absolute bare minimum possible to be able to make changes to documentation, so while CSS add-ons is on face less code diff and simpler to implement right now, it doesn’t fit with the single API doctrine.<div class=""><br class=""><div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div>Best regards,<br class=""><br class="">Jacob Faibussowitsch<br class="">(Jacob Fai - booss - oh - vitch)<br class=""></div></div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Apr 27, 2021, at 09:33, Karl Rupp <<a href="mailto:rupp@iue.tuwien.ac.at" class="">rupp@iue.tuwien.ac.at</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi,<br class=""><br class="">such adjustments should not need a direct modification of the theme. One can just override the CSS settings in custom CSS files instead:<br class=""> <a href="https://docs.readthedocs.io/en/stable/guides/adding-custom-css.html" class="">https://docs.readthedocs.io/en/stable/guides/adding-custom-css.html</a><br class=""><br class="">The benefit of such an approach is that all future updates of the theme will continue to work. Plus, one has all CSS-tweaks neatly collected in a small file (ideally just a few lines).<br class=""><br class="">Best regards,<br class="">Karli<br class=""><br class="">On 4/26/21 8:58 AM, Patrick Sanan wrote:<br class=""><blockquote type="cite" class="">As far as I know (which isn't very far, with web stuff), changing things on that level requires somehow getting into CSS.<br class="">For instance, you can see what it looks like with other widths directly from Firefox (fun, didn't know you could do this):<br class="">- go to the page<br class="">- hit F12<br class="">- click around on the left to find the <div> that corresponds to the part you care about<br class="">- look in the middle column to find the piece of CSS that's controlling things (here, something called .col-md-3)<br class="">- edit the CSS - in attached screenshot I change the max width of that sidebar to 5%.<br class="">But, I want to avoid having to do things on the level of CSS and HTML - I think that should be done as a collective effort in maintaining the theme (and Sphinx itself).<br class="">If we really care enough about the width of that sidebar, we'll create a fork of the theme, add a setting for it, and try to get it merged to the theme's release branch.<br class=""><blockquote type="cite" class="">Am 23.04.2021 um 23:12 schrieb Barry Smith <<a href="mailto:bsmith@petsc.dev" class="">bsmith@petsc.dev</a> <<a href="mailto:bsmith@petsc.dev" class="">mailto:bsmith@petsc.dev</a>>>:<br class=""><br class=""><br class=""> Thanks. Even if we just leave it is there a way to make it a little "skinnier", it seems very wide in my default browser.<br class=""><br class=""><br class=""><br class=""><blockquote type="cite" class="">On Apr 23, 2021, at 1:08 PM, Patrick Sanan <<a href="mailto:patrick.sanan@gmail.com" class="">patrick.sanan@gmail.com</a> <<a href="mailto:patrick.sanan@gmail.com" class="">mailto:patrick.sanan@gmail.com</a>>> wrote:<br class=""><br class="">It is possible to put things there, as in this link which is both documentation and example:<br class=""><a href="https://pydata-sphinx-theme.readthedocs.io/en/latest/user_guide/sections.html#the-left-sidebar" class="">https://pydata-sphinx-theme.readthedocs.io/en/latest/user_guide/sections.html#the-left-sidebar</a> <<a href="https://pydata-sphinx-theme.readthedocs.io/en/latest/user_guide/sections.html#the-left-sidebar" class="">https://pydata-sphinx-theme.readthedocs.io/en/latest/user_guide/sections.html#the-left-sidebar</a>><br class=""><br class="">Other projects using this theme have the mostly-empty left sidebar:<br class=""><a href="https://numpy.org/doc/stable/" class="">https://numpy.org/doc/stable/</a> <<a href="https://numpy.org/doc/stable/" class="">https://numpy.org/doc/stable/</a>><br class=""><a href="https://jupyter.readthedocs.io/en/latest/" class="">https://jupyter.readthedocs.io/en/latest/</a> <<a href="https://jupyter.readthedocs.io/en/latest/" class="">https://jupyter.readthedocs.io/en/latest/</a>><br class=""><br class="">(They also have fancier landing pages, though, which we have been discussing).<br class=""><br class=""><br class="">It goes away on mobile devices or small windows, at least.<br class=""><br class=""><br class=""><blockquote type="cite" class="">Am 23.04.2021 um 19:21 schrieb Barry Smith <<a href="mailto:bsmith@petsc.dev" class="">bsmith@petsc.dev</a> <<a href="mailto:bsmith@petsc.dev" class="">mailto:bsmith@petsc.dev</a>>>:<br class=""><br class=""><br class=""> There is a lot of empty space on the left side of the website pages; under the Search slot. Does this empty left side need to be so large, seems to waste a lot of the screen?<br class=""><br class=""> Barry<br class=""><br class=""></blockquote><br class=""></blockquote><br class=""></blockquote></blockquote></div></div></blockquote></div><br class=""></div></body></html>