Note: a TikiWiki admin should turn on the Wiki feature: admin-> wiki -> Open page as structure so that pages open with structure navigation by default.  Otherwise, intermediate pages with only a {toc} will appear blank.  This does not affect pages not part of a structure.

Details
==========

The permissions were not setup in TikiWiki to allow me to create a Structure top page from an existing page.  So a shadow page that owns the structure was created in two cases.  These shadow pages were redirected back to the main page.  And then an auto table of content tag ({tag}) was added to the main page that referenced the new shadow structure (page).  Eventually this will be cleaned up and merged back by someone with the right permissions.  The "English Instructions for LimeSurvey" already had a shadow page named "English Manual".  This was made to conform to this shadow mechanism of the two new books already mentioned.

(Note: I held off doing the insertion of the {toc} on the Wiki Home page to avoid disruption at the top level.  But it can be added there easily.  Simply add the following two lines to the top of the page:
{DIV(float=>right)}^Structured Table of Contents (automatic):{toc structID=170}^{DIV}
-=Original Page (Historical)=-
See the shadow page for an example of what this will look like. 

The "Orphan Pages" feature in TikiWiki is part of the Structure mechanism and meant to show those pages not linked into a Book.  By making Structures out of the two main pages (Development, Wiki Home) in addition to the existing English Manual, there is now a Structure (Book) home for all English pages.  Thus "Orphan Pages" can be used to find English documentation pages created but not yet linked into one of the three main books and their table of contents.  

Most pages are now linked into one of these three Structures; all will eventually be.  We are down to 20 English pages not linked into one of the three Books from 150 originally.  Many pages that were totally orphaned are being discovered.  Some that are likely deprecated and can be deleted or redirected.

As mentioned in the initial proposal, the advantage of using Structures is the {toc} tag can be used to keep the outline and links to other pages automatic.  As new features or pages are added, they simply need to be added into the Structure in the appropriate place.  Then the referencing page will automatically list them.  {toc} parameters such as "maxdepth", "showdesc", etc. will be added as necessary to help create nicer navigation references in certain pages.

Now structure edits, splitting of existing pages into multiple pages, and similar changes can easily occur-- without out dating higher level content pages.  As an example, as tasked today, will work to merge and split the two Templates pages into likely 4 pages with a top page on the overall subject of Templates (including styles) that references them.  The original two names will be redirects to the new, single top level page.  Let's see if I can get to that this weekend.

As we go along, everyone should review pages for missing content and add new headings or new pages to the structure as placeholders to identify where content is missing.  Due to gaps in the documentation now appearing, it may be better to focus on editing the current manual into a complete reference manual first and then come back looking for the cookbook, process descriptions to more gently introduce topics to new users of various levels.