IBX-5100: Reorganize Admin Panel/Content model doc

docs/administration/admin_panel/admin_panel.md

@@ -0,0 +1,21 @@
+---
+description: Ibexa DXP Back Office contains managements options for permissions, users, languages, Content Types, as well as system information.
+---
+
+# Admin panel
+
+Once you set up your environment you can start your work as an administrator.
+Your most useful tools can be found in **Admin Panel**.
+
+To access Admin Panel, click the icon: ![Admin Panel Icon](admin_panel_icon.png){.inline-image}.
+
+[[= cards([
+    "administration/admin_panel/users_admin_panel",
+    "administration/admin_panel/roles_admin_panel",
+    "administration/admin_panel/url_management_admin_panel",
+    "administration/admin_panel/languages_admin_panel",
+    "administration/admin_panel/segments_admin_panel",
+    "administration/admin_panel/corporate_admin_panel",
+    "administration/admin_panel/workflow_admin_panel",
+    "administration/admin_panel/system_information_admin_panel",                
+], columns=4) =]]

docs/administration/admin_panel/corporate_admin_panel.md

@@ -0,0 +1,15 @@
+---
+description: You can manage companies profiles in the Admin Panel.
+---
+
+# Corporate
+
+You can manage companies profiles in the Admin Panel.
+
+There, in the **Corporate** section, you can find basic information about existing companies, 
+for example, details, versions, locations, translations, a list of members, billing addresses 
+and technical details regarding the organization, such as visibility, IDs, or relations.
+
+![Corporate section](admin_panel_corporate.png "Corporate section")
+
+See [Customer management](https://doc.ibexa.co/projects/userguide/en/latest/customer_management/manage_customers/) for further information. 

docs/administration/admin_panel/languages_admin_panel.md

@@ -0,0 +1,21 @@
+---
+description: Ibexa DXP offers the ability to create multiple translations of your website.
+---
+
+# Languages
+
+[[= product_name =]] offers the ability to create multiple translations of your website.
+Which version is shown to a visitor depends on the way your installation is set up.
+A new language version for the website can be added in the [Admin Panel](admin_panel.md) in the **Languages** tab.
+
+Every new language must have a name and a language code, written in the `xxx-XX` format, for example `eng-GB` etc.
+
+![Languages](admin_panel_languages.png "Languages")
+
+The multilanguage system operates based on a global translation list 
+that contains all languages available in the installation.
+After adding a language you may have to reload the application to be able to use it.
+Depending on your set up, additional configuration may be necessary 
+for the new language to work properly, especially with SiteAccesses.
+
+See [Languages](languages.md) for further information.

docs/administration/admin_panel/roles_admin_panel.md

@@ -0,0 +1,43 @@
+---
+description: To give users an access to your website you need to assign them Roles in the Admin Panel.
+---
+
+# Roles
+
+To give users an access to your website you need to assign them Roles in the Admin Panel.
+
+![Roles](admin_panel_roles.png "Roles")
+
+Each Role consists of:
+
+**Policies**
+
+![Policies](admin_panel_policies.png "Policies")
+
+Rules that give users access to different function in a module.
+You can restrict what user can do with Limitations.
+The available Limitations depend on the chosen Policy.
+When Policy has more than one Limitation, all of them have to apply.
+See [example use case](permission_use_cases.md#restrict-editing-to-part-of-the-tree).
+
+!!! note
+
+    Limitation specifies what a User can do, not what they can't do.
+    A `Location` Limitation, for example, gives the User access to content with a specific Location, 
+    not prohibits it. See [Available Limitations](limitations.md#available-limitations) for further information.
+
+**Assignments**
+
+![Assignments](admin_panel_assignments.png "Assignments")
+
+After you created all Policies, you can assign the Role to Users and/or User Groups with possible additional Limitations.
+Every User or User Group can have multiple Roles.
+A User can also belong to many groups, for example, Administrators, Editors, Subscribers.
+
+Best practice is to avoid assigning Roles to Users directly.
+Model your content (Content Types, Sections, Locations etc.) in a way that can be accessed by generic Roles.
+That way system will be more secure and easier to manage.
+This approach also improves performance. Role assignments and Policies are taken into account during search/load queries.
+
+See [Permissions overview](permissions.md) for further information
+and [Permission use cases](permission_use_cases.md) for details on how to customize access to different parts of the Back Office.

docs/administration/admin_panel/segments_admin_panel.md

@@ -0,0 +1,18 @@
+---
+description: You can use Segments to display specific content to specific Users.
+---
+
+# Segments
+
+You can use Segments to display specific content to specific [Users](users.md).
+They are used out of the box in the Targeting and Dynamic targeting blocks in the Page.
+
+Segments are collected in Segment Groups:
+
+![Segment Groups](admin_panel_segment_groups.png)
+
+Each Segment Group can contain Segments that you can target content for.
+
+![Segment](admin_panel_segment.png)
+
+You can assign Users to Segments [through the API](segment_api.md#assigning-users).

docs/administration/admin_panel/system_information_admin_panel.md

@@ -0,0 +1,10 @@
+---
+description: System information provides basic system information such as versions of all installed packages.
+---
+
+# System Information
+
+The System Information panel in the Back Office is sourced in the [`ibexa/support-tools` repository](https://github.com/ibexa/support-tools).
+There you will also find basic system information such as versions of all installed packages.
+
+![System Information](admin_panel_system_info.png "System Information")

docs/administration/admin_panel/url_management_admin_panel.md

@@ -0,0 +1,12 @@
+---
+description: URL Management let you manage external URL addresses and URL wildcards.
+---
+
+# URL Management
+
+You can manage external URL addresses and URL wildcards in the Admin Panel.
+Configure URL aliases to have human-readable URL addresses throughout your system.
+
+See [URL management](url_management.md) for further information.
+
+![URL Management](admin_panel_url_management.png "URL Management")

docs/administration/admin_panel/users_admin_panel.md

@@ -0,0 +1,17 @@
+---
+description: All User Groups and Users can be accessed in the Users tab.
+---
+
+# Users
+
+[Users](users.md) in [[= product_name =]] are treated the same way as Content items.
+They are organized in groups such as *Guests*, *Editors*, *Anonymous*, 
+which makes it easier to manage them and their permissions.
+All User Groups and Users can be accessed in the Admin panel by selecting Users.
+
+![Users and User Groups](admin_panel_users.png "Users and User Groups")
+
+!!! caution
+
+    Be careful not to delete an existing User account. 
+    If you do this, content created by this User will be broken and the application can face malfunction.

docs/administration/admin_panel/workflow_admin_panel.md

@@ -0,0 +1,12 @@
+---
+description: The workflow functionality passes a Content item version through a series of stages.
+---
+
+# Workflow
+
+The workflow functionality passes a Content item version through a series of stages.
+Each workflow consists of stages and transitions between them.
+
+See [Workflow](workflow.md) for further information.
+
+![Workflow](admin_panel_workflow.png "Workflow")

docs/administration/administration.md

@@ -7,7 +7,7 @@ description: Administer and configure your Ibexa DXP installation.
 Administer and configure your [[= product_name =]] installation.
 
 [[= cards([
-    "administration/admin_panel",
+    "administration/admin_panel/admin_panel",
     "administration/project_organization/project_organization",
     "administration/configuration/configuration",
     "administration/back_office/back_office",