Glad to help! I meant to say that I agree with your other suggestions
in this thread, by the way.
There are 2 more negatives for {contentbylabel} to be aware of:
2) The title of each link is just the page name, and some of the
Tapestry pages have less-than-great names (like "Test" and "Upload").
3) You can't directly control the ordering of the links in the list.
But overall I still like this approach.
On Thu, Dec 9, 2010 at 3:35 AM, Christophe Cordenier
<[email protected]> wrote:
> Thank you Bob for all these informations !
>
> 2010/12/9 Bob Harner <[email protected]>
>
>> The more automated way to maintain a "related topics" list in
>> Confluence is by assigning "labels" to related pages. For example,
>> both the "IoC cookbook - pattern" and "IoC - command" pages could have
>> a "chain-of-command" label, and both could have a "Related Articles"
>> box with just this little bit of markup:
>>
>> {float:right|background=#eee}
>> {contentbylabel:title=Related
>> Articles|showLabels=false|showSpace=false|labels=chain-of-command}
>> {float}
>>
>> Take a look at this on the following sandbox page:
>>
>>
>> https://cwiki.apache.org/confluence/display/TAPESTRY/Documentation+Improvement+Tasks
>>
>> One negative is that {contentbylabel} displays an unwanted link to the
>> current page. But overall the result is quite nice. (Eventually we
>> could add some javascript on the page that removes or hides those
>> redundant links from the Related Articles div.)
>>
>> There is also the {navmap} macro, but it is more of a horizontal list
>> and never seems to look very good.
>>
>> On Wed, Dec 8, 2010 at 7:54 AM, Christophe Cordenier
>> <[email protected]> wrote:
>> > Hi
>> >
>> > I have made some modifications on the documentation root page, feel free
>> to
>> > change !
>> > But i think we should really keep this page as light as possible. As a
>> > reader I hate to scroll, and this is where Spring documentation fails in
>> its
>> > reference guide IMHO.
>> >
>> > I have seen Howard's initiative to create a macro for the tutorial, I
>> think
>> > this should be used for other topics : having a root page and children
>> with
>> > navigation menu (Javascript, Ajax, Components, Testing...) Also to have a
>> > consistent breadcrumb we must provide consistent page structures.
>> >
>> > I also like the idea of related topics, but find it hard to maintain if
>> > written inside the document itself... Is there any other way to do this
>> with
>> > Confluence ?
>> >
>> > Cheers,
>> > Christophe.
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
>
> --
> 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]
