diff --git a/src/blog/2023/03/comparing-node-red-dashboards.md b/src/blog/2023/03/comparing-node-red-dashboards.md index 1ba7213036..92653e433d 100644 --- a/src/blog/2023/03/comparing-node-red-dashboards.md +++ b/src/blog/2023/03/comparing-node-red-dashboards.md @@ -22,7 +22,7 @@ Dashboards are a great feature of Node-RED, allowing you to easily expose data v

UPDATE: Since this article was published, it's worth noting a couple of important updates:

@@ -175,7 +175,7 @@ After using FlexDash over the past couple of weeks and finding it to be already ### Dashboard - third place -***Important Update: New Generation of Node-RED Dashboard Released:*** *A new generation of the outdated and unmaintained Node-RED Dashboard has been released to replace it. Introducing [Node-RED Dashboard 2.0](https://dashboard.flowfuse.com/), built on Vue.js, offering significantly more versatility than its predecessor. This new dashboard, managed by FlowFuse, is designed to allow full customization, addressing the limitations of the previous version.* +***Important Update: New Generation of Node-RED Dashboard Released:*** *A new generation of the outdated and unmaintained Node-RED Dashboard has been released to replace it. Introducing [Node-RED Dashboard 2.0](/platform/dashboard/), built on Vue.js, offering significantly more versatility than its predecessor. This new dashboard, managed by FlowFuse, is designed to allow full customization, addressing the limitations of the previous version.* *Node-RED Dashboard 2.0 retains most of the widgets and concepts from the old version, so transitioning from Node-RED Dashboard 1.0 to 2.0 is easy. For a full feature comparison you can check out the [Migration Guide](https://dashboard.flowfuse.com/user/migration.html). diff --git a/src/blog/2023/05/chatgpt-nodered-fcn-node.md b/src/blog/2023/05/chatgpt-nodered-fcn-node.md index 39183802c3..58736f71f1 100644 --- a/src/blog/2023/05/chatgpt-nodered-fcn-node.md +++ b/src/blog/2023/05/chatgpt-nodered-fcn-node.md @@ -82,7 +82,7 @@ Great news! You no longer need to manage OpenAI API keys or configure ChatGPT no Available on FlowFuse Cloud, the Assistant offers: - **Quick Function Node Creation**: Add function nodes to your flow without dragging from the palette -- **In-line Code Generation**: Generate JavaScript code for function nodes, JSON for JSON editors, and Vue.js for FlowFuse Dashboard ui-template widgets +- **In-line Code Generation**: Generate JavaScript code for function nodes, JSON for JSON editors, and Vue.js for [FlowFuse Dashboard](/platform/dashboard/) ui-template widgets - **Flow Explainer**: Select nodes and click "Explain Flows" to understand what they do FlowFuse Assistant helps developers work faster and smarter with Node-RED. [Start your free trial](https://app.flowfuse.com/account/create) to experience AI-powered Node-RED development on FlowFuse Cloud. \ No newline at end of file diff --git a/src/blog/2023/05/community-news-05.md b/src/blog/2023/05/community-news-05.md index d487be180b..1630534fe2 100644 --- a/src/blog/2023/05/community-news-05.md +++ b/src/blog/2023/05/community-news-05.md @@ -21,7 +21,7 @@ Welcome to the FlowFuse newsletter for May 2023, a monthly roundup of what’s b Our monthly Node-RED AMA session will have a special focus on debugging. Nick and Rob will lead us through some useful debug workflows to show how they approach debugging Node-RED applications. During the live coding sessions there will be opportunities for attendees to ask questions in real-time. Join us to learn from the experts on the tips and tricks for debugging Node-RED flows. ### Getting Started with Node-RED Dashboard -How can you use Node-RED to create dashboards and interactive graphs of your data? The answer is the Node-RED Dashboard node, the most popular node in the Node-RED community. In this webinar, Rob Marcer will take you through the steps of how to get started with the Node-RED Dashboard. [Register today](/webinars/2023/getting-started-nodered-dashboard/). +How can you use Node-RED to create dashboards and interactive graphs of your data? The answer is the [Node-RED Dashboard](/platform/dashboard/) node, the most popular node in the Node-RED community. In this webinar, Rob Marcer will take you through the steps of how to get started with the Node-RED Dashboard. [Register today](/webinars/2023/getting-started-nodered-dashboard/). ## From our Blog diff --git a/src/blog/2023/05/persisting-chart-data-in-node-red.md b/src/blog/2023/05/persisting-chart-data-in-node-red.md index fb0136cc1e..bb3fbe08c5 100644 --- a/src/blog/2023/05/persisting-chart-data-in-node-red.md +++ b/src/blog/2023/05/persisting-chart-data-in-node-red.md @@ -20,7 +20,7 @@ One of the most useful features of Dashboard 1 is the ability to store historic

UPDATE: Since this article was published, Node-RED Dashboard (1.0) has been deprecated.

-

Instead, it is recommended to use FlowFuse Dashboard (Dashboard 2.0) which is a more modern and feature-rich dashboard solution for Node-RED.

+

Instead, it is recommended to use FlowFuse Dashboard (Dashboard 2.0) which is a more modern and feature-rich dashboard solution for Node-RED.

### The Importance of Persisting Chart Data diff --git a/src/blog/2023/10/blueprints.md b/src/blog/2023/10/blueprints.md index e9cfaa4d6b..2bf75487d5 100644 --- a/src/blog/2023/10/blueprints.md +++ b/src/blog/2023/10/blueprints.md @@ -25,7 +25,7 @@ All our FlowFuse Cloud users can select a Blueprint directly while creating a ne ## The first three Blueprints -In the coming weeks, we'll be releasing a multitude of blueprints tailored for diverse use cases. However, we decided to start with with three foundational manufacturing applications designed with the [Node-RED Dashboard 2.0](https://dashboard.flowfuse.com/). +In the coming weeks, we'll be releasing a multitude of blueprints tailored for diverse use cases. However, we decided to start with with three foundational manufacturing applications designed with the [Node-RED Dashboard 2.0](/platform/dashboard/). ### ANDON Operator Terminal The Andon Operator Terminal is designed to be at the start of an Andon process, allowing end-users to report any issues with the cell to a supervisor. diff --git a/src/blog/2023/12/flowfuse-year-review-2023.md b/src/blog/2023/12/flowfuse-year-review-2023.md index 31fdab39f6..8c2b09910f 100644 --- a/src/blog/2023/12/flowfuse-year-review-2023.md +++ b/src/blog/2023/12/flowfuse-year-review-2023.md @@ -24,7 +24,7 @@ On the product side: Growth in adoption of the FlowFuse platform has been tremen 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). +Further, this year we’ve started [Dashboard 2.0](/platform/dashboard/). 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). With the product improvements to FlowFuse, we’ve empowered large audiences to try and adopt the product. We’ve seen adoption in many areas: diff --git a/src/blog/2024/01/import-a-file.md b/src/blog/2024/01/import-a-file.md index b8a5bac415..6567e8a124 100644 --- a/src/blog/2024/01/import-a-file.md +++ b/src/blog/2024/01/import-a-file.md @@ -26,7 +26,7 @@ Furthermore, on the management layer of most companies, Excel and Google Sheets ![csv dashboard](./images/csv-dashboard.png) -This simple flow allows the user to visualize data from a CSV in the Node-RED Dashboard. The button then allows the user to initiate a request to send the data to the next step. This next step could be anything from loading into a SQL database to saving it. +This simple flow allows the user to visualize data from a CSV in the [Node-RED Dashboard](/platform/dashboard/). The button then allows the user to initiate a request to send the data to the next step. This next step could be anything from loading into a SQL database to saving it. ### Instructions ### 1. Install Node-RED Dashboard 2.0. Follow these [instructions](/blog/2024/03/dashboard-getting-started/) to install. diff --git a/src/blog/2024/03/looking-towards-node-red-4.md b/src/blog/2024/03/looking-towards-node-red-4.md index 87ac9183e6..0c6acae056 100644 --- a/src/blog/2024/03/looking-towards-node-red-4.md +++ b/src/blog/2024/03/looking-towards-node-red-4.md @@ -69,7 +69,7 @@ However, in that example, the MQTT node's broker configuration would be locked t We're making it possible to expose the choice of a configuration node in the Subflow properties - so each instance can be customised even further. -Another common use for this will be with Node-RED Dashboard - which uses config nodes to set the location of a widget. With Node-RED today, you cannot really use dashboard nodes inside subflows as you end up with multiple copies of the widgets all packed into the same group. With this update, you'll be able to configure the subflow instance with exactly what dashboard group to place its contents into. +Another common use for this will be with [Node-RED Dashboard](/platform/dashboard/) - which uses config nodes to set the location of a widget. With Node-RED today, you cannot really use dashboard nodes inside subflows as you end up with multiple copies of the widgets all packed into the same group. With this update, you'll be able to configure the subflow instance with exactly what dashboard group to place its contents into. ### Updated JSONata diff --git a/src/blog/2024/04/building-an-admin-panel-in-node-red-with-dashboard-2.md b/src/blog/2024/04/building-an-admin-panel-in-node-red-with-dashboard-2.md index e7727b0f63..8c7e93de9e 100644 --- a/src/blog/2024/04/building-an-admin-panel-in-node-red-with-dashboard-2.md +++ b/src/blog/2024/04/building-an-admin-panel-in-node-red-with-dashboard-2.md @@ -65,7 +65,7 @@ meta: tldr: "This guide shows how to build a secure admin-only page in Node-RED Dashboard 2.0 using FlowFuse user authentication and the Multiuser Addon. By storing admin usernames in global context and wiring a ui-event through a switch node to a ui-control widget, you can dynamically show or hide the admin page based on the logged-in user's role, while keeping the page hidden by default for all other users." --- -Managing and analyzing increasing amounts of data becomes crucial for organizations. Dashboard 2.0 and Node-RED help organizations access the data, normalize it, and visualize it. But what about controlling who can access what data? That's where an admin-only page comes in. Now With Node-RED Dashboard 2.0, we can also create robust and secure admin-only pages easily. In this guide, we'll provide you with step-by-step instructions to Build an Admin-only page with Node-RED Dashboard 2.0. +Managing and analyzing increasing amounts of data becomes crucial for organizations. Dashboard 2.0 and Node-RED help organizations access the data, normalize it, and visualize it. But what about controlling who can access what data? That's where an admin-only page comes in. Now With [Node-RED Dashboard 2.0](/platform/dashboard/), we can also create robust and secure admin-only pages easily. In this guide, we'll provide you with step-by-step instructions to Build an Admin-only page with Node-RED Dashboard 2.0. diff --git a/src/blog/2024/04/displaying-logged-in-users-on-dashboard.md b/src/blog/2024/04/displaying-logged-in-users-on-dashboard.md index f637eaebdc..6b6c9f9fee 100644 --- a/src/blog/2024/04/displaying-logged-in-users-on-dashboard.md +++ b/src/blog/2024/04/displaying-logged-in-users-on-dashboard.md @@ -69,7 +69,7 @@ If you're new to Dashboard 2.0, refer to our blog post [Getting Started with Das ## Enabling FlowFuse User Authentication -Before we display logged-in user data on the dashboard, first we need to set up a login mechanism with FlowFuse for the dashboard. This simplifies securing Node-RED Dashboards and provides contextual user data within the Dashboard itself for who is logged in. +Before we display logged-in user data on the dashboard, first we need to set up a login mechanism with FlowFuse for the dashboard. This simplifies securing [Node-RED Dashboard](/platform/dashboard/)s and provides contextual user data within the Dashboard itself for who is logged in. 1. Navigate to the Instance "settings". 2. Select the "Security" tab. diff --git a/src/blog/2024/04/how-to-build-an-application-with-node-red-dashboard-2.md b/src/blog/2024/04/how-to-build-an-application-with-node-red-dashboard-2.md index f6ae3d9c5b..7111c0683b 100644 --- a/src/blog/2024/04/how-to-build-an-application-with-node-red-dashboard-2.md +++ b/src/blog/2024/04/how-to-build-an-application-with-node-red-dashboard-2.md @@ -78,7 +78,7 @@ If you're new to Dashboard 2.0, refer to our blog post [Getting Started with Das ## Installing Flowfuse user addon -The FlowFuse User Addon is a plugin developed for Dashboard 2.0, that levereges the FlowFuse API to access logged in user's information at Dashboard 2.0. For detailed information refer to the [Exploring the FlowFuse User Addon](/blog/2024/04/displaying-logged-in-users-on-dashboard/#exploring-the-flowfuse-user-addon) and make sure to install it. +The FlowFuse User Addon is a plugin developed for [Dashboard 2.0](/platform/dashboard/), that levereges the FlowFuse API to access logged in user's information at Dashboard 2.0. For detailed information refer to the [Exploring the FlowFuse User Addon](/blog/2024/04/displaying-logged-in-users-on-dashboard/#exploring-the-flowfuse-user-addon) and make sure to install it. Before you begin the application development process, please make sure that FlowFuse user authentication is enabled. This feature adds a layer of security to your application with a login page. By combining the FlowFuse user addon with user authentication, we gain access to the logged in user's data within our application. For more information on FlowFuse user authentication, refer to the [documentation](/docs/user/instance-settings/#flowfuse-user-authentication) and make sure that it is enabled. diff --git a/src/blog/2024/04/node-red-architecture.md b/src/blog/2024/04/node-red-architecture.md index d9259773b8..a81b5bd286 100644 --- a/src/blog/2024/04/node-red-architecture.md +++ b/src/blog/2024/04/node-red-architecture.md @@ -41,7 +41,7 @@ At the top, we find the Enterprise Layer. This can signify either cloud services ## Applications Across Factory Layers -**Shopfloor:** Node-RED's versatility shines at the shopfloor level, where it’s typically installed on a variety of industrial devices. A prominent application is the development of simple Human-Machine Interfaces (HMIs) using the [Dashboard module](https://dashboard.flowfuse.com/), which enables operators to interact with the machines visually and intuitively. Additionally, Node-RED is instrumental in data acquisition tasks, where it can gather, process, and interpret data from sensors and actuators in real-time. This capability allows for the monitoring of production processes, predictive maintenance, and the triggering of automated workflows in response to specific conditions or anomalies detected on the shop floor. +**Shopfloor:** Node-RED's versatility shines at the shopfloor level, where it’s typically installed on a variety of industrial devices. A prominent application is the development of simple Human-Machine Interfaces (HMIs) using the [Dashboard module](/platform/dashboard/), which enables operators to interact with the machines visually and intuitively. Additionally, Node-RED is instrumental in data acquisition tasks, where it can gather, process, and interpret data from sensors and actuators in real-time. This capability allows for the monitoring of production processes, predictive maintenance, and the triggering of automated workflows in response to specific conditions or anomalies detected on the shop floor. **Edge:** At the edge level, Node-RED plays a pivotal role in harmonizing the divide between Operational Technology (OT) and Information Technology (IT). Its gateway functionalities are not only integral in facilitating the flow of data between the shopfloor devices and the enterprise-level systems but also it is at this juncture that plant-wide Key Performance Indicators (KPIs) are generated. These KPIs, aggregated from various data points across the production line, are essential for operational oversight and strategic decision-making. Edge-level Node-RED instances can run local analytics and manage alarms. diff --git a/src/blog/2024/05/exploring-node-red-dashboard-2-widgets.md b/src/blog/2024/05/exploring-node-red-dashboard-2-widgets.md index 8d0c3bfc38..47c859b511 100644 --- a/src/blog/2024/05/exploring-node-red-dashboard-2-widgets.md +++ b/src/blog/2024/05/exploring-node-red-dashboard-2-widgets.md @@ -15,7 +15,7 @@ cta: description: FlowFuse gives you everything you need to build, secure, and scale Node-RED Dashboard applications, with multi-user support, authentication, and production-ready deployment built in. --- -This guide delves into Node-RED Dashboard 2.0 widgets. It is a guide on how to build a Dashboard application, and will cover many of the widgets available today. +This guide delves into [Node-RED Dashboard 2.0](/platform/dashboard/) widgets. It is a guide on how to build a Dashboard application, and will cover many of the widgets available today. diff --git a/src/blog/2024/06/dashboard-1-deprecated.md b/src/blog/2024/06/dashboard-1-deprecated.md index 7896b0ac9b..aaa43d4c0e 100644 --- a/src/blog/2024/06/dashboard-1-deprecated.md +++ b/src/blog/2024/06/dashboard-1-deprecated.md @@ -18,7 +18,7 @@ tldr: "Node-RED Dashboard (Dashboard 1.0) has been formally deprecated, with no Dave Conway-Jones, the lead maintainer of Node-RED Dashboard, has [just announced](https://discourse.nodered.org/t/node-red-dashboard-v1-deprecation-notice/89006) that Node-RED Dashboard has been formally deprecated, meaning there will be no further development activity on the project. -[FlowFuse Dashboard](https://dashboard.flowfuse.com/) (also known as Node-RED Dashboard 2.0) is a natural successor to Node-RED Dashboard, and in this article, we detail what FlowFuse Dashboard offers, and how you can get started. +[FlowFuse Dashboard](/platform/dashboard/) (also known as Node-RED Dashboard 2.0) is a natural successor to Node-RED Dashboard, and in this article, we detail what FlowFuse Dashboard offers, and how you can get started. diff --git a/src/blog/2024/07/building-on-flowfuse-devices.md b/src/blog/2024/07/building-on-flowfuse-devices.md index 7b4cb59b19..36fa9d0a18 100644 --- a/src/blog/2024/07/building-on-flowfuse-devices.md +++ b/src/blog/2024/07/building-on-flowfuse-devices.md @@ -73,7 +73,7 @@ Given the above architecture, let's take a look at the relevant FlowFuse offerin ![Lineup of each of the FlowFuse offerings](./images/ff-ecosystem-lineup.png){data-zoomable} - **Node-RED:** Low-code, drag-and-drop integration platform. Here we'd be using it in multiple places to read and parse data from the hardware, define the application logic, conduct analysis and provide alerting. -- **FlowFuse Dashboard:** An add-on to Node-RED for building interactive user interfaces and dashboards. We use this here to provide visual feedback on local Dashboards for some devices, as well as at the Planet-level to provide an at-a-glance view of our plant. +- **[FlowFuse Dashboard](/platform/dashboard/):** An add-on to Node-RED for building interactive user interfaces and dashboards. We use this here to provide visual feedback on local Dashboards for some devices, as well as at the Planet-level to provide an at-a-glance view of our plant. - **FlowFuse:** Centralized platform that provides a single entry point to manage all of your Node-RED applications and deployments, from your device inetrgators, through to your dashboards. FlowFuse provides role-based access control out of the box, so we can easily control who has access to flows, Dashboards and other configurations. - **FlowFuse Device Agent:** Installed onto the relevant servers and hardware, this links you directly, and securely to FlowFuse. Here, we're deploying it to multiple pieces of machinery, as well as local servers, such that we can easily manage (deploy, upgrade, debug) all of those Node-RED deployments remotely from FlowFuse. - **FlowFuse Project Nodes:** A small collection of nodes for Node-RED, running on FlowFuse, that provide communication over a secure (MQTT-based) connection between devices (our Node-RED deployments on our hardware in this case) and our hosted instances of Node-RED on FlowFuse. Extremely useful for reporting live sensor data back to FlowFuse for analysis, and for reporting information back to our devices. \ No newline at end of file diff --git a/src/blog/2024/07/dashboard-new-charts.md b/src/blog/2024/07/dashboard-new-charts.md index f43d144c6a..b23650573c 100644 --- a/src/blog/2024/07/dashboard-new-charts.md +++ b/src/blog/2024/07/dashboard-new-charts.md @@ -12,7 +12,7 @@ tags: - dashboard --- -It's been a while coming, but we've finally introduced a new set of chart types to FlowFuse Dashboard. We've added Pie, Donut and Grouped (Stacks and Side-by-Side) Bar charts to the UI Chart node. We've also shipped plenty of other improvements and fixes in this release, so let's dive in. +It's been a while coming, but we've finally introduced a new set of chart types to [FlowFuse Dashboard](/platform/dashboard/). We've added Pie, Donut and Grouped (Stacks and Side-by-Side) Bar charts to the UI Chart node. We've also shipped plenty of other improvements and fixes in this release, so let's dive in. diff --git a/src/blog/2024/08/comparing-dashboard-2-with-uibuilder.md b/src/blog/2024/08/comparing-dashboard-2-with-uibuilder.md index ad641d8a94..d5b1aec606 100644 --- a/src/blog/2024/08/comparing-dashboard-2-with-uibuilder.md +++ b/src/blog/2024/08/comparing-dashboard-2-with-uibuilder.md @@ -20,7 +20,7 @@ cta: tldr: "FlowFuse Dashboard (Dashboard 2.0) and UI-Builder are the two most popular Node-RED dashboard solutions after the deprecation of Node-RED Dashboard 1.0. FlowFuse Dashboard offers an easier low-code setup, a guided migration path from Dashboard 1.0, and active development, while UI-Builder requires deeper coding knowledge and a full rebuild when migrating." --- -When choosing a dashboard solution for Node-RED, two popular options are FlowFuse Dashboard (also known as Dashboard 2.0) and UI-Builder. This article compares these tools across several key areas, including installation, ease of use, development activity, and customizability, to help you decide which one best suits your needs. +When choosing a dashboard solution for Node-RED, two popular options are [FlowFuse Dashboard](/platform/dashboard/) (also known as Dashboard 2.0) and UI-Builder. This article compares these tools across several key areas, including installation, ease of use, development activity, and customizability, to help you decide which one best suits your needs. diff --git a/src/blog/2024/08/customise-theming-in-your-dashboards.md b/src/blog/2024/08/customise-theming-in-your-dashboards.md index b92b0b0247..2b3dfd7c8e 100644 --- a/src/blog/2024/08/customise-theming-in-your-dashboards.md +++ b/src/blog/2024/08/customise-theming-in-your-dashboards.md @@ -62,7 +62,7 @@ meta: tldr: "FlowFuse Dashboard now supports deep visual customization including custom headers, themes, and layout modifications. Using Teleports inside the ui-template node, you can inject custom elements into specific dashboard areas without complex CSS. This guide covers adding header buttons, custom logos, modifying color themes, and adjusting group and page padding." --- -A recent release of FlowFuse Dashboard (Dashboard 2.0) has taken customization to the next level. +A recent release of [FlowFuse Dashboard](/platform/dashboard/) (Dashboard 2.0) has taken customization to the next level. diff --git a/src/blog/2024/10/exploring-flowfuse-security-features.md b/src/blog/2024/10/exploring-flowfuse-security-features.md index a727dad0d4..a3193140dd 100644 --- a/src/blog/2024/10/exploring-flowfuse-security-features.md +++ b/src/blog/2024/10/exploring-flowfuse-security-features.md @@ -111,7 +111,7 @@ With Instance Protection Mode activated, team members can still view flows, but HTTP is one of the most widely used protocols for enabling communication between different applications and services. In Node-RED, you can quickly create these APIs using HTTP-In nodes, which allow for communication. However, while this convenience is excellent, ensuring that only authorized users can access your APIs is essential. -FlowFuse provides robust options for securing all HTTP endpoints served by Flow and the Node-RED Dashboard. To manage this, each instance has a dedicated interface that you can access by navigating to **your instance -> Settings -> Security**. Here, you’ll find several options for securing your APIs: +FlowFuse provides robust options for securing all HTTP endpoints served by Flow and the [Node-RED Dashboard](/platform/dashboard/). To manage this, each instance has a dedicated interface that you can access by navigating to **your instance -> Settings -> Security**. Here, you’ll find several options for securing your APIs: ![Options to enable authentication for the HTTP endpoints created in the Node-RED instance](./images/http-api-auth.png){data-zoomable} _Flowfuse: Options to enable authentication for the HTTP endpoints created in the Node-RED instance._ diff --git a/src/blog/2024/11/dashboard-new-group-type-app-icon-and-charts.md b/src/blog/2024/11/dashboard-new-group-type-app-icon-and-charts.md index 7978abb852..c8b5076af1 100644 --- a/src/blog/2024/11/dashboard-new-group-type-app-icon-and-charts.md +++ b/src/blog/2024/11/dashboard-new-group-type-app-icon-and-charts.md @@ -12,7 +12,7 @@ tags: - dashboard --- -It has been one of the most requested features for FlowFuse Dashboard, and is now available in its first iteration. It is now possible to resize and move groups in the Dashboard itself using the new "Edit Layout" feature. That's not all though, we've added a new "Spacer" widget to assist with layouts, added improvements to the rendering of charts and plenty more. +It has been one of the most requested features for [FlowFuse Dashboard](/platform/dashboard/), and is now available in its first iteration. It is now possible to resize and move groups in the Dashboard itself using the new "Edit Layout" feature. That's not all though, we've added a new "Spacer" widget to assist with layouts, added improvements to the rendering of charts and plenty more. diff --git a/src/blog/2024/12/publishing-modbus-data-to-uns.md b/src/blog/2024/12/publishing-modbus-data-to-uns.md index d908c99fb8..a471bba9d5 100644 --- a/src/blog/2024/12/publishing-modbus-data-to-uns.md +++ b/src/blog/2024/12/publishing-modbus-data-to-uns.md @@ -322,7 +322,7 @@ _FlowFuse topic hierarchy interface showing UNS structure_ Once your flow is successfully publishing data, you've established your Unified Namespace. Other systems can now subscribe to these MQTT topics to consume the data for: - **Cloud analytics platforms** for historical analysis and reporting -- **[FlowFuse Dashboard](https://dashboard.flowfuse.com/)** for real-time monitoring and visualization +- **[FlowFuse Dashboard](/platform/dashboard/)** for real-time monitoring and visualization - **Predictive maintenance systems** for equipment health monitoring - **Business intelligence tools** for operational insights - **Alert and notification systems** for automated responses to threshold breaches diff --git a/src/blog/2025/04/build-manufacturing-oee-dashboard.md b/src/blog/2025/04/build-manufacturing-oee-dashboard.md index 2bf846abe9..853b068407 100644 --- a/src/blog/2025/04/build-manufacturing-oee-dashboard.md +++ b/src/blog/2025/04/build-manufacturing-oee-dashboard.md @@ -54,7 +54,7 @@ tldr: "Build a manufacturing OEE dashboard in FlowFuse: generate simulated produ --- In [Part 1](/blog/2025/04/what-is-an-oee-dashboard/), we explored the fundamentals of OEE, outlined a basic design of the dashboard, and identified the key elements to include in the OEE dashboard. -In this second part, we will focus on building the OEE dashboard interface using [FlowFuse Dashboard](https://dashboard.flowfuse.com/) (Node-RED Dashboard 2.0) and FlowFuse, utilizing simulated production and downtime data, the same kind of data you'd track for torque, weld cycle time, or paint throughput on an [automotive](/industries/automotive/) line. +In this second part, we will focus on building the OEE dashboard interface using [FlowFuse Dashboard](/platform/dashboard/) (Node-RED Dashboard 2.0) and FlowFuse, utilizing simulated production and downtime data, the same kind of data you'd track for torque, weld cycle time, or paint throughput on an [automotive](/industries/automotive/) line. diff --git a/src/blog/2025/04/design-and-scale-oee-dashboard.md b/src/blog/2025/04/design-and-scale-oee-dashboard.md index e8c193f1b8..25311c0600 100644 --- a/src/blog/2025/04/design-and-scale-oee-dashboard.md +++ b/src/blog/2025/04/design-and-scale-oee-dashboard.md @@ -128,7 +128,7 @@ _OEE Dashboard broken layout on smaller screen_ ### To make the dashboard truly responsive: -1. Open the **Page Settings** in the Node-RED Dashboard editor. +1. Open the **Page Settings** in the [Node-RED Dashboard](/platform/dashboard/) editor. 2. Scroll down to locate the **Breakpoint Settings Table** for different device sizes. 3. Identify the **Tablet** row in the table. 4. Notice that the current Tablet column count is set to `9`. diff --git a/src/blog/2025/05/displaying-embeded-webpages-on-node-red-dashboard.md b/src/blog/2025/05/displaying-embeded-webpages-on-node-red-dashboard.md index afa50db11a..f7ba67ec90 100644 --- a/src/blog/2025/05/displaying-embeded-webpages-on-node-red-dashboard.md +++ b/src/blog/2025/05/displaying-embeded-webpages-on-node-red-dashboard.md @@ -32,7 +32,7 @@ Embedding external content into your FlowFuse dashboard is straightforward and f ### Prerequisites -Before you begin embedding webpages on FlowFuse Dashboard, make sure you have the following: +Before you begin embedding webpages on [FlowFuse Dashboard](/platform/dashboard/), make sure you have the following: - **Running FlowFuse Instance:** Make sure you have a FlowFuse instance set up and running. If you don't have an account, check out our [free trial](https://app.flowfuse.com/account/create). - **FlowFuse Dashboard:** Ensure you have [FlowFuse Dashboard](https://flows.nodered.org/node/@flowfuse/node-red-dashboard) (also known as Node-RED Dashboard 2.0 in the community) installed and properly configured on your instance. diff --git a/src/blog/2025/06/building-andon-task-manager-dashboard-with-ff.md b/src/blog/2025/06/building-andon-task-manager-dashboard-with-ff.md index b48721dce3..24076efdfa 100644 --- a/src/blog/2025/06/building-andon-task-manager-dashboard-with-ff.md +++ b/src/blog/2025/06/building-andon-task-manager-dashboard-with-ff.md @@ -14,7 +14,7 @@ In [Part 1](/blog/2025/05/building-andon-task-manager-with-ff/), we introduced t -In this part 2, we move from planning to implementation. The focus now shifts to building the actual system using [FlowFuse Dashboard](https://dashboard.flowfuse.com) (Node-RED Dashboard 2.0), hosted on the FlowFuse platform. We will begin by developing the **Lines view** for regular users, along with a line selection menu. The Department View and Admin interface will follow in a later part of the series. +In this part 2, we move from planning to implementation. The focus now shifts to building the actual system using [FlowFuse Dashboard](/platform/dashboard/) (Node-RED Dashboard 2.0), hosted on the FlowFuse platform. We will begin by developing the **Lines view** for regular users, along with a line selection menu. The Department View and Admin interface will follow in a later part of the series. ## Getting Started diff --git a/src/blog/2025/06/flowfuse-forms-easy-data-collection-factory-floor.md b/src/blog/2025/06/flowfuse-forms-easy-data-collection-factory-floor.md index e7bf92de39..3e8e970126 100644 --- a/src/blog/2025/06/flowfuse-forms-easy-data-collection-factory-floor.md +++ b/src/blog/2025/06/flowfuse-forms-easy-data-collection-factory-floor.md @@ -14,7 +14,7 @@ It's often a pain to get important data from the factory floor. Things like doin -This article will show you an easy way to gather data via a form entry. We'll look at how forms in FlowFuse Dashboard can make collecting data from factory workers much simpler. You'll learn how to build useful forms that connects your team's knowledge directly to your industrial processes. As a practical example, we'll walk you through building a solution to digitize production recipe updates, showing you exactly how to implement it. +This article will show you an easy way to gather data via a form entry. We'll look at how forms in [FlowFuse Dashboard](/platform/dashboard/) can make collecting data from factory workers much simpler. You'll learn how to build useful forms that connects your team's knowledge directly to your industrial processes. As a practical example, we'll walk you through building a solution to digitize production recipe updates, showing you exactly how to implement it. ## Prerequisites diff --git a/src/blog/2025/06/shop-floor-kpis-for-mes.md b/src/blog/2025/06/shop-floor-kpis-for-mes.md index 79dd94180b..6447ab9415 100644 --- a/src/blog/2025/06/shop-floor-kpis-for-mes.md +++ b/src/blog/2025/06/shop-floor-kpis-for-mes.md @@ -129,7 +129,7 @@ WHERE machine_id = $machine_id 12. **Deploy** the flow to continuously calculate and output the Machine Downtime Percentage in real time. -After deploying the flow, observe the debug sidebar on the right. You'll see the calculated machine downtime percentage being continuously printed. To present this data visually, leverage [Flowfuse Dashboard](https://dashboard.flowfuse.com). +After deploying the flow, observe the debug sidebar on the right. You'll see the calculated machine downtime percentage being continuously printed. To present this data visually, leverage [Flowfuse Dashboard](/platform/dashboard/). ![Downtime printed on debug panel](./images/downtime.png){data-zoomable} _Downtime printed on debug panel_ diff --git a/src/blog/2025/06/structuring-storing-data-mes-integration.md b/src/blog/2025/06/structuring-storing-data-mes-integration.md index 0d070641f4..64a97c6431 100644 --- a/src/blog/2025/06/structuring-storing-data-mes-integration.md +++ b/src/blog/2025/06/structuring-storing-data-mes-integration.md @@ -170,7 +170,7 @@ Plus, FlowFuse **connects** to big Data Lakes and Cloud Storage services like [A Once your factory data is effectively structured, validated, and routed by FlowFuse to the right place, it becomes an incredibly powerful asset for your MES. -FlowFuse doesn't just manage your data; it also empowers you to easily build the user interface (UI) for your MES. You can create insightful dashboards and industrial applications using a no-code, drag-and-drop approach with components from [FlowFuse Dashboard](https://dashboard.flowfuse.com/). This allows you to design the screens operators use to visualize critical information and control processes, all built upon the reliable data foundation you've established. +FlowFuse doesn't just manage your data; it also empowers you to easily build the user interface (UI) for your MES. You can create insightful dashboards and industrial applications using a no-code, drag-and-drop approach with components from [FlowFuse Dashboard](/platform/dashboard/). This allows you to design the screens operators use to visualize critical information and control processes, all built upon the reliable data foundation you've established. ## Final Thought diff --git a/src/blog/2025/07/flowfuse-ai-assistant-better-node-red-manufacturing.md b/src/blog/2025/07/flowfuse-ai-assistant-better-node-red-manufacturing.md index baba6ef4b8..45e47b16d3 100644 --- a/src/blog/2025/07/flowfuse-ai-assistant-better-node-red-manufacturing.md +++ b/src/blog/2025/07/flowfuse-ai-assistant-better-node-red-manufacturing.md @@ -68,7 +68,7 @@ _FlowFuse Expert creating realistic test data for manufacturing dashboards, comp ## Building Custom Dashboards Without Web Development -[FlowFuse Dashboard](https://dashboard.flowfuse.com) widgets cover most UI needs, but manufacturing can often demand more. Custom visualizations for specific KPIs can be build in Dashboard with the ["Template"](https://dashboard.flowfuse.com/nodes/widgets/ui-template) node, where developers can write their own Vue.js templates. +[FlowFuse Dashboard](/platform/dashboard/) widgets cover most UI needs, but manufacturing can often demand more. Custom visualizations for specific KPIs can be build in Dashboard with the ["Template"](https://dashboard.flowfuse.com/nodes/widgets/ui-template) node, where developers can write their own Vue.js templates. Developing custom components to match your HMI design standards takes CSS expertise. Whether you're building new widgets or styling existing ones, you're suddenly in web development territory, far from where most automation engineers want to be. diff --git a/src/blog/2025/07/reading-and-writing-plc-data-using-opc-ua.md b/src/blog/2025/07/reading-and-writing-plc-data-using-opc-ua.md index 9699228f38..9b290c40e2 100644 --- a/src/blog/2025/07/reading-and-writing-plc-data-using-opc-ua.md +++ b/src/blog/2025/07/reading-and-writing-plc-data-using-opc-ua.md @@ -281,7 +281,7 @@ This setup allows you to prepare multiple tag values and write them all at once, You’ve now mastered the fundamentals of OPC UA integration, connecting to servers, browsing tags, and reading or writing data. These core building blocks lay the foundation for powerful industrial automation. -In real deployments, you will want more than Inject nodes and debug panels. With **FlowFuse Dashboard 2.0**, you can build full operator interfaces, live gauges, control buttons, trend charts, fully connected to your OPC UA data. +In real deployments, you will want more than Inject nodes and debug panels. With **[FlowFuse Dashboard](/platform/dashboard/) 2.0**, you can build full operator interfaces, live gauges, control buttons, trend charts, fully connected to your OPC UA data. This guide covered the basics, but OPC UA offers far more. In the next article, we will explore: diff --git a/src/blog/2025/08/advanced-opcua-real-time-subscriptions-alarms-historical-data.md b/src/blog/2025/08/advanced-opcua-real-time-subscriptions-alarms-historical-data.md index c13c16b698..189d3c0b83 100644 --- a/src/blog/2025/08/advanced-opcua-real-time-subscriptions-alarms-historical-data.md +++ b/src/blog/2025/08/advanced-opcua-real-time-subscriptions-alarms-historical-data.md @@ -59,7 +59,7 @@ To create your first subscription: 1. Drag an Inject node onto your canvas. This will trigger the subscription to start. -> Note: This article uses Inject nodes for manual triggering to illustrate key concepts. In production, it is advisable to create interactive dashboards with FlowFuse Dashboard to enable effective monitoring and control. For more information on designing operator interfaces, please refer to [this article](/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red/). +> Note: This article uses Inject nodes for manual triggering to illustrate key concepts. In production, it is advisable to create interactive dashboards with [FlowFuse Dashboard](/platform/dashboard/) to enable effective monitoring and control. For more information on designing operator interfaces, please refer to [this article](/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red/). 2. Add an OpcUa-Item node. Double-click it and enter the NodeId of the tag you want to monitor, like `ns=2;i=2007`. Select the correct data type for your tag. diff --git a/src/blog/2025/09/integrating-lorawan-with-flowfuse-node-red.md b/src/blog/2025/09/integrating-lorawan-with-flowfuse-node-red.md index 638894a83c..09279ba0d5 100644 --- a/src/blog/2025/09/integrating-lorawan-with-flowfuse-node-red.md +++ b/src/blog/2025/09/integrating-lorawan-with-flowfuse-node-red.md @@ -179,7 +179,7 @@ In the image below, you can see FlowFuse sending and processing the downlink mes Next, you can store this data in a database. With FlowFuse, a managed PostgreSQL database is already provided, so you do not need to install or configure one manually. FlowFuse also offers a Query node that is automatically configured for your instance. Inside the Query node, you can use FlowFuse Expert, which allows you to write natural language prompts instead of SQL queries. The assistant will generate SQL automatically based on your table schema. -For a complete guide on storing and visualizing data, see the article on [Building Historical Data Dashboards with FlowFuse Tables](/blog/2025/08/time-series-dashboard-flowfuse-postgresql/). It also includes step-by-step instructions for creating dashboards using [FlowFuse Dashboard](https://dashboard.flowfuse.com/), a low-code way to build powerful industrial dashboards that also allows you to send downlink data to devices interactively. +For a complete guide on storing and visualizing data, see the article on [Building Historical Data Dashboards with FlowFuse Tables](/blog/2025/08/time-series-dashboard-flowfuse-postgresql/). It also includes step-by-step instructions for creating dashboards using [FlowFuse Dashboard](/platform/dashboard/), a low-code way to build powerful industrial dashboards that also allows you to send downlink data to devices interactively. With FlowFuse, you get a complete enterprise-grade platform built around visual programming, perfect for production-ready IoT deployments. It adds powerful capabilities like centralized management of Node-RED instances, DevOps tools, snapshots, real-time team collaboration, audit logs, RBAC, SSO, Built mqtt broker and database service and more, all designed to help you scale and manage your applications with ease. diff --git a/src/blog/2025/09/using-modbus-with-flowfuse.md b/src/blog/2025/09/using-modbus-with-flowfuse.md index 169fdf0f1f..e915509b87 100644 --- a/src/blog/2025/09/using-modbus-with-flowfuse.md +++ b/src/blog/2025/09/using-modbus-with-flowfuse.md @@ -130,7 +130,7 @@ Follow these steps to configure and test writing: 4. Deploy the flow and press **Inject**. The Modbus device should update immediately. -**Tip:** Use a **UI input (slider, switch, or numeric box)** from the [FlowFuse Dashboard](https://dashboard.flowfuse.com/) instead of an Inject node for real-time control via a web interface. +**Tip:** Use a **UI input (slider, switch, or numeric box)** from the [FlowFuse Dashboard](/platform/dashboard/) instead of an Inject node for real-time control via a web interface. ## Scaling and Interpreting Values diff --git a/src/blog/2025/10/building-mcp-server-using-flowfuse.md b/src/blog/2025/10/building-mcp-server-using-flowfuse.md index 197e6259a0..dc294b3e27 100644 --- a/src/blog/2025/10/building-mcp-server-using-flowfuse.md +++ b/src/blog/2025/10/building-mcp-server-using-flowfuse.md @@ -243,7 +243,7 @@ Your MCP Tool is now active. When an AI agent invokes it, the connected flow exe #### Example: Scheduling Maintenance for Production Lines -In this example, the flow includes a tool that triggers a POST request to the maintenance system API, which was developed using FlowFuse and the FlowFuse Dashboard. The AI Assistant was then asked to identify which production line was performing the worst and schedule a maintenance task for it. +In this example, the flow includes a tool that triggers a POST request to the maintenance system API, which was developed using FlowFuse and the [FlowFuse Dashboard](/platform/dashboard/). The AI Assistant was then asked to identify which production line was performing the worst and schedule a maintenance task for it. *AI agent scheduling maintenance using an MCP Tool* diff --git a/src/blog/2025/10/node-red-vs-flowfuse.md b/src/blog/2025/10/node-red-vs-flowfuse.md index a6ab737285..079599aa00 100644 --- a/src/blog/2025/10/node-red-vs-flowfuse.md +++ b/src/blog/2025/10/node-red-vs-flowfuse.md @@ -127,7 +127,7 @@ No. Node-RED and FlowFuse are not competitors, they’re complementary. FlowFuse When Node-RED improves, FlowFuse improves too. This is the same dynamic seen in other open-source ecosystems: Linux thrives alongside Red Hat, Kubernetes powers enterprise platforms, and PostgreSQL continues to evolve while vendors provide enterprise features. The open-source project remains free and independent, while the commercial platform adds operational value on top. -FlowFuse also invests back into the ecosystem. A good example is the [FlowFuse Dashboard](https://dashboard.flowfuse.com) (often called Node-RED Dashboard 2.0), which replaced the deprecated original Node-RED Dashboard. By sponsoring and maintaining this project, FlowFuse ensures the community continues to have a modern, supported visualization tool. +FlowFuse also invests back into the ecosystem. A good example is the [FlowFuse Dashboard](/platform/dashboard/) (often called Node-RED Dashboard 2.0), which replaced the deprecated original Node-RED Dashboard. By sponsoring and maintaining this project, FlowFuse ensures the community continues to have a modern, supported visualization tool. And importantly, your flows remain portable. Anything you build in FlowFuse works in plain Node-RED. There is no vendor lock-in. FlowFuse exists to extend Node-RED, not replace it. diff --git a/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md b/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md index a10d85d5e3..5ffd9739ad 100644 --- a/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md +++ b/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md @@ -185,7 +185,7 @@ If your tag belongs to a different scope, click the “+ Add” button at the to ## Getting Started -Before we start, I'd like to show you what I've prepared, a flow where I'm sending commands to the PLC to control the stack light. To interact with it, I've built a nice dashboard using [FlowFuse Dashboard](https://dashboard.flowfuse.com/). Here's a quick demonstration: +Before we start, I'd like to show you what I've prepared, a flow where I'm sending commands to the PLC to control the stack light. To interact with it, I've built a nice dashboard using [FlowFuse Dashboard](/platform/dashboard/). Here's a quick demonstration: diff --git a/src/blog/2025/11/building-hmi-for-equipment-control.md b/src/blog/2025/11/building-hmi-for-equipment-control.md index 06fbff2130..6f1e4a91a5 100644 --- a/src/blog/2025/11/building-hmi-for-equipment-control.md +++ b/src/blog/2025/11/building-hmi-for-equipment-control.md @@ -139,7 +139,7 @@ Once you see live values in the debug panel, your PLC connection is working and ## Step 3: Build Your HMI Dashboard -With your PLC connected, let's create the operator interface using FlowFuse Dashboard, a set of UI nodes that build web-based interfaces without writing HTML or JavaScript. +With your PLC connected, let's create the operator interface using [FlowFuse Dashboard](/platform/dashboard/), a set of UI nodes that build web-based interfaces without writing HTML or JavaScript. ### Install Dashboard 2.0 diff --git a/src/blog/2025/11/building-label-scanner-with-flowfuse.md b/src/blog/2025/11/building-label-scanner-with-flowfuse.md index 4a91ef8506..99dc4b5c82 100644 --- a/src/blog/2025/11/building-label-scanner-with-flowfuse.md +++ b/src/blog/2025/11/building-label-scanner-with-flowfuse.md @@ -39,7 +39,7 @@ If you do not have one yet, you can [sign up for the 30-day free trial](https:// To perform text extraction from images, you’ll need to install the `@sumit_shinde_84/node-red-contrib-simple-ocr` node in your FlowFuse instance. This node uses the Tesseract OCR engine under the hood to recognize text from image files or image buffers. -To capture images and build a dashboard, you’ll also need the **FlowFuse Dashboard** and **Webcam** packages. +To capture images and build a dashboard, you’ll also need the **[FlowFuse Dashboard](/platform/dashboard/)** and **Webcam** packages. 1. Open your **FlowFuse** editor. 2. From the main menu, select **Manage palette → Install**. diff --git a/src/blog/2025/12/getting-weather-data-in-node-red.md b/src/blog/2025/12/getting-weather-data-in-node-red.md index c0387b2ef8..c44706be62 100644 --- a/src/blog/2025/12/getting-weather-data-in-node-red.md +++ b/src/blog/2025/12/getting-weather-data-in-node-red.md @@ -58,7 +58,7 @@ A weather dashboard is honestly the best first project if you're getting into No This isn't one of our typical deep-dive industrial posts, it's a straightforward starter tutorial. You'll be building something real: calling an actual weather API, handling JSON responses, and watching live data appear on your dashboard. It's the kind of project that makes Node-RED's flow-based approach suddenly make sense. Once you've built it, you'll have a solid foundation for more complex projects. -We'll use FlowFuse Dashboard for the UI since it's modern and easier to work with. If you know how to drag nodes around and hit the deploy button, you're ready to start. +We'll use [FlowFuse Dashboard](/platform/dashboard/) for the UI since it's modern and easier to work with. If you know how to drag nodes around and hit the deploy button, you're ready to start. ## What You'll Need diff --git a/src/blog/2026/01/node-red-history-community-industrial-iot-flowfuse.md b/src/blog/2026/01/node-red-history-community-industrial-iot-flowfuse.md index 4e4ce3772e..60a844760c 100644 --- a/src/blog/2026/01/node-red-history-community-industrial-iot-flowfuse.md +++ b/src/blog/2026/01/node-red-history-community-industrial-iot-flowfuse.md @@ -171,7 +171,7 @@ Together, they have raised $14.5 million to build the infrastructure enterprises Between 2021 and 2025, FlowFuse evolved into a full industrial ecosystem through deliberate focus on operational maturity. The journey began with team collaboration and scaling, introducing version control, team permissions, and DevOps pipelines that let engineering teams work together on flows like software projects, then deploy updates across thousands of remote Node-RED instances with discipline. With collaboration and scale established, the focus shifted to enterprise security, adding SSO, RBAC, and SOC 2 compliance to meet strict governance requirements. Next came infrastructure independence, integrating a built-in MQTT broker and FlowFuse Tables to reduce reliance on external services. By 2025, as AI began reshaping industry, FlowFuse entered the intelligence era with MCP nodes, and FlowFuse Expert, an AI that converts plain-English industrial problems directly into working Node-RED flows. -FlowFuse's mission went beyond enterprise features. It invested continuously in Node-RED core development and community sustainability. When the original [Node-RED Dashboard was deprecated](https://discourse.nodered.org/t/announcement-node-red-dashboard-v1-deprecation-notice/89006/2), FlowFuse rebuilt [Node-RED Dashboard 2.0](https://dashboard.flowfuse.com) from the ground up. +FlowFuse's mission went beyond enterprise features. It invested continuously in Node-RED core development and community sustainability. When the original [Node-RED Dashboard was deprecated](https://discourse.nodered.org/t/announcement-node-red-dashboard-v1-deprecation-notice/89006/2), FlowFuse rebuilt [Node-RED Dashboard 2.0](/platform/dashboard/) from the ground up. That commitment extended to the ecosystem itself. Through the [Certified Nodes program](/blog/2025/07/certified-nodes-v2/), FlowFuse identifies critical community nodes and subjects them to rigorous security and quality testing. To ensure long-term reliability, FlowFuse supports maintainers financially or assumes maintenance responsibility, an approach aligned with the expectations of large industrial organizations. diff --git a/src/blog/2026/02/mapping-mtconnect-streams.md b/src/blog/2026/02/mapping-mtconnect-streams.md index 9ed916c4b5..6ae476c224 100644 --- a/src/blog/2026/02/mapping-mtconnect-streams.md +++ b/src/blog/2026/02/mapping-mtconnect-streams.md @@ -104,7 +104,7 @@ When the node successfully retrieves data, it outputs the following fields: `msg ## Building the Dashboard -Now that you're successfully retrieving MTConnect data, the next step is to display it on a live dashboard. FlowFuse makes this straightforward with its [dashboard package](https://dashboard.flowfuse.com). You can bind any data item to a visual component, and it updates automatically whenever new data arrives. +Now that you're successfully retrieving MTConnect data, the next step is to display it on a live dashboard. FlowFuse makes this straightforward with its [dashboard package](/platform/dashboard/). You can bind any data item to a visual component, and it updates automatically whenever new data arrives. Before you start, make sure to install the `@flowfuse/node-red-dashboard` package to add the dashboard nodes. diff --git a/src/blog/2026/02/motor-anomaly-detector-ai.md b/src/blog/2026/02/motor-anomaly-detector-ai.md index f60f211dfb..09fe3ecc34 100644 --- a/src/blog/2026/02/motor-anomaly-detector-ai.md +++ b/src/blog/2026/02/motor-anomaly-detector-ai.md @@ -548,7 +548,7 @@ Once deployed, the flow should look like this: **5. Act on the Result** -Connect the scoring output to whatever suits your operation. For testing, a debug node shows results in real time. For production, an mqtt-out node can publish anomaly alerts downstream, the [FlowFuse Dashboard](https://dashboard.flowfuse.com) package can visualise the anomaly score over time with a clear motor state indicator, and alerting nodes can notify your team directly, via [Telegram](/node-red/notification/email/), [email](/node-red/notification/telegram/), or [SIGNL4](/blueprints/other/mobile-alerting/) for structured mobile alerts with on-call scheduling and acknowledgement tracking. +Connect the scoring output to whatever suits your operation. For testing, a debug node shows results in real time. For production, an mqtt-out node can publish anomaly alerts downstream, the [FlowFuse Dashboard](/platform/dashboard/) package can visualise the anomaly score over time with a clear motor state indicator, and alerting nodes can notify your team directly, via [Telegram](/node-red/notification/email/), [email](/node-red/notification/telegram/), or [SIGNL4](/blueprints/other/mobile-alerting/) for structured mobile alerts with on-call scheduling and acknowledgement tracking. ### What the Output Looks Like diff --git a/src/blog/2026/03/how-to-monitor-industrial-network-usign-snmp.md b/src/blog/2026/03/how-to-monitor-industrial-network-usign-snmp.md index 294e750463..163eb51622 100644 --- a/src/blog/2026/03/how-to-monitor-industrial-network-usign-snmp.md +++ b/src/blog/2026/03/how-to-monitor-industrial-network-usign-snmp.md @@ -328,7 +328,7 @@ The debug panel will show a concise status array for every interface: This is the most efficient way to run a continuous interface health check, one subtree poll every 10 seconds tells you the operational state of every interface on the device without fetching data you do not need. -With all three polling operations in place, the next step is wiring this data into a [FlowFuse Dashboard](https://dashboard.flowfuse.com/) so the information is visible at a glance. +With all three polling operations in place, the next step is wiring this data into a [FlowFuse Dashboard](/platform/dashboard/) so the information is visible at a glance. ## Wrapping Up diff --git a/src/blog/2026/05/manufacturing-software-built-in-stages.md b/src/blog/2026/05/manufacturing-software-built-in-stages.md index 84fec6cbdd..9f8124d1c1 100644 --- a/src/blog/2026/05/manufacturing-software-built-in-stages.md +++ b/src/blog/2026/05/manufacturing-software-built-in-stages.md @@ -84,7 +84,7 @@ FlowFuse sits in the middle layer, connecting to these systems through protocols A key advantage is FlowFuse's built-in MQTT broker, which enables you to build a [Unified Namespace (UNS)](/blog/2024/11/building-uns-with-flowfuse/), a standardized data structure that simplifies how machines, applications, and business systems communicate. With a UNS in place, integrations become faster to build and easier to maintain as your stack grows. -On top of this data layer, manufacturers can build applications with [FlowFuse Dashboards](https://dashboard.flowfuse.com/) for OEE tracking, quality workflows, downtime monitoring, maintenance alerts, and work order management. Because these capabilities remain independent, teams can deploy and improve them incrementally as requirements evolve. +On top of this data layer, manufacturers can build applications with [FlowFuse Dashboards](/platform/dashboard/) for OEE tracking, quality workflows, downtime monitoring, maintenance alerts, and work order management. Because these capabilities remain independent, teams can deploy and improve them incrementally as requirements evolve. FlowFuse also includes the enterprise capabilities needed to operate these applications at scale, including: diff --git a/src/blog/2026/06/opcua-to-influxdb.md b/src/blog/2026/06/opcua-to-influxdb.md index 4d0069c383..94db9b0f6d 100644 --- a/src/blog/2026/06/opcua-to-influxdb.md +++ b/src/blog/2026/06/opcua-to-influxdb.md @@ -194,7 +194,7 @@ _InfluxDB Data Explorer showing the temperature filling in_ You'll see your readings listed in a table, one row per read interval. If new rows keep appearing as time passes, your pipeline is working end to end: equipment to OPC UA to FlowFuse to InfluxDB. -Storing data is only half the story. The InfluxDB In node lets you query readings back from InfluxDB, whether you need the latest values, historical trends, or aggregated metrics. You can then feed the results directly into a [FlowFuse Dashboard](https://dashboard.flowfuse.com) to build charts, tables, and real-time monitoring views of your OPC UA data. +Storing data is only half the story. The InfluxDB In node lets you query readings back from InfluxDB, whether you need the latest values, historical trends, or aggregated metrics. You can then feed the results directly into a [FlowFuse Dashboard](/platform/dashboard/) to build charts, tables, and real-time monitoring views of your OPC UA data. ## Where to go from here diff --git a/src/blog/2026/06/process-rtsp-camera-feeds-at-the-edge.md b/src/blog/2026/06/process-rtsp-camera-feeds-at-the-edge.md index 8a8d5ad805..cb779b559d 100644 --- a/src/blog/2026/06/process-rtsp-camera-feeds-at-the-edge.md +++ b/src/blog/2026/06/process-rtsp-camera-feeds-at-the-edge.md @@ -117,7 +117,7 @@ Once the node connects, it shows a green Running status underneath it on the can A buffer in the debug sidebar confirms the feed works, but it's no use to an operator. Let's get the frame onto a screen anyone can open in a browser. -This assumes you have FlowFuse Dashboard 2.0 installed. If you don't, follow the [Getting Started guide](https://dashboard.flowfuse.com/getting-started.html#installation) to add it and set up your first page, then come back. +This assumes you have [FlowFuse Dashboard](/platform/dashboard/) 2.0 installed. If you don't, follow the [Getting Started guide](https://dashboard.flowfuse.com/getting-started.html#installation) to add it and set up your first page, then come back. FlowFuse Dashboard has no built-in widget that takes a raw image buffer, so we turn each PNG into a base64 data URI and render it with a standard image tag. The conversion is handled by the **base64** node, which you'll need to install: add `node-red-node-base64` from the Palette Manager. diff --git a/src/blog/2026/07/build-downtime-logger.md b/src/blog/2026/07/build-downtime-logger.md index 3118257295..f8b304a868 100644 --- a/src/blog/2026/07/build-downtime-logger.md +++ b/src/blog/2026/07/build-downtime-logger.md @@ -68,7 +68,7 @@ Before you start building, get these ready: - **A FlowFuse account.** Sign up for FlowFuse Cloud, or use a self-hosted instance. - **A FlowFuse instance up and running.** If you don't have one yet, create a new instance from your FlowFuse Platform. -- **FlowFuse Dashboard installed.** This tutorial uses `@flowfuse/node-red-dashboard` nodes (`ui-button`, `ui-table`, `ui-chart`) to build the operator interface. Install it from the Palette Manager if it isn't already in your instance. +- **[FlowFuse Dashboard](/platform/dashboard/) installed.** This tutorial uses `@flowfuse/node-red-dashboard` nodes (`ui-button`, `ui-table`, `ui-chart`) to build the operator interface. Install it from the Palette Manager if it isn't already in your instance. - **The Humanizer node installed.** This is what turns raw downtime into readable text like "12 minutes." It comes from the `node-red-contrib-moment` package, install it from the Palette Manager. You won't need a PLC or any real hardware for this tutorial. We'll simulate machine stop and start events with inject nodes, and the same flow logic applies later when you connect real signals. diff --git a/src/blog/2026/07/calibration-management-dashboard.md b/src/blog/2026/07/calibration-management-dashboard.md index 4a684edd10..08ace58802 100644 --- a/src/blog/2026/07/calibration-management-dashboard.md +++ b/src/blog/2026/07/calibration-management-dashboard.md @@ -81,7 +81,7 @@ Before you start building, get these ready: - **A FlowFuse account.** [Sign up](https://app.flowfuse.com/account/create) for FlowFuse Cloud, or use a self-hosted instance. - **A FlowFuse instance up and running.** If you don't have one yet, create a new instance from your FlowFuse Platform. -- **FlowFuse Dashboard installed.** This tutorial uses `@flowfuse/node-red-dashboard` nodes (`ui-template`, `ui-event`, `ui-button`, `ui-markdown`, `ui-notification`, `ui-page`, `ui-group`, `ui-theme`) to build both pages. Install it from the Palette Manager if it isn't already in your instance. +- **[FlowFuse Dashboard](/platform/dashboard/) installed.** This tutorial uses `@flowfuse/node-red-dashboard` nodes (`ui-template`, `ui-event`, `ui-button`, `ui-markdown`, `ui-notification`, `ui-page`, `ui-group`, `ui-theme`) to build both pages. Install it from the Palette Manager if it isn't already in your instance. - **A webcam node and an OCR node.** The Tool Check page uses `@sumit_shinde_84/node-red-dashboard-2-ui-webcam` to capture the label and `@sumit_shinde_84/node-red-contrib-simple-ocr` to read it. Install both from the Palette Manager. - **A device with a camera** for the Tool Check page, since the scanner works through the browser. diff --git a/src/blog/2026/07/digital-work-instruction.md b/src/blog/2026/07/digital-work-instruction.md index d6e6b5fb2a..e15e65234e 100644 --- a/src/blog/2026/07/digital-work-instruction.md +++ b/src/blog/2026/07/digital-work-instruction.md @@ -78,7 +78,7 @@ Before you start building, get these ready: - **A FlowFuse account.** [Sign up](https://app.flowfuse.com/account/create) for FlowFuse Cloud, or use a self-hosted instance. - **A FlowFuse instance up and running.** If you don't have one yet, create a new instance from your FlowFuse Platform. -- **FlowFuse Dashboard installed.** This tutorial uses `@flowfuse/node-red-dashboard` nodes (`ui-template`, `ui-table`, `ui-form`, `ui-button`, `ui-control`, `ui-event`, `ui-text`) to build the operator interface. Install it from the Palette Manager if it isn't already in your instance. +- **[FlowFuse Dashboard](/platform/dashboard/) installed.** This tutorial uses `@flowfuse/node-red-dashboard` nodes (`ui-template`, `ui-table`, `ui-form`, `ui-button`, `ui-control`, `ui-event`, `ui-text`) to build the operator interface. Install it from the Palette Manager if it isn't already in your instance. - **The FlowFuse Dashboard user addon.** This is what attaches the logged-in user to every dashboard message. We'll install it in the first section. > Note: The Multi-User addon is available to Teams and Enterprise Self-Hosted customers. If you're on a different tier, [contact us](/contact-us/) for the configuration to get started. diff --git a/src/blog/2026/08/dashboard-themes-and-rendering-fixes.md b/src/blog/2026/08/dashboard-themes-and-rendering-fixes.md index 053d5101e6..ec48003894 100644 --- a/src/blog/2026/08/dashboard-themes-and-rendering-fixes.md +++ b/src/blog/2026/08/dashboard-themes-and-rendering-fixes.md @@ -12,7 +12,7 @@ tags: - dashboard --- -FlowFuse Dashboard 1.31.0 adds five built-in themes, giving you everything you need to build a dark mode dashboard, along with layout improvements for charts, buttons, and gauges. Previously, dark mode had contrast issues across widgets, charts collapsed to empty boxes at their default size, long button labels clipped mid-word, and gauges got sliced off by their own card. +[FlowFuse Dashboard](/platform/dashboard/) 1.31.0 adds five built-in themes, giving you everything you need to build a dark mode dashboard, along with layout improvements for charts, buttons, and gauges. Previously, dark mode had contrast issues across widgets, charts collapsed to empty boxes at their default size, long button labels clipped mid-word, and gauges got sliced off by their own card. diff --git a/src/changelog/2024/04/device-auto-snapshot.md b/src/changelog/2024/04/device-auto-snapshot.md index 7bfaf0ee8f..fc955ec306 100644 --- a/src/changelog/2024/04/device-auto-snapshot.md +++ b/src/changelog/2024/04/device-auto-snapshot.md @@ -14,4 +14,4 @@ We have added quick access buttons to help you navigate to your Dashboard 2.0 UI _Dashboard button is displayed alongside the Open Editor button when an instance has `@flowfuse/node-red-dashboard` installed._ -Click the link to learn more about [Flowfuse Dashboard 2.0](https://dashboard.flowfuse.com/) +Click the link to learn more about [Flowfuse Dashboard 2.0](/platform/dashboard/) diff --git a/src/changelog/2024/06/library-blueprints.md b/src/changelog/2024/06/library-blueprints.md index e25cde0800..ba820d4ff5 100644 --- a/src/changelog/2024/06/library-blueprints.md +++ b/src/changelog/2024/06/library-blueprints.md @@ -16,7 +16,7 @@ Within FlowFuse Cloud, Node-RED instances are reached by their provided url: ` diff --git a/src/node-red/flowfuse/edge/cip-suite.md b/src/node-red/flowfuse/edge/cip-suite.md index 804efa197d..59beccf64c 100644 --- a/src/node-red/flowfuse/edge/cip-suite.md +++ b/src/node-red/flowfuse/edge/cip-suite.md @@ -58,7 +58,7 @@ The result: production counts, machine states, and reject rates are available to ### Where this shows up in practice - **OEE and downtime tracking**: feed `ConveyorRunning` and cycle-time tags into a calculation flow to surface availability and performance losses as they happen, instead of reconstructing them from end-of-shift reports. -- **Live operations dashboards**: wire tag changes straight into [FlowFuse Dashboard](https://dashboard.flowfuse.com/) widgets so operators and supervisors see machine state and counts update in real time. +- **Live operations dashboards**: wire tag changes straight into [FlowFuse Dashboard](/platform/dashboard/) widgets so operators and supervisors see machine state and counts update in real time. - **Recipe and setpoint downloads**: use `cip-write` to push new setpoints, batch parameters, or recipe values to the PLC from an MES, a dashboard form, or a database lookup. - **Threshold alerting**: route a `Temperature` or `Pressure` tag through a `switch` node and fire a Slack, Teams, or email notification the moment a value crosses a quality limit. - **Unified Namespace / MQTT bridging**: treat the PLC as a data source feeding a plant-wide UNS, so IT and OT systems consume the same live tag data instead of duplicating integrations per PLC. diff --git a/src/node-red/flowfuse/edge/rtsp.md b/src/node-red/flowfuse/edge/rtsp.md index 5ed418625a..63be992d27 100644 --- a/src/node-red/flowfuse/edge/rtsp.md +++ b/src/node-red/flowfuse/edge/rtsp.md @@ -33,7 +33,7 @@ A camera above a packaging line already streams to the site NVR. Point the RTSP ### Where this shows up in practice - **Machine vision**: feed frames to a [FlowFuse AI node](/node-red/flowfuse/ai/) for object detection or image classification, then act on the result, for example counting parts on a line, checking a fill level, or verifying a safety gate is closed. -- **Remote monitoring**: display the frames live on a [FlowFuse Dashboard](https://dashboard.flowfuse.com/) so an operator can watch a machine or area from anywhere the dashboard is reachable, alongside the process data on the same page. +- **Remote monitoring**: display the frames live on a [FlowFuse Dashboard](/platform/dashboard/) so an operator can watch a machine or area from anywhere the dashboard is reachable, alongside the process data on the same page. - **Event snapshots**: route frames through a `function` or `switch` node and keep only the ones that matter, for example the frame captured the moment a PLC tag or sensor reports a fault, and forward it with an [`mqtt out`](/node-red/flowfuse/mqtt/mqtt-out/) node or attach it to an alert. - **Timelapse and archiving**: switch to disk-writing mode and the node writes a numbered sequence of PNG files for later review or timelapse assembly, without adding any messages to the flow. @@ -98,7 +98,7 @@ The node emits each captured frame as a message at the configured FPS rate. | `msg.payload` | Buffer | The captured frame as a PNG image buffer. | | `msg.topic` | String | The topic configured on the node. | -The output can be wired to any node that accepts an image buffer, including [FlowFuse Dashboard widgets](https://dashboard.flowfuse.com/), [MQTT out nodes](/node-red/flowfuse/mqtt/mqtt-out/), and [FlowFuse AI nodes](/node-red/flowfuse/ai/). +The output can be wired to any node that accepts an image buffer, including [FlowFuse Dashboard widgets](/platform/dashboard/), [MQTT out nodes](/node-red/flowfuse/mqtt/mqtt-out/), and [FlowFuse AI nodes](/node-red/flowfuse/ai/). {% note %} Every captured frame becomes a message in the flow. A high FPS value increases the number and size of messages being processed. Set FPS no higher than your use case requires. diff --git a/src/node-red/index.njk b/src/node-red/index.njk index b6026d7bbd..f9f4c04677 100644 --- a/src/node-red/index.njk +++ b/src/node-red/index.njk @@ -129,7 +129,7 @@ sitemapPriority: 0.8 { "svgPath": "components/icons/document-chart-bar.svg", "title": "Data Visualization", - "description": 'Node-RED Dashboard makes it easy + "description": 'Node-RED Dashboard makes it easy to visualize your data in charts that integrate directly with actions and events that respond to the data.' } diff --git a/src/node-red/integration-technologies/rest.md b/src/node-red/integration-technologies/rest.md index d8a9b98c9c..ed358518b4 100644 --- a/src/node-red/integration-technologies/rest.md +++ b/src/node-red/integration-technologies/rest.md @@ -107,7 +107,7 @@ Never use `*` for `Allow-Origin` in production, specify exact domains. Now that you've learned how to create REST APIs in Node-RED, let's explore an example of reading data using a HTTP GET request. This example will demonstrate how to fetch data from an external API and process it and display on dashboard chart. -For the example we will fetch the data of Node-RED Dashboard 2.0 Downloads from npm registry api. +For the example we will fetch the data of [Node-RED Dashboard 2.0](/platform/dashboard/) Downloads from npm registry api. `https://api.npmjs.org/downloads/range/last-month/@flowforge/node-red-dashboard`. A simple flow to fetch data from npm registry would be: diff --git a/src/node-red/peripheral/barcodescanner.md b/src/node-red/peripheral/barcodescanner.md index a72acb1b9e..0b39e07010 100644 --- a/src/node-red/peripheral/barcodescanner.md +++ b/src/node-red/peripheral/barcodescanner.md @@ -28,7 +28,7 @@ Test your barcode scanner against any barcode your scanner works with and you sh ![USB HID Scanned Barcode in Node-RED](./images/usbhid-scanned-barcode.png) -You could even take it a step further and create a [QR code](https://smalldev.tools/qr-code-generator-online) for your favorite pizza ingredients as seen here on the new [Dashboard 2.0](https://dashboard.flowfuse.com/). +You could even take it a step further and create a [QR code](https://smalldev.tools/qr-code-generator-online) for your favorite pizza ingredients as seen here on the new [Dashboard 2.0](/platform/dashboard/). ![USB HID Scanned Barcode Pizza Ingredients](./images/usbhid-qr-pizza-order.png) diff --git a/src/platform/dashboard.njk b/src/platform/dashboard.njk index 00074a3e25..6e47a4c6ef 100644 --- a/src/platform/dashboard.njk +++ b/src/platform/dashboard.njk @@ -1,8 +1,9 @@ --- layout: nohero meta: - title: FlowFuse Dashboard - description: Build enterprise-class dashboards for Node-RED without writing CSS. Five built-in themes that all pass WCAG AA contrast, included with FlowFuse Edge, Hub and Fleet. + title: "Production and IIoT Dashboard platform" + description: Build a production dashboard or IIoT dashboard for Node-RED without writing CSS. Five WCAG AA themes, included with FlowFuse Edge, Hub, and Fleet. + keywords: production dashboard, IIoT dashboard, industrial IoT dashboard, factory dashboard, operations dashboard, machine dashboard, industrial dashboard, Node-RED dashboard --- @@ -13,14 +14,18 @@ meta:

- A dashboard that looks right the moment you build it. - Without writing CSS. + Build Industrial Production Dashboards with + The FlowFuse Dashboard.

- FlowFuse Dashboard is how your Node-RED application gets a user interface that - looks finished. With five built-in themes that all pass WCAG AA contrast, - you can deploy enterprise-class dashboards quickly and easily. You get deeper - context, easier access to insights, and flexible visualisation — included + Deploy a full production dashboard in seconds, unifying + your factory operations and machine metrics into a single view. No more wasted time + searching for reports or filling out a spreadsheet - just clean data for all your + machines, sites, and systems. This means reduced operational costs, better + visualisation, and deeper context for everyone. +

+

+ The FlowFuse Dashboard is included with FlowFuse Edge, Hub, and Fleet. @@ -181,18 +186,18 @@ meta:

In the box

- What You Get with FlowFuse Dashboard + What You Get with The FlowFuse Dashboard

- The Dashboard is how a FlowFuse instance can display its data in a human-friendly, - visual way. You can surface your data and insights — and then leverage - governance, hosting, and deployment via the core FlowFuse product to power your entire - system. + The FlowFuse Dashboard is how a FlowFuse instance turns raw data into an industrial dashboard + — a machine dashboard on the line, or a plant-wide view for management. You can + surface your data and insights, then leverage governance, hosting, and deployment via + the core FlowFuse product to power your entire system.

-

Governed on the FlowFuse platform

+

Governance for Your Operations Dashboard

Application-level RBAC Endpoint security @@ -202,18 +207,29 @@ meta:
-

Adaptive Widgets

+

Widgets for Any Machine Dashboard

- Charts - Gauges - Tables - Forms - Buttons - Text input - Dropdowns - Sliders & switches - Markdown - Templates + Chart + Gauge + Table + Form + Button + Button group + Text + Text input + Number input + Dropdown + Radio group + Slider + Switch + Markdown + Template + Notification + Progress + File input + Control + Audio + Spacer
@@ -226,7 +242,7 @@ meta:
-

Easy to Deploy

+

Deploy a Factory Dashboard Fast

5 theme presets WCAG AA contrast @@ -250,10 +266,12 @@ meta:
Migration

- Coming from Dashboard 1.0? Bring your flows. + Coming from deprecated Dashboard 1.0? Bring your flows.

- Upload your flow and migrate to FlowFuse Dashboard. Today, you can convert the + Dashboard 1.0 is + deprecated. + Upload your flow and migrate to The FlowFuse Dashboard. Today, you can convert the following nodes:

@@ -286,7 +304,7 @@ meta:
Learn -

Get a Dashboard By This Afternoon

+

Get a Production Dashboard By This Afternoon

    {%- for item in dashboard.resources -%}
  • @@ -308,6 +326,37 @@ meta: All Dashboard posts {% include "components/icons/arrow-long-right.svg" %}
+ +

Recommended Video Tutorials

+
+
+ + + Getting Started — Node-RED & The FlowFuse Dashboard + +
+
+ + + Visualising Data with The FlowFuse Dashboard + +
+
+ + + Writing Custom Templates in The FlowFuse Dashboard + +
+
@@ -317,12 +366,12 @@ meta:
The rest of the platform

- Dashboard is the face. Here is what runs behind it. + Your production dashboard is the face. Here is what runs behind it.

- The Dashboard is how a FlowFuse instance can display its data in a human-friendly, - visual way. You can surface your data and insights — and then leverage - governance, hosting, and deployment via the core FlowFuse product to power your entire system. + Dashboards are only as good as the systems feeding them. FlowFuse handles the + governance, hosting, and deployment underneath — so the view your operators see + stays live, secure, and reliable.

diff --git a/src/webinars/2025/from-node-red-to-flowfuse-it-ot-integration-and-automation-in-container-terminals.md b/src/webinars/2025/from-node-red-to-flowfuse-it-ot-integration-and-automation-in-container-terminals.md index 625bd6d98c..fa70f28b75 100644 --- a/src/webinars/2025/from-node-red-to-flowfuse-it-ot-integration-and-automation-in-container-terminals.md +++ b/src/webinars/2025/from-node-red-to-flowfuse-it-ot-integration-and-automation-in-container-terminals.md @@ -37,7 +37,7 @@ The terminal further enhanced operational visibility by integrating Node-RED flo The session includes a live demonstration of: -- **FlowFuse Dashboard 2.0** for operational monitoring. +- **[FlowFuse Dashboard](/platform/dashboard/) 2.0** for operational monitoring. - **Automated ticket printing** using TCP nodes for thermal receipt printers. - **PDFMaker integration** to generate digital transaction reports. diff --git a/src/webinars/2026/industrial-iot-solutions.md b/src/webinars/2026/industrial-iot-solutions.md index 2432fbabe7..fa29e2fd4a 100644 --- a/src/webinars/2026/industrial-iot-solutions.md +++ b/src/webinars/2026/industrial-iot-solutions.md @@ -16,7 +16,7 @@ meta: It comes down to where your applications live: a data center (Hub), a plant floor (Edge), or thousands of field devices (Fleet). We'll walk through all three live in the webinar and help map your specific setup to one of them. Bring your architecture and we'll sort it live in the Q&A. - question: "Can I build real-time dashboards with FlowFuse?" answer: > - Yes. FlowFuse Dashboard ships with five built-in themes, all WCAG AA contrast-compliant, so dark mode stays legible instead of washed out. Charts render live instead of leaving empty boxes, and tables show readable dates instead of raw epoch numbers, on top of smaller fixes that keep labels and gauges inside their cards at narrow widths. We'll demo it during the webinar, + Yes. FlowFuse Dashboard ships with five built-in themes, all WCAG AA contrast-compliant, so dark mode stays legible instead of washed out. Charts render live instead of leaving empty boxes, and tables show readable dates instead of raw epoch numbers, on top of smaller fixes that keep labels and gauges inside their cards at narrow widths. We'll demo it during the webinar, - question: "Do I need to already use FlowFuse to attend?" answer: > No. The webinar works for both first-time evaluators and current customers. If you're new, you'll leave knowing which product to trial and how to start. If you already run FlowFuse, you'll leave knowing what's changed and which workarounds you get to delete. @@ -47,7 +47,7 @@ Join Kristopher Sandoval (Product Marketing), Jamie Strusz (Engineering), Drew G - FlowFuse Hub integrates [enterprise systems](/landing/enterprise-integration/) and [APIs](/node-red/core-nodes/http-request/), FlowFuse Edge connects [PLCs](/landing/plc/) and machines across sites, FlowFuse Fleet manages [Node-RED](/node-red/) across thousands of devices. We'll map your setup to one of the three, live. - Build faster with Industrial AI: [FlowFuse Expert](/docs/user/expert/) opens its [MCP server](/blog/2025/10/building-mcp-server-using-flowfuse/) to 3rd party agents, such as Cursor, Claude Code, Gemini CLI, and even in-house agents. Any MCP-speaking agent works. Point your AI agent at your FlowFuse instance and it builds, debugs, and fixes flows directly. - See what's running, everywhere: [role-based access control](/docs/user/role-based-access-control/), [audit logging](/docs/user/logs/#audit-log), and [one place to manage every instance and device](/blog/2024/10/managing-node-red-instances-in-centralize-platfrom/), no matter which product you run. -- Read a [dashboard](https://dashboard.flowfuse.com/) at a glance: new [built-in themes](https://dashboard.flowfuse.com/nodes/config/ui-theme.html) with WCAG AA contrast, [charts](https://dashboard.flowfuse.com/nodes/widgets/ui-chart) that render instead of leaving empty boxes, and readable dates instead of raw timestamps. +- Read a [dashboard](/platform/dashboard/) at a glance: new [built-in themes](https://dashboard.flowfuse.com/nodes/config/ui-theme.html) with WCAG AA contrast, [charts](https://dashboard.flowfuse.com/nodes/widgets/ui-chart) that render instead of leaving empty boxes, and readable dates instead of raw timestamps. - Live Q&A: This is the best part! Bring your hard questions and let's talk about it live. ## Who should attend this FlowFuse product launch webinar?