Difference between revisions of "User:Clements/Wiki Systems"
(→Hierarchy / Navigation) |
(→Macros) |
||
| Line 174: | Line 174: | ||
Nope: http://extensions.xwiki.org/xwiki/bin/view/Extension/Python+Macro | Nope: http://extensions.xwiki.org/xwiki/bin/view/Extension/Python+Macro | ||
| + | |||
| + | Also the include macro: | ||
| + | * http://extensions.xwiki.org/xwiki/bin/view/Extension/Include+Macro | ||
| + | |||
| + | which does not take parameters. | ||
== Code Highlighting == | == Code Highlighting == | ||
Revision as of 17:29, 18 March 2011
I did a walkthrough of wikimatrix.org and ended up with MoinMoin and XWiki as choices. MoinMoin is Python based, while XWiki is Java based. I'm guessing we will lean hard towards MoinMoin.
Contents
MoinMoin
The documentation home is http://moinmo.in/Documentation. There does not appear to be a single HTML page or PDF version of the doc, and it's spread out. Therefore, my notes here will be spread out too.
Page Hierarchy
Does it support this?
- http://moinmo.in/PagesHierarchy
- Says use SubPages, which appear to be a single level of organization; mechanism similar to BitBucket's.
- http://moinmo.in/HelpOnEditing/SubPages - They can be nested to multiple levels.
- http://moinmo.in/HierarchicalWiki
- Answers the question: NO.
- Points at http://moinmo.in/FacetedClassificationInMoin, which I don't think is implemented.
Doc seems to be in a chaotic state. Making me miss TWiki already.
Categories / Tags
MoinMoin supports this. Does not appear to support category hierarchy.
Attachments
Files are attached to particular pages, but can be linked to from other pages.
CamelCase
Camel Case links are native. Links with Embedded spaces are also supported.
Images
Can embed and resize internal and external images, but I don't think you can control the link.
In Wiki syntax, you can make an image be a link.
Page Watching
Can get email notification of changes to specific pages.
Themes
- Modernized is the default
- Rightsidebar moves several items from top to right side.
None of the preinstalled defaults particularly grabs me.
http://moinmo.in/ThemeMarket lists several contributions.
Of these:
- http://moinmo.in/ThemeMarket/Mandarin is prettiest.
- http://moinmo.in/ThemeMarket/BPlus is very clean, but might be missing something.
- http://moinmo.in/ThemeMarket/Moniker is very clean too.
I'd pick one of those three, perhaps Moniker.
Links
Can encode get strings.
Anchors and Headings
Can insert anchors arbitrarily, but I don't think section names automatically generate them.
Heading may not contain wiki markup.
Tables
Standard table markup forces all columns onto a single row.
Macros
It supports Macros that are Python code. It also supports page includes. I'm not sure if it supports variables/parameters in the includes.
There is a list of 19 contributed macros at
Markup Languages
Supports these out of the box.
- wiki - the default MoinMoin
- creole
- ReST
- XML/XSLT/DocBook
Supports highlighting of code, given the language.
Can install contributed plugins for
- GraphViz
- Textile
Page Templates
When a new page is created, MoinMoin gives you the choice of using an existing page template to prepopulate the new page.
You can define your own template on any page ending with Template.
ACLs
MoinMoin supports ACLs.
Mercurial and Mass Updates
The MoinMoin team uses Mercurial for MoinMoin, but the wiki pages themselves are not stored in Mercurial as on BitBucket.
From http://moinmo.in/HelpOnPageDeletion
- The only way to unrevertably and completely delete a page (including backups, history, attachments, etc.) is via the shell on the host system. The page files are found in the "data/pages/<PageName>" directory, and you can simply delete the whole <PageName> directory - no way back in that case.
No word on mass updates yet.
XWiki
Decided to ignore backing technology as a decision point on 2011/03/18 call. Therefore XWiki is back on the table.
Access Control
Can control it at the wiki level, the space level, or the page level.
Page hierarchy is supported.
Tagging is also supported. You can either have free text, or use a restricted set of tags.
Markup Syntaxes
XWiki also supports:
- JSPWiki
- MediaWiki
- Confluence
- TWiki
- Creole 1.0
- XHTML 1.0
Markups, but only partially, and this is not well documented.
Extensions
There are 372 defined extensions.
You can change the whole skin, or just the color scheme.
Backend / Mass Updates
Pages are stored in an RDBMS. Postgres is supported.
Programmatic access is too, It's not pretty, but it's not hard.
Linking
Linking is done with square brackets. Only odd part is the renaming of the link, which is non standard.
HTML Embedding
Can go to straight HTML if needed.
Macros
Looks promising:
HAve to learn Groovy or Velocity to do this. Is this the classic power versus ease tradeoff?
Nope: http://extensions.xwiki.org/xwiki/bin/view/Extension/Python+Macro
Also the include macro:
which does not take parameters.
Code Highlighting
Uses Pygments for highlighting. See http://extensions.xwiki.org/xwiki/bin/view/Extension/Code+Macro
Foswiki
Alsoi looked at Foswiki, the successor to TWiki.
Linking
Uses CamelCase. I'd say that's a drawback.
Creole
No creole support.
OK, well that was a short investigation.
Not going with Foswiki. Adieu.
