[WIP] h1 page title has parent group title instead of parent path element

[danielkec]

When referencing documents from shared folder, h1 title parent is derived from parent path element:

Use parent group title from navigation like this:

Signed-off-by: Daniel Kec daniel.kec@oracle.com

[romain-grecourt]

Your first screenshot does not show the route, but based on your changes seems that you are changing the routes.

I'm guessing that you are including an .adoc file in the navigation from something like shared/.

• Is this file supposed to be included in-place in the navigation multiple times ?
• Or is is supposed to be included using an include directive in two documents that have different titles and routes ?

The route in your screenshot is like this: #/se/reactivestreams/02_engine/Reactive+Streams.
Why is there an extra slash between engine and reactive ?

The current way of computing the routes based on path has some major flaws, (e.g. the nav order based on filename), however the routes should still be based on the file path.

It seems that you are trying to base the route of the navigation hierarchy because you are including something for shared/ directly in the navigation under Reactive Streams. Can you try instead to have a document under reactivestreams/ that uses an includes directive to include content from shared/ ?

[danielkec]

@romain-grecourt I've been trying to avoid an extra doc with includes by smuggling parent group title as a path param(Reactive+Streams is escaped goup.title from navigation), so I can use it in h1 title. It almost worked, but assciidoc internal links got broken horribly so I'm going back to the intermediate adoc with include reference as you suggest.

[romain-grecourt]

Yeah, the current implementation is far from perfect, and touching the routes will have tons of side effects.