Difference between revisions of "Manual:Content organization"
[unchecked revision] | [quality revision] |
m (P technik moved page Organize content sensibly to Content organization without leaving a redirect) |
m (Tag: Visual edit) |
The A guiding principle in a wiki environment is that all : All users can easily and immediately share their knowledge immediately in writing and collaborate on content. For this it is not absolutely necessary important for the users to 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 as a user with write permissions, 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 immediately.
In practice, however, there are many content-related relationships between the individual pages. In addition, there are often different target groups for the respective 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:

To clarify how these wiki functions can be used efficiently for a single wiki or Wiki wiki farm, a content organization and content management concept should be developed. Here are You should consider the following areas to consider:
-
Content Strategystrategy:
- What content is shared types of content do you share on the wiki?
- Who creates what which content?
- Is there a need for pre-structured content formats?
-
Information architecture
- How do I organize content, navigation paths and search capabilities to provide user-friendly access to existing information?
- Who has what kind of access rights to the content?
- Which What are the target groups are available for the respective different content areas?
-
Quality management
- Which content must be checked and by whom?
- Is there Do you have content with a defined predefined life cycle?
- Are Is all content meaningfully categorized?
If there is no exact idea about the you don't have a content strategy, the an information architecture and the ideas about quality management when setting up a new wiki, the wiki can also already be used while being unstructured. Content is created and collected Collect and create content as soon as the wiki is technically available. It is only important here 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. From then on, content will be created and organized according to the new content structure.
TheA guiding principle in a wiki environment is that all : All users can easily and immediately share their knowledge immediately in writing and collaborate on content. For this it is not absolutely necessary important for the users to 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 as a user with write permissions, I can immediately create a new page as a user with write access to the searched keyword. First of all, it is . It is, first of all, important that the information is shared. Where the resulting wiki page ultimately lieslives and how it is found does not necessarily have to be decided immediately. In practice, however, there are many content-related relationships between the individual pages. In addition, there are often different target groups for the respective 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 rights *Content structuring elements: **namespaces **Categoriespermissions *Elements for structuring content: **namespaces **categories **pages and subpages The following is a simple example offor content organization: {{#drawio:inhaltsorganisation}} To clarify how these wiki functions can be used efficiently for a single wiki or Wikiwiki farm, a content organization and content management concept should be developed. Here are You should consider the following areas to consider: #'''Content Strategystrategy:''' ##What types of content is shared do you share on the wiki? ##Who creates whatwhich content? ##Is there a need for pre-structured content formats? #'''Information architecture''' ##How do I organize content, navigation paths and search capabilities to provide user-friendly access to existing information? ##Who has what kind of access rights to the content? ##Which target groups are available for the respective##What are the target groups for the different content areas? #'''Quality management''' ##Which content must be checked and by whom? ##Is there ##Do you have content with a definedpredefined life cycle? ##Are##Is all content meaningfully categorized? If there is no exact idea about the content strategy, the information architecture and the you don't have a content strategy, an information architecture and ideas about quality management when setting up a new wiki, the wiki can alsoalready be used while being unstructured. Content is created and collectedCollect and create content as soon as the wiki is technically available. It is only important here that data protection aspects wereare clarified in advance and communicated accordingly when sharing company information and communicated accordingly. Through the search function and various special pages, the content can theneasily be searched accordinglyand retrieved. As the content grows, administrators can then take stockinventory and retrospectively structure the content based on that information. From then on, content will be created and organized according to the new content structure. [[en:{{FULLPAGENAME}}]] [[de:Inhaltsorganisation]]
Line 1: | Line 1: | ||
− | + | A guiding principle in a wiki environment is: All users can easily and immediately share their knowledge in writing and collaborate on content. For this it is not important for users to know how the wiki is organized. | |
− | + | Initially, a page can be created anywhere in the wiki, wherever a user has write access. If I do not find important information in the wiki as a user with write permissions, I can immediately create a new page. | |
− | + | It is, first of all, important that the information is shared. Where the resulting wiki page ultimately lives and how it is found does not necessarily have to be decided immediately. | |
− | In practice, however, there are many | + | In practice, however, there are many relationships between the individual pages. In addition, there are often different target groups for the respective 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: | 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 | + | *User roles and permissions |
− | * | + | *Elements for structuring content: |
**namespaces | **namespaces | ||
− | ** | + | **categories |
**pages and subpages | **pages and subpages | ||
− | The following is a simple example | + | The following is a simple example for content organization: |
{{#drawio:inhaltsorganisation}} | {{#drawio:inhaltsorganisation}} | ||
Line 23: | Line 23: | ||
− | To clarify how these wiki functions can be used efficiently for a single wiki or | + | To clarify how these wiki functions can be used efficiently for a single wiki or wiki farm, a content organization and content management concept should be developed. You should consider the following areas: |
− | #'''Content | + | #'''Content strategy:''' |
− | ##What content | + | ##What types of content do you share on the wiki? |
− | ##Who creates | + | ##Who creates which content? |
##Is there a need for pre-structured content formats? | ##Is there a need for pre-structured content formats? | ||
#'''Information architecture''' | #'''Information architecture''' | ||
##How do I organize content, navigation paths and search capabilities to provide user-friendly access to existing information? | ##How do I organize content, navigation paths and search capabilities to provide user-friendly access to existing information? | ||
− | ##Who has what access | + | ##Who has what kind of access to the content? |
− | ## | + | ##What are the target groups for the different content areas? |
#'''Quality management''' | #'''Quality management''' | ||
− | ##Which content must be checked by whom? | + | ##Which content must be checked and by whom? |
− | ## | + | ##Do you have content with a predefined life cycle? |
− | ## | + | ##Is all content meaningfully categorized? |
− | If | + | If you don't have a content strategy, an information architecture and ideas about quality management when setting up a new wiki, the wiki can already be used while being unstructured. Collect and create content as soon as the wiki is technically available. It is only important that data protection aspects are clarified in advance and communicated accordingly when sharing company information. Through the search function and various special pages, the content can easily be searched and retrieved. |
− | As the content grows, administrators can then take | + | As the content grows, administrators can then take inventory and structure the content based on that information. From then on, content will be created and organized according to the new content structure. |
[[en:{{FULLPAGENAME}}]] | [[en:{{FULLPAGENAME}}]] | ||
[[de:Inhaltsorganisation]] | [[de:Inhaltsorganisation]] |