FlowFuse · ZJvandeWeg · Aug 10, 2026 · Aug 10, 2026
diff --git a/src/blog/2022/09/community-news-08.md b/src/blog/2022/09/community-news-08.md
@@ -23,7 +23,7 @@ If you’d like to learn more about what else was included in 0.9 you can do so
 [**Node-RED Con 2022**](https://nrcon.nodered.org/)  
 We are happy to again be involved in Node-RED con. The event is being held online on 7th October, with content for both English and Japanese speakers. You can find out more on the [Node-RED Con website](https://nrcon.nodered.org/).  
 
-[**FlowFuse Team News**](/team/)    
+[**FlowFuse Team News**](/about/)    
 We’d like to welcome Rob Marcer to the FlowFuse team. Rob has joined as our Developer Educator, he's going to work to help you get the best value from FlowFuse by developing our documentation and community support.  
 
 We are also recruiting for [NodeJS Developers](https://boards.greenhouse.io/flowfuse/jobs/4463977004), if you’re interested in joining our team please [apply here](https://boards.greenhouse.io/flowfuse/jobs/4463977004#app).

diff --git a/src/blog/2022/11/community-news-10.md b/src/blog/2022/11/community-news-10.md
@@ -29,7 +29,7 @@ Earlier this week, we announced a $7.25M seed round led by [Cota Capital](https:
 [**Node-RED Dashboard - Beginners Guide**](https://stevesnoderedguide.com/node-red-dashboard)  
 It's great to see members of the Node-RED community taking their personal time to help us all build better projects. This write up takes you through the basics of creating your first Dashboard through to more advanced techniques to help your interfaces look professional and provide great user experiences.
 
-[**FlowFuse Team News**](/team/)    
+[**FlowFuse Team News**](/about/)    
 We are currently recruiting [NodeJS Developers](https://boards.greenhouse.io/flowfuse/jobs/4463977004), a [Product Manager](https://boards.greenhouse.io/flowfuse/jobs/4717778004), a [Recruiter / PeopleOps Manager](https://boards.greenhouse.io/flowfuse/jobs/4687876004) and a [Senior Community Manager](https://boards.greenhouse.io/flowfuse/jobs/4700809004). You can view any of the roles we currently have open and apply on our [Jobs page](https://boards.greenhouse.io/flowfuse).
 
 We'd also like to welcome [Pez Cuckow](https://github.com/Pezmc) who joined FlowFuse as a Senior Software Engineer in October.

diff --git a/src/blog/2022/12/community-news-11.md b/src/blog/2022/12/community-news-11.md
@@ -31,7 +31,7 @@ FlowFuse is a fully remote team, we currently have a strong skew towards western
 
 !["The FlowFuse team pictured during our visit to Clue Capers"](./images/clue-capers.jpg "The FlowFuse team pictured during our visit to Clue Capers")
 
-[**FlowFuse Team News**](/team/)    
+[**FlowFuse Team News**](/about/)    
 We are currently recruiting a [Product Manager](https://boards.greenhouse.io/flowfuse/jobs/4717778004), and a [Senior Community Manager](https://boards.greenhouse.io/flowfuse/jobs/4700809004). You can view any of the roles we currently have open and apply on our [Jobs page](https://boards.greenhouse.io/flowfuse).
 
 [**Try FlowFuse for Free**](https://app.flowfuse.com/account/create?code=RELEASE11)  

diff --git a/src/blog/2023/01/community-news-12.md b/src/blog/2023/01/community-news-12.md
@@ -29,7 +29,7 @@ According to this detailed article from iot-analytics.com, on average, four new
 [**Custom Node Spotlight - node-red-contrib-string**](https://flows.nodered.org/node/node-red-contrib-string)
 String manipulation is the bread and butter of so many programming tasks. Node-RED has a lot of tools to help you edit your strings including support for [JSONata](https://jsonata.org/) and using the trusty function node. For those of us who prefer to keep things 'no-code' [node-red-contrib-string](https://flows.nodered.org/node/node-red-contrib-string) allows you to stack string manipulations together quickly and easily. It has a huge library of ready to use functions.
 
-[**FlowFuse Team News**](/team/)    
+[**FlowFuse Team News**](/about/)    
 We’d like to welcome two new members to the FlowFuse team. [Ian Skerrett](https://twitter.com/ianskerrett) has joined as our Head of Marketing and [Tracy Anthony](https://www.linkedin.com/in/tracyanthonyfernandez/) has joined as our HR Manager. FlowFuse continues to grow and we are becoming a truly global team.
 
 Would you like to work for FlowFuse? We are currently recruiting [NodeJS Developers](https://boards.greenhouse.io/flowfuse/jobs/4463977004) to join our team. You can view any of the roles we currently have open and apply on our [Jobs page](https://boards.greenhouse.io/flowfuse). 

diff --git a/src/blog/2023/02/community-news-02.md b/src/blog/2023/02/community-news-02.md
@@ -37,7 +37,7 @@ We're now working towards release 1.4 which is due on 16th February. You can see
 
 If you’d like to learn more about what else was included in 1.3 you can do so on our [blog post](/blog/2023/01/flowforge-1-3-0-released/), [GitHub release page](https://github.com/FlowFuse/flowfuse/releases/tag/v1.3.0), and [Youtube channel](https://www.youtube.com/watch?v=ey3xv5j5x7k).
 
-### [Team News](/team)
+### [Team News](/about/)
 We are currently recruiting [NodeJS Developers](https://boards.greenhouse.io/flowfuse/jobs/4463977004) as well as a [Graphic Designer](https://boards.greenhouse.io/flowfuse/jobs/4785058004) to join our team. You can view any of the roles we currently have open and apply on our [Jobs page](https://boards.greenhouse.io/flowfuse).
 
 ## Node-RED in the Community

diff --git a/src/blog/2023/06/import-modules.md b/src/blog/2023/06/import-modules.md
@@ -101,7 +101,7 @@ Something we see [a lot on the Node-RED Forums](https://discourse.nodered.org/se
   <source src="https://website-data.s3.eu-west-1.amazonaws.com/PostHog+Node+Demo.mp4" type="video/mp4">
 </video>
 
-Node-RED is great for [data integration](/solutions/data-integration/). We use <a href="https://posthog.com/" target="_blank">PostHog</a> for our internal Product Analysis. We record live events as they occur on FlowFuse Cloud to better understand features that are (and are not) used.
+Node-RED is great for [data integration](/use-cases/data-integration/). We use <a href="https://posthog.com/" target="_blank">PostHog</a> for our internal Product Analysis. We record live events as they occur on FlowFuse Cloud to better understand features that are (and are not) used.
 
 We wanted to investigate whether or not we could add backdated data, which in theory was possible via their <a href="https://posthog.com/docs/libraries/node" target="_blank">posthog-node</a> module. We wanted to populate it with data driven from our own database and API. 
 

diff --git a/src/blog/2023/12/flowfuse-year-review-2023.md b/src/blog/2023/12/flowfuse-year-review-2023.md
@@ -22,7 +22,7 @@ First off; in 2023 we were known as FlowForge. But, due to some trademark challe
 
 On the product side: Growth in adoption of the FlowFuse platform has been tremendous, in many dimensions; revenue generated, customers onboarded, and how many users are now professionalizing their usage of Node-RED. Our development platform has been used by thousands of developers to acquire data from various sources and visualize it to build rich applications for their use cases. And at every step of the way we’ve been able to improve their experience.
 
-Data acquisition was always possible  without FlowFuse, however we’ve improved on the status quo through the [Certified Nodes](/certified-nodes/) program. A nascent program that vets often used custom nodes from the community to ensure business readiness and validate nodes to ensure there’s no malicious code installed.
+Data acquisition was always possible  without FlowFuse, however we’ve improved on the status quo through the [Certified Nodes](/integrations/?certified=1) program. A nascent program that vets often used custom nodes from the community to ensure business readiness and validate nodes to ensure there’s no malicious code installed.
 
 Further, this year we’ve started [Dashboard 2.0](https://dashboard.flowfuse.com/). The development of the successor of [node-red-dashboard](https://flows.nodered.org/node/node-red-dashboard), which is built on deprecated technology and effectively on life-support. The development of the new Dashboard technology has taken massive steps and it’s very stable. Feature parity is not yet achieved, though we’re happy with the adoption of Dashboard 2.0 and the community [reporting issues and improvements](https://github.com/FlowFuse/node-red-dashboard/issues).
 

diff --git a/src/blog/2023/12/introduction-to-unified-namespace.md b/src/blog/2023/12/introduction-to-unified-namespace.md
@@ -14,7 +14,7 @@ tags:
 
 As your organization is generating more data there’s key architectural
 decisions to be made to ensure the full value can be unlocked and you’re
-leveraging not just the tip of the iceberg. The [Unified Namespace (UNS)](/solutions/uns/)
+leveraging not just the tip of the iceberg. The [Unified Namespace (UNS)](/use-cases/uns/)
 provides a blueprint to allow data to be consumed by many data-consumers.
 FlowFuse helps you manage this migration and the operationalization of your
 data.

diff --git a/src/blog/2024/01/dashboard-2-multi-user.md b/src/blog/2024/01/dashboard-2-multi-user.md
@@ -40,7 +40,7 @@ All instances on FlowFuse can be configured with _"FlowFuse User Authentication"
 
 _Note: Every instance created from today onwards automatically comes with the necessary configuration. Already created instances need to be manually restarted._
 
-The Personalised Multi-User Dashboard plugin, `@flowfuse/node-red-dashboard-2-user-addon`, is available in our [Certified Nodes](/certified-nodes/) catalogue, accessible to our Teams and Enterprise customers.
+The Personalised Multi-User Dashboard plugin, `@flowfuse/node-red-dashboard-2-user-addon`, is available in our [Certified Nodes](/integrations/?certified=1) catalogue, accessible to our Teams and Enterprise customers.
 
 Once the "FlowFuse User Authentication" option has been enabled on your instance, you can then install our plugin, `@flowfuse/node-red-dashboard-2-user-addon`, through the "Manage Palette" option in the Node-RED Editor.
 

diff --git a/src/blog/2024/03/installing-operating-node-red-behind-firewall.md b/src/blog/2024/03/installing-operating-node-red-behind-firewall.md
@@ -27,7 +27,7 @@ First, ask for a temporary exception. Node-RED is installed in a few minutes, so
 
 As FlowFuse can be installed in a VPN behind a firewall, there’s no requirement to open up a ‘gate’ in your firewall to FlowFuse servers. The safe perimeter provided remains to the outside world. The security aspect remains, though as a Node-RED developer, there are still everyday tasks you’ll need access to the outside world.
 
-Consider installing third party nodes to connect your Node-RED instance to virtually any protocol or digital service. There are over 5000 of these nodes available, and as an organization it’s challenging to keep on top of. Your firewall provides one layer of security so that the data you’re accessing remains safe. FlowFuse provides a second layer of protection; we’ve introduced a [“Certified Nodes” catalog](/certified-nodes/). These nodes have gone through automated and manual inspection to prevent malicious code from making it onto your production systems.
+Consider installing third party nodes to connect your Node-RED instance to virtually any protocol or digital service. There are over 5000 of these nodes available, and as an organization it’s challenging to keep on top of. Your firewall provides one layer of security so that the data you’re accessing remains safe. FlowFuse provides a second layer of protection; we’ve introduced a [“Certified Nodes” catalog](/integrations/?certified=1). These nodes have gone through automated and manual inspection to prevent malicious code from making it onto your production systems.
 
 Installing these packages would typically still require you to obtain files from NPM. With FlowFuse however, a cache can be built with only vetted nodes – All other nodes remain unavailable.
 

diff --git a/src/blog/2024/04/node-red-architecture.md b/src/blog/2024/04/node-red-architecture.md
@@ -19,7 +19,7 @@ cta:
   description: FlowFuse helps you deploy and manage Node-RED across every layer of your factory, from shopfloor devices to enterprise systems, with centralized control and full visibility across every instance.
 ---
 
-The architecture of a factory's Node-RED infrastructure is a common topic of discussion and inquiry. Fundamentally, my response to such queries unfolds in two parts. Initially, the focus must be on data organization. I champion a structure centered around a [Unified Namespace](/solutions/uns/), a concept I explore in depth in this article ["Node-RED in a Unified Namespace Architecture."](/blog/2024/02/node-red-unified-namespace-architecture/) However, this is only one part of the inquiry. The other part of the question delves into the positioning of FlowFuse and Node-RED within the network infrastructure.
+The architecture of a factory's Node-RED infrastructure is a common topic of discussion and inquiry. Fundamentally, my response to such queries unfolds in two parts. Initially, the focus must be on data organization. I champion a structure centered around a [Unified Namespace](/use-cases/uns/), a concept I explore in depth in this article ["Node-RED in a Unified Namespace Architecture."](/blog/2024/02/node-red-unified-namespace-architecture/) However, this is only one part of the inquiry. The other part of the question delves into the positioning of FlowFuse and Node-RED within the network infrastructure.
 
 <!--more-->
 

diff --git a/src/blog/2024/05/product-strategy-updates.md b/src/blog/2024/05/product-strategy-updates.md
@@ -64,4 +64,4 @@ In the mean time, please do reach out if there are any features you'd like to se
 If you're interested in learning more about our company and product strategies, you can read more detail in our Handbook:
 
 - [Company Strategy](/handbook/company/strategy)
-- [Product Mission Statement](/handbook/engineering/product/strategy)
+- [Product Mission Statement](/handbook/engineering/product/)
diff --git a/src/blog/2024/08/using-mqtt-sparkplugb-with-node-red.md b/src/blog/2024/08/using-mqtt-sparkplugb-with-node-red.md
@@ -45,7 +45,7 @@ Connected devices can generate a lot of data, but without a standardized format,
 
 ## What is MQTT Sparkplug?
 
-MQTT Sparkplug B is an open-source specification governed by the [Eclipse Foundation Specification Process (EFSP)](https://www.eclipse.org/projects/efsp/). It defines a standardized MQTT topic namespace and payload format specifically designed for Industrial IoT (IIoT), with particular focus on real-time [SCADA](/solutions/scada/), control systems, and [HMI](/blog/2025/11/building-hmi-for-equipment-control/) solutions.
+MQTT Sparkplug B is an open-source specification governed by the [Eclipse Foundation Specification Process (EFSP)](https://www.eclipse.org/projects/efsp/). It defines a standardized MQTT topic namespace and payload format specifically designed for Industrial IoT (IIoT), with particular focus on real-time [SCADA](/use-cases/scada/), control systems, and [HMI](/blog/2025/11/building-hmi-for-equipment-control/) solutions.
 
 At its core, Sparkplug B extends MQTT 3.1.1 by adding structured topic namespace conventions, Google Protocol Buffer encoded payloads, state-aware birth and death certificates, metric aliasing for bandwidth optimization, and store-and-forward capabilities for intermittent connectivity. These additions transform MQTT from a simple messaging protocol into a complete industrial communication framework.
 

diff --git a/src/blog/2024/10/announcement-mqtt-broker.md b/src/blog/2024/10/announcement-mqtt-broker.md
@@ -17,7 +17,7 @@ In our [recent product update](/blog/2024/10/flowfuse-release-2-10) we have adde
 
 <!--more-->
 
-The MQTT Service is available now on [FlowFuse Cloud](/platform/cloud/). FlowFuse permits you to setup your own secure clients to begin publishing and subscribing to your own topics.
+The MQTT Service is available now on [FlowFuse Cloud](https://app.flowfuse.com/account/create/). FlowFuse permits you to setup your own secure clients to begin publishing and subscribing to your own topics.
 
 You can now use FlowFuse to manage your own MQTT Clients alongside your Node-RED instances, making it easier to build full-stack, event-driven applications within FlowFuse.
 

diff --git a/src/blog/2024/10/managing-node-red-instances-in-centralize-platfrom.md b/src/blog/2024/10/managing-node-red-instances-in-centralize-platfrom.md
@@ -57,7 +57,7 @@ With FlowFuse, you can organize your Node-RED instances into teams for improved
 ![Immersive Editor](./images/imersive-editor.png)  
 *Image showing how FlowFuse's immersive editor simplifies managing settings and configuration within the Node-RED editor.*
 
-FlowFuse also simplifies the [monitoring and controlling of edge devices](/solutions/edge-connectivity/) through the [FlowFuse Device Agent](/platform/device-agent/), which quickly connects your devices to the cloud platform and allows you to build and monitor applications remotely.
+FlowFuse also simplifies the [monitoring and controlling of edge devices](/use-cases/edge-connectivity/) through the [FlowFuse Device Agent](/platform/device-agent/), which quickly connects your devices to the cloud platform and allows you to build and monitor applications remotely.
 
 ![Device Management](./images/devices.png)  
 *Image showing remote edge devices connected through the FlowFuse platform for remote monitoring and control.*

diff --git a/src/blog/2024/11/building-uns-with-flowfuse.md b/src/blog/2024/11/building-uns-with-flowfuse.md
@@ -17,7 +17,7 @@ cta:
   description: FlowFuse brings together Node-RED, a built-in MQTT broker, and centralized device management, everything you need to connect your shop floor data into a single, real-time namespace.
 ---
 
-As systems and devices become more connected, managing data from different sources can be tricky. A [Unified Namespace (UNS)](/solutions/uns/) solves this by centralizing all your data in one place, making it easy to access and use.
+As systems and devices become more connected, managing data from different sources can be tricky. A [Unified Namespace (UNS)](/use-cases/uns/) solves this by centralizing all your data in one place, making it easy to access and use.
 
 <!--more-->
 

diff --git a/src/blog/2024/12/why-uns-need-data-modeling.md b/src/blog/2024/12/why-uns-need-data-modeling.md
@@ -16,7 +16,7 @@ cta:
   description: FlowFuse helps you connect, collect, transform, and visualize industrial data, with the data modeling tools you need to make your Unified Namespace actually work.
 ---
 
-In manufacturing, data flows from various sources, machines, sensors, enterprise systems, and more. A [Unified Namespace (UNS)](/solutions/uns/) brings all this data into a central hub. However, centralizing data isn't enough to truly call it a UNS. It's not just about aggregating information. A true UNS goes beyond being a data repository; it organizes, structures, and contextualizes that data, transforming it into something valuable and actionable for your business.
+In manufacturing, data flows from various sources, machines, sensors, enterprise systems, and more. A [Unified Namespace (UNS)](/use-cases/uns/) brings all this data into a central hub. However, centralizing data isn't enough to truly call it a UNS. It's not just about aggregating information. A true UNS goes beyond being a data repository; it organizes, structures, and contextualizes that data, transforming it into something valuable and actionable for your business.
 
 <!--more-->
 

diff --git a/src/blog/2025/01/mqtt-frontrunner-for-uns.md b/src/blog/2025/01/mqtt-frontrunner-for-uns.md
@@ -19,7 +19,7 @@ Choosing the right broker for your UNS is crucial. It must support real-time dat
 
 In this first part of our series, we’ll explain why MQTT is the standout choice for UNS implementations. With its focus on lightweight, real-time messaging and robust reliability, MQTT delivers the performance IIoT environments demand, making it the perfect fit for a future-proof, scalable UNS.
 
-The [Unified Namespace (UNS)](/solutions/uns/) is a data architecture (not just a tool or new technology) that centralizes and organizes data from various sources into a single, unified structure. It eliminates data silos by providing a standardized way to represent, access, and share information across different devices, systems, and services. For more information on what is UNS, read our article: [Introduction to the Unified Namespace](/blog/2023/12/introduction-to-unified-namespace/).
+The [Unified Namespace (UNS)](/use-cases/uns/) is a data architecture (not just a tool or new technology) that centralizes and organizes data from various sources into a single, unified structure. It eliminates data silos by providing a standardized way to represent, access, and share information across different devices, systems, and services. For more information on what is UNS, read our article: [Introduction to the Unified Namespace](/blog/2023/12/introduction-to-unified-namespace/).
 
 When choosing a broker for your UNS, it's crucial to consider how well the selected broker fits the specific requirements of your IIoT environment, including the types of devices and systems involved, as well as factors like scalability, reliability, and ease of integration. Several options are available alongside MQTT, including [AMQP](/node-red/protocol/amqp/), [Kafka](/blog/2024/03/using-kafka-with-node-red/), and cloud message brokers like AWS Kinesis and GCP Pub/Sub. While these alternatives offer unique features, MQTT stands out, and we’ll explain why later in this article. But If you’re interested in a brief overview of why these alternatives are not the best fit for UNS, check out our article: [Unified Namespace: What Broker to Use?](/blog/2024/01/unified-namespace-what-broker/)