Please list questions about how to get the most out of the Coop wiki.

• how do I move a page? And are there conventions we should follow to notify people when we *do* move pages?
  • cf https://wiki.libraries.coop/doku.php?id=cooperative:wiki:orientation&do=admin&page=move (but you can DEFINITELY ask for help with this, and probably SHOULD ask for help with full namespace moves)
• how do I archive a page if I am unsure whether I should delete it?
  • cf z_archive namespace; rename pages to "old_namespace_pagename"
• are there any tricks for making tables easier? (yes)
  • cf http://donaldmerand.com/code/2012/05/08/convert-a-spreadsheet-to-dokuwiki-format.html
  • there is a conflict between sortable tables (which we currently use) and the wysiwyg table editor - if there is enough demand, we can test the wysiwyg editor on our staging server for the wiki, and if it is _that_ much easier, maybe implement instead of the sortables plugin.
• how can I get two column display on a page?
  • cf "wrap" plugin - https://www.dokuwiki.org/plugin:wrap
• what are some of the macros and other extensions I can use to make wiki pages work better?
  • cf https://wiki.libraries.coop/doku.php?id=wiki:syntax&do=admin&page=extension
  • e.g. https://www.dokuwiki.org/plugin:include
  • embed raw html (use sparingly) https://www.dokuwiki.org/wiki:syntax#embedding_html_and_php
  • """" and """
  • there is a HUGE number of other ones at https://www.dokuwiki.org/plugins - maybe browse to see if there are some that could be useful, and we can try out on the staging server first.
• how do you do that slideshow trick?
  • cf https://www.dokuwiki.org/plugin:s5
  • put {slideshow} at the top of the page, and {/slideshow} at the end; top level headings represent new slides
• how do you create the Check boxes in list format (To Do list?)
  • cf https://www.dokuwiki.org/plugin:todo - basically put <todo> tags around your items
• There are two namespaces on pages like this one, one for pages that have a :start namespace, and another for pages which do not. What are some good conventions to use when creating a new page?
  • so to create a namespace you create a new page but with a trailing colon, like newspace:
  • however, ideally you would create a new namespace by creating a new index new page first, like newspace:start. Any page named "start" is the default index page for a space.
  • to create a new page, easiest way is to simply edit the URL and create a new path. Also easy to create a link on an existing page, then click through to it.

Typically, when you delete the contents of the page, you also delete that page unless it has children. If a page also appears in menu, however, you can't remove it by deleting the content: instead, move the page to namespace "z-archive". Only then will it disappear.

Subscribe to parts of – or the whole! – wiki to receive an email when someone makes changes to pages or namespaces. To subscribe:

1. Navigate to the page or namespace to which you want to subscribe;
2. On the right-hand menu which contains the main edit link on every page, find the envelope with the scroll-over text "Manage Subscriptions";
3. Choose your preferences and click "Subscribe".
4. Repeat for other pages or namespaces!

When getting too many search results, use the tricks listed here. Specifically useful may be:

You can search for exact phrases by putting double quotes around a set of words, e.g. [ "installing dokuwiki" ].

You can restrict the search to namespaces. To search pages within a namespace, prefix @ or ns: to the namespace. To not search pages within a namespace, prefix ^ or -ns: to the namespace.

For example, the query [ dokuwiki @wiki ^wiki:docs ] will find pages which contain a word “dokuwiki” and are within “wiki” namespace but not within “wiki:docs” namespace. The query [ dokuwiki ns:wiki -ns:wiki:docs ] will do the same thing.

Note that you have to search a namespace (e.g. something that has a URL that ends in “:start”) — otherwise you are searching a page. So, searching with [ ns:public:nnels:etext:template-styles ] does not work, but searching in [ ns:public:nnels:etext ] most certainly does.