You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 15/umbraco-ui-builder/getting-started/user-interface.md
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,54 +8,54 @@ Before diving into Umbraco UI Builder, it’s important to understand some of th
8
8
9
9
## Section
10
10
11
-
12
-
13
11
A section in Umbraco is a distinct area within the backoffice where related content and functionality are grouped. For example, the Content section is where content management happens, while the Media section handles media files.
14
12
15
-
## Tree
13
+
16
14
17
-
15
+
## Tree
18
16
19
17
The tree represents the hierarchical structure of items within a section. It organizes content, settings, and data, for quick navigation and locating items. For example, the content tree shows the pages of a website in a nested format.
20
18
19
+
20
+
21
21
## Dashboard
22
22
23
-
23
+
Each section in the Umbraco backoffice typically starts with a dashboard. This is an introductory screen for the section. It often includes useful links or shortcuts, providing an overview or quick access to the most commonly used features.
24
24
25
-
Each section in the Umbraco backoffice typically starts with a dashboard. This is the introductory screen for the section and often includes useful links or shortcuts, providing an overview or quick access to the most commonly used features.
25
+
26
26
27
27
## Collection
28
28
29
-
30
-
31
29
The collection displays a list of items in a tree node. It provides an overview of content or data in a table format, with sortable columns and the option to filter or search through the items. This view is used when you need to work with multiple items at once.
32
30
33
-
## Editor
31
+
34
32
35
-
33
+
## Editor
36
34
37
35
The editor is where the main content editing occurs. It is structured using tabs, fieldsets, and fields. Tabs organize different sections of content, and fieldsets group related fields together. Each field represents a specific piece of data, such as a text box or an image upload.
38
36
39
-
## Workspace Views
37
+
40
38
41
-
39
+
## Workspace Views
42
40
43
41
Workspace Views are additional functionality that can be added to an editor. They provide extra features based on the content of the item being edited. For instance, a media content app might allow you to resize or crop an image directly from the editor.
44
42
45
-
## Tabs
43
+
46
44
47
-
45
+
## Tabs
48
46
49
47
Tabs are used to organize content within the editor, allowing users to switch between different sections of a content item. For example, one tab might contain the general settings, while another contains media or advanced options.
50
48
51
-
## Menu Item
49
+
52
50
53
-
51
+
## Menu Item
54
52
55
53
A menu item represents an action within the context of a tree node or a list item. It is a clickable item that triggers specific tasks, such as deleting or editing an item.
56
54
57
-
## Bulk Action
55
+
58
56
59
-
57
+
## Bulk Action
60
58
61
59
Bulk actions allow you to perform an operation on multiple items in the list view at once. For example, you might use a bulk action to delete multiple content items or update their status in a single step.
0 commit comments