A major generic issue we had with JSPWiki is the set of preinstalled pages. These are for our purposes way to many. We trimmed the set down, and in many cases created direct interwiki links to the JSPWiki documentation wiki. 

We use the following default page names for our "empty" wiki setup. The advantage of prefixing as many system pages as possible (without violating intuition) with "Wiki" is that the namespace of the new Wiki (as seen in PageIndex) is relatively clean, and newly authored pages are easily distinguished from system pages. 

__I propose to distribute future versions of JSPWiki only with this list.__

* [About]
* [Copyright]
* [CopyrightLabel]
* [Main]
* [PageIndex]
* [PleaseDeleteMe]
* [PleaseRenameMe]
* [RecentChanges]
* [RecentChangesComplete]
* [UndefinedPages]
* [UnusedPages]
* [WikiAdministration]
* [WikiAdvancedFormatting]
* [WikiEditorFormattingNotes]
* [WikiEditorSubmissionNotes]
* [WikiFormattingQuickReference]
* [WikiHeaderTools]
* [WikiHelp]
* [WikiSideMenu]
* [WikiSideMenuFooter]
* [WikiRejectedMessage]
* [WikiSandBox]
* [WikiSystemInfo]

-- Gregor Hagedorn, 2005-09-07

PS An example of how the large set of "preinstalled" default pages addressing developer issues clutters up a content-oriented JSPWiki is [http://seek.ecoinformatics.org/Wiki.jsp?page=PageIndex]. Many of the page names are amgiguous, requiring users to open the page to figure out whether Wiki content or Wiki setup is being addressed. -- GH

----

Return to [Configurable Template]

----

QUESTION: Should I link the content of our "clean" default pages in here, or would this clog up the JSPWiki? I could prefix all with "~ProposedDefault_"? What do you think?

-- Gregor Hagedorn, 2005-09-07