Ok thanks, I now understand your idea and how you see it as being some demo. It’s also true that the AWM examples currently located in the Help module are demos too.
In order to move them under the Help module, they would need to be used in the Help pages. That’s not too hard to do and to present them as demo page templates.
So I’m not against doing this. We would need to decide if we move them inside the help-ui module or as new modules. The pro of having separate modules (ie separate extensions) is that users can uninstall them separately (they might want to keep the page templates but not the AWM demo pages for example). However, this causes a problem: the main help UI has a dep on them so it would need to be code with some velocity script that adapts the UI display if the pages are not present (or even better, provide a UIXP for extensions to contribute new help topics, and then have help-awm-ui and help-pagetemplates-ui modules bringing both the demo pages + the associate help topics).
The other option, is to tell users to not uninstall but delete pages (marked as demo pages in the pom) that they don’t want to see. That would still cause the problem with the help UI that would have broken links possibly.
So if we want to go the help way, I’d be for the following:
- Introduce a UIXP for help topics if we don’t already have one. It’s not too hard since we have a grid of help topics and it’s easy to imagine contributing more cells in that grid.
- Move AWM demo pages to some
help-awm-uimodule and move the help related to AWM there (UIX). - Create a
help-pagetemplates-uimodule with its UIX.
WDYT?
Thanks