Howard -- meanwhile I've gone ahead and reparented those "special"
pages to under Index for you.

On Mon, Jan 3, 2011 at 2:56 PM, Katia Aresti <[email protected]> wrote:
> Hi,
>
> I said something last year - happy new year ^_^
> I'm just thinking about something lighter, more detailed or adapted to every
> page. Personally I find the current menu not very navigable and usable,
> despite the quick way to generate it. Of course, this is just my impression
> and felling, this point can be discussed.
>
> Concerning what I have in mind, I need some days to find time, make some
> tests and show you an example.
>
> Katia
>
>
> 2011/1/3 Bob Harner <[email protected]>
>
>> As long as the page names don't change, I don't think there's any
>> problem with moving pages around in the hierarchy, since their final
>> exported file names won't change (and therefore no links will break on
>> the exported site).
>>
>> Katia had said something a few days ago about reworking how that
>> section of the documentation page looked, but not sure what she had in
>> mind specifically.
>>
>> On Mon, Jan 3, 2011 at 2:04 PM, Howard Lewis Ship <[email protected]>
>> wrote:
>> > The index down the right side of the Documentation page has a few odd
>> > entries towards the end, such as Board Reports, menuLeft, etc.
>> >
>> > I there any reason I can't move these to children of, say, the Index
>> page,
>> > so that they won't show up within the Documentation?
>> >
>> > --
>> > 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]
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to