CINXE.COM

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> <meta http-equiv="X-UA-Compatible" content="IE=Edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <meta name="verify-v1" content="0WyQ+hn2OtHJ8nIJUihkSAkxCHyVcRg+RXh9VxId8jU="> <script type="text/javascript"> /* <![CDATA[ */ (function() { var s = document.createElement('script'), t = document.getElementsByTagName('script')[0]; s.type = 'text/javascript'; s.async = true; s.src = '//api.flattr.com/js/0.6/load.js?mode=auto'; t.parentNode.insertBefore(s, t); })(); /* ]]> */ </script> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"> <meta name="robots" content="index,nofollow"> <title>PagesHierarchy - MoinMoin</title> <script type="text/javascript" src="/moin_static19/common/js/common.js"></script> <script type="text/javascript">  </script> <link rel="stylesheet" type="text/css" charset="utf-8" media="all" href="/moin_static19/modernized/css/common.css"> <link rel="stylesheet" type="text/css" charset="utf-8" media="screen" href="/moin_static19/modernized/css/screen.css"> <link rel="stylesheet" type="text/css" charset="utf-8" media="print" href="/moin_static19/modernized/css/print.css"> <link rel="stylesheet" type="text/css" charset="utf-8" media="projection" href="/moin_static19/modernized/css/projection.css">   <link rel="alternate" title="MoinMoin: PagesHierarchy" href="/action/rss_rc/PagesHierarchy?diffs=1&show_att=1&action=rss_rc&unique=0&page=PagesHierarchy&ddiffs=1" type="application/rss+xml"> <link rel="Start" href="/MoinMoinWiki"> <link rel="Alternate" title="Wiki Markup" href="/action/raw/PagesHierarchy?action=raw"> <link rel="Alternate" media="print" title="Print View" href="/action/print/PagesHierarchy?action=print"> <link rel="Search" href="/FindPage"> <link rel="Index" href="/TitleIndex"> <link rel="Glossary" href="/WordIndex"> <link rel="Help" href="/HelpOnFormatting"> </head> <body lang="en" dir="ltr"> <div id="header"> <form id="searchform" method="get" action="/PagesHierarchy"> <div> <input type="hidden" name="action" value="fullsearch"> <input type="hidden" name="context" value="180"> <label for="searchinput">Search:</label> <input id="searchinput" type="text" name="value" value="" size="20" onfocus="searchFocus(this)" onblur="searchBlur(this)" onkeyup="searchChange(this)" onchange="searchChange(this)" alt="Search"> <input id="titlesearch" name="titlesearch" type="submit" value="Titles" alt="Search Titles"> <input id="fullsearch" name="fullsearch" type="submit" value="Text" alt="Search Full Text"> </div> </form> <script type="text/javascript">  </script> <div id="logo"><a href="/MoinMoinWiki"><img src="/moin_static19/common/moinmoin.png" alt="MoinMoin Logo"></a></div> <div id="username"><a href="/action/login/PagesHierarchy?action=login" id="login" rel="nofollow">Login</a></div> <h1 id="locationline"> <a href="/MoinMoinWiki" rel="nofollow">MoinMoin</a>: <a href="/PagesHierarchy">PagesHierarchy</a> </h1> <ul id="navibar"> <li class="wikilink"><a href="/RecentChanges">RecentChanges</a></li><li class="wikilink"><a href="/FindPage">FindPage</a></li><li class="wikilink"><a href="/HelpContents">HelpContents</a></li><li class="current"><a href="/PagesHierarchy">PagesHierarchy</a></li> </ul> <div id="pageline"><hr style="display:none;"></div> <ul class="editbar"><li>Immutable Page</li><li class="toggleCommentsButton" style="display:none;"><a href="#" class="nbcomment" onClick="toggleComments();return false;">Comments</a></li><li><a class="nbinfo" href="/action/info/PagesHierarchy?action=info" rel="nofollow">Info</a></li><li><a class="nbattachments" href="/action/AttachFile/PagesHierarchy?action=AttachFile" rel="nofollow">Attachments</a></li><li> <form class="actionsmenu" method="GET" action="/PagesHierarchy"> <div> <label>More Actions:</label> <select name="action" onchange="if ((this.selectedIndex != 0) && (this.options[this.selectedIndex].disabled == false)) { this.form.submit(); } this.selectedIndex = 0;"> <option value="raw">Raw Text</option> <option value="print">Print View</option> <option value="RenderAsDocbook">Render as Docbook</option> <option value="refresh">Delete Cache</option> <option value="show" disabled class="disabled">------------------------</option> <option value="SpellCheck">Check Spelling</option> <option value="LikePages">Like Pages</option> <option value="LocalSiteMap">Local Site Map</option> <option value="show" disabled class="disabled">------------------------</option> <option value="RenamePage" disabled class="disabled">Rename Page</option> <option value="DeletePage" disabled class="disabled">Delete Page</option> <option value="show" disabled class="disabled">------------------------</option> <option value="show" disabled class="disabled">Subscribe User</option> <option value="show" disabled class="disabled">------------------------</option> <option value="show" disabled class="disabled">Remove Spam</option> <option value="show" disabled class="disabled">Revert to this revision</option> <option value="PackagePages">Package Pages</option> <option value="SyncPages">Sync Pages</option> <option value="show" disabled class="disabled">------------------------</option> <option value="Load">Load</option> <option value="Save">Save</option> <option value="SlideShow">SlideShow</option> </select> <input type="submit" value="Do"> </div> <script type="text/javascript">  </script> </form> </li></ul> </div> <div id="page" lang="en" dir="ltr"> <div dir="ltr" id="content" lang="en"> Making the wiki easier to use for both new users and wiki administrators by using sub pages. See also: <a href="/FacetedClassificationInMoin">FacetedClassificationInMoin</a>, <a href="/FacetBrowsingTheme">FacetBrowsingTheme</a>, <a href="/HierarchicalWiki">HierarchicalWiki</a>, <a href="/MoinMoinPatch/HierarchicalACL">MoinMoinPatch/HierarchicalACL</a> <div class="table-of-contents">Contents<ol><li> <a href="#The_Problem">The Problem</a></li><li> <a href="#The_Solution">The Solution</a></li><li> <a href="#Using_subpages">Using subpages</a></li><li> <a href="#Discussion">Discussion</a></li></ol></div> <h1 id="The_Problem">The Problem</h1> A wiki is a big mess. Its hard to find information by browsing, although a wiki has several indexes and other aids. Its hard to update an existing wiki with a new <a href="/MoinMoin">MoinMoin</a> version. Few example: <ul><li>Where should one create this page? in the root level? under <a href="/MoinDev">MoinDev</a>? </li><li>Where can I find information about translation? is it <a class="nonexistent" href="/GibberishTranslation">GibberishTranslation</a> or <a class="nonexistent" href="/MoinDev/GibberishTranslation">MoinDev/GibberishTranslation</a> or <a class="nonexistent" href="/MoinMoinTranslation/GibberishLanguage">MoinMoinTranslation/GibberishLanguage</a>? </li><li>Is <a class="nonexistent" href="/HelpOnGibberish">HelpOnGibberish</a> a system page or a user created page? should I update this page from the new wiki version? </li><li>What are the main parts of this wiki? where do you find this information when you visit a new wiki? </li></ul>The typical comment you hear from new users is "I can't find anything" In Hebrew people say they "can't find their hands and feet". <h1 id="The_Solution">The Solution</h1> The wiki structure will be clear. The design will help the new user to answer these questions: <ul><li>What is this site? - they may land in the site right from Google </li><li>Where am I in this site? </li><li>What are the other pages in this part of the wiki? </li><li>Where can I go from here? </li></ul>How to do this in an easy way for both the wiki admin and users: <ul><li>The structure will be displayed automatically - without configuration or user added parts like macros. </li><li>Each page at the root level will be displayed in the wiki pages list </li><li>System pages that every moin wiki has, will be displayed at the same location and order on every wiki </li><li>Wiki specific pages will be displayed at the same location on every wiki. </li><li>Some or all the pages in a wiki part will be displayed in the same place in every wiki. </li><li>The complete path to the page you are in will be displayed in the same place on every wiki. </li><li>System page will be separated from the wiki specific pages, with other ACL rights </li></ul> <h1 id="Using_subpages">Using subpages</h1> We have to tool to make this situation much better: sub pages. Here is how it can be done: <h2 id="System_Pages">System Pages</h2> System Pages - the same on every wiki. They could be actually be in <tt class="backtick">data/__system__/lang_iso_code</tt>, or in a wiki farm, at the roof of the wiki farm, all immutable. Then you can upgrade your wiki easily. <ul><li><a href="/FrontPage">FrontPage</a> - default front page for new wiki </li><li><a href="/RecentChanges">RecentChanges</a> </li><li>Help - main pages for help <ul><li>Help/Editing </li><li>Help/Editing/CreatingLinks </li></ul></li><li>Find - main page for find pages <ul><li>Find/TitleIndex </li><li>Find/WordIndex </li><li>Find/Other find related pages... </li></ul></li></ul>... Maybe Navigtaion would be better then Find? Eg. <ul><li>Navigation <ul><li>Navigation/TitleIndex </li><li>Navigation/WordIndex </li><li>Navigation/FindPage </li><li>... </li></ul></li></ul>The idea is to have one stating point when you want to find something, and the simple search box on every page is not enough. There two ways to find: searches and browsing. The Find page can have both search form, and links to all kinds of indexes, like this page: <a class="http" href="http://nirs.dyndns.org/nirs/NewFindPage">http://nirs.dyndns.org/nirs/NewFindPage</a>. <h2 id="Wiki_Specific_Pages">Wiki Specific Pages</h2> Wiki pages - change for each wiki. They would live in the wiki instance directory. Here a quick list for this wiki, just for the example: <ul><li><a href="/FrontPage">FrontPage</a> - Each wiki will have its own front page, overriding the system front page. </li><li><a class="nonexistent" href="/MoinDevelopers">MoinDevelopers</a> <ul><li><a class="nonexistent" href="/MoinDevelopers/ThommasWaldmann">MoinDevelopers/ThommasWaldmann</a> </li><li>Other developers pages... </li></ul></li><li><a class="nonexistent" href="/MoinTranslation">MoinTranslation</a> <ul><li>MoinTranslation/Language... </li></ul></li><li><a class="nonexistent" href="/MoinPlanning">MoinPlanning</a> <ul><li>MoinPlanning/Vesionxx </li></ul></li><li><a class="nonexistent" href="/MoinBugs">MoinBugs</a> - index page for all bug pages <ul><li><a class="nonexistent" href="/MoinBugs/WikiMarkup">MoinBugs/WikiMarkup</a> - index page for all wiki markup bugs </li><li><a class="nonexistent" href="/MoinBugs/WikiMakrup/SpecificBug">MoinBugs/WikiMakrup/SpecificBug</a>... </li></ul></li><li><a class="nonexistent" href="/MoinMarket">MoinMarket</a> <ul><li>MoinMarket/Themes </li><li>MoinMarket/Themes/Modern </li></ul></li></ul>... The main difference from the current system is that the structure is revealing itself without the need for configuration. We can let the users and administrator to override the default structure, as we do today. <h2 id="User_Specific_Pages">User Specific Pages</h2> The pages the user want to bookmark - will show on the same place on every wiki. These could be the last pages you visited, or the last pages you edited, or a list you define. We can give all options, the user will use what best fits. Pages that belong to this part: <ul><li>The user home page </li><li>The user preferences page </li><li>Last pages </li><li>Specific pages </li></ul> <h2 id="Location_Line">Location Line</h2> On the top of each page, probably just above the page title, we can have the navigation line: <a href="/MoinMoinWiki">MoinMoinWiki</a><tt class="backtick">:</tt> <a class="nonexistent" href="/MoinBugs">MoinBugs</a><tt class="backtick">:</tt> <a href="/WikiMarkup">WikiMarkup</a><tt class="backtick">:</tt> <a class="nonexistent" href="/%3C"><</a> <a class="nonexistent" href="/OtherBug">OtherBug</a> | <a class="nonexistent" href="/PreviousBug">PreviousBug</a> | SpecificBug | <a class="nonexistent" href="/NextBug">NextBug</a> | <a class="nonexistent" href="/YetAnotherBug">YetAnotherBug</a> <a class="nonexistent" href="/%3E">></a> When you are at a very big part of the wiki, the siblings links are not so useful, but if you are in a smaller part of the wiki which have 3-5 pages, the siblings are very useful. Maybe this can be automatic or controlled by the page editor. <h2 id="Wiki_Main_Parts">Wiki Main Parts</h2> On each page, we will have the wiki main parts: <a href="/FrontPage">FrontPage</a> | <a href="/RecentChanges">RecentChanges</a> | Find <tt class="backtick">[____________]</tt> <img alt="[?]" height="16" src="/moin_static19/modernized/img/moin-search.png" title="[?]" width="16" /> | Help<tt class="backtick">  </tt><a class="nonexistent" href="/MoinDevelopers">MoinDevelopers</a> | <a class="nonexistent" href="/MoinPlaning">MoinPlaning</a> | <a class="nonexistent" href="/MoinTranslation">MoinTranslation</a> | <a class="nonexistent" href="/MoinOhterMainPage">MoinOhterMainPage</a>... This could be implemented in the top of the page like we do today, but will be much better in a side bar: <div><table style="width: 100%"><tbody><tr> <td> <img alt="" height="" src="/moin_static19/modernized/img/moinmoin.png" title="" width="" /> <a href="/FrontPage">FrontPage</a> <a href="/RecentChanges">RecentChanges</a> <a href="/FindPage">FindPage</a> <tt class="backtick">[____________]</tt> <img alt="[?]" height="16" src="/moin_static19/modernized/img/moin-search.png" title="[?]" width="16" /> <a class="nonexistent" href="/HelpPage">HelpPage</a> </td> <td colspan="1" rowspan="3" style="width: 80%; text-align: center"> Content </td> </tr> <tr> <td> <a class="nonexistent" href="/MoinDevelopers">MoinDevelopers</a> <a class="nonexistent" href="/MoinPlaning">MoinPlaning</a> <a class="nonexistent" href="/MoinTranslation">MoinTranslation</a> <a class="nonexistent" href="/MoinOtherMainPage">MoinOtherMainPage</a>... </td> </tr> <tr> <td> <a class="nonexistent" href="/MyHomePage">MyHomePage</a> <a class="nonexistent" href="/MyPreferences">MyPreferences</a> </td> </tr> </tbody></table></div>This maps directly to the urls of this wiki: <ul><li><a class="http" href="http://thisdomain/FrontPage">http://thisdomain/FrontPage</a> </li><li><a class="http" href="http://thisdomain/MoinDevelopers">http://thisdomain/MoinDevelopers</a> </li><li><a class="http" href="http://thisdomain/MyHomePage">http://thisdomain/MyHomePage</a> </li><li style="list-style-type:none">.. </li></ul>At the side bar, this list can grow according to the wiki or user needs. Since page content display is useful only at 400-600 pixels, due to readability rules, (number of words in a line), this leave us plenty of space around the text, which is generally used in each well designed site. <h2 id="Automatic_Sub_Page_Listing">Automatic Sub Page Listing</h2> we can list the sub pages automatically, without any user or admin extra work. We can just put a <tt class="backtick">[[Children(depth=2, description=1)]]</tt> macro to get a list of this type: <ul><li><a class="nonexistent" href="/SubPage">SubPage</a> - description <ul><li><a class="nonexistent" href="/SubSubPage">SubSubPage</a> - description </li></ul></li><li><a class="nonexistent" href="/AnotherSubPage">AnotherSubPage</a> - description </li></ul>... The description line could be the first line of the page, which also appear in search results both in the wiki and on Google. We can put a description line field on a new page creation form, then put this line in the wiki page like this: <pre>## Description - every page should have a one line description at the top of the page: The text that the user entered in the create new page form... ## Content ...</pre> <h2 id="Creating_New_Pages">Creating New Pages</h2> Read the section "How to create a new bug report?" on <a href="/MoinMoinBugs">MoinMoinBugs</a>. Do we really need 6 steps to do this simple task? Now this could be the new "How to create a new bug report?" section: <ul><li style="list-style-type:none">To create a new bug report, go the category page and click the "Create New Bug Report" link at the top. A new bug report will be opened, add the details and save the page. The page will automatically be listed here. </li></ul>And this is the new "How to create a new bug category?" section: <ul><li style="list-style-type:none">To create a new bug category, click on the link "Create New Bug Category" and the top of this page. A new bug category page will be opened, add the details and save the page. The page will automatically be listed here. </li></ul>Technically, the new bug category could be a <a class="nonexistent" href="/MoinBugsSubPageTemplate">MoinBugsSubPageTemplate</a>, and a new bug report would be <a class="nonexistent" href="/MoinBugsSubSubPageTemplate">MoinBugsSubSubPageTemplate</a> or another similar system. Using this system the user does not have to select a template, because the template is selected for him by choosing the wiki part he is adding a page to. <h1 id="Discussion">Discussion</h1> I am going to build this system with or without changes in moin code, for my own needs at <a class="http" href="http://mac.plonter.co.il/plonwiki">MacMac</a> -- <a href="/NirSoffer">NirSoffer</a> 2004-06-19 18:43:46 Hi Nir. I'm thinking like you: <ul><li>At my work i just have had a great discussion about "Unscalability" of a Wiki-Documentation-System: <ul><li>One from my colleagues would prefer to use plone for the documentation in my section, because <a class="http" href="http://plone.org/">Plone</a> easily provides a folder-based hierarchically storage area. And he believes, that everybody of my section would need a folder-based Clipboard for storing informations. If we would be able to realize a more simple structure in the wiki, i think, some potential users would like wiki too. And if we would be able to present information in a folder-based hierachy like the Windows-Explorer, other users would find informations much easier. </li></ul></li><li>I don't say, that the structure of the wikipages is bad. But i would say, that some people need a menu-based or a folder-based presentation of the contents of a <a href="/WikiWikiWeb">WikiWikiWeb</a>... -- <a href="/KlausHeinisch">KlausHeinisch</a> (2004-06-21 20:41) </li></ul><hr /> Hierarchies only help if the data is hierarchical (== tree-like) - and often it isn't (because it is a full graph, not a tree). If you try to fit everything in a hierarchy, you will get new problems because: <ul><li>it often isn't clear how the hierarchy should look like, often there are multiple ways to do it and it is unclear which is better </li><li>the place in the hierarchy new content should be put in is unclear, especially if there are multiple thinkable pathes. </li><li>Furthermore, using subpage hierarchies can be painful to address as you can not simply say <tt class="backtick">look at ThisPage</tt>, but you have to say <tt class="backtick">look at FirstLevel/SecondLevel/ThirdLevel/ThisPage</tt>. </li></ul>IMHO a better solution is using some kind of facets, but this is not a current option, maybe rather a long term goal after having put much more thoughts into it. -- <a href="/ThomasWaldmann">ThomasWaldmann</a> 2004-06-22 16:51:44 <hr /> I agree completely with Thomas. Not only the information in a wiki is a (aciclic) graph, but the need to categorize in a hierarchy makes the creation and evolution of content more difficult and rigid, by forcing choices that are not always clear (where does this node "belongs"?), that change over time (now "belongs" here but tomorrow maybe not), and not unique (this node should be in the categories a, d, g, l, and m also). The idea of facets is powerful, and in the meantime, maybe we could start using more the wiki categories we already have. For example, we could list the categories in the navigation bar (separated from the main nodes). This would give the user an overall idea of what is here, and a few big groups to start at the same time. This possibility balances the idea of grouping (powerful and known for the user) with multiple categorization and a mechanism that we already have working. -- <a href="/EduardoMercovich">EduardoMercovich</a> (2004-06-24) I didn't even know about the <a href="/CategoryCategory">CategoryCategory</a> page till i read this thread and did a search. I think categories are very powerful in wiki, allowing for non-tree based information systems. However, at work were we are also implementing Moin as an intranet, i need to follow / implement a basic top-level layout to please the "boss" ;). This dosen't prevent one from still using the fluid nature of wiki and categories to allow for flexible "placement" of nodes. <a href="/JosYule">JosYule</a> Its true that information is usually more complicated then a simple tree. But you can describe any information as a tree. The description does not have to the best representation of the information - the purpose is to make it easier for people to understand your site. You do the same with a book or an article, when you break it into chapters and paragraphs. You do the same in a site when you break it into some parts, and those parts into other parts. My idea is to show this internal structure of the wiki automatically. The major problem with my idea is the death of the <a href="/WikiName">WikiName</a>. All links would be <a class="nonexistent" href="/PartName/PageName">PartName/PageName</a> of worse <a class="nonexistent" href="/PartName/SubPart/PageName">PartName/SubPart/PageName</a>. I'm convinced that we need a clear structure and it should show without special effort, but it seems that creating it with sub pages would make more harm. We can use subpage for help pages and general system pages. Using Help/FormatText, Help/CreateLinks and Find/TitleIndex Find/OrphanedPages or similar system would not have the bad effect Thomas and Eduardo describe, and the wiki specific pages can use single name space. So the basic structure for every wiki can be: <ul><li><a href="/FrontPage">FrontPage</a> </li><li><a href="/RecentChanges">RecentChanges</a> </li><li>Find </li><li>Help </li></ul>The specific structure can be exposed by other means. For example, by showing the name of pages that end with <a href="/RoadMap">RoadMap</a>. Let say in a wiki about linux you will have a lot of <a class="nonexistent" href="/HowToDoThis">HowToDoThis</a> pages, and a page named <a class="nonexistent" href="/HowToRoadMap">HowToRoadMap</a> describing these pages. We can show all the names of the road map pages in the wiki specific pages list: <ul><li><a href="/HowTo">HowTo</a> (Link to <a class="nonexistent" href="/HowToRoadMap">HowToRoadMap</a>) </li><li>Distributions </li><li><a class="nonexistent" href="/NewUser">NewUser</a> </li></ul>This list can show automatically - the wiki will be self documenting. Today we can do the same by adding page names to the navigar page list in config. This will help wiki admins to create easier to navigate wikis. -- <a href="/NirSoffer">NirSoffer</a> 2004-06-24 17:38:10 <hr /> I was very interested in the possible application of facets in wikis in general and Moin in particular. But even if the discussion spawns from here, it deserves its own page. So please take a look at <a href="/FacetedClassificationInMoin">FacetedClassificationInMoin</a>. -- <a href="/EduardoMercovich">EduardoMercovich</a> (05/07/04). <hr /> This appears all well and good. However, I think that the solution can be explained very simply (as many of you have above): <ul><li>Pages are not always hierachical </li><li>Pages belong to one or more parent categories. </li><li>Not everyone believes that 'automatic' solutions such as <a class="nonexistent" href="/FirstLevel/SecondLevel/ThirdLevel/ThisPage">FirstLevel/SecondLevel/ThirdLevel/ThisPage</a> </li></ul>What not add a #parentCategory Parent1,Parent2 preprocessor? Alternatively, since I see that no solution yet exists :(.... Why not reserve a special page (eg <a class="nonexistent" href="/WikiNavContents">WikiNavContents</a>) that is automatically displayed on the left of each wiki page? You could then edit <a class="nonexistent" href="/WikiNavContents">WikiNavContents</a> in any way you like? -- C (2005-10-4) <ul><li style="list-style-type:none">This is a very good idea, I have already thought about implementing it. -- <a href="/AlexanderSchremmer">AlexanderSchremmer</a> 2005-10-04 15:14:12 </li></ul></div>MoinMoin: PagesHierarchy (last edited 2010-07-13 15:17:01 by wp) <div id="pagebottom"></div> </div> <div id="footer"> <ul class="editbar"><li>Immutable Page</li><li class="toggleCommentsButton" style="display:none;"><a href="#" class="nbcomment" onClick="toggleComments();return false;">Comments</a></li><li><a class="nbinfo" href="/action/info/PagesHierarchy?action=info" rel="nofollow">Info</a></li><li><a class="nbattachments" href="/action/AttachFile/PagesHierarchy?action=AttachFile" rel="nofollow">Attachments</a></li><li> <form class="actionsmenu" method="GET" action="/PagesHierarchy"> <div> <label>More Actions:</label> <select name="action" onchange="if ((this.selectedIndex != 0) && (this.options[this.selectedIndex].disabled == false)) { this.form.submit(); } this.selectedIndex = 0;"> <option value="raw">Raw Text</option> <option value="print">Print View</option> <option value="RenderAsDocbook">Render as Docbook</option> <option value="refresh">Delete Cache</option> <option value="show" disabled class="disabled">------------------------</option> <option value="SpellCheck">Check Spelling</option> <option value="LikePages">Like Pages</option> <option value="LocalSiteMap">Local Site Map</option> <option value="show" disabled class="disabled">------------------------</option> <option value="RenamePage" disabled class="disabled">Rename Page</option> <option value="DeletePage" disabled class="disabled">Delete Page</option> <option value="show" disabled class="disabled">------------------------</option> <option value="show" disabled class="disabled">Subscribe User</option> <option value="show" disabled class="disabled">------------------------</option> <option value="show" disabled class="disabled">Remove Spam</option> <option value="show" disabled class="disabled">Revert to this revision</option> <option value="PackagePages">Package Pages</option> <option value="SyncPages">Sync Pages</option> <option value="show" disabled class="disabled">------------------------</option> <option value="Load">Load</option> <option value="Save">Save</option> <option value="SlideShow">SlideShow</option> </select> <input type="submit" value="Do"> </div> <script type="text/javascript">  </script> </form> </li></ul> <ul id="credits"> <li><a href="http://moinmo.in/" title="This site uses the MoinMoin Wiki software.">MoinMoin Powered</a></li><li><a href="http://moinmo.in/Python" title="MoinMoin is written in Python.">Python Powered</a></li><li><a href="http://moinmo.in/GPL" title="MoinMoin is GPL licensed.">GPL licensed</a></li><li><a href="http://validator.w3.org/check?uri=referer" title="Click here to validate this page.">Valid HTML 4.01</a></li> </ul> </div> </body> </html>