Bureaucrats, developer, Administrators
9,854
edits
(amazing. i actually have something to blog) |
m (fix typos) |
||
Line 7: | Line 7: | ||
Now if we implement this [[WikiVote]] thing then there are two or three different types of votes and three is too much imho. | Now if we implement this [[WikiVote]] thing then there are two or three different types of votes and three is too much imho. | ||
But the "new" [[Wiki]] approach and the [[features|original vision]] can be brought closer by using strictly named subarticles that are then "collapsed" into a viewable document for the [[consumer]] based on her/his [[preferences]] ie. articles and their subarticles form a tree and [[preferences]] define what branches and leaves are visible and in what order. If you want to see ecological stuff first when fine. If you want labor issues first, fine. If you want consumer reviews first, fine. And this way we can have more fine grained version control (signatures) and editors can concentrate on the subarticle that is closest to their expertese. Also newbie editors are less likely to get | But the "new" [[Wiki]] approach and the [[features|original vision]] can be brought closer by using strictly named subarticles that are then "collapsed" into a viewable document for the [[consumer]] based on her/his [[preferences]] ie. articles and their subarticles form a tree and [[preferences]] define what branches and leaves are visible and in what order. If you want to see ecological stuff first when fine. If you want labor issues first, fine. If you want consumer reviews first, fine. And this way we can have more fine grained version control (signatures) and editors can concentrate on the subarticle that is closest to their expertese. Also newbie editors are less likely to get irritated over the syntax requirements that are not usually present in wikis. Parsing monolithic articles would also hog more resources | ||
---- | ---- | ||
11.10.2003 | 11.10.2003 |