Confluence has options for both creating tabbed views on pages, and
for creating dynamically hidden/revealed sections. I think the latter
might work well, so you start with a list of modules and can expend
them to get to the detail links for that module.
BTW, instead of using the {code} macro, use the {newcode} macro ...
just noticed it. Much prettier output!
On Wed, Sep 29, 2010 at 9:56 AM, Christophe Cordenier
<[email protected]> wrote:
> Sorry for spamming, but i think that we have to discuss these kind of
> thing before going further with Confluence documentation.
>
> Actually, i have chosed to display Tapestry IOC, then CORE... then
> display the reference links in each version
>
> What about the other modules, if you create a section for every module
> the Documentation page will become un-readable...
>
> I suggest to create a page for reference links, but i am not convinced.
>
> Any idea ?
>
> --
> Regards,
> Christophe Cordenier.
>
> Committer on Apache Tapestry 5
> Co-creator of wooki @wookicentral.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
