Page History

...

• Inherited navigational elements
• Using submenus
• Ability to generate within the subproject, or at the top level and get the same results (with the exception of aggregated reports)
• No strict requirements on filesystem layout other than those that already exist for Maven projects
• Ability to aggregate reports (individual report technique out of scope here)
• Breadcrumbing

...

<menu name="Commons Common">
  <item ... />
</menu>

<menu name="Commons Specifics" inherit="false">
  <item ... />
</menu>

Using Submenus

We have the collapse="true" element that can be added to a (sub)menu to indicate whether it is only expanded when inside that part of the navigation. We would need to add collapse="inherit" to use the parent behaviour.

Symmetric generation

When generating within the top level, content will be generated into the target/site location of the subproject, then copied into the right place within the target/site of the top level project, using the difference between the top level URL and the subproject's URL as the relative path to use (which will default to artifactId).

When generated within the subproject, it is only generated into the subproject. The site will appear correctly, but navigating to upper levels will not be possible when previewing. However, it can be deployed from there directly into the right subdirectory on the site.