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.
Best regards, Jacob Faibussowitsch (Jacob Fai - booss - oh - vitch) > On Apr 27, 2021, at 09:33, Karl Rupp <[email protected]> wrote: > > Hi, > > such adjustments should not need a direct modification of the theme. One can > just override the CSS settings in custom CSS files instead: > https://docs.readthedocs.io/en/stable/guides/adding-custom-css.html > > 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). > > Best regards, > Karli > > On 4/26/21 8:58 AM, Patrick Sanan wrote: >> As far as I know (which isn't very far, with web stuff), changing things on >> that level requires somehow getting into CSS. >> For instance, you can see what it looks like with other widths directly from >> Firefox (fun, didn't know you could do this): >> - go to the page >> - hit F12 >> - click around on the left to find the <div> that corresponds to the part >> you care about >> - look in the middle column to find the piece of CSS that's controlling >> things (here, something called .col-md-3) >> - edit the CSS - in attached screenshot I change the max width of that >> sidebar to 5%. >> 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). >> 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. >>> Am 23.04.2021 um 23:12 schrieb Barry Smith <[email protected] >>> <mailto:[email protected]>>: >>> >>> >>> 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. >>> >>> >>> >>>> On Apr 23, 2021, at 1:08 PM, Patrick Sanan <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> >>>> It is possible to put things there, as in this link which is both >>>> documentation and example: >>>> https://pydata-sphinx-theme.readthedocs.io/en/latest/user_guide/sections.html#the-left-sidebar >>>> >>>> <https://pydata-sphinx-theme.readthedocs.io/en/latest/user_guide/sections.html#the-left-sidebar> >>>> >>>> Other projects using this theme have the mostly-empty left sidebar: >>>> https://numpy.org/doc/stable/ <https://numpy.org/doc/stable/> >>>> https://jupyter.readthedocs.io/en/latest/ >>>> <https://jupyter.readthedocs.io/en/latest/> >>>> >>>> (They also have fancier landing pages, though, which we have been >>>> discussing). >>>> >>>> >>>> It goes away on mobile devices or small windows, at least. >>>> >>>> >>>>> Am 23.04.2021 um 19:21 schrieb Barry Smith <[email protected] >>>>> <mailto:[email protected]>>: >>>>> >>>>> >>>>> 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? >>>>> >>>>> Barry >>>>> >>>> >>>
