Re: Too many levels of menu before content in docs?
On Feb 25, 2008, at 5:42 PM, David Jencks wrote: This seems a wee bit excessive to me... ...Documentation Administration Administrative Tasks Administering applications Installing and removing applications Can we get expandable trees in the Documentation page? If so I think the links on Documentation should take you directly to documentation If not I'd be happier with a maximum of 1 layer of additional menus Agreed that it should be a flatter structure. I'm assuming that we'll be fixing these issues over time. IMO, best to get the documentation in place and then clean things up... --kevan
Re: Too many levels of menu before content in docs?
Dave, we need to figure out a way to organize th content. For 2.1 we'll hopefully end up around 200 pages, we can't have them all listed on one page. More specifically on Installing and removing applications it will only take 2 clicks to get there once in the 2.1 doc space From http://cwiki.apache.org/GMOxDOC21/documentation.html click on *Administration* and then on *Installing and removing applications*. The breadcrumbs help navigate through the hierarchy, a user will not necessarily have to navigate through every single one of those topics to get to the content wanted. On the 2.1 doc home page we definitively need to show a subset of topics, I think a 3 level (as we have it now) is OK. Maybe lower it to just 2 levels if we rework the titles and rearrange the structure. What do others think? Cheers! Hernan David Jencks wrote: This seems a wee bit excessive to me... ...Documentation Administration Administrative Tasks Administering applications Installing and removing applications Can we get expandable trees in the Documentation page? If so I think the links on Documentation should take you directly to documentation If not I'd be happier with a maximum of 1 layer of additional menus thanks david jencks
Re: Too many levels of menu before content in docs?
I liked David's idea of collapsible trees. Is that possible with the wiki? It doesn't seem like something a wiki would be able to inherently handle but one can hope. On Tue, Feb 26, 2008 at 1:41 PM, Hernan Cunico [EMAIL PROTECTED] wrote: Dave, we need to figure out a way to organize th content. For 2.1 we'll hopefully end up around 200 pages, we can't have them all listed on one page. More specifically on Installing and removing applications it will only take 2 clicks to get there once in the 2.1 doc space From http://cwiki.apache.org/GMOxDOC21/documentation.html click on *Administration* and then on *Installing and removing applications*. The breadcrumbs help navigate through the hierarchy, a user will not necessarily have to navigate through every single one of those topics to get to the content wanted. On the 2.1 doc home page we definitively need to show a subset of topics, I think a 3 level (as we have it now) is OK. Maybe lower it to just 2 levels if we rework the titles and rearrange the structure. What do others think? Cheers! Hernan David Jencks wrote: This seems a wee bit excessive to me... ...Documentation Administration Administrative Tasks Administering applications Installing and removing applications Can we get expandable trees in the Documentation page? If so I think the links on Documentation should take you directly to documentation If not I'd be happier with a maximum of 1 layer of additional menus thanks david jencks -- ~Jason Warner
Re: Too many levels of menu before content in docs?
Hi All, To reduce the number of layers... any thoughts on implementing a page that encompasses the main subject with well defined heading hierarchy then referencing using page + anchors? I recognize that for some documentation (administrative tasks...) this would yield an excessively long page - but with the right combination we may be able to reduce quite a few levels? Also, i like the tree idea Jason and David mentioned above. Wishing you all the best, Joseph Leong On Tue, Feb 26, 2008 at 1:49 PM, Jason Warner [EMAIL PROTECTED] wrote: I liked David's idea of collapsible trees. Is that possible with the wiki? It doesn't seem like something a wiki would be able to inherently handle but one can hope. On Tue, Feb 26, 2008 at 1:41 PM, Hernan Cunico [EMAIL PROTECTED] wrote: Dave, we need to figure out a way to organize th content. For 2.1 we'll hopefully end up around 200 pages, we can't have them all listed on one page. More specifically on Installing and removing applications it will only take 2 clicks to get there once in the 2.1 doc space From http://cwiki.apache.org/GMOxDOC21/documentation.html click on *Administration* and then on *Installing and removing applications*. The breadcrumbs help navigate through the hierarchy, a user will not necessarily have to navigate through every single one of those topics to get to the content wanted. On the 2.1 doc home page we definitively need to show a subset of topics, I think a 3 level (as we have it now) is OK. Maybe lower it to just 2 levels if we rework the titles and rearrange the structure. What do others think? Cheers! Hernan David Jencks wrote: This seems a wee bit excessive to me... ...Documentation Administration Administrative Tasks Administering applications Installing and removing applications Can we get expandable trees in the Documentation page? If so I think the links on Documentation should take you directly to documentation If not I'd be happier with a maximum of 1 layer of additional menus thanks david jencks -- ~Jason Warner
Re: Too many levels of menu before content in docs?
just so I understand better what the issue seem to be. A) is it because of how/where the content is displayed? or B) is it because the content is organized in a multi level structure? As for collapsible sections, that could address A). There are a few issues to workout with the autoexport plugin if we want to use features already available from Confluence. Cheers! Hernan Joseph Leong wrote: Hi All, To reduce the number of layers... any thoughts on implementing a page that encompasses the main subject with well defined heading hierarchy then referencing using page + anchors? I recognize that for some documentation (administrative tasks...) this would yield an excessively long page - but with the right combination we may be able to reduce quite a few levels? Also, i like the tree idea Jason and David mentioned above. Wishing you all the best, Joseph Leong On Tue, Feb 26, 2008 at 1:49 PM, Jason Warner [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I liked David's idea of collapsible trees. Is that possible with the wiki? It doesn't seem like something a wiki would be able to inherently handle but one can hope. On Tue, Feb 26, 2008 at 1:41 PM, Hernan Cunico [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Dave, we need to figure out a way to organize th content. For 2.1 we'll hopefully end up around 200 pages, we can't have them all listed on one page. More specifically on Installing and removing applications it will only take 2 clicks to get there once in the 2.1 doc space From http://cwiki.apache.org/GMOxDOC21/documentation.html click on *Administration* and then on *Installing and removing applications*. The breadcrumbs help navigate through the hierarchy, a user will not necessarily have to navigate through every single one of those topics to get to the content wanted. On the 2.1 doc home page we definitively need to show a subset of topics, I think a 3 level (as we have it now) is OK. Maybe lower it to just 2 levels if we rework the titles and rearrange the structure. What do others think? Cheers! Hernan David Jencks wrote: This seems a wee bit excessive to me... ...Documentation Administration Administrative Tasks Administering applications Installing and removing applications Can we get expandable trees in the Documentation page? If so I think the links on Documentation should take you directly to documentation If not I'd be happier with a maximum of 1 layer of additional menus thanks david jencks -- ~Jason Warner
Too many levels of menu before content in docs?
This seems a wee bit excessive to me... Documentation Administration Administrative Tasks Administering applications Installing and removing applications Can we get expandable trees in the Documentation page? If so I think the links on Documentation should take you directly to documentation If not I'd be happier with a maximum of 1 layer of additional menus thanks david jencks
