Hi all,
I was a little worried about this work-around as I thought it might
make our already sometimes hard to navigate wiki more difficult to
read (if some, but not all, the page names were preceded with
numbers). Today I did some investigation and discovered that in
Confluence 2.8 (we are running 2.5) you *can* actually change the
order of child pages: http://confluence.atlassian.com/display/DOC/
Moving+Pages+within+a+Space#MovingPageswithinaSpace-
ChangingthePageOrder.
I tried following these instructions on re-ordering child pages:
http://confluence.atlassian.com/display/DOC/Moving+Pages+within+a
+Space in our (version 2.5) wiki, but unfortunately it didn't seem to
work there. I'm not sure if Confluence 2.6 or 2.7 offer this
functionality, but thought before investigating it would be best to
ask first if there is any possibility of upgrading to Confluence 2.8?
I think this is a serious usability issue (for both the PDF release
and the wiki), which merits an upgrade to 2.8 if at all possible
(since the functionality we are looking for is apparently there).
Cheers,
Allison
On May 8, 2008, at 1:15 PM, Daphne Ogle wrote:
I think this could work since the child page order is less important
(except some pages with many children pages) when you're looking at it
on-line. Most of the time their tends to links to the child pages
from within the parent page anyway.
I vote for giving it a try in a few places. We can always change it
back pretty easily by getting rid of the numbers (or once the reorder
is implemented in confluence :) ). Paul and I have a task to do some
clean up of the UX release docs so we can give it a try.
-Daphne
On May 8, 2008, at 7:42 AM, Michelle D'Souza wrote:
Michelle, are you suggesting that only the 'release' pages be
prefaced by a number, and that if a page is not going to be included
in a release, it not have a number?
Yes, I think that the numbers in the titles of the pages would be a
good marker for what is release documentation.
Another option is to have a separate section of the wiki that is the
'manual'. I don't think a 'manual' section would be ideal because our
documentation is so varied and comes from different logical sections
such as API docs, UX information etc.
Michelle
------------------------------------------------------
Michelle D'Souza
Software Developer, Fluid Project
Adaptive Technology Resource Centre
University of Toronto
_______________________________________________
fluid-work mailing list
[email protected]
http://fluidproject.org/mailman/listinfo/fluid-work
Daphne Ogle
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
[EMAIL PROTECTED]
cell (510)847-0308
_______________________________________________
fluid-work mailing list
[email protected]
http://fluidproject.org/mailman/listinfo/fluid-work
Allison Bloodworth
Senior User Interaction Designer
Educational Technology Services
University of California, Berkeley
(415) 377-8243
[EMAIL PROTECTED]
_______________________________________________
fluid-work mailing list
[email protected]
http://fluidproject.org/mailman/listinfo/fluid-work
