User:Peter Schmitt/Idea
The account of this former contributor was not re-activated after the server upgrade of March 2022.
Remark: Comments on the talk page are welcome.
Workgroups
It is necessary to keep the following issues separate:
(1) organizing Editor competence (2) subject classification (3) organizing collaboration
Editor competence
Subject classification
As long as categories are dedicated to organization should should be done differently (not via subgroups)
Collaboration
"Proper" workgroups (for working together) should be created on an ad-hoc bases if there is a need. If there are no Citizens who collaborate, no workgroup is needed.
Metadata
(needs MC support)
Extend Metadata to cover all meta-information, including credits to sources (like WP imports) and housekeeping information.
Move Metadata to its own namespace (MD: or Metadata:)
- Once created (correctly) do not move Metadata, but record name changes
- Use Metadata (instead of Talk) without display of prefix
Definitions
(when CZ skin and layout is redesigned) Display definitons below the main page title.
Question: Should /Definitions have a separate namespace?
- Since a definition depends on the title of a page it cannot be moved (without a change) when a page is renamed.
Sources
Merge the /Bibliography and /External Links subpages to a /Sources (or other) subpage.
- (needs MC and technical support) A bot has to combine existing subpages, to merge histories, and to change wiki links.
Context
Rename /Related Articles to /Context (shorter!) and dedicate it to
- recommendations for further reading -- true recommendations, not everything loosely related.
- For loosely related pages (e.g., names) links in the text are sufficient.
- Allow a structure adapted to the topic ("parent topics, subtopic, other related topics" is too restrictive)
- showing the context by listing the appropriate subject classifications.
- Core articles (or other top level articles) can have an extended /Context page listing a tree of (sub)topics.
Subpages
Is it indeed useful to have (so many) "predefined" subpages (other than the "obligatory" ones)? (Most pages are essentially "catalogs", anyway!)
- Handle all subpages as "article-specific", added via the Metadata.
- Allow chosing the titles of subpages more freely.
Subject classification
(instead of categories)
Use a separate namespace (SC, Subj/Subject, Class/Classification) to create a network of subjects:
- Each subject class has its own page that contains
- a brief description/definition of this subject class and
- links to its 'immediate parents.
- The /Context subpage links to all relevant subject classes.
- "What links here" can be used to show
- the immediate subclasses (links from the SC: namespace), and
- all pages carrying this classification (links from the main namespace).
EC and MC matter
CZ archive
Create a namespace for a (structured and indexed) archive on CZ history (Arc/Archive or Hist/History).
- Move outdated policy pages there to document pre-Charter history.
- While the history of (completely rewritten) pages is preserved, these versions are not readily available e.g. for text search.
- Leaving outdated pages in the CZ namespace will be shown by searches.