Nginx Wiki - alternatives

[mike]

Wiki's to me are a decent concept but for the most part I am always
disappointed by the implementation. Especially MediaWiki. Blech.

I am annoyed by wiki markup. I'd rather just have a limited amount of
HTML available and work on that. Maybe auto convert newlines (unless
specificly asked not to when posting) - otherwise, stop
auto-formatting and breaking my stuff!

However, I can't really give any other solution for a general
documenting tool that allows multiple authors. I'd suggest even a
basic WordPress or other type of basic content publishing tool like
that and instead of a wiki concept, just publish articles. But the
change history isn't there, it'd require registration typically (which
I don't think is a bad thing) ... oh well.

that's just my two cents. A Lot of wikis make it harder especially
with code samples and things, in my experience. We're actually moving
away from a wiki originally designed for developers sharing advice,
code and other things internally at my work, and we're just going to
use a home-made simple CMS type system that tracks changes instead and
has a limited whitelist of allowed HTML for formatting..

either way, whatever makes it easiest for nginx development,
documentation and such is what I'm interested in. I'm in the middle of
converting my entire life (work, side business, play) to nginx so soon
I will be a die-hard fanboy...



On 4/9/08, Cliff Wells <cliff at develix.com> wrote:
> http://wiki.mindtouch.com/Deki_Wiki/Deki_Wiki_Features
>
> This seems to fit the bill pretty damn well.  And a bump from Miguel
> can't be a bad thing =)
>
> Any objections?  I'll get it setup in a VPS for testing.
>
> Cliff
>
>
>
> On Wed, 2008-04-02 at 13:50 -0700, Cliff Wells wrote:
> > Hi all,
> >
> > I'd like to bring up the idea of getting off of MoinMoin at some point.
> > The spam issue is a constant headache and Moin 1.6's solution isn't
> > appealing (textcha's) for several reasons:
> >
> > 1) it's annoying and error-prone.
> > 2) it won't work against humans (which happen to be the source of a lot
> > of wiki and blog spam).
> >
> > I'm thinking what we need is something more like Plone that has actual
> > workflow and permissions.  That is to say, anyone could register and
> > edit content, but only established users could actually publish content.
> > Clearly we'll still get spam attempts, but the spam will never make it
> > to the web, so the incentive to spam goes away.
> >
> > Of course, I want to make it as easy as possible for established people
> > to make changes, so my thought is that we could just promote people to
> > publishers once they'd actually made a valid addition to the site, so
> > people could just short-circuit the workflow cycle and publish their own
> > changes.  I doubt spammers will ever make valid contributions to the
> > site, but if they did, I suppose it would all balance out =)
> >
> > 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.
> >
> > Another nice thing about a system like this is certain sections could
> > actually belong to a particular user (e.g. Evan's Guide to Nginx Module
> > Development) who wanted to retain control of a document for whatever
> > reason but also wanted it highly visible.
> >
> > Any suggestions?  Wikis (or even CMS's) with workflow seem a rare breed.
> >
> > Regards,
> > Cliff
> >
> >
>
>
>