Hi Hernan,
No problem on changing the names, I just did that. I have also added
the {scrollbar} macro to it.
I tried switching to the children macro and the only problem seems to be
that the Introduction is listed after the diagrams and the GBeans
section. Do I have the ability change the order of the children pages?
Thanks,
Ryan
Hernan Cunico wrote:
Hi Ryan,
The Architecture doc is looking great, thanks for your contributions.
I do have some "Confluence" related comments that will help with the
entire Geronimo spaces integration.
For example.
http://cwiki.apache.org/confluence/display/GMOxDEV/Geronimo+Architecture
In that page you are using Alias for each page link
[Introduction|ArchitectureIntroduction]
[GBeans|ArchitectureGBeans]
[Geronimo Kernel|Geronimo Kernel]
[Module View|GeronimoModuleView]
[Deployment Subsystem|DeploymentSubsystem]
I would suggest you create the page with the final title, for example
Architecture Introduction
GBeans Architecture
Geronimo Kernel
Geronimo Module View
Deployment Subsystem
Don't worry about the blanks in the title, Confluence can manage these
and what's even better, the autoexport plugin does even a better job.
Using the "final" name in the page title instead of an alias has some
additional benefits, specially for automatically built TOCs. See
http://cwiki.apache.org/confluence/display/GMOxDEV/Index as an example
for automatically built TOC.
Another tip, all across the doc we are using the macro {scrollbar}
(although the GMOxDEV is not the best example), this macro helps the
back and forth navigation across similar topics grouped under the same
parent page.
Nice doc !!!
Cheers!
Hernan
