Hi, Thank you both for your replies. I know that the standard is to make one .rst file per HTML page, but here is some context on why I would prefer splitting at sections. The manuals I am musing about converting to Sphinx (from Texinfo with a Python preprocessor and a fragile and horrifyingly complicated build system) are here:
https://lilypond.org/doc/v2.23/Documentation/web/manuals.html with the main one being: https://lilypond.org/doc/v2.23/Documentation/notation/index.html As you can see, there is basically an image after every paragraph in most sections. I don't have a slow Internet connection or a poor browser to test, and maybe this is paranoid, but I fear pages are going to be too slow to load for some people if I keep the current structure which is generally one file per section, whereas there is an HTML page for each subsection. As a data point, you can visit https://lilypond.org/doc/v2.23/Documentation/notation-big-page which is the single-page HTML and takes some long seconds to load for me. Also, this is a mature piece of software, people are used to this documentation. I would prefer not to change its feel change too much, and keeping the current structure would mean making 145 files for Sphinx whereas there are 25 in Texinfo -- I at least find the latter more convenient for editing. So I guess I will have to plunge into the internals of HTML builders. Best regards, Jean -- You received this message because you are subscribed to the Google Groups "sphinx-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to sphinx-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sphinx-users/449bc509-5473-7d98-3efe-831379deb702%40abou-samra.fr.
