phplist Documentation: Pros and cons of Wikka vs. Tikiwiki

~-YanB: I suggested it, & I like it, no surprise.
~-MichielD: I think it's fine and it works quite well. It's nice that it's not too cluttered with all kinds of other stuff that we don't need. There seem to be only 28 pages in the other one, so cutting and pasting to move the content across should not take too long.
~-Damien: Much nicer than TikiWiki. One complaint I had with the TikiWiki development team way back when (1.5-1.6 timeline) was that they were building too much in and not refactoring the code like they should, e.g. they had several different code lines for handling comments, forums, etc, when those are all the same data just presented in a different format. Anyway, looks good, thanks for finding it.
~-PascalVanHecke: This is indeed a more "pure" wiki. There's however one asset I think tikiwiki has, and that is the combination pdf generation and structures. That makes it possible to generate a manual out of the wiki (and structures add more "structure" anyway ;-) ). In the last tikiwiki version I installed myself (1.8.4, Polaris) that didn't really work yet like it should, but it still it is one of the goals of the project, and it is the way how tikiwiki produces it's own manual: see http://64.233.183.104/search?q=cache:LWUrf5Nj51kJ:doc.tikiwiki.org/tiki-index.php%3Fpage%3DStructures%2BUser+site:doc.tikiwiki.org+pdf+structures&hl=en (link from google cache, doc.tikiwiki.org was unreachable...). Still, if that's not a prerequisite, I don't have any objections against switching.
~~&Pascal: what do you mean with 'structure'? Otherwise, PDF is a good idea, but I honestly don't think it would be very useful. On sites offering the same, I never download the PDF files, but rather browse the website. But that's just me. --YanB
~~~&Yan: structures are a feature of TikiWiki, see http://doc.tikiwiki.org/tiki-index.php?page=Structures . Basically if you put a page in a structure, TOC and navigation are created for you. PDF Generation of a structure then could result in a very simple, low-effort manual. Structures are tikiwiki-"proprietary" yet they are a way of avoiding the risk of "wiki-chaos". I suggest to build a structure for each of the main sections: http://mail.tincan.co.uk/archive/tincan.co.uk/phplist-developers/msg00274.html
~~~~&Pascal: thanks for the links. There's nothing like structures on the wikka, and it seems interesting indeed -- though as usual the tiki documentation is incomplete and almost incomprehensible to me ! :( And there's no PDF on the wikka either, but I think someone is working on that feature. OTH, there **is** a 'Category' function with the wikka that we could use to generate something like smart indexes. For instance, CategoryDocumentation, CategoryDevelopment, etc. can list all the wiki pages that deal with these issues, as long as we include the note: Categoryxxx at the end of the page. As for wiki-chaos, yes I understand! but if we determine smart Categories and create templates people should use when they create new pages, it should minimize damage. Also, if we're a few wikiadmins, I don't think it should be that bad to maintain some order (especially in the 'official documentation' sections). But this may be wishful thinking. --YanB
~~~~~&Yan: TikiWiki has categories as wel, have a look at http://doc.tikiwiki.org/tiki-index.php?page=Categories . With a structure , you can put pages in a hierarchy, with categories, you can tag and group pages that have some property in common throughout the wiki. I suggested a way of categorising the docs pages according to status here: http://mail.tincan.co.uk/archive/tincan.co.uk/phplist-developers/msg00300.html (and there are lots of other ways we might work with categories) but maybe that's overkill.
~-...

~~~-YanB: I suggested it,~~

~-YanB: I suggested it,

~-YanB: I suggested it, & I like it, no surprise.
~-MichielD: I think it's fine and it works quite well. It's nice that it's not too cluttered with all kinds of other stuff that we don't need. There seem to be only 28 pages in the other one, so cutting and pasting to move the content across should not take too long.
~-Damien: Much nicer than TikiWiki. One complaint I had with the TikiWiki development team way back when (1.5-1.6 timeline) was that they were building too much in and not refactoring the code like they should, e.g. they had several different code lines for handling comments, forums, etc, when those are all the same data just presented in a different format. Anyway, looks good, thanks for finding it.
~-PascalVanHecke: This is indeed a more "pure" wiki. There's however one asset I think tikiwiki has, and that is the combination pdf generation and structures. That makes it possible to generate a manual out of the wiki (and structures add more "structure" anyway ;-) ). In the last tikiwiki version I installed myself (1.8.4, Polaris) that didn't really work yet like it should, but it still it is one of the goals of the project, and it is the way how tikiwiki produces it's own manual: see http://64.233.183.104/search?q=cache:LWUrf5Nj51kJ:doc.tikiwiki.org/tiki-index.php%3Fpage%3DStructures%2BUser+site:doc.tikiwiki.org+pdf+structures&hl=en (link from google cache, doc.tikiwiki.org was unreachable...). Still, if that's not a prerequisite, I don't have any objections against switching.
~~&Pascal: what do you mean with 'structure'? Otherwise, PDF is a good idea, but I honestly don't think it would be very useful. On sites offering the same, I never download the PDF files, but rather browse the website. But that's just me. --YanB
~~~&Yan: structures are a feature of TikiWiki, see http://doc.tikiwiki.org/tiki-index.php?page=Structures . Basically if you put a page in a structure, TOC and navigation are created for you. PDF Generation of a structure then could result in a very simple, low-effort manual. Structures are tikiwiki-"proprietary" yet they are a way of avoiding the risk of "wiki-chaos". I suggest to build a structure for each of the main sections: http://mail.tincan.co.uk/archive/tincan.co.uk/phplist-developers/msg00274.html
~~~~&Pascal: thanks for the links. There's nothing like structures on the wikka, and it seems interesting indeed -- though as usual the tiki documentation is incomplete and almost incomprehensible to me ! :( And there's no PDF on the wikka either, but I think someone is working on that feature. OTH, there **is** a 'Category' function with the wikka that we could use to generate something like smart indexes. For instance, CategoryDocumentation, CategoryDevelopment, etc. can list all the wiki pages that deal with these issues, as long as we include the note: Categoryxxx at the end of the page. As for wiki-chaos, yes I understand! but if we determine smart Categories and create templates people should use when they create new pages, it should minimize damage. Also, if we're a few wikiadmins, I don't think it should be that bad to maintain some order (especially in the 'official documentation' sections). But this may be wishful thinking. --YanB
~~~~~&Yan: TikiWiki has categories as wel, have a look at http://doc.tikiwiki.org/tiki-index.php?page=Categories . With a structure , you can put pages in a hierarchy, with categories, you can tag and group pages that have some property in common throughout the wiki. I suggested a way of categorising the docs pages according to status here: http://mail.tincan.co.uk/archive/tincan.co.uk/phplist-developers/msg00300.html (and there are lots of other ways we might work with categories) but maybe that's overkill.
~-...

~~~-YanB: I suggested it,~~

~-YanB: I suggested it,

~-YanB: I suggested it, & I like it, no surprise.
~-MichielD: I think it's fine and it works quite well. It's nice that it's not too cluttered with all kinds of other stuff that we don't need. There seem to be only 28 pages in the other one, so cutting and pasting to move the content across should not take too long.
~-Damien: Much nicer than TikiWiki. One complaint I had with the TikiWiki development team way back when (1.5-1.6 timeline) was that they were building too much in and not refactoring the code like they should, e.g. they had several different code lines for handling comments, forums, etc, when those are all the same data just presented in a different format. Anyway, looks good, thanks for finding it.
~-PascalVanHecke: This is indeed a more "pure" wiki. There's however one asset I think tikiwiki has, and that is the combination pdf generation and structures. That makes it possible to generate a manual out of the wiki (and structures add more "structure" anyway ;-) ). In the last tikiwiki version I installed myself (1.8.4, Polaris) that didn't really work yet like it should, but it still it is one of the goals of the project, and it is the way how tikiwiki produces it's own manual: see http://64.233.183.104/search?q=cache:LWUrf5Nj51kJ:doc.tikiwiki.org/tiki-index.php%3Fpage%3DStructures%2BUser+site:doc.tikiwiki.org+pdf+structures&hl=en (link from google cache, doc.tikiwiki.org was unreachable...). Still, if that's not a prerequisite, I don't have any objections against switching.
~~&Pascal: what do you mean with 'structure'? Otherwise, PDF is a good idea, but I honestly don't think it would be very useful. On sites offering the same, I never download the PDF files, but rather browse the website. But that's just me. --YanB
~~~&Yan: structures are a feature of TikiWiki, see http://doc.tikiwiki.org/tiki-index.php?page=Structures . Basically if you put a page in a structure, TOC and navigation are created for you. PDF Generation of a structure then could result in a very simple, low-effort manual. Structures are tikiwiki-"proprietary" yet they are a way of avoiding the risk of "wiki-chaos". I suggest to build a structure for each of the main sections: http://mail.tincan.co.uk/archive/tincan.co.uk/phplist-developers/msg00274.html
~~~~&Pascal: thanks for the links. There's nothing like structures on the wikka, and it seems interesting indeed -- though as usual the tiki documentation is incomplete and almost incomprehensible to me ! :( And there's no PDF on the wikka either, but I think someone is working on that feature. OTH, there **is** a 'Category' function with the wikka that we could use to generate something like smart indexes. For instance, CategoryDocumentation, CategoryDevelopment, etc. can list all the wiki pages that deal with these issues, as long as we include the note: Categoryxxx at the end of the page. As for wiki-chaos, yes I understand! but if we determine smart Categories and create templates people should use when they create new pages, it should minimize damage. Also, if we're a few wikiadmins, I don't think it should be that bad to maintain some order (especially in the 'official documentation' sections). But this may be wishful thinking. --YanB
~~~~~&Yan: TikiWiki has categories as wel, have a look at http://doc.tikiwiki.org/tiki-index.php?page=Categories . With a structure , you can put pages in a hierarchy, with categories, you can tag and group pages that have some property in common throughout the wiki. I suggested a way of categorising the docs pages according to status here: http://mail.tincan.co.uk/archive/tincan.co.uk/phplist-developers/msg00300.html (and there are lots of other ways we might work with categories) but maybe that's overkill.
~-...

~-MichielD: I think it's fine and it works quite well. It's nice that it's not too cluttered with all kinds of other stuff that we don't need. There seem to be only 28 pages in the other one, so cutting and pasting to move the content across should not take too long.

~-MichelD: I think it's fine and it works quite well. It's nice that it's not too cluttered with all kinds of other stuff that we don't need. There seem to be only 28 pages in the other one, so cutting and pasting to move the content across should not take too long.

{{backlinks}}{{lastedit show="3"}}
===Pros and cons of Wikka vs. Tikiwiki===

~~Pros and cons of Wikka vs. Tikiwiki~~

phplist Documentation : WikkaVsTiki

Revision [1258]

Additions:

Deletions:

Revision [1244]

Additions:

Deletions:

Revision [1114]

Additions:

Deletions:

Revision [1086]

Additions:

Deletions:

Revision [394]

Additions:

Deletions:

Revision [59]

Additions:

Deletions:

Revision [58]