Remove toc warnings

[kwankyu]

Part of #33833. Fix

• "ERROR: Adding a table of contents in Furo-based documentation is unnecessary" - https://73e5aa3fbbec2d751a47064c14479fc0d55c3de9--sagemath-tobias.netlify.app/installation/source.html#installation-in-a-multiuser-environment

We add :class: like

.. contents::
   :class: this-will-duplicate-information-and-it-is-still-useful-here

to remove the furo's warning, since those toc's are useful for pdf docs and not bad even for html docs.

Depends on #34252

Component: documentation

Author: Kwankyu Lee

Branch: 16cbb44

Reviewer: Matthias Koeppe

Issue created by migration from https://trac.sagemath.org/ticket/34262

[kwankyu]

Branch: u/klee/remove_toc_warnings

[kwankyu]

Commit: 49a9316

[kwankyu]

Author: Kwankyu Lee

[kwankyu]

Last 10 new commits:

f19b597	Add link to the logo
09d5f5c	Fix the logo link for reference
ae75d53	Fix a subtle reference problem for build_options
3519bed	Run docbuild workflow with single thread
1274718	Fix a suspicious part of categories doc
e5b1f7e	Add search.html
ebd3b77	Better pygments style
73e5aa3	Make white logo transparent to match with furo
183e558	Merge branch 'develop' into t/34252/revive-furo
49a9316	Remove toc warnings

[kwankyu]

Dependencies: #34252

[mkoeppe]

comment:7

I still see this warning in https://49a9316b46ff867a3501f031fb9d5f4fbd846569--sagemath-tobias.netlify.app/installation/source.html#installation-in-a-multiuser-environment

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

16cbb44

Take care of a missed toc directive

[sagetrac-git]

Changed commit from 49a9316 to 16cbb44

[kwankyu]

comment:9

While working on this ticket, I experienced ./configure --enable-editable, which is the default now. I needed to search the whole src/doc directory and subdirectories, but then since the src tree was cluttered with lots of build artifacts, the search would take much more time. Hence I did ./configure --disable-editable to go back to the "normal" state of the src tree. From my experience, I doubt if the new default is really good for developers...

[mkoeppe]

comment:11

It may need some time to get used to it coming from longstanding Sage practice, but editable builds are the standard way to develop in the Python world

[kwankyu]

comment:12

Replying to @mkoeppe:

but editable builds are the standard way to develop in the Python world

Okay.

[mkoeppe]

Reviewer: Matthias Koeppe

[vbraun]

Changed branch from u/klee/remove_toc_warnings to 16cbb44

[tobiasdiez]

Changed commit from 16cbb44 to none

[tobiasdiez]

comment:15

Would it be possible to only display the toc in the pdf? In my opinion, they just duplicate information that is already displayed in the right column.

[kwankyu]

comment:16

Replying to @tobiasdiez:

Would it be possible to only display the toc in the pdf? In my opinion, they just duplicate information that is already displayed in the right column.

They are duplicated but often a short version of the full toc on the right column, and hence they are still useful. So I think it is not worth the effort to try to find a way to show them only in the pdf.