I'm inclined to agree. To improve navigation it might be worth combining some of the smaller pages, such as the entire introduction, into a single page with subheadings that would appear in an embedded table of contents. Larger pages should probably still be broken up.
I'll have a play and let you know what I come up with. Cheers, Symon. Symon Rottem http://blog.symbiotic-development.com 2010/7/29 Krzysztof Koźmic <[email protected]> > Current structure is certainly not ideal - it was ported from the old > non-wiki based doco IIRC. On the left hand side there should be link to > 'root'. Also the way I do things in Windsor I try at the end of each page > have a See Also and/or External resources sections with links to other > topics in the wiki and external pages/blogs respectively. > > Any other ideas? > Krzysztof > > > > On 2010-07-30 07:14, Symon Rottem wrote: > > This is certainly an easier way of letting the community update the docs, > so bravo! > > One of the issues I have with the existing structure is that although the > flow of each topic leads from one page to another there doesn't appear to be > an easy way back to the index or to move forward or backward between pages > in a topic. Is there any mechanism you'd suggest that might make this > easier? > > Also, are these docs ready to be linked from the MonoRail Wikipedia entry > yet? > > Cheers, > > Symon. > > Symon Rottem > http://blog.symbiotic-development.com > > > 2010/7/29 Krzysztof Koźmic <[email protected]> > >> While we have received some really great contributions to the new >> documentation wiki, we're still quite far from being completely migrated. >> Therefore I wanted to remind everyone that the wiki is located here >> http://stw.castleproject.org/MainPage.ashx >> and everyone is more than welcome to come and improve on it. >> >> Especially documentation for MonoRail and Active Record still requires a >> lot of work. >> >> If you have any experience with any part of Castle project and have a few >> spare minutes go ahead and help us have great documentation for the project. >> Be it by updating what's already there, expanding, adding new topics, or >> restructuring for better readability - register and start editing. >> >> To keep everything consistent take a look at >> http://stw.castleproject.org/Editors%20guide.ashx for quick info on the >> formatting we use. >> >> cheers and thanks for your contributions! >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Castle Project Users" group. >> To post to this group, send email to >> [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<castle-project-users%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/castle-project-users?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/castle-project-users?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]<castle-project-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/castle-project-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
