> First, I found the name of Pier really good. It really reflects
> that it is more than a wiki (for me the wiki is just a component
> among others...).
Lukas, do you want to go furter in removing the wiki part ? Why not
creating a package Pier-Wiki which should have all the classes
related to wiki (PRPage for example). Then, the Pier package will
be smaller. It is interesting because it shows that Pier is very
Yeah, the wiki part (at least the parser and visitor) could be easily
removed, but since the wiki is an integral part, e.g. to build the
environment by providing an abstraction over xhtml, I don't see much
sense removing it.
Moreover Pier should be something that is runnable out of the box, so
that people can start to add content right after the installation.
Removing the wiki part from pier would prevent this simplicity and
give the well known Zope effect where you have to start coding weird