Description of problem: Chapter, section, and process entries in the content specification cannot contain any text so you need to add another topic with the same name. This also hampers the structures of guides. Expected results: Make chapters, sections and process entries to be topics. Also, it would be nice to define a chapter, section, or process only through the indentation. So it would look something like this: Part: Introduction Business Process Model and Notation [13577] About JBoss BPMS [13504] Components [13492] Core Engine [13776] Tools [13496] Process Designer [13773] Form Builder [13774] Guvnor Repository [13775] INSTEAD OF: Part: Introduction Chapter: Introduction Business Process Model and Notation [13577] About JBoss BPMS [13504] Section: Components Components [13492] Core Engine [13776] Section: Tools Tools [13496] Process Designer [13773] Form Builder [13774] Guvnor Repository [13775]
The Markers are there as it is impossible to tell based on Indentation, as well as human readability . ie. The following (Ignoring the "Part:" you used, since it makes little sense to enforce it in some places and not others): Introduction Business Process Model and Notation About JBoss BPMS Components [13492] Core Engine [13776] Tools Process Designer [13773] Form Builder [13774] Guvnor Repository [13775] could either be interpreted as: Chapter: Introduction Section: Business Process Model and Notation [13577] Section: About JBoss BPMS [13504] Components [13492] Core Engine [13776] Section: Tools [13496] Process Designer [13773] Form Builder [13774] Guvnor Repository [13775] or Part: Introduction Chapter: Business Process Model and Notation [13577] Section: About JBoss BPMS [13504] Components [13492] Core Engine [13776] Section: Tools [13496] Process Designer [13773] Form Builder [13774] Guvnor Repository [13775] or Chapter: Introduction Section: Business Process Model and Notation Process: About JBoss BPMS Components [13492] Core Engine [13776] Section: Tools [13496] Process Designer [13773] Form Builder [13774] Guvnor Repository [13775] As for the other part of the bug there is already an RFE for it Bug #805380, with technical limitations described in Bug #799924 *** This bug has been marked as a duplicate of bug 805380 ***