Nginx Wiki - alternatives
cliff at develix.com
Thu Apr 3 07:59:13 MSD 2008
On Wed, 2008-04-02 at 23:24 +0200, Alexander Staubo wrote:
> On 4/2/08, Cliff Wells <cliff at develix.com> wrote:
> > However, as much as I think Plone fits the bill, I've yet to implement
> > anything successfully with Plone (or Zope), so I think I'd rather look
> > elsewhere for something a little less complicated.
> I have used Plone and Zope extensively, and while I have great respect
> for Zope's technical heritage -- I used to be a Zope developer almost
> exclusively -- I would urge anyone to stay a long way away from Plone.
> It is horribly complex and inflexible, and any kind of customization
> requires a lot of work. And I say this after once having worked with
> Plone Solutions as a consultant on what was in theory a very modest,
> trivial site.
That's been my experience as well (albeit just a couple short, painful
> I would rather recommend a simpler CMS such as Drupal or a proven wiki
> such as MediaWiki.
AFAIK, MediaWiki is even worse than Moin in this regard. I'm not to
certain about Drupal but I'm wary of PHP apps in general (I've audited
tons of PHP code for security issues and have yet to find myself happy
with the results).
> You don't need a formal workflow, really; just a
> way to restrict editing to verified users, which is something a lot of
> CMSs and wikis do just fine.
Yes and no. We don't really need the formal workflow, but we need some
of it, and it appears to be an all-or-nothing proposition. Moin and
Wikimedia don't distinguish between *types* of users, just whether
someone is logged in or not. We need the ability to promote people from
editor to publisher (we don't care who edits, but we do care who
A cheap, interim solution would be to stick with Moin and require that
people jump through a hoop of sorts to get a username (i.e. request one
here on the list or something similar), and if that doesn't seem too
invasive I could work on it.
More information about the nginx