Skip to content

Commit e810bab

Browse files
eshanrnheshanrnh
authored
Merge branch 'main' into lychee-fix
2 parents 1c2298b + bc3b518 commit e810bab

File tree

12 files changed

+149
-207
lines changed

12 files changed

+149
-207
lines changed

‎.github/lychee.toml‎

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
# .github/lychee.toml
2+
3+
############################# Display #############################
4+
# Verbose program output
5+
# Accepts log level: "error", "warn", "info", "debug", "trace"
6+
verbose = "info"
7+
8+
# Don't show interactive progress bar while checking links.
9+
no_progress = true
10+
11+
############################# Cache ###############################
12+
# Enable link caching. This can be helpful to avoid checking the same links on
13+
# multiple runs.
14+
cache = false
15+
16+
############################# Runtime #############################
17+
# Maximum number of concurrent link checks.
18+
max_concurrency = 12
19+
20+
# Maximum number of allowed redirects.
21+
max_redirects = 5
22+
23+
# Maximum number of allowed retries before a link is declared dead.
24+
max_retries = 1
25+
26+
############################# Requests ############################
27+
# Website timeout from connect to response finished.
28+
timeout = 10
29+
30+
# Minimum wait time in seconds between retries of failed requests.
31+
retry_wait_time = 1
32+
33+
# Accept more status codes (follow redirects automatically)
34+
accept = ["200..=204", "301..=308", "429"]
35+
36+
# Avoid false fragment errors
37+
include_fragments = false
38+
39+
# Only test links with the given schemes (e.g. https).
40+
# Omit to check links with any other scheme.
41+
# At the moment, we support http, https, file, and mailto.
42+
scheme = ["https"]
43+
44+
# When links are available using HTTPS, treat HTTP links as errors.
45+
require_https = false
46+
47+
# Fallback extensions to apply when a URL does not specify one.
48+
# This is common in documentation tools that cross-reference files without extensions.
49+
fallback_extensions = ["md", "html"]
50+
51+
############################# Exclusions ##########################
52+
# Exclude URLs and mail addresses from checking (supports regex).
53+
exclude = [
54+
'^mailto:',
55+
'^https?://localhost',
56+
'^https?://127\\.0\\.0\\.1',
57+
'^https://www\.linkedin\.com',
58+
'^https?://issues\.umbraco\.org/',
59+
'^https?://web\\.archive\\.org/web/'
60+
]
61+
62+
# Exclude these filesystem paths from getting checked.
63+
exclude_path = [
64+
'(^|/)node_modules/',
65+
'(^|/)dist/',
66+
'(^|/)bin/',
67+
'\\.txt$', # skip .txt extensions
68+
'(^|/)test/' # skip directories named "test"
69+
]
70+
71+
# URLs to check (supports regex). Has preference over all excludes.
72+
include = ['gist\.github\.com.*']
73+
74+
# Skip checking mail addresses
75+
include_mail = true
76+
77+
############################# Content Checks ######################
78+
# Mark pages as broken if the body contains "page not found" or "404"
79+
[content]
80+
deny = ["(?i)page not found", "(?i)404"]

‎.github/workflows/check-broken-pr-links.yml‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -76,6 +76,7 @@ jobs:
7676
msg = $0
7777
sub(/^- \[ \] /, "", msg)
7878
sub(/^\[404\] /, "", msg)
79+
7980
print "\n❌ 404 Not Found → " msg "\n" >> "lychee/comment.md"
8081
next
8182
}

‎.gitignore‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,3 +4,4 @@
44
*.orig
55
.vscode
66
.idea
7+
.lycheecache

‎.lycheeignore‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
# These links are ignored by lychee link checker: https://github.com/lycheeverse/lychee
2+
# The file allows you to list multiple regular expressions for exclusion (one pattern per line).
3+
# The `.lycheeignore` file is only used for excluding URLs, not paths. Use the `exclude_path` key in the `lychee.toml` file. ref: https://lychee.cli.rs/recipes/excluding-paths/
4+
5+
# GitHub blob/tree fragment links
6+
^https://github\.com/umbraco/Umbraco-CMS/blob/.*/.*#L.*
7+
^https://github\.com/umbraco/Umbraco-CMS/tree/.*
8+
^https://github\.com/Shazwazza/Articulate/blob/.*/.*#L.*
9+
^https://github\.com/umbraco/Umbraco-CMS/blob/.*
10+
^https://github\.com/.*/issues/[0-9]+#issuecomment-[0-9]+
11+
12+
# Anchor/fragment links causing false positives
13+
^https://apidocs\.umbraco\.com/.*/#.*
14+
^https://tinymce\.github\.io/.*/#.*
15+
^https://openid\.net/.*/#.*
16+
^https://docs\.microsoft\.com/.*#.*
17+
^https://learn\.microsoft\.com/.*#.*
18+
^https://developer\.mozilla\.org/.*/#.*
19+
^https://learning\.postman\.com/docs/.*/#.*
20+
^https://nginx\.org/.*/#.*
21+
^https://azure\.microsoft\.com/en-gb/services/media-services/.*
22+
^https://www\.tiny\.cloud/docs/.*
23+
24+
# TinyMCE anchors
25+
^https://github\.com/tinymce/tinymce/issues/.*#.*
26+
27+
# NIST FIPS and other static docs
28+
^https://csrc\.nist\.gov/publications/PubsFIPS\.html#.*
29+
30+
# Timeout-prone Umbraco issue links
31+
^https://issues\.umbraco\.org/issue/.*
32+
^https://issues\.umbraco\.org/issues/.*

‎13/umbraco-commerce/how-to-guides/customizing-templates.md‎

Lines changed: 1 addition & 59 deletions
Original file line numberDiff line numberDiff line change
@@ -14,62 +14,4 @@ Download the custom templates and place them in `/Views/Partials/Commerce/Email/
1414

1515
{% file src="../.gitbook/assets/Umbraco.Commerce.Templates.v13.zip" %}
1616
Umbraco Commerce Custom Templates
17-
{% endfile %}
18-
19-
## Creating Custom Templates
20-
21-
### Email Templates
22-
23-
To Create a Custom Email Template:
24-
25-
1. Create a Razor view file (`.cshtml`) in `/Views/Partials/Commerce/Email/.`
26-
2. Implement the `IEmailTemplate` interface to make the template available in Umbraco Commerce:
27-
28-
```csharp
29-
using Umbraco.Commerce.Core.Interfaces;
30-
31-
public class CustomOrderEmailTemplate : IEmailTemplate
32-
{
33-
public virtual string FileName => "CustomOrderEmail.cshtml";
34-
}
35-
36-
```
37-
38-
3. Register the Template in a Composer:
39-
40-
```csharp
41-
using Umbraco.Cms.Core.Composing;
42-
using Umbraco.Cms.Core.DependencyInjection;
43-
44-
public class CustomTemplateComposer : IComposer
45-
{
46-
public void Compose(IUmbracoBuilder builder)
47-
{
48-
builder.EmailTemplates().Add<CustomOrderEmailTemplate>();
49-
}
50-
}
51-
52-
```
53-
54-
### Print and Export Templates
55-
56-
To create Print/Export Templates:
57-
58-
1. Create a Razor view file (`.cshtml`) under the relevant paths:
59-
60-
```
61-
/Views/Partials/Commerce/Prints/
62-
/Views/Partials/Commerce/Exports/
63-
```
64-
65-
2. Implement the `IPrintTemplate` or `IExportTemplate` interface to make the template available in Umbraco Commerce.
66-
3. Register the template in a Composer similar to the email template process.
67-
68-
## Shipping Custom Templates in a Razor Class Library
69-
70-
To distribute custom templates as part of a Razor Class Library (RCL):
71-
72-
1. Create a new Razor Class Library project.
73-
2. Add the template files under appropriate paths, for example, `Views/Partials/Commerce/Emails/`.
74-
3. Implement interfaces like `IEmailTemplate,` `IPrintTemplate,`or `IExportTemplate` .
75-
4. Use a composer to register your custom templates.
17+
{% endfile %}

‎13/umbraco-deploy/release-notes.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,12 @@ If you are upgrading to a new major version you can find the details about the b
1616

1717
This section contains the release notes for Umbraco Deploy 13 including all changes for this version.
1818

19+
### [13.4.1](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.4.1) (September 5th 2025)
20+
21+
* Fix parsing root UDI range when custom `tryParseEntityIdFromNodeId` is used when [registering a transfer entity type](./extending/extending.md#backoffice-integrated-transfers)
22+
* Fix updating restore descriptions when the selected workspace is changed
23+
* Set default row span in block area configuration when migrating to Block Grid editor [#270](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/270#issuecomment-3068861453)
24+
1925
### [13.4.0](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.4.0) (February 6th 2025)
2026

2127
* All items from 13.4.0-rc1

‎15/umbraco-commerce/how-to-guides/customizing-templates.md‎

Lines changed: 0 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -16,60 +16,3 @@ Download the custom templates and place them in `/Views/Partials/Commerce/Email/
1616
Umbraco Commerce Custom Templates
1717
{% endfile %}
1818

19-
## Creating Custom Templates
20-
21-
### Email Templates
22-
23-
To Create a Custom Email Template:
24-
25-
1. Create a Razor view file (`.cshtml`) in `/Views/Partials/Commerce/Email/.`
26-
2. Implement the `IEmailTemplate` interface to make the template available in Umbraco Commerce:
27-
28-
```csharp
29-
using Umbraco.Commerce.Core.Interfaces;
30-
31-
public class CustomOrderEmailTemplate : IEmailTemplate
32-
{
33-
public virtual string FileName => "CustomOrderEmail.cshtml";
34-
}
35-
36-
```
37-
38-
3. Register the Template in a Composer:
39-
40-
```csharp
41-
using Umbraco.Cms.Core.Composing;
42-
using Umbraco.Cms.Core.DependencyInjection;
43-
44-
public class CustomTemplateComposer : IComposer
45-
{
46-
public void Compose(IUmbracoBuilder builder)
47-
{
48-
builder.EmailTemplates().Add<CustomOrderEmailTemplate>();
49-
}
50-
}
51-
52-
```
53-
54-
### Print and Export Templates
55-
56-
To create Print/Export Templates:
57-
58-
1. Create a Razor view file (`.cshtml`) under the relevant paths:
59-
60-
```
61-
/Views/Partials/Commerce/Prints/
62-
/Views/Partials/Commerce/Exports/
63-
```
64-
65-
2. Implement the `IPrintTemplate` or `IExportTemplate` interface to make the template available in Umbraco Commerce.
66-
3. Register the template in a Composer similar to the email template process.
67-
68-
## Shipping Custom Templates in a Razor Class Library
69-
70-
To distribute custom templates as part of a Razor Class Library (RCL):
71-
72-
1. Create a new Razor Class Library project.
73-
2. Add the template files under appropriate paths, for example, `Views/Partials/Commerce/Emails/`.
74-
3. Implement interfaces like `IEmailTemplate,` `IPrintTemplate,`or `IExportTemplate` .
75-
4. Use a composer to register your custom templates.

‎16/umbraco-commerce/how-to-guides/customizing-templates.md‎

Lines changed: 0 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -16,60 +16,3 @@ Download the custom templates and place them in `/Views/Partials/Commerce/Email/
1616
Umbraco Commerce Custom Templates
1717
{% endfile %}
1818

19-
## Creating Custom Templates
20-
21-
### Email Templates
22-
23-
To Create a Custom Email Template:
24-
25-
1. Create a Razor view file (`.cshtml`) in `/Views/Partials/Commerce/Email/.`
26-
2. Implement the `IEmailTemplate` interface to make the template available in Umbraco Commerce:
27-
28-
```csharp
29-
using Umbraco.Commerce.Core.Interfaces;
30-
31-
public class CustomOrderEmailTemplate : IEmailTemplate
32-
{
33-
public virtual string FileName => "CustomOrderEmail.cshtml";
34-
}
35-
36-
```
37-
38-
3. Register the Template in a Composer:
39-
40-
```csharp
41-
using Umbraco.Cms.Core.Composing;
42-
using Umbraco.Cms.Core.DependencyInjection;
43-
44-
public class CustomTemplateComposer : IComposer
45-
{
46-
public void Compose(IUmbracoBuilder builder)
47-
{
48-
builder.EmailTemplates().Add<CustomOrderEmailTemplate>();
49-
}
50-
}
51-
52-
```
53-
54-
### Print and Export Templates
55-
56-
To create Print/Export Templates:
57-
58-
1. Create a Razor view file (`.cshtml`) under the relevant paths:
59-
60-
```
61-
/Views/Partials/Commerce/Prints/
62-
/Views/Partials/Commerce/Exports/
63-
```
64-
65-
2. Implement the `IPrintTemplate` or `IExportTemplate` interface to make the template available in Umbraco Commerce.
66-
3. Register the template in a Composer similar to the email template process.
67-
68-
## Shipping Custom Templates in a Razor Class Library
69-
70-
To distribute custom templates as part of a Razor Class Library (RCL):
71-
72-
1. Create a new Razor Class Library project.
73-
2. Add the template files under appropriate paths, for example, `Views/Partials/Commerce/Emails/`.
74-
3. Implement interfaces like `IEmailTemplate,` `IPrintTemplate,`or `IExportTemplate` .
75-
4. Use a composer to register your custom templates.

‎16/umbraco-deploy/release-notes.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,14 @@ If you are upgrading to a new major version you can find the details about the b
1616

1717
This section contains the release notes for Umbraco Deploy 15 including all changes for this version.
1818

19+
### [16.0.1](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F16.0.1) (September 5th 2025)
20+
21+
* Fix remote entity tree implementation causing conflicts with CMS culture switcher, tree icons, and inherited document permissions [#275](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/275)
22+
* Fix remote entity pickers not showing tree items (when selecting an item for partial restore)
23+
* Fix document-specific Deploy permissions
24+
* Fix dashboard UI layout issues and translations
25+
* Set default row span in block area configuration when migrating to Block Grid editor [#270](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/270#issuecomment-3068861453)
26+
1927
### [16.0.0](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F16.0.0) (May 12th 2025)
2028

2129
* Compatibility with Umbraco 16.0.0

‎umbraco-cloud/README.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,11 @@ layout:
2020

2121
# Welcome to Umbraco Cloud Documentation
2222

23-
The Umbraco Cloud documentation is now organized around the user journey, not just features. Why? Because building and managing a project is more than a list of tools, it’s a progression of real-life steps you take from first login to go-live and beyond.
23+
The Umbraco Cloud documentation is structured to follow the user journey rather than only listing features. This change acknowledges that building and managing a project involves real-life steps. It begins with your initial login and continues through the go-live phase and beyond.
2424

2525
<figure><img src=".gitbook/assets/Cloud Docs Restructure.png" alt=""><figcaption><p>User Journey</p></figcaption></figure>
2626

27-
Whether you’re new to Umbraco Cloud or already building amazing projects on Umbraco Cloud, this is your go-to hub for understanding, using, and mastering Umbraco Cloud.
27+
Whether you're new to Umbraco Cloud or a seasoned user, this hub is your essential resource for understanding and mastering Umbraco Cloud.
2828

2929
## Explore by Phase: Your Umbraco Cloud Journey
3030

@@ -34,10 +34,10 @@ The documentation is structured to match your journey. From discovery to going l
3434

3535
### Quick Links
3636

37-
{% content-ref url="broken-reference" %}
38-
[Broken link](broken-reference)
37+
{% content-ref url="begin-your-cloud-journey/the-cloud-portal/README.md" %}
38+
[The Cloud Portal](begin-your-cloud-journey/the-cloud-portal/README.md)
3939
{% endcontent-ref %}
4040

41-
### New to Umbraco Cloud? <a href="#new-to-umbraco-cloud" id="new-to-umbraco-cloud"></a>
41+
### New to Umbraco Cloud?
4242

4343
Start with the tour of the [Umbraco Cloud Portal](begin-your-cloud-journey/the-cloud-portal/) or try a [free trial project](https://try.umbraco.com/cloud) to explore without commitment.

0 commit comments

Comments
 (0)