diff --git a/15/umbraco-cms/customizing/property-editors/README.md b/15/umbraco-cms/customizing/property-editors/README.md index b38eab37472..03463d2d372 100644 --- a/15/umbraco-cms/customizing/property-editors/README.md +++ b/15/umbraco-cms/customizing/property-editors/README.md @@ -30,7 +30,7 @@ Convert the stored property data value to a useful object returned by the Publis Use Property Actions to add additional functionaility to your custom property editors. -## [Tracking References](broken-reference) +## [Tracking References](tracking.md) Learn how to extend Property editors to track entity references inside the property editor. diff --git a/15/umbraco-cms/customizing/property-editors/integrate-validation.md b/15/umbraco-cms/customizing/property-editors/integrate-validation.md index ce369abcda9..2b960b020cb 100644 --- a/15/umbraco-cms/customizing/property-editors/integrate-validation.md +++ b/15/umbraco-cms/customizing/property-editors/integrate-validation.md @@ -85,4 +85,4 @@ render() { ## Server Validation and more -This documentation is not available at the moment. For the moment you can find more information in the [Backoffice repository](https://github.com/umbraco/Umbraco.CMS.Backoffice/tree/main/src/packages/core/validation). +This documentation is not available at the moment. For the moment you can find more information in the [Backoffice repository](https://github.com/umbraco/Umbraco-CMS/tree/ced3db8542d390bb12082ca63ef71b790da220c5/src/Umbraco.Web.UI.Client/src/packages/core/validation). diff --git a/15/umbraco-cms/customizing/umbraco-package.md b/15/umbraco-cms/customizing/umbraco-package.md index e655f30ebb0..26c68621c35 100644 --- a/15/umbraco-cms/customizing/umbraco-package.md +++ b/15/umbraco-cms/customizing/umbraco-package.md @@ -162,7 +162,7 @@ These are the current types of UI Extensions: | searchProvider | A search provider is a provider that can be used to provide search results for the search bar in the Backoffice. | | searchResultItem | A search result item is a component that can be added to the search results. | | theme | A theme is a set of styles that can be added to the Backoffice. The user can select their preferred theme in the current user modal. | -| tinyMcePlugin | A TinyMCE plugin is a plugin that can be added to the TinyMCE editor. Read more about [TinyMCE Plugins](../fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor/rte-plugins.md). | +| tinyMcePlugin | A TinyMCE plugin is a plugin that can be added to the TinyMCE editor. Read more about [TinyMCE Plugins](../fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor-tinymce/plugins.md). | | treeItem | A tree item that can be added to the tree. | | tree | A tree that can be added to a section. | | ufmComponent | This type of component is a formatter that can be added to the [Umbraco Flavoured Markdown](../reference/umbraco-flavored-markdown.md), which is used in property descriptions and advanced labels. | @@ -205,7 +205,7 @@ These are the current types of UI Extensions: | workspaceFooterApp | A workspace footer app is a component that can be added to the workspace footer. | | workspaceView | A workspace view is a view that can be added to a workspace. It is displayed in the main content area of the workspace. More than one view can be added to a workspace, and the user can switch between them. In that case, the views are displayed as tabs. Read more about [Workspace Views](extending-overview/extension-types/workspaces/workspace-views.md). | -Read more about [Extension Types](broken-reference/) in the Backoffice to get a better understanding of the different types of extensions. +Read more about [Extension Types](extending-overview/extension-types/README.md) in the Backoffice to get a better understanding of the different types of extensions. ## Package Manifest IntelliSense diff --git a/15/umbraco-cms/extending/backoffice-search.md b/15/umbraco-cms/extending/backoffice-search.md index c6eb6646bfe..ff396b6f9e5 100644 --- a/15/umbraco-cms/extending/backoffice-search.md +++ b/15/umbraco-cms/extending/backoffice-search.md @@ -100,4 +100,4 @@ You cannot use this to search on integer types in the index, as an example `pare ## More advanced extensions -For further extensibility of the Umbraco Backoffice search implementation check [ISearchableTree](../customizing/section-trees/searchable-trees.md) +For further extensibility of the Umbraco Backoffice search implementation check [ISearchableTree](../customizing/searchable-trees.md) diff --git a/15/umbraco-cms/extending/language-files/net-localization.md b/15/umbraco-cms/extending/language-files/net-localization.md index 5cdd05aab90..d84a86072ac 100644 --- a/15/umbraco-cms/extending/language-files/net-localization.md +++ b/15/umbraco-cms/extending/language-files/net-localization.md @@ -4,13 +4,11 @@ description: NET Umbraco Core Localization files. # .NET Localization -## .NET Localization - In this article, you will find information about the Core Localization files. You can also find information about where to find and use them, and how to keep them up-to-date. -### Use cases +## Use cases -.NET localization has limited use cases in Umbraco, as all backoffice localization is performed with [UI Localization](../../customizing/ui-localization.md). +.NET localization has limited use cases in Umbraco, as all backoffice localization is performed with [UI Localization](../../customizing/foundation/localization.md). In other words, .NET localization is only applied server-side with no accompanying UI - for example: @@ -18,7 +16,7 @@ In other words, .NET localization is only applied server-side with no accompanyi * User login error handling. * Health checks. -### Where to find the core localization files +## Where to find the core localization files The core Umbraco localization files are found at the following location within the [Umbraco source](https://github.com/umbraco/Umbraco-CMS/tree/contrib/src/Umbraco.Core/EmbeddedResources/Lang): @@ -28,7 +26,7 @@ Umbraco-CMS/src/Umbraco.Core/EmbeddedResources/Lang/ These localization files are shipped with Umbraco and should not be modified. -#### User localization files +### User localization files If you want to override Umbraco Core .NET localization, create new files in the following location and format: @@ -48,7 +46,7 @@ In order for these files to deploy when you do a `dotnet publish`, you need to a ``` -### Using the localizations +## Using the localizations `ILocalizedTextService` is used to localize strings, and is available through dependency injection. You can use the `Localize()` method available in the namespace `Umbraco.Extensions` to localize the string by `area` and `key`: @@ -69,7 +67,7 @@ public class LocalizationSample } ``` -### Help keep the language files up to date +## Help keep the language files up to date As Umbraco is a continually evolving product it is inevitable that new text is added regularly to the English language version of these files. This may mean that some of the above languages are no longer up to date. diff --git a/15/umbraco-cms/fundamentals/backoffice/login.md b/15/umbraco-cms/fundamentals/backoffice/login.md index 8632878add7..287dd04a98a 100644 --- a/15/umbraco-cms/fundamentals/backoffice/login.md +++ b/15/umbraco-cms/fundamentals/backoffice/login.md @@ -68,7 +68,7 @@ export default { This will override the default greetings with the ones you provide. The login screen will now display "It is Sunday" instead of "Welcome" for example. {% hint style="info" %} -The login screen has its own set of localization files independent of the rest of the Backoffice. You can read more about Backoffice localization in the [UI Localization](../../customizing/ui-localization.md) article. +The login screen has its own set of localization files independent of the rest of the Backoffice. You can read more about Backoffice localization in the [UI Localization](../../customizing/foundation/localization.md) article. {% endhint %} You can customize other text on the login screen as well. First, grab the default values and keys from the [en.ts](https://github.com/umbraco/Umbraco-CMS/blob/contrib/src/Umbraco.Web.UI.Login/src/localization/lang/en.ts) in the Umbraco CMS GitHub repository. Thereafter copy the ones you want to translate into `~/App_Plugins/Login/umbraco-package.json` file. diff --git a/15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/collection.md b/15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/collection.md index af89d2b0a96..89b88a394a6 100644 --- a/15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/collection.md +++ b/15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/collection.md @@ -92,7 +92,7 @@ This example shows how to use a generic field from a child item and display its ![Collection content email label template](images/collection-label-template.png) -You can use the [Umbraco Flavored Markdown](../../../../umbraco-flavored-markdown.md) syntax to display the label value. Here, the `{=value}` placeholder retrieves the value of the *Email* property and displays it in the collection, as shown in the image below: +You can use the [Umbraco Flavored Markdown](../../../../reference/umbraco-flavored-markdown.md) syntax to display the label value. Here, the `{=value}` placeholder retrieves the value of the *Email* property and displays it in the collection, as shown in the image below: ![Collection content email value displayed](images/collections-display-email.png) diff --git a/15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor-tinymce/plugins.md b/15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor-tinymce/plugins.md index 6cdcc287cc9..fa585b480a3 100644 --- a/15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor-tinymce/plugins.md +++ b/15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor-tinymce/plugins.md @@ -21,7 +21,7 @@ TinyMCE also has a number of [premium plugins](https://www.tiny.cloud/docs/tinym To enable plugins in the rich text editor, you need to add an extension type called `tinyMcePlugin` in a manifest file. The manifest file is a JSON file that describes the plugin and how it should be loaded. You can add a plugin such as the open source [Word Count Plugin](https://www.tiny.cloud/docs/tinymce/6/wordcount/) to the rich text editor. You can also define your own custom plugin to extend the functionality of the editor. This way you can add custom buttons, dialogs, or other features to the editor. {% hint style="info" %} -The manifest file should be placed in a folder in `App_Plugins/{YourPackageName}`, with the name `umbraco-package.json`. Learn how to use the [package manifests](../../../../../extending/property-editors/package-manifest.md). +The manifest file should be placed in a folder in `App_Plugins/{YourPackageName}`, with the name `umbraco-package.json`. {% endhint %} {% code title="App_Plugins/YourPackageName/umbraco-package.json" lineNumbers="true" %} diff --git a/15/umbraco-cms/fundamentals/data/dictionary-items.md b/15/umbraco-cms/fundamentals/data/dictionary-items.md index 0a71eb0c1f0..a0098c749eb 100644 --- a/15/umbraco-cms/fundamentals/data/dictionary-items.md +++ b/15/umbraco-cms/fundamentals/data/dictionary-items.md @@ -51,7 +51,7 @@ To edit a dictionary item, follow these steps: {% hint style="info" %} It will only be possible to edit the language(s) that the given user has access to. The value of the remaining languages will be _read-only_. -Which language a user has access to is determined by the "Language permissions" set on the User Group. Learn more about this feature in the [Users](users.md#creating-a-user-group) article. +Which language a user has access to is determined by the "Language permissions" set on the User Group. Learn more about this feature in the [Users](users/README.md#creating-a-user-group) article. {% endhint %} ## Fetching Dictionary Values in the Template @@ -62,7 +62,7 @@ To fetch dictionary values in the template, replace the text with the following @Umbraco.GetDictionaryValue("Welcome") ``` -![Rendering dictionary item](../../../../10/umbraco-cms/fundamentals/data/images/rendering-dictionary-item.png) +![Rendering dictionary item](images/rendering-dictionary-item.png) Alternatively, you can specify an `altText` which will be returned if the dictionary value is empty. @@ -70,7 +70,7 @@ Alternatively, you can specify an `altText` which will be returned if the dictio @Umbraco.GetDictionaryValueOrDefault("Welcome", "Another amazing day in Umbraco") ``` -![Rendering dictionary item](../../../../10/umbraco-cms/fundamentals/data/images/rendering-altvalue-dictionary-item.png) +![Rendering dictionary item](images/rendering-altvalue-dictionary-item.png) ## Importing and exporting Dictionary Items @@ -87,7 +87,7 @@ In some cases, you might want to use the same Dictionary Items on multiple Umbra This will download a `.udt` file which you can use to import the Dictionary items on another Umbraco website. -![Options menu with the Export feature](../../../../10/umbraco-cms/fundamentals/data/images/export.png) +![Options menu with the Export feature](images/export.png) ### Importing Dictionary Items @@ -103,7 +103,7 @@ This will download a `.udt` file which you can use to import the Dictionary item The Dictionary Items have now been added to your website. -![Review the Dictionary Items for import before confirming](../../../../10/umbraco-cms/fundamentals/data/images/import.png) +![Review the Dictionary Items for import before confirming](images/import.png) ## Using Dictionary Item in a Multilingual website diff --git a/15/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps.md b/15/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps.md index 83708d80af7..6bc861c805c 100644 --- a/15/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps.md +++ b/15/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps.md @@ -8,7 +8,7 @@ They have been called a few names in the past, many people still know Azure Web > App Service is a fully Managed Platform for professional developers that brings a rich set of capabilities to web, mobile and integration scenarios. Quickly create and deploy mission critical web Apps that scale with your business by using Azure App Service. -[You can read more about them here](https://azure.microsoft.com/en-us/documentation/articles/app-service-web-overview/) +[You can read more about them here](https://azure.microsoft.com/en-us/products/app-service/web) Umbraco will run on Azure Web Apps but there are some configuration options and specific Azure Web Apps environment limitations to be aware of. diff --git a/15/umbraco-cms/reference/cache/cache-seeding.md b/15/umbraco-cms/reference/cache/cache-seeding.md index c09cd4b5319..e9b5d6af900 100644 --- a/15/umbraco-cms/reference/cache/cache-seeding.md +++ b/15/umbraco-cms/reference/cache/cache-seeding.md @@ -39,4 +39,4 @@ The returned keys of all the seed key providers are unioned into a single set. T As mentioned above the provided keys are cached. Only the keys returned at startup will be considered seeded until the server restarts and the provider is rerun. -For a specific example of implementing a custom seed key provider, see [Creating a Custom Seed Key Provider](../extending/creating-custom-seed-key-provider.md). +For a specific example of implementing a custom seed key provider, see [Creating a Custom Seed Key Provider](../../extending/creating-custom-seed-key-provider.md). diff --git a/15/umbraco-cms/reference/content-delivery-api/custom-property-editors-support.md b/15/umbraco-cms/reference/content-delivery-api/custom-property-editors-support.md index 30f520625a6..789bfaf844f 100644 --- a/15/umbraco-cms/reference/content-delivery-api/custom-property-editors-support.md +++ b/15/umbraco-cms/reference/content-delivery-api/custom-property-editors-support.md @@ -8,13 +8,13 @@ description: >- Out of the box, the Delivery API supports custom property editors, ensuring they are rendered alongside the built-in ones in Umbraco. However, if the output generated by your property editor isn't optimal for a headless context, you have the ability to customize the API response. This customization won't impact the Razor rendering, allowing you to tailor the Content Delivery API response according to your specific requirements. -In this article, we'll look into how you can work with the `IDeliveryApiPropertyValueConverter` interface and implement custom [property expansion](./#property-expansion) for your custom property editors. +In this article, we'll look into how you can work with the `IDeliveryApiPropertyValueConverter` interface and implement custom [property expansion](./property-expansion-and-limiting.md) for your custom property editors. ## Prerequisite The examples in this article revolve around the fictional `My.Custom.Picker` property editor. This property editor stores the key of a single content item and is backed by a property value converter. -We will not dive into the details of creating a custom property editor for Umbraco in this article. If you need guidance on that, please refer to the [Creating a Property Editor](https://docs.umbraco.com/umbraco-cms/tutorials/creating-a-property-editor) and [Property Value Converters](https://docs.umbraco.com/umbraco-cms/extending/property-editors/property-value-converters) articles. +We will not dive into the details of creating a custom property editor for Umbraco in this article. If you need guidance on that, please refer to the [Creating a Property Editor](../../tutorials/creating-a-property-editor/README.md) and [Property Value Converters](../../customizing/property-editors/property-value-converters.md) articles. ## Implementation @@ -24,7 +24,7 @@ The code example below showcases the implementation of this interface in the pro Towards the end of the example, you will find the response models that we will be using. -The `IsConverter()` and `GetPropertyValueType()` methods are inherited from the `PropertyValueConverterBase` class, which is covered in the [Property Value Converters](https://docs.umbraco.com/umbraco-cms/extending/property-editors/property-value-converters) article. +The `IsConverter()` and `GetPropertyValueType()` methods are inherited from the `PropertyValueConverterBase` class, which is covered in the [Property Value Converters](../../customizing/property-editors/property-value-converters.md) article. {% include "../../.gitbook/includes/obsolete-warning-snapshot.md" %} @@ -121,7 +121,7 @@ public class DeliveryApiItemDetails The Implementation of the `IDeliveryApiPropertyValueConverter` interface can be found in the following methods: * `GetDeliveryApiPropertyCacheLevel()`: This method specifies the cache level used for our property representation in the Delivery API response. -* `GetDeliveryApiPropertyCacheLevelForExpansion()`: This method specifies the cache level used for our property representation in the Delivery API response when [property expansion](./property-expansion-and-limiting) is applied. +* `GetDeliveryApiPropertyCacheLevelForExpansion()`: This method specifies the cache level used for our property representation in the Delivery API response when [property expansion](./property-expansion-and-limiting.md) is applied. * `GetDeliveryApiPropertyValueType()`: This method defines the value type of the custom property output for the Delivery API response. * `ConvertIntermediateToDeliveryApiObject()`: This method converts the value from the property editor to the desired custom object in a headless context. diff --git a/15/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md b/15/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md index 7d927644d0a..c19cdea5343 100644 --- a/15/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md +++ b/15/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md @@ -10,7 +10,7 @@ Umbraco allows for restricting access to content. Using the "Public access" feat By default, protected content is ignored by the Delivery API, and is never exposed through any API endpoints. However, by enabling member authorization in the Delivery API, protected content can be accessed by means of access tokens. {% hint style="info" %} -If you are not familiar with members in Umbraco, please read the [Members](https://docs.umbraco.com/umbraco-cms/fundamentals/data/members) article. +If you are not familiar with members in Umbraco, please read the [Members](../../../fundamentals/data/members) article. {% endhint %} {% hint style="info" %} @@ -69,7 +69,7 @@ When changing the `MemberAuthorization` configuration, Umbraco must be restarted {% hint style="warning" %} When enabling or disabling member authentication, the `DeliveryApiContentIndex` must be rebuilt to correctly reflect the existing content protection state. -The index can be rebuilt from the [Examine Management dashboard](https://docs.umbraco.com/umbraco-cms/reference/searching/examine/examine-management). +The index can be rebuilt from the [Examine Management dashboard](../../searching/examine/examine-management). {% endhint %} ## Server endpoints @@ -211,11 +211,11 @@ If everything works as expected, the request will yield a redirect to the login Do not worry about the URL construction and subsequent handling of the `code` parameter. This complexity is what the OpenId Connect client libraries handle for us. {% endhint %} -For more inspiration on using the built-in member authentication, check the [Members Registration and Login](https://docs.umbraco.com/umbraco-cms/tutorials/members-registration-and-login) article. Here you will also learn how to create member sign-up functionality. +For more inspiration on using the built-in member authentication, check the [Members Registration and Login](../../../tutorials/members-registration-and-login) article. Here you will also learn how to create member sign-up functionality. ### How to use external identity providers -Umbraco allows adding external identity providers for both backoffice users and members. The process is documented in detail in the [External Login Providers](https://docs.umbraco.com/umbraco-cms/reference/security/external-login-providers/) article. +Umbraco allows adding external identity providers for both backoffice users and members. The process is documented in detail in the [External Login Providers](../../security/external-login-providers/) article. The Delivery API supports the same functionality. In the following we'll be using GitHub to test this. @@ -302,7 +302,7 @@ builder.CreateUmbracoBuilder() {% hint style="info" %} There are multiple ways of registering extensions and dependencies like these in your Umbraco project. Which method to use depends on your implementation and preferred way of working. -Learn more about this in the [Dependency Injection](../using-ioc.md) article. +Learn more about this in the [Dependency Injection](../../using-ioc.md) article. {% endhint %} Now we can test the setup. We'll be calling `https://{server-host}/umbraco/delivery/api/v1/security/member/authorize` as described previously, but we need to add one more query string parameter: @@ -389,7 +389,7 @@ The Delivery API Swagger document can be configured to support member authentica Before we can do that, we need two things in place: -1. We have to implement a login page [as described above](./#logging-in-members). +1. We have to implement a login page [as described above](#logging-in-members). 2. We must add `https://{server-host}/umbraco/swagger/oauth2-redirect.html` to the configured `LoginRedirectUrls`. With these in place, we can enable member authentication in Swagger for the Delivery API by adding the following to `Program.cs`: diff --git a/15/umbraco-cms/reference/routing/request-pipeline/published-content-request-preparation.md b/15/umbraco-cms/reference/routing/request-pipeline/published-content-request-preparation.md index 44d53d6c1aa..79d8667f9b1 100644 --- a/15/umbraco-cms/reference/routing/request-pipeline/published-content-request-preparation.md +++ b/15/umbraco-cms/reference/routing/request-pipeline/published-content-request-preparation.md @@ -46,11 +46,11 @@ We will discuss a few of these steps below. The FindDomain method looks for a domain matching the request Uri -* Using a greedy match: “domain.com/foo” takes over “domain.com”. +* Using a greedy match: `domain.com/foo` takes over `domain.com`. * Sets published content request’s domain. * If a domain was found. * Sets published content request’s culture accordingly. - * Computes domain Uri based upon the current request ("domain.com" for "http://domain.com" or "https://domain.com"). + * Computes domain Uri based upon the current request (`domain.com` for `http://domain.com` or `https://domain.com`). * Else. * Sets published content request’s culture by default (first language, else system). diff --git a/15/umbraco-cms/reference/routing/umbraco-api-controllers/README.md b/15/umbraco-cms/reference/routing/umbraco-api-controllers/README.md index 0abc7a31cc0..78f902727fc 100644 --- a/15/umbraco-cms/reference/routing/umbraco-api-controllers/README.md +++ b/15/umbraco-cms/reference/routing/umbraco-api-controllers/README.md @@ -145,7 +145,7 @@ public class ProductsController : Controller ## Backoffice API Controllers -Read the [Creating a Backoffice API article](../tutorials/creating-a-backoffice-api/README.md) for a comprehensive guide to writing APIs for the Management API. +Read the [Creating a Backoffice API article](../../../tutorials/creating-a-backoffice-api/README.md) for a comprehensive guide to writing APIs for the Management API. {% hint style="info" %} The Umbraco Backoffice API is also known as the Management API. Thus, a Backoffice API Controller is often referred to as a Management API Controller. diff --git a/15/umbraco-cms/reference/security/ssl-https.md b/15/umbraco-cms/reference/security/ssl-https.md index d052fdac998..6fbb9e3a981 100644 --- a/15/umbraco-cms/reference/security/ssl-https.md +++ b/15/umbraco-cms/reference/security/ssl-https.md @@ -65,7 +65,7 @@ app.UseHttpsRedirection(); Once you enable HTTPS for your site you should redirect all requests to your site to HTTPS. This can be done with an IIS rewrite rule. The IIS rewrite module needs to be installed for this to work, most hosting providers will have that enabled by default. -In your `web.config` find or add the `` section and put the following rule in there. This rule will redirect all requests for the site http://mysite.com URL to the secure https://mysite.com URL and respond with a permanent redirect status. +In your `web.config` find or add the `` section and put the following rule in there. This rule will redirect all requests for the site `http://mysite.com` URL to the secure `https://mysite.com` URL and respond with a permanent redirect status. ```xml diff --git a/15/umbraco-cms/reference/umbraco-flavored-markdown.md b/15/umbraco-cms/reference/umbraco-flavored-markdown.md index df92752e4d8..7bb6f77394d 100644 --- a/15/umbraco-cms/reference/umbraco-flavored-markdown.md +++ b/15/umbraco-cms/reference/umbraco-flavored-markdown.md @@ -41,7 +41,7 @@ With this example, the syntax `{umbValue: bodyText}` would be processed and rend ``` -The internal working of the `ufm-label-value` component would then be able to access the property's value using the [Context API](../extending/backoffice-setup/working-with-data/context-api). +The internal working of the `ufm-label-value` component would then be able to access the property's value using the [Context API](../customizing/foundation/working-with-data/context-api.md). ### Filters diff --git a/15/umbraco-cms/tutorials/creating-a-custom-dashboard/extending-the-dashboard-using-umbraco-ui-library.md b/15/umbraco-cms/tutorials/creating-a-custom-dashboard/extending-the-dashboard-using-umbraco-ui-library.md index eabce7dd7c6..c9367dc42ef 100644 --- a/15/umbraco-cms/tutorials/creating-a-custom-dashboard/extending-the-dashboard-using-umbraco-ui-library.md +++ b/15/umbraco-cms/tutorials/creating-a-custom-dashboard/extending-the-dashboard-using-umbraco-ui-library.md @@ -18,7 +18,7 @@ The steps we will go through in this part are: ### Umbraco UI Library -The [Umbraco UI Library](../../customizing/ui-documentation.md) is a set of web components and variables that we can use to build Umbraco User Interfaces. It is already part of the Backoffice, which means you can already start to use it. +The [Umbraco UI Library](../../customizing/foundation/localization.md) is a set of web components and variables that we can use to build Umbraco User Interfaces. It is already part of the Backoffice, which means you can already start to use it. By using the variables available from the UI Library, you ensure that your extensions are a consistent size with the rest of the backoffice. diff --git a/15/umbraco-cms/tutorials/members-registration-and-login.md b/15/umbraco-cms/tutorials/members-registration-and-login.md index 46227ff1b92..a7801410863 100644 --- a/15/umbraco-cms/tutorials/members-registration-and-login.md +++ b/15/umbraco-cms/tutorials/members-registration-and-login.md @@ -139,12 +139,10 @@ If you are on Umbraco Cloud you need to do the following steps to be able to res 1. Go to the Users section in the Backoffice. 2. Select your User. -3. Add the "Sensitive Data" Group. ![Assign User Access group](images/v8-17-Assign-User-Access-Group.png) +3. Add the "Sensitive Data" Group. Once you have added the "Sensitive Data" group go to the Members section in the backoffice. In the Members section you need to select each member and approve them by toggling the Approved button. -Approve Member - Once the users have been approved, you can go ahead and continue the tutorial. {% endhint %}