wiki specification (draft)

1, 2
avatar twiggin Feb 12. 2007. 10:05 pm #11
>Are there any other plain English words that define "product of writing" that are understandable to everyone?

If "Pages" is taken by Apple, what about "Prose?" "Documents" seems a little too close to the exiting "Files" tab.
avatar quux Mar 4. 2007. 1:41 am #12
I am very happy to see that wiki will be included in aC ... and I'd just like to throw my vote behind a few things (+ for positive vote, - for negative vote):

+++ on no wikisyntax. wikiwyg or fckeditor or xinha or similar wysiwyg editing, please ohmigod *please* don't force users to learn textile, markdown, or whatever other wikisyntax du jour.
+ for one wiki per project, with permissions determined by the project permissions
+ one person mentioned stikipad. I have not used it, but they have a very nice feature - saves a draft every ten seconds so edits are not lost on browser freeze, timed logout, etc.
+ for 'make a wikibook' or something similar
+ for separate comments space on wiki pages

- on calling it something other than 'wiki'. That was a geeky term in times past but it is gaining more and more acceptance. Don't worry too much about this; if the editing is easy, people will not be intimidated.

Good integration of a wiki, and the ability to host my own copy of the system, will make me want to pay for aC!
avatar ffman Mar 21. 2007. 12:27 am #13
I prefer MediaWiki with http://en.wikipedia.org/wiki/WP:WIKED wiked, but that is jsut waht I am used to from wikipedia.
The nice thing about MW is it is easily scalable across multiple servers, and looks professinal. I like wikisyntax, it is pretty easy to use, but WYSIWYG like WikEd would be best IMO. Publishing pages and mass "namespace wide printing" would be awesome.
avatar laurentsj Pro Oct 6. 2007. 1:29 pm #14
Rolando:
As promised I return with my ideas about the way a wiki should be used in aC. For clarification I posted a picture in the aC Flickr group

(http://www.flickr.com/photos/rolandwoldt/311314873/) so please take a look at it if you think I'm talking nonsense ;-)

Overall proposal

- there should be only one wiki per aC installation

What do you think?


The graph does make sense.

Now that we've got AC1.0 out, I would place the wiki as one of the top feature request.

But i'm not sure it should be restricted to one wiki.


Im my situation, i would have two versions:

A backend wiki for the development team and contractors
A front-end reference wiki / knowledge base / online documentation for clients.

Futhermore, i did also request in another thread to have the option to duplicate and move milestones/tasks/papers/discussions inside part of the wiki.

Another way of looking at it is to simply create one project that we make permanent and name "Wiki", and allow tasks/milestones/files/papers/discussions to be copied and moved across projects.

In fact, this would be an ideal feature, killing two birds with one stone.



3mille.com | websemantique.com | virtuel-immobilier.com | flickr.com/photos/laurentsj/
avatar laurentsj Pro Oct 6. 2007. 2:53 pm #15
I'm not getting much feedback on the wiki, so I'll use the "pages" for project specific wikis, and will create a project named "wiki" for all permanent wiki information.
3mille.com | websemantique.com | virtuel-immobilier.com | flickr.com/photos/laurentsj/