Hi Jacques,
I like your approach too. I propose creating a Tour page in Confluence.
This tour page will have a direct child page for the recent OFBiz releases,
like the following menu structure:
Tour
-> Release 13.7
-> Release 16.11
Each of the Release xx.x page is a Table of Content that links to other
existing pages.
The tour is meant for beginner and they are expected to go through the
topics from top to bottom.
With this approach, there will not be direct child page under each Release
xx.x page. Existing documentation isn’t affected.
Regards,
James
Jacques Le Roux wrote
> Hi James,
>
> I'm all for it.
>
> Note that I already used another strategy by referring to the history of
> few major pages[1] while documenting the Gradle from Ant. It though was a
> more an expedient than a structured way as you are proposing. But it could
> still be used when referring to old pages...
>
> [1] These pages contain the sentence "the pre-Gradle documentation is
> here", eg
> https://cwiki.apache.org/confluence/display/OFBIZ/Demo+and+Test+Setup+Guide
>
> Jacques
>
>
> Le 08/03/2017 à 18:05, james yong a écrit :
>> Hi all,
>>
>> I am planning to add some new documentation in Confluence but will have
>> them
>> placed/linked under the affected OFBiz release / version. For a user
>> navigating the documentation, the user can click on a particular OFBiz
>> release on the menu tree to display the list of topic for that OFBiz
>> version.
>>
>> What do you think of this approach? Are there better ways to structure
>> the
>> menu items?
>>
>> Cheers,
>> James Yong
>>
>>
>>
>> --
>> View this message in context:
>> http://ofbiz.135035.n4.nabble.com/Documentation-by-Release-Version-tp4703069.html
>> Sent from the OFBiz - Dev mailing list archive at Nabble.com.
>>
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Documentation-by-Release-Version-tp4703069p4703111.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
