You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like this is really the full left column of collapsible API pages.
@drammock have you thought about how this could be optimized at the pydata-sphinx-theme end? We have ~500 of these docs so we are talking about something like 50MB of redundancy in content around these pages, all of which is identical except for which are collapsed/shown (which is maybe easy to take care of in JavaScript?). Maybe it's not worth worrying about, in which case feel free to close.
The text was updated successfully, but these errors were encountered:
This is a known issue upstream. I haven't followed the discussion too closely but I'll look at it again and see what, if anything, can be done about it
Here are the possibly relevant issues / guidance for reducing TOC size within the theme. I haven't re-read all of these recently, just collecting them here as a breadcrumb for whenever I or someone else has time to fix this. TLDR: it probably involves either limiting TOC depth with a theme setting, or suppressing (via path/wildcard) certain TOC entries from showing up at all (regardless of their depth).
Waiting for CircleCI to upload artifacts, I noticed:
locally, it looks like ~80 kB is in a
<ul>
with ~3k lines of the form:Looks like this is really the full left column of collapsible API pages.
@drammock have you thought about how this could be optimized at the pydata-sphinx-theme end? We have ~500 of these docs so we are talking about something like 50MB of redundancy in content around these pages, all of which is identical except for which are collapsed/shown (which is maybe easy to take care of in JavaScript?). Maybe it's not worth worrying about, in which case feel free to close.
The text was updated successfully, but these errors were encountered: