On Wed, Oct 14, 2026 at 04:35:57PM +0100, Gavin Smith wrote: > On Tue, Oct 13, 2026 at 10:18:09PM +0200, Patrice Dumas wrote: > > On Tue, Oct 13, 2026 at 08:52:08PM +0100, Gavin Smith wrote: > > > I've done some work on this but I have a lot more to do on this as it will > > > likely involve reviewing several different parts of the documentation. > > > > It is a big change, but I think that it would be better if the manual was > > reorganized as the following: > > > > Have "Chapter Structuring" before "Nodes" > > Is the thinking to have the more familiar concept described to users first > as those familiar with other markup languages (e.g. HTML, Markdown) will > easily > grasp the idea of a sectioning(*) command? It would also be supporting users > to write files without using the @node command which may be a common use case.
It was more for your second sentence, to put first the common use case, which would by now be hierarchical document, no @node unless different from the sectioning command, automatic menus. > In the "Nodes" chapter, the "Texinfo Document Structure" node refers to the > "sectioning structure", even though we haven't had the chapter on sectioning > commands yet, so it may provide a better flow of information to have the > chapter > on sectioning commands first. Especially to describe the hierarchical document structure. > There is quite a lot of information in both chapters so we should proceed > carefully to avoid making a mess. For newcommers who do not need compatibility with older texi2any/makeinfo versions, the current way the manual is written has to much irrelevant information, in my opinion, something that Heime also reported. We should keep some information on the old ways, both for user who see older manuals, and also because it is stil very relevant in case of non hierarchical manuals, but it should not be on the way of a first read, if possible. -- Pat
