Wiki Design, Design Considerations, and Feedback

When developing a wiki application, what should I consider?

So far I:

  • changes
  • different text analysis
  • tracking links on wikis and pages that link to other pages.
  • related wikis, i.e. wikis are related to others.

What else do you need to create a wiki?

+3
source share
9 answers

, /.

, wiki - , , wiki http://c2.com/. , , . , (NO WYSIWYG!!!), , ( ), . , .

- , , , , . , . WYSIWYG - , "" , , .., , /, . "" , -, "", . , wiki - , .

+5

TiddlyWiki. , , . ( "" "", TiddlyWiki - . , ):

  • "" (WikiWords )
  • ( )
  • ,

. , , , , .

+3

:

  • . , Redmine.

, , (.. wiki).

+3

- , , MediaWiki, TikiWiki .

- - ​​ . , , , , , , .

wiki (, MediaWiki), WYSIWYG.

+1

, , .

, - /, , .

(, ):

  • wiki VCS, / (, , ), .
  • API , mashup.
  • (, , ), .
  • .
  • / ( -) WYSIWYG.
  • ...
+1

, Ward Cunningham Wiki.

+1

, , XSS. , , .

0

, - , . WYSIWYG , StackOverflow . - , ( , ), , .

Along the same lines, another annoyance is that each wiki seems to use slightly different markup. I think every designer thinks they can do it better than before. I would suggest using either the MediaWiki syntax or something like MarkDown, so standard that power users have an easier time.

Finally, think about what will happen to your wikia, besides the many many other wikis that already exist, and how your design will affect this.

0
source

Source: https://habr.com/ru/post/1699299/


All Articles