redirect: Resolve internal links to final dest

FlowFuse · Aug 22, 2023 · fb9d645 · fb9d645
1 parent 42c0738
commit fb9d645
Show file tree

Hide file tree

Showing 11 changed files with 11 additions and 11 deletions.
diff --git a/src/blog/2022/04/flowforge-04-released.md b/src/blog/2022/04/flowforge-04-released.md
@@ -59,7 +59,7 @@ of the platform:
 ### Upgrading FlowFuse
 
 If you installed a previous version of FlowFuse  and want to upgrade, our documentation provides a
-guide for [upgrading FlowFuse on a local server](/docs/install#upgrade).
+guide for [upgrading FlowFuse on a local server](/docs/upgrade/#upgrading-flowforge).
 
 ### Getting help
 

diff --git a/src/blog/2022/05/flowforge-05-released.md b/src/blog/2022/05/flowforge-05-released.md
@@ -81,7 +81,7 @@ on devices.
 ### Upgrading FlowFuse
 
 If you installed a previous version of FlowFuse  and want to upgrade, our documentation provides a
-guide for [upgrading FlowFuse on a local server](/docs/install#upgrade).
+guide for [upgrading FlowFuse on a local server](/docs/upgrade/#upgrading-flowforge).
 
 ### Getting help
 

diff --git a/src/blog/2022/06/flowforge-06-released.md b/src/blog/2022/06/flowforge-06-released.md
@@ -70,7 +70,7 @@ Node-RED editor sessions you have open.
 you to start creating snapshots and adding devices right now.
 
 If you installed a previous version of FlowFuse and want to upgrade, our documentation provides a
-guide for [upgrading FlowFuse on a local server](/docs/install#upgrade).
+guide for [upgrading FlowFuse on a local server](/docs/upgrade/#upgrading-flowforge).
 
 ### Getting help
 

diff --git a/src/blog/2022/07/flowforge-07-released.md b/src/blog/2022/07/flowforge-07-released.md
@@ -61,7 +61,7 @@ We've fixed the following bugs in this release.
 you to try out rollbacks and the new theme. 
 
 If you installed a previous version of FlowFuse and want to upgrade, our documentation provides a
-guide for [upgrading FlowFuse on a local server](/docs/install#upgrade).
+guide for [upgrading FlowFuse on a local server](/docs/upgrade/#upgrading-flowforge).
 
 ### Getting help
 

diff --git a/src/blog/2022/08/flowforge-08-released.md b/src/blog/2022/08/flowforge-08-released.md
@@ -68,7 +68,7 @@ As an open-source project, we welcome the community involvement in what we're bu
 [FlowFuse Cloud](https://app.flowforge.com) is already running 0.8 and the stacks updated. Upgrade your project stacks to the latest version and start using the Project Link nodes now.
 
 If you installed a previous version of FlowFuse and want to upgrade, our documentation provides a
-guide for [upgrading FlowFuse on a local server](/docs/install#upgrade).
+guide for [upgrading FlowFuse on a local server](/docs/upgrade/#upgrading-flowforge).
 
 ### Getting help
 

diff --git a/src/blog/2022/09/flowforge-010-released.md b/src/blog/2022/09/flowforge-010-released.md
@@ -69,7 +69,7 @@ As an open-source project, we welcome the community involvement in what we're bu
 [FlowFuse Cloud](https://app.flowforge.com) is already running 0.10 and the stacks updated. Upgrade your project stacks to the latest version to make sure you get all the latest changes.
 
 If you installed a previous version of FlowFuse and want to upgrade, our documentation provides a
-guide for [upgrading FlowFuse on a local server](/docs/install#upgrade).
+guide for [upgrading FlowFuse on a local server](/docs/upgrade/#upgrading-flowforge).
 
 ### Getting help
 

diff --git a/src/blog/2022/09/flowforge-09-released.md b/src/blog/2022/09/flowforge-09-released.md
@@ -77,7 +77,7 @@ As an open-source project, we welcome the community involvement in what we're bu
 [FlowFuse Cloud](https://app.flowforge.com) is already running 0.9 and the stacks updated. Upgrade your project stacks to the latest version and start using the Project Link nodes now.
 
 If you installed a previous version of FlowFuse and want to upgrade, our documentation provides a
-guide for [upgrading FlowFuse on a local server](/docs/install#upgrade).
+guide for [upgrading FlowFuse on a local server](/docs/upgrade/#upgrading-flowforge).
 
 ### Getting help
 

diff --git a/src/blog/2022/10/flowforge-1-released.md b/src/blog/2022/10/flowforge-1-released.md
@@ -72,7 +72,7 @@ As an open-source project, we welcome community involvement in what we're buildi
 Our managed [FlowFuse](https://app.flowforge.com) is already running 1.0. Upgrade your project Stacks to the latest version to make sure you get all the latest changes.
 
 If you installed a previous version of FlowFuse and want to upgrade, our documentation provides a
-guide for [upgrading FlowFuse on a local server](/docs/install#upgrade).
+guide for [upgrading FlowFuse on a local server](/docs/upgrade/#upgrading-flowforge).
 
 ### Getting help
 

diff --git a/src/blog/2022/12/flowforge-joins-openjs-foundation.md b/src/blog/2022/12/flowforge-joins-openjs-foundation.md
@@ -15,7 +15,7 @@ support for the Node-RED community.
 
 <!--more-->
 
-One of our [founding principles](/handbook/company/#open-source-stewardship) is
+One of our [founding principles](/handbook/company/principles/#open-source-stewardship) is
 the importance of Open Source being at the core of what we do.
 
 Node-RED has been part of the [OpenJS Foundation](https://openjsf.org/) since it was formed in 2019.

diff --git a/src/blog/2023/03/flowforge-1-5-0-released.md b/src/blog/2023/03/flowforge-1-5-0-released.md
@@ -53,7 +53,7 @@ Devices are now bound to "Instances", you'll see these in the "Devices" view, an
 
 ## Node-RED 3.1 Beta Available
 
-FlowFuse Cloud is a great place to try out the new Node-RED features, with FlowFuse Cloud now including the [Node-RED 3.1.0-beta.2](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192). If you want to try this version you can [duplicate your application](/docs/user/instance-settings/#copy-project) or [upgrade your stack](/docs/user/changestack/).
+FlowFuse Cloud is a great place to try out the new Node-RED features, with FlowFuse Cloud now including the [Node-RED 3.1.0-beta.2](https://discourse.nodered.org/t/node-red-3-1-0-beta-2-released/76192). If you want to try this version you can [duplicate your application](https://flowfuse.com/docs/user/instance-settings/#copy-instance) or [upgrade your stack](/docs/user/changestack/).
 
 ## Other Improvements
 

diff --git a/src/handbook/marketing/blog.md b/src/handbook/marketing/blog.md
@@ -15,7 +15,7 @@ Content creation and blogging are an effective way to communicate with our commu
 4. Create the draft blog post in a Google Doc. The document should be stored in the [Marketing -> Content](https://drive.google.com/drive/folders/1sdyVfD29dFE74i7zfmL0Cp9tPmPyK0-8?usp=share_link){rel="nofollow"} folder. Everyone at FlowFuse should be given access to comment on the document.  Add a link to the document in the GitHub issue.
 5. Ask people to review the document draft by sharing it directly with them using the Share button in the document. This will send your reviewers an email notification. 
 6. As a document reviewer, you should leave red-line edits in the document or add comments to the document.
-7. Once the document is finished, create a new branch of the website repository and then follow our standard [development processes](/handbook/development/#development-board). Google Docs has an [extension to convert the document to markdown](https://workspace.google.com/marketplace/app/docs_to_markdown/700168918607?hl=en&pann=docs_addon_widget).
+7. Once the document is finished, create a new branch of the website repository and then follow our standard [development processes](/handbook/development/releases/planning/#development-board). Google Docs has an [extension to convert the document to markdown](https://workspace.google.com/marketplace/app/docs_to_markdown/700168918607?hl=en&pann=docs_addon_widget).
 5. It is OK for you to merge your own PR to main without review where the content is urgent or has been reviewed outside of Git but where it is practical to follow the [standard process](/handbook/development/#development-board) we encourage you to do so.
 
 ### Blog CMS