Re: [Slashcode-development] Slash Wiki plugin... Needs a home.

[Bill S. <wsk...@sp...>]

Hi Gerry,

Gerry Gleason wrote:

> When I'm not thinking completely straight, I want to adapt this tool 
> for use with Slashcode.  The idea would be a versioned content 
> management systems for testing and development, then you would upload 
> the content to the database as a complete release.  Basically, I want 
> the versioned content management system for the "authored" parts of 
> the content, but I still want the comment system and fast database 
> implementation of Slashcode. 


So it sounds like you basically want to have a Wiki, that only those 
with privileges can edit -- (versioning is part of the Wiki), but still 
have the comment system as implemented by Slash.  Sorry, just thinking 
out loud so that I'm clear.

This is a great idea, and I bet that it wouldn't be too out of the 
question to implement using chromatic's stuff as a base.  (I'm assuming 
you're speaking of written content though, and not code content)  The 
"upload file as bodytext" functions already exist elsewhere, you could 
implement this without too much trouble probably... 

I'd also like to look into chromatic's Wiki module, because this could 
also be extended to allow more tags.  I looked around at other Wikis and 
found that there are some tags like "==" that indicate a <h2> font or 
whatever.  I saw another that made WikiWords in a grey color if their 
page(s) hadn't been defined yet.  That was another good idea.

Regardless, I think the Wiki concept is pretty cool.  It was hard to 
explain to the guys in my department.  Funny how something so simple can 
be so effective.  For pages like FAQs and whatnot, it's the ticket.  The 
problem is that I can't get people to contribute!!

--Bill