cloning layouts, fields, categories, roles

docs/control-panel/categories.md

@@ -23,7 +23,7 @@ Category groups are _collections_ of categories that can be assigned to channels
 
 **Control Panel Location: `Content > Categories > New/Edit Category`**
 
-Catagories have the following settings:
+Categories have the following settings:
 
 - **Name** -- The name of the new category. The name may include spaces.
 - **URL title** -- The human readable category name used in the URL when using [Category URL Titles in Links](control-panel/settings/content-design.md).
@@ -32,6 +32,13 @@ Catagories have the following settings:
 - **Parent category** -- This drop-down list allows you to create a hierarchical relationship between categories. The list dynamically contains all existing categories for this category group. Selecting a parent category means that the new category will be a "child" of the parent in the hierarchy. The "None" option is available and will make the new category a "top level" category with no parent.
 - **Custom Fields** -- Any [custom category fields](#fields-tab) that exist for this category group will be included in the form.
 
+The categories can be saved by clicking "Save" button or pressing `Ctrl`+`s` (`cmd`+`s`) on keyboard. Upon saving, the category editing page remains open so you can make other changes.
+
+Extra saving options are also available from the dropdown menu under "Save": 
+- "Save & New" - opens a new category form after saving
+- "Save & Close" - redirects to categories list after saving
+- "Clone to New Category" - saves the changes into a new category. The current category is used as a "template" and remains unchanged.
+
 ## Create/Edit Category Groups
 
 **Control Panel Location: `Content > Categories > New/Edit Category Group`**

docs/control-panel/channels.md

@@ -129,6 +129,8 @@ NOTE: **Note:** We recommend using the default base URL variable `{base_url}` de
 
 **Control Panel Location: `Developer > Channels > Layouts`**
 
+![Channel Publish Layouts Link](_images/channel-publish-layouts.png)
+
 The Publish/Edit page can be customized, with the layout saved per member role, per channel.
 
 ### Create/Edit Publish Layouts
@@ -137,6 +139,14 @@ The Publish/Edit page can be customized, with the layout saved per member role,
 
 This section of the control panel is where channel layouts are created or edited.
 
+Editors in a member role will see the Publish / Edit entry page in accordance with the assigned publish layout for that channel.
+
+The publish layouts are capable of organizing fields into tabs, reordering fields, changing their width for organizing into columns, and hiding the fields that should not be visible.
+
+Each layout needs to be assigned to one or several member roles. However, each role can have only one publish layout assigned.
+
+You can have one publish layout for all editor roles, or you can have different layouts for different roles. When only a small adjustment is needed, the publish layout can be duplicated using "Clone to New Layout" option in "Save" dropdown.
+
 ## Channel Set Import
 
 **Control Panel Location: `Developer > Channels > Import`**

docs/control-panel/field-manager/edit-field.md

@@ -0,0 +1,38 @@
+<!--
+    This source file is part of the open source project
+    ExpressionEngine User Guide (https://github.com/ExpressionEngine/ExpressionEngine-User-Guide)
+
+    @link      https://expressionengine.com/
+    @copyright Copyright (c) 2003-2023, Packet Tide, LLC (https://packettide.com)
+    @license   https://expressionengine.com/license Licensed under Apache License, Version 2.0
+-->
+
+# Create/Edit Field
+
+**Control Panel Location: `Developer > Fields > New/Edit Field`**
+
+This section of the control panel allows you to create and edit [Fields](/fieldtypes/overview.md) to be used in channel entries.
+
+A new field can be added by clicking the "New Field" button, or by picking "Clone to New Field" from the existing field's "Save" dropdown. In that case, the original field will serve as "template" and the changes would be applied to new field only.
+
+If you are viewing a certain field group when clicking the "New Field" button, the field will be assigned to that group. The existing fields can be assigned to multiple field groups by editing the Field Group.
+
+Fields have the following settings:
+
+- **Type** -- The type of field. [List of available fieldtypes](fieldtypes/overview.md).
+- **Name** -- The descriptive name for the field which is displayed in the publish form. Unlike the Short Name, the Name (you can think of it as a label) does not need to be unique within the system, so you can use the same name on multiple fields in different field groups.
+- **Short Name** -- This is the internal or "short name" for the field. The field name must be unique within the system, which means that you cannot have two field groups each containing a field with the field name of "body". The short name is typically used as the variable name in your [Channel Entries Tag](channels/entries.md)
+- **Instructions** -- These are instructions for authors on how or what to enter into the field when submitting an entry. The instructions will appear below the Field Label in your publish page.
+- **Require field?** -- If the field is required and the user leaves it blank, upon submission they will receive an error message prompting them to correct it. Required fields are only required when not [conditionally hidden](control-panel/field-manager/conditional-fields.md).
+- **Include in search?** -- This determines whether the contents of this field will be included in searches that are within the entry content.
+- **Hide field?** -- Shows or hides the field on the publish page. When hidden, the field will be collapsed by default.
+- **Enable front-end editing?** -- Enable/disable [frontedit](/advanced-usage/front-end/frontend.md) links for this field.
+- **Make Conditional?** -- Shows or hides the field on the publish page based on [conditional settings](control-panel/field-manager/conditional-fields.md). Fields which are conditionally hidden are not shown at all on the publish page until conditions are met.
+- **Channels** -- Read-only list of [channels](control-panel/channels.md) this field is assigned to. The field can be assigned to channel in several ways:
+    - By editing channel and assigning field directly
+    - By editing channel and assigning field group, which in turn has been edited and assigned this field
+    - When a field is used in [Fluid field](fieldtypes/fluid.md) which is assigned to a channel, the field is also assigned to the channel (though not available outside of Fluid)
+
+- **Field Options** -- Each fieldtype may have additional options. See the [individual field types](fieldtypes/overview.md) for details.
+
+![](_images/cp_fields_edit.png)

docs/control-panel/field-manager/field-manager-settings.md

@@ -21,20 +21,10 @@ This section of the Control Panel is where custom fields are created, edited and
 
 **Control Panel Location: `Developer > Fields > New/Edit Field`**
 
-This section of the control panel allows you to create and edit [Fields](/fieldtypes/overview.md) and Field Groups.
-
-Fields have the following settings:
-
-- **Type** -- The type of field. [List of available fieldtypes](fieldtypes/overview.md).
-- **Name** -- The descriptive name for the field which is displayed in the publish form. Unlike the Field Name, the label does not need to be unique within the system, so you can use the same label on multiple fields in different field groups.
-- **Short Name** -- This is the internal or "short name" for the field. The field name must be unique within the system, which means that you cannot have two field groups each containing a field with the field name of "body". The short name is typically used as the variable name in your [Channel Entries Tag](channels/entries.md)
-- **Instructions** -- These are instructions for authors on how or what to enter into the field when submitting an entry. The instructions will appear below the Field Label in your publish page.
-- **Require field?** -- If the field is required and the user leaves it blank, upon submission they will receive an error message prompting them to correct it. Required fields are only required when not [conditionally hidden](control-panel/field-manager/conditional-fields.md).
-- **Include in search?** -- This determines whether the contents of this field will be included in searches that are within the entry content.
-- **Hide field?** -- Shows or hides the field on the publish page. When hidden, the field will be collapsed by default.
-- **Make Conditional?** -- Shows or hides the field on the publish page based on [conditional settings](control-panel/field-manager/conditional-fields.md). Fields which are conditionally hidden are not shown at all on the publish page until conditions are met.
-- **Enable front-end editing?** -- Enable/disable [frontedit](/advanced-usage/front-end/frontend.md) links for this field.
-- **Field Options** -- Each fieldtype may have additional options. See the [individual field types](fieldtypes/overview.md) for details.
+This section of the control panel allows you to create and edit [Fields](/fieldtypes/overview.md) to be used in channel entries.
+
+Visit the [**Create/Edit Field**](control-panel/field-manager/edit-field.md) page for detailed information.
+
 
 ## Create/Edit Field Group
 

docs/control-panel/member-manager.md

@@ -33,7 +33,20 @@ You can assign multiple roles to a member.
 
 **Control Panel Location: `Members > Member Roles > Create/Edit`**
 
-This sections allows you to set the various permissions and settings for the selected Member Role
+This sections allows you to set the various permissions and settings for the selected Member Role.
+
+ExpressionEngine comes with 5 built-in Roles:
+- Super Admin _(#1)_ - has full control over the site and all system settings. We advise that all members in this role use [Multi-factor authentication](member/mfa.md)
+- Banned _(#2)_ - reserved role for members that are registered, but have been banned from accessing the site
+- Guests _(#3)_ - reserved role for visitors that are not logged in. It is recommended not to assign any actual member accounts to this role.
+- Pending _(#4)_ - members who submitted the registration form, but have not been approved yet (by admin or by verifying their email address, depending on your membership preferences)
+- Members _(#5)_ - regular site members. This is the default role that everyone gets registered into, unless specified differently
+
+These roles should never be deleted.
+
+If you need a custom set of permissions for the role, we suggest creating a new role for each case. You can do that by clicking "New Role" button, or you can create a new role based on an exsting one by picking "Clone to New Role" from the role's "Save" dropdown.
+
+Edit the role by clicking its name in the list.
 
 ## Custom Member Fields
 

docs/toc_sections/_the_fundamentals_toc.yml

@@ -39,6 +39,8 @@
       items:
         - name: Settings
           href: control-panel/field-manager/field-manager-settings.md
+        - name: Create/Edit Field
+          href: control-panel/field-manager/edit-field.md
         - name: Conditional Fields
           href: control-panel/field-manager/conditional-fields.md
     - name: Member Manager