Editing Consumerium plans as of 2013
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 46: | Line 46: | ||
== Consumium wiki structure == | == Consumium wiki structure == | ||
The old plans called for having two wikis either [[Research Wiki]] and [[Publish Wiki]] ( suggested by the [[trolls]], focus on distinction of researchable stuff from publishable stuff ) or [[Content Wiki]] and [[Opinion Wiki]] ( suggested by [[User:Juxo]], effort founder, focus on isolation of factual content from subjective opinions ) but currently it looks like those plans are scrapped in favor of having only one [[Implementation Wiki]] to minimize governmental overhead. | The old plans called for having two wikis either [[Research Wiki]] and [[Publish Wiki]] ( suggested by the [[trolls]], focus on distinction of researchable stuff from publishable stuff ) or [[Content Wiki]] and [[Opinion Wiki]] ( suggested by [[User:Juxo]], effort founder, focus on isolation of factual content from subjective opinions ) but currently it looks like those plans are scrapped in favor of having only one [[Implementation Wiki]] to minimize governmental overhead. | ||
The '''[[voting]] pages''' of users will be copyright of the page owner i.e. '''not [[copyleft]]ed''' and not included in the dumps for forking. The voting pages of users will be NOINDEX and NOFOLLOW to stop them from getting included in search engine results. Likely the talk-namespace will be NOINDEX, NOFOLLOW so that the talk-pages of articles will be the research side of it and the actual main-namespace articles will be the publish side of it | |||
The upcoming [[Universal Language Selector]] conforms to the MediaWiki style of having the language code coming after the article, not before it, though our method would be navigationally perhaps better. | The upcoming [[Universal Language Selector]] conforms to the MediaWiki style of having the language code coming after the article, not before it, though our method would be navigationally perhaps better. |