Skip to content

Commit 684c7af

Browse files
Sofie Toft Kristensengitbook-bot
authored andcommitted
GITBOOK-65: No subject
1 parent e5a76ad commit 684c7af

File tree

36 files changed

+223
-296
lines changed

36 files changed

+223
-296
lines changed
30.3 KB
Loading

15/umbraco-cms/README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,5 +46,6 @@ The documentation for Umbraco CMS provides information for experienced Umbraco a
4646

4747
***
4848

49-
{% include ".gitbook/includes/umbraco-fundamentals-training-course.md" %}
49+
### Umbraco Training
5050

51+
{% include ".gitbook/includes/umbraco-fundamentals-training-course.md" %}

15/umbraco-cms/customizing/extending-overview/custom-extension-type.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
1-
# Custom Extension Types
1+
# Custom Extension types
22

3-
The extension registry is an open system, which can hold any Extension Manifest Type. This article describes how you can declare your types.
4-
Types can be declared for re-useability/maintainability or to open up for other package extensions.
3+
The extension registry is an open system, which can hold any Extension Manifest Type. This article describes how you can declare your types. Types can be declared for re-useability/maintainability or to open up for other package extensions.
54

65
## Manifest Type Declaration
76

15/umbraco-cms/customizing/overview.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,5 +28,6 @@ In this section, you will find all the resources you need to build an intuitive
2828

2929
***
3030

31-
{% include "../.gitbook/includes/umbraco-extending-the-backoffice-training-course.md" %}
31+
### Umbraco Training
3232

33+
{% include "../.gitbook/includes/umbraco-extending-the-backoffice-training-course.md" %}

15/umbraco-cms/customizing/property-editors/property-value-converters.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,16 @@
11
---
2-
description: "A guide to creating a custom property value converter in Umbraco"
2+
description: A guide to creating a custom property value converter in Umbraco
33
---
44

5-
65
# Property Value Converters
76

87
A Property Value Converter converts a property editor's database-stored value to another type. The converted value can be accessed from MVC Razor or any other Published Content API.
98

109
Published property values have four "Values":
1110

12-
- **Source** - The raw data stored in the database, this is generally a `String`
13-
- **Intermediate** - An object of a type that is appropriate to the property, for example a nodeId should be an `Int` or a collection of nodeIds would be an integer array, `Int[]`
14-
- **Object** - The object to be used when accessing the property using a Published Content API, for example UmbracoHelper's `GetPropertyValue<T>` method
11+
* **Source** - The raw data stored in the database, this is generally a `String`
12+
* **Intermediate** - An object of a type that is appropriate to the property, for example a nodeId should be an `Int` or a collection of nodeIds would be an integer array, `Int[]`
13+
* **Object** - The object to be used when accessing the property using a Published Content API, for example UmbracoHelper's `GetPropertyValue<T>` method
1514

1615
## Registering PropertyValueConverters
1716

@@ -59,8 +58,7 @@ public class ContentPickerValueConverter : IPropertyValueConverter
5958

6059
This method is called for each PublishedPropertyType (Document Type Property) at application startup. By returning `True` your value converter will be registered for that property type and your conversion methods will be executed whenever that value is requested.
6160

62-
Example: Checking if the IPublishedPropertyType EditorAlias property is equal to the alias of the core content editor.
63-
This check is a string comparison but we recommend creating a constant for it to avoid spelling errors:
61+
Example: Checking if the IPublishedPropertyType EditorAlias property is equal to the alias of the core content editor. This check is a string comparison but we recommend creating a constant for it to avoid spelling errors:
6462

6563
```csharp
6664
public bool IsConverter(IPublishedPropertyType propertyType)
@@ -100,8 +98,8 @@ Do not use this cache level unless you know exactly what you're doing. We recomm
10098

10199
The property value will be cached until its _element_ is modified. The element is what holds (or owns) the property. For example:
102100

103-
- For properties used at the page level, the element is the entire page.
104-
- For properties contained within Block List items, the element is the individual Block List item.
101+
* For properties used at the page level, the element is the entire page.
102+
* For properties contained within Block List items, the element is the individual Block List item.
105103

106104
This is the most commonly used cache level and should be your default, unless you have specific reasons to do otherwise.
107105

15/umbraco-cms/extending/health-check/guides/fixedapplicationurl.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,6 @@
1-
# Health check: Fixed Application URL
2-
3-
_Check to make sure a fixed application URL is specified. This URL is for example used when sending emails from backoffice.
4-
If this is not specified in configuration, Umbraco gets the application URL from last host used to request the application_
1+
# Fixed Application Url
52

3+
_Check to make sure a fixed application URL is specified. This URL is for example used when sending emails from backoffice. If this is not specified in configuration, Umbraco gets the application URL from last host used to request the application_
64

75
## How to fix this health check
86

@@ -39,4 +37,7 @@ One example that can be used in production
3937
}
4038
}
4139
```
42-
{% hint style="info" %} If the site is hosted on Umbraco Cloud, changing the above configuration will have no effect. The site will always use the URL set in the`umbraco-cloud.json` file, which can not be changed. {% endhint %}
40+
41+
{% hint style="info" %}
42+
If the site is hosted on Umbraco Cloud, changing the above configuration will have no effect. The site will always use the URL set in the\`umbraco-cloud.json\` file, which can not be changed.
43+
{% endhint %}

15/umbraco-cms/fundamentals/data/creating-media/README.md

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -91,8 +91,7 @@ To edit properties on a single media item, click the name of the item, which you
9191

9292
![Edit media item](../../../../../10/umbraco-cms/fundamentals/data/creating-media/images/hover-over.png)
9393

94-
From the top-right corner of the Media section, you can toggle between the list and grid view. There is also an option to search for the items in the Media section.
95-
![Media Section - List view](images/switch-view-v14.png)
94+
From the top-right corner of the Media section, you can toggle between the list and grid view. There is also an option to search for the items in the Media section. ![Media Section - List view](images/switch-view-v14.png)
9695

9796
## Using media items in the Content section
9897

@@ -151,10 +150,7 @@ Follow the steps outlined below to add the properties to the Media Type:
151150
6. Rename the editor _Employee Image Cropper_.
152151
7. Add two new crops called _Thumbnail_ (200px x 350px) and _wideThumbnail_ (350px x 200px).
153152

154-
![Defining crops](images/new-data-type-v14.png)
155-
8. Click **Save**.
156-
9. Click **Add**.
157-
10. Name the remaining four properties _Width_, _Height_, _Size_, and _Type_, and give them the aliases as mentioned above. They should all use the **Label** editor.
153+
![Defining crops](images/new-data-type-v14.png) 8. Click **Save**. 9. Click **Add**. 10. Name the remaining four properties _Width_, _Height_, _Size_, and _Type_, and give them the aliases as mentioned above. They should all use the **Label** editor.
158154

159155
As mentioned before these properties will automatically be populated once an image has been uploaded.
160156

@@ -171,8 +167,7 @@ Next up, we will create a folder to hold the employee images. We could use the e
171167
5. Click **Configure as a Collection** under **Presentation.**
172168
6. Choose **List view - Media.**
173169

174-
![Configure Collection](images/configure-collection-v14.png)
175-
7. Click **Save**.
170+
![Configure Collection](images/configure-collection-v14.png) 7. Click **Save**.
176171

177172
The new folder is created under the Media Types folder. We also need to only allow the Employee Image Media Type in our new folder. Both of these configurations can be set on the **Structure** tab.
178173

@@ -188,8 +183,7 @@ The new folder is created under the Media Types folder. We also need to only all
188183

189184
1. Go to the **Media** section.
190185
2. Select **...** next to Media.
191-
3. Click **Create** > **Employee Images** folder.
192-
![Employee Images](images/employee-images-folder.png)
186+
3. Click **Create** > **Employee Images** folder. ![Employee Images](images/employee-images-folder.png)
193187
4. Name it _Employee Images_.
194188
5. Click **Save**.
195189

15/umbraco-cms/fundamentals/data/users/README.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -71,6 +71,16 @@ The available user permissions are defined under **Default Permissions** in the
7171

7272
![Default permissions](../../../../../14/umbraco-cms/fundamentals/data/images/default-permissions.png)
7373

74+
## Granular Permissions
75+
76+
As an addition to the Default Permissions, it is also possible to add more granular permissions on a User Group level.
77+
78+
<figure><img src="../../../.gitbook/assets/Screenshot 2025-06-04 at 12.45.05.png" alt=""><figcaption></figcaption></figure>
79+
80+
With the **Documents** permission, you can define granular permissions on specific documents. This is useful when a User Group should only have limited access to a certain page on the website. Clicking **Add** opens a dialog where you can choose between documents from the Content section.
81+
82+
With the **Document Property Values** permission, you can define both read and write permissions for individual properties on a Document Type. This is useful if a User Group should have limited access to edit the content on a specific type of document. Clicking **Add** opens a dialog where you select a Document Type, choose a Property, and, finally, set the read and write permissions.
83+
7484
### Setting User Permissions
7585

7686
When a new user is created, you can set specific permissions for that user on different domains and subdomains. You can also set permissions on different User Groups, even for the default types.

15/umbraco-cms/fundamentals/design/stylesheets-javascript.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
---
2-
description: >-
3-
Information on working with stylesheets and JavaScript in Umbraco, including
4-
bundling & minification.
2+
description: Information on working with stylesheets and JavaScript in Umbraco.
53
---
64

75
# Stylesheets And JavaScript

15/umbraco-cms/fundamentals/setup/install/install-umbraco-with-templates.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,7 @@ Video Tutorial
1111
## Install the template
1212

1313
1. Install the latest [.NET SDK](https://dotnet.microsoft.com/download).
14-
2. Run `dotnet new install Umbraco.Templates` to install the project templates.
15-
_The solution is packaged up into the NuGet package [Umbraco.Templates](https://www.nuget.org/packages/Umbraco.Templates) and can be installed into the dotnet CLI_.
14+
2. Run `dotnet new install Umbraco.Templates` to install the project templates. _The solution is packaged up into the NuGet package_ [_Umbraco.Templates_](https://www.nuget.org/packages/Umbraco.Templates) _and can be installed into the dotnet CLI_.
1615

1716
```cli
1817
Templates Short Name Language Tags

0 commit comments

Comments
 (0)