Skip to content

Commit 2db4a7e

Browse files
committed
Fix soft-wrap and text formatting across "Section" documentation.
1 parent 155cc38 commit 2db4a7e

File tree

3 files changed

+15
-34
lines changed

3 files changed

+15
-34
lines changed

16/umbraco-cms/customizing/extending-overview/extension-types/sections/section-sidebar.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,7 @@ Section Sidebar extensions can be composed of **one or more** section sidebar ap
2020

2121
### Custom Sidebar App Example
2222

23-
Section Sidebar extension authors can place any custom web component into the sidebar. Extension authors will need to
24-
supply the `element` property with the path of their custom web component. Specify the full path, starting from the
25-
Umbraco project root.
23+
Section Sidebar extension authors can place any custom web component into the sidebar. Extension authors will need to supply the `element` property with the path of their custom web component. Specify the full path, starting from the Umbraco project root.
2624

2725
Sidebar Section extension authors may specify where the Section Sidebar app appears using
2826
[extension conditions](../condition.md).
@@ -94,9 +92,7 @@ For more information, see the documentation for the [menus](../menu.md) extensio
9492

9593
#### Coordinating subviews with menu items
9694

97-
Menu sidebar apps can coordinate navigation between subviews in the section extension by referencing
98-
[workspace extensions](../workspaces/workspace.md). Modify the menu item extension to include the `meta:entityType`
99-
property, and assign it the same value as a workspace view extensions' own `meta:entityType` property.
95+
Menu sidebar apps can coordinate navigation between subviews in the section extension by referencing [workspace extensions](../workspaces/workspace.md). Modify the menu item extension to include the `meta:entityType` property, and assign it the same value as a workspace view extensions' own `meta:entityType` property.
10096

10197
{% code title="umbraco-package.json" %}
10298
```json

16/umbraco-cms/customizing/extending-overview/extension-types/sections/section-view.md

Lines changed: 6 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,7 @@ Section View extensions are containers for custom Umbraco packages or other back
1111

1212
## Creating a custom Section View
1313

14-
Custom Section View extensions are straightforward to create. Extension authors register the Section View extension and
15-
subsequently implement the content or interface they desire to display within the Section View.
14+
Custom Section View extensions are straightforward to create. Extension authors register the Section View extension and subsequently implement the content or interface they desire to display within the Section View.
1615

1716
### Registering Section View extensions
1817

@@ -51,8 +50,7 @@ Extensions authors can register the Section View extension using a JSON declarat
5150
```
5251
{% endcode %}
5352

54-
Tip: Use the absolute path, starting from the root of your Umbraco project, in the `element` property for
55-
JSON declarations. TypeScript declarations are capable of employing relative paths.
53+
Tip: Use the absolute path, starting from the root of your Umbraco project, in the `element` property for JSON declarations. TypeScript declarations are capable of employing relative paths.
5654

5755
{% endtab %}
5856

@@ -133,13 +131,11 @@ declare global {
133131

134132
## Adding Section Views to your own package
135133

136-
When developing a Section View extension for their own package, an extension author must create a Section extension to
137-
host the Section View extension.
134+
When developing a Section View extension for their own package, an extension author must create a Section extension to host the Section View extension.
138135

139136
Guidelines on creating Section extensions can be found at [this link](./section.md).
140137

141-
To link a Section View with a Section, set the `match` property in the condition to the same value as the Section's `alias`. In the
142-
provided example, this value is `NetworkServices.Section`.
138+
To link a Section View with a Section, set the `match` property in the condition to the same value as the Section's `alias`. In the provided example, this value is `NetworkServices.Section`.
143139

144140
{% code title="umbraco-package.json" %}
145141
```json
@@ -178,11 +174,9 @@ provided example, this value is `NetworkServices.Section`.
178174

179175
The Umbraco backoffice architecture places a strong emphasis on composing. Authors can extend existing sections, including core ones like Content, Media, and Settings, with Section View extensions.
180176

181-
After an author has completed their Section View extension, they can control the placement of the extension using
182-
conditions in the manifest definition.
177+
After an author has completed their Section View extension, they can control the placement of the extension using conditions in the manifest definition.
183178

184-
The `match` property demonstrates how an extension author can incorporate a custom Section View within the Content
185-
section.
179+
The `match` property demonstrates how an extension author can incorporate a custom Section View within the Content section.
186180

187181
{% code title="umbraco-package.json" %}
188182
```json

16/umbraco-cms/customizing/extending-overview/extension-types/sections/section.md

Lines changed: 7 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,9 @@ description: Introducing Section extensions, a home for custom content and funct
44

55
# Section
66

7-
Umbraco extension authors can place their extension in the top-level navigation of the backoffice using Sections. The
8-
extension will be placed among the default options such as Content, Media, Settings, etc.
7+
Umbraco extension authors can place their extension in the top-level navigation of the backoffice using Sections. The extension will be placed among the default options such as Content, Media, Settings, etc.
98

10-
Within the section, authors can add menus, section views, workspace views, or any other content or interface they
11-
desire.
9+
Within the section, authors can add menus, section views, workspace views, or any other content or interface they desire.
1210

1311
<figure><img src="../../../../.gitbook/assets/section.svg" alt=""><figcaption><p>Section</p></figcaption></figure>
1412

@@ -34,14 +32,11 @@ Sections can be created by adding a definition in the extension's manifest file.
3432

3533
### **Group permissions**
3634

37-
To enable custom sections for backoffice users, site administrators must first assign permissions to those users. This
38-
involves configuring the permission for a user group and assigning users to that group.
35+
To enable custom sections for backoffice users, site administrators must first assign permissions to those users. This involves configuring the permission for a user group and assigning users to that group.
3936

40-
To grant access to the custom section, open the Umbraco backoffice, navigate to the **Users** section, and select the
41-
**User groups** menu item. Site administrators can create a new user group or modify an existing one.
37+
To grant access to the custom section, open the Umbraco backoffice, navigate to the **Users** section, and select the **User groups** menu item. Site administrators can create a new user group or modify an existing one.
4238

43-
Once the user group is open, click the **Choose** button under the Sections section. Select the custom section from the
44-
slide-out modal to enable access.
39+
Once the user group is open, click the **Choose** button under the Sections section. Select the custom section from the slide-out modal to enable access.
4540

4641
<figure><img src="../../../../.gitbook/assets/sections-assigning.png" alt=""><figcaption><p>Enabling new Sections</p></figcaption></figure>
4742

@@ -51,15 +46,11 @@ After assigning permission, users may need to reload the backoffice for the chan
5146

5247
### **Entry points**
5348

54-
When creating a new section, create an [Entry Point](../backoffice-entry-point.md) extension in the
55-
[Umbraco Package Manifest](../../../umbraco-package.md) to complement it. Entry Point extensions add initialization and
56-
teardown lifecycle events that may be helpful in coordinating behavior inside the section.
49+
When creating a new section, create an [Entry Point](../backoffice-entry-point.md) extension in the [Umbraco Package Manifest](../../../umbraco-package.md) to complement it. Entry Point extensions add initialization and teardown lifecycle events that may be helpful in coordinating behavior inside the section.
5750

5851
## **Extend with Sidebar, Dashboards, and more**
5952

60-
Sections serve as blank canvases within the Umbraco backoffice. Extension authors can integrate other Umbraco extensions
61-
into sections, including [custom dashboards](../../../../tutorials/creating-a-custom-dashboard/),
62-
[sidebars](section-sidebar.md), and [section views](section-view.md).
53+
Sections serve as blank canvases within the Umbraco backoffice. Extension authors can integrate other Umbraco extensions into sections, including [custom dashboards](../../../../tutorials/creating-a-custom-dashboard/), [sidebars](section-sidebar.md), and [section views](section-view.md).
6354

6455
Section authors can also skip Umbraco backoffice components and build a fully custom view by creating an empty element.
6556

0 commit comments

Comments
 (0)