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

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

InitiallyFirst of all, 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.

It is, first First of all, it is important that the information is shared. Where the resulting wiki page ultimately lives lies 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 permissionsaccess rights
  • Elements for Content structuring contentelements:
    • namespacescategories
    • Categories
    • pages and subpages


The following is a simple example for of content organization:

drawio: inhaltsorganisation
drawio: inhaltsorganisation



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. You should consider Here are the following areas to consider:

  1. Content strategyStrategy:
    1. What types of content do you share content is shared on the wiki?
    2. Who creates which what content?
    3. 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 to the content?
    3. What are the Which target groups are available for the different respective content areas?
  3. Quality management
    1. Which content must be checked and by whom?
    2. Do you have Is there content with a predefined defined life cycle?
    3. Is Are all content meaningfully categorized?

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

As the content grows, administrators can then take inventory stock and retrospectively structure the content based on that information. From then on, content will be created and organized according to the new content structure.

AThe guiding principle in a wiki environment is: All  that all users can easily and immediately share their knowledge immediately in writing and collaborate on content. For this it is not important absolutely necessary for the users to know how the wiki is organized.
        
InitiallyFirst of all, 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.
            

            It is, first of all,  as a user with write access to the searched keyword.
            

            First of all, it is important that the information is shared. Where the resulting wiki page ultimately liveslies 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 permissions
            
            *Elements for structuring content:
            
            **namespaces
            
            **categoriesaccess rights
            
            *Content structuring elements:
            
            **namespaces
            
            **Categories
        
        **pages and subpages
        

        The following is a simple example forof 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. You should consider Here are the following areas to consider:
        

        #'''Content strategyStrategy:'''
        
        ##What types of content do you share is shared on the wiki?
        
        ##Who creates whichwhat 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 access rights to the content?
        ##What are the target groups  for the different##Which target groups are available for the respective content areas?
        
        #'''Quality management'''
        
        ##Which content must be checked and by whom?
        ##Do you have ##Is there content with a predefineddefined life cycle?
        ##Is##Are all content meaningfully categorized?
        

        If you don't have a content strategy, an information architecture and ideas about there is no exact idea about the content strategy, the information architecture and the quality management when setting up a new wiki, the wiki can alreadyalso be used while being unstructured. Collect and create content Content is created and collected as soon as the wiki is technically available. It is only important here that data protection aspects arewere clarified in advance and communicated accordingly when sharing company information and communicated accordingly. Through the search function and various special pages, the content can easilythen be searched and retrievedaccordingly.
        

        As the content grows, administrators can then take inventorystock 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:
The guiding principle in a wiki environment is that all users can easily share their knowledge immediately in writing. For this it is not absolutely necessary for the users to know how the wiki is organized.
+
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.
  
First of all, 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.
+
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.
  
First of all, it is important that the information is shared. Where the resulting wiki page ultimately lies and how it is found does not necessarily have to be decided immediately.
+
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 content-related relationships between the individual pages. In addition, there are often different target groups for the respective content.
+
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 access rights
+
*User roles and permissions
*Content structuring elements:
+
*Elements for structuring content:
 
**namespaces
 
**namespaces
**Categories
+
**categories
 
**pages and subpages
 
**pages and subpages
  
  
The following is a simple example of content organization:
+
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 Wiki farm, a content organization and content management concept should be developed. Here are the following areas to consider:
+
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 Strategy:'''
+
#'''Content strategy:'''
##What content is shared on the wiki?
+
##What types of content do you share on the wiki?
##Who creates what content?
+
##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 rights to the content?
+
##Who has what kind of access to the content?
##Which target groups are available for the respective content areas?
+
##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?
##Is there content with a defined life cycle?
+
##Do you have content with a predefined life cycle?
##Are all content meaningfully categorized?
+
##Is all content meaningfully categorized?
  
If there is no exact idea about the content strategy, the information architecture and the quality management when setting up a new wiki, the wiki can also be used unstructured. Content is created and collected as soon as the wiki is technically available. It is only important here that data protection aspects were clarified in advance when sharing company information and communicated accordingly. Through the search function and various special pages, the content can then be searched accordingly.
+
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 stock and retrospectively structure the content. From then on, content will be created and organized according to the new content structure.
+
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]]

Attachments

Discussions