• [Wiki] - [Plugin|Wiki.Plugin]: i have not tested NamespacePlugin but links to upper hierarchies seem to make sense.
  
  Even better: 'NamespaceTag' (to be written) that replaces <wiki:PageName /> in Header.jsp and writes
  
  Wiki.Plugin.Index
  
  (one link for Wiki, one link for Wiki.Plugin; plain text for Wiki.Plugin.Index as this is the actual page)
• !!!Index Plugin: a big heading for each page seems to be better than relying on page names (at least for internationalized pages)
• Parameters with their default values should be listed in a table (clear and compact; names for table headings are copied from http://www.jspwiki.org/wiki/WikiMap)
• Example output should be displayed with some background color so that the reader sees it at one glance.
• Suggestions and Discussions: should stand on a separate page ending with '.Discussion'. A documentation page should describe the actual function of the software and old bugs or further ideas should be placed elsewhere.

-- Frank_Fischer

• You can't mean that all documentation pages should look like this, can you? This is appropriate for a reference (say, to a particular plugin), but I think there are many topics that need a more conversational style. DanF

• This skeleton could be usable for documentaion of most plugins and tags, forms, aliases, URLProviders etc.
  Many of the current pages fall into this scheme.

• For more conversational style some features should remain, some have to be added and some are not applicable. I have added an unfinished proposal above.

• There will still be some pages that need a different approach.
  How about my Proposal for Documentation of Wiki Syntax ?
  (uses tabbedSection; incomplete, German language)

-- Frank_Fischer