Manual:Content organization

The A guiding principle in a wiki environment is that all : All users can easily and immediately share their knowledge immediately in writingand collaborate on content. For this to happen, it is not absolutely necessary for the users to necessarily important that users know how the wiki is organized.

First of allInitially, a page can be created anywhere in the wiki, or wherever a user has write access. If I do not find important information in the wiki, I can immediately create a new page as a user with write access to the searched keyword. First It is, first of all, it is important that the information is shared. Where the resulting wiki page ultimately lies lives and how it is found does not necessarily have to be decided immediatelyright away.

In practice, however, there are many content-related relationships between the individual pages. In addition, there are often different target groups for the respective different types of content.

Therefore, it is important for administrators to set up the wiki so that the content can be meaningfully organized. There are important areas to consider:

• User roles and access rightspermissions
• Content Elements for structuring elementscontent:
  • namespacesCategories
  • categories
  • pages and subpages

The following is a simple example of for content organization:

[Edit]

Content Strategy

To clarify how these wiki functions can be used efficiently for a single wiki or wiki farm, a content organization and management concept should be developed. Consider the following areas:

1. Content strategy:
   1. What content is shared types of content do you share on the wiki?
   2. Who creates

what

1. 1. which content?
   2. Is there a need for pre-structured content formats?
2. Information architecture
   1. How do I organize content, navigation paths and search capabilities to provide user-friendly access to existing information?
   2. Who has what kind of access
   rights
   1. to the content?
   Which
   1. What are the target groups
   are available
   1. for the
   respective
   1. different content areas?
3. Quality management
   1. Which content must be checked and by whom?
   2. Is there Do you have content with a defined predefined life cycle?
   3. Are Is all content meaningfully categorized?

If there is no exact idea about the content strategy, the you don't have a content strategy or an information architecture and the ideas about quality management in place when setting up a new wiki, don't hesitate to start using the wiki can also be used unstructured. Content is created and collected . Collect and create content as soon as the wiki is technically available. It is only important here Just make sure that data protection aspects were are clarified in advance and communicated accordingly when sharing company information and communicated accordingly. Through the search function and various special pages, the content can then easily be searched accordinglyand retrieved.

As the content grows, administrators can then take stock inventory and retrospectively structure the content based on that information and determine policies, processes and the information architecture. The most important decisions should be written down in a formal governance document. From then on, content will be created and organized according to the new content structurepolicies, processes and architecture decisions that are specified in this document.