Skip to content

Commit 6c9c502

Browse files
committed
Update broken links
1 parent fe7666c commit 6c9c502

File tree

5 files changed

+6
-7
lines changed

5 files changed

+6
-7
lines changed

content/changelog/v10.0.0.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ We added a new taxonomy view action that allows you to tag/untag taxonomy to mul
2626

2727
![Tag your taxonomy](/releases/v10.0.0/taxonomy-tagging.webp)
2828

29-
> **Info**: More information can be found in the [taxonomy documentation](/docs/taxonomy-view#tag-content).
29+
> **Info**: More information can be found in the [taxonomy documentation](/docs/dashboard/taxonomy-view#tag-content).
3030
3131
## Media Content Types
3232

content/changelog/v4_0_0.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ lastmod: '2021-09-22T08:00:43.170Z'
77

88
## Team level settings
99

10-
As Front Matter is not a single-user extension, we wanted to bring it to a higher level. With the new Team level settings functionality, you can manage your site by sharing the configuration on the team level with the new `frontmatter.json` file.
10+
As Front Matter is not a single-user extension, we wanted to bring it to a higher level. With the new Team level settings functionality, you can manage your site by sharing the configuration on the team level with the new `frontmatter.json` file.
1111

1212
With this new functionality you don't have to share your local `.vscode/settings.json` file anymore, which is good, as it isn't meant to be shared, as it are personal settings you want to use in your project/solution.
1313

@@ -37,7 +37,7 @@ A CMS won't be complete if it doesn't allow you to define your own content types
3737

3838
![Define your own content types](/releases/v4_0_0/content-type.png)
3939

40-
> **Info**: Find out more on our new content type support in the [content creation section](docs/content-creation).
40+
> **Info**: Find out more on our new content type support in the [content creation section](/docs/content-creation).
4141
4242
### Supported field types
4343

content/changelog/v8.2.0.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ The `frontMatter.content.pageFolders` setting has two new properties which can b
3535

3636
Single data entry files are now supported. This means that you can now have a data file that contains a single entry, instead of an array of entries.
3737

38-
> **Info**: For more info, check out the [Data files](/doc/dashboard/datafiles-view#creating-a-data-file) documentation.
38+
> **Info**: For more info, check out the [Data files](/docs/dashboard/datafiles-view#creating-a-data-file) documentation.
3939
4040
## Improved UX for inserting media files to your content
4141

content/docs/content-creation/content-folders.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ content in the correct place, you need to register the content/page folders.
1919
## Registering content folders
2020

2121
The registration of the page folders is typically performed during the setup of
22-
the CMS: [Step 3: Register content folder(s)][01],
22+
the CMS: [Step 3: Register content folder(s)](/docs/getting-started#step-3:-register-content-folder(s)),
2323
but you can perform changes at any time.
2424

2525
Content folders are stored in the [frontMatter.content.pageFolders][02] setting.
@@ -120,7 +120,6 @@ and clicking on `Register folder` under the Front Matter CMS context menu.
120120
121121
<!-- Links -->
122122

123-
[01]: "/docs/getting-started#step-3:-register-content-folder(s)"
124123
[02]: /docs/settings/overview#frontmatter.content.pagefolders
125124
[03]: /docs/site-preview#configuration
126125
[04]: /docs/content-creation/multilingual

content/docs/content-creation/multilingual.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -219,7 +219,7 @@ Follow the next steps in order to configure the DeepL authentication key:
219219

220220
### Start translating
221221

222-
Once you configured Deepl or Azure AI Translator, when you [create a new translation](docs/content-creation/multilingual#create-a-translation),
222+
Once you configured Deepl or Azure AI Translator, when you [create a new translation](/docs/content-creation/multilingual#create-a-translation),
223223
the CMS will automatically submit the article title, description, and content to the
224224
translation service.
225225

0 commit comments

Comments
 (0)