Thread:Talk:Auth systems/SUL2/"Central wiki"/reply (4)

Greetings
 * I am really looking forward to see the birth of a central wiki.
 * The user space there should be used to administrate global preferences as well as global resource pages, mainly CSS and JavaScript. Moreover the user page will serve as a global business card, which could tell what languages are understood, where the home ground is, and perhaps good old PGP fingerprint or whatever.
 * Since there wouldn't be many volunteers to do global cleanup, removing vandalism from project pages and deleting illegal storage of undesired material and so on, creation of pages by non-sysops might be limited to the own user page, the standardized resource files like mypage/common.css or mypage/vector.js and nothing else.
 * I do expect to see both global and local preferences and resource pages in a cascading manner.
 * There might be things I want to be configured world-wide for any wiki. They are put on the global wiki.
 * When working on a particular wiki of particular type, I need special configuration for this human language, with those project pages, on this type of project like wikipedia or wikidata or wikisource or commons.
 * I expect the following sequence when working on a local wiki (CSS example): MWGlobal.css → site:Common.css → site:Vector.css → SUL:common.css → SUL:vector.css → user:common.css → user:vector.css (leaving empty what I won't need).
 * Since meta: is already loaded with many thousands of project pages and it is a working project, I might want to have local adaptions on meta: and I don't want those to be shared with all other projects.
 * Threfore I would prefer a blank wiki with only some tutorial pages and nothing else to do than editing the own user pages.