Update stale content for new product offerings - #5595
Open
KristopherLeads wants to merge 44 commits into
Open
Conversation
KristopherLeads
marked this pull request as draft
August 13, 2026 16:24
Updated the note about deprecated FlowFuse account types and changed the HTML div to a markdown warning block.
Added an update about FlowFuse products and their capabilities for managing industrial applications.
Added a note about FlowFuse products and their applications.
Added an update about FlowFuse products and their applications with InfluxDB.
Added a note about FlowFuse products and their capabilities.
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Added information about new product offerings and annual billing details.
Added a note about new FlowFuse products and their features.
Updated lastUpdated date for the PLC to MQTT blog post.
Updated lastUpdated date for the historical data dashboard article.
Added lastUpdated field and promotional note about FlowFuse products.
Added lastUpdated field and product offerings note to the MQTT announcement.
Added details about email alerts for Audit Log events and updated product offerings.
Added details about upcoming server maintenance and product updates.
KristopherLeads
marked this pull request as ready for review
August 13, 2026 17:15
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Yndira-E
reviewed
Aug 14, 2026
Contributor
There was a problem hiding this comment.
@KristopherLeads since it was the same copy for all the md files, I've created a nuxt component. It'll be easier to update if we need to.
Yndira-E
reviewed
Aug 14, 2026
Contributor
There was a problem hiding this comment.
@KristopherLeads this is still processed by 11ty, and since it's the only one, no component was created. It should be updated when we migrate it to nuxt.
Yndira-E
approved these changes
Aug 14, 2026
Yndira-E
force-pushed
the
stale-content-fix
branch
from
August 14, 2026 08:02
9318a35 to
736fd96
Compare
Yndira-E
force-pushed
the
stale-content-fix
branch
from
August 14, 2026 08:03
736fd96 to
e595baa
Compare
| - `node-red-contrib-opcua` – OPC UA servers | ||
| - `node-red-contrib-cip-ethernet-ip` – Allen-Bradley PLCs | ||
| - `node-red-contrib-mcprotocol` – Mitsubishi PLCs | ||
| - `node-red-contrib-mctocol` – Mitsubishi PLCs |
Contributor
There was a problem hiding this comment.
Why this is updated? the node name was correct node-red-contrib-mcprotocol?
Suggested change
| - `node-red-contrib-mctocol` – Mitsubishi PLCs | |
| - `node-red-contrib-mcprotocol` – Mitsubishi PLCs |
| - and many more | ||
|
|
||
| Adding a protocol node to your FlowFuse instance takes just a few clicks. Open the palette manager from the hamburger menu, select **Manage palette**, go to the **Install** tab, and search for the node you need. | ||
| Adding a tocol node to your FlowFuse instance takes just a few clicks. Open the palette manager from the hamburger menu, select **Manage palette**, go to the **Install** tab, and search for the node you need. |
Contributor
There was a problem hiding this comment.
I think this was done accidentally
Suggested change
| Adding a tocol node to your FlowFuse instance takes just a few clicks. Open the palette manager from the hamburger menu, select **Manage palette**, go to the **Install** tab, and search for the node you need. | |
| Adding a protocol node to your FlowFuse instance takes just a few clicks. Open the palette manager from the hamburger menu, select **Manage palette**, go to the **Install** tab, and search for the node you need. |
Contributor
|
@KristopherLeads, this PR removes every occurrence of |
sumitshinde-84
requested changes
Aug 14, 2026
| When talking to people in the IIoT community, one recurring challenge always comes up, **convincing the IT team**. | ||
|
|
||
| Traditional industrial gateways require inbound connections from the cloud. This means opening specific ports in your firewall, creating security exceptions, and giving external systems a pathway into your production network. IT security teams push back on this, and rightly so. Inbound connections expand your attack surface and violate the principle of defense in depth. | ||
| Traditional industrial gateways require inbound connections from the cloud. This means opening specific ports in your firewall, creating security exceptions, and giving external systems a pathway into your duction network. IT security teams push back on this, and rightly so. Inbound connections expand your attack surface and violate the principle of defense in depth. |
Contributor
There was a problem hiding this comment.
Suggested change
| Traditional industrial gateways require inbound connections from the cloud. This means opening specific ports in your firewall, creating security exceptions, and giving external systems a pathway into your duction network. IT security teams push back on this, and rightly so. Inbound connections expand your attack surface and violate the principle of defense in depth. | |
| Traditional industrial gateways require inbound connections from the cloud. This means opening specific ports in your firewall, creating security exceptions, and giving external systems a pathway into your production network. IT security teams push back on this, and rightly so. Inbound connections expand your attack surface and violate the principle of defense in depth. |
| Traditional industrial gateways require inbound connections from the cloud. This means opening specific ports in your firewall, creating security exceptions, and giving external systems a pathway into your duction network. IT security teams push back on this, and rightly so. Inbound connections expand your attack surface and violate the principle of defense in depth. | ||
|
|
||
| FlowFuse solves this with an **edge-first architecture**. The Device Agent installs directly on hardware inside your factory network, a Raspberry Pi, an industrial PC, or even directly on supported PLCs. Once running, the agent initiates **outbound** connections to the FlowFuse platform using standard web protocols (HTTPS and WebSocket over port 443). All communication flows through this outbound connection. The platform never initiates connections back to your network. | ||
| FlowFuse solves this with an **edge-first architecture**. The Device Agent installs directly on hardware inside your factory network, a Raspberry Pi, an industrial PC, or even directly on supported PLCs. Once running, the agent initiates **outbound** connections to the FlowFuse platform using standard web tocols (HTTPS and WebSocket over port 443). All communication flows through this outbound connection. The platform never initiates connections back to your network. |
Contributor
There was a problem hiding this comment.
Suggested change
| FlowFuse solves this with an **edge-first architecture**. The Device Agent installs directly on hardware inside your factory network, a Raspberry Pi, an industrial PC, or even directly on supported PLCs. Once running, the agent initiates **outbound** connections to the FlowFuse platform using standard web tocols (HTTPS and WebSocket over port 443). All communication flows through this outbound connection. The platform never initiates connections back to your network. | |
| FlowFuse solves this with an **edge-first architecture**. The Device Agent installs directly on hardware inside your factory network, a Raspberry Pi, an industrial PC, or even directly on supported PLCs. Once running, the agent initiates **outbound** connections to the FlowFuse platform using standard web protocols (HTTPS and WebSocket over port 443). All communication flows through this outbound connection. The platform never initiates connections back to your network. |
| The device agent behaves like any other business application making secure outbound HTTPS requests, something your network already allows. | ||
|
|
||
| For networks with proxy servers, the agent supports standard proxy configurations through environment variables. For air-gapped networks, you can pre-cache Node-RED modules and deploy without internet connectivity after the initial setup. | ||
| For networks with xy servers, the agent supports standard xy configurations through environment variables. For air-gapped networks, you can pre-cache Node-RED modules and deploy without internet connectivity after the initial setup. |
Contributor
There was a problem hiding this comment.
Suggested change
| For networks with xy servers, the agent supports standard xy configurations through environment variables. For air-gapped networks, you can pre-cache Node-RED modules and deploy without internet connectivity after the initial setup. | |
| For networks with proxy servers, the agent supports standard proxy configurations through environment variables. For air-gapped networks, you can pre-cache Node-RED modules and deploy without internet connectivity after the initial setup. |
| Change nodes handle simple transformations without coding. They allow you to map fields, modify values, convert units, and add metadata using dropdowns and form fields. JSONata allows more advanced data manipulation directly within the Change node. | ||
|
|
||
| Plant engineers can work directly with these visual tools, no programming required. | ||
| Plant engineers can work directly with these visual tools, no gramming required. |
Contributor
There was a problem hiding this comment.
Suggested change
| Plant engineers can work directly with these visual tools, no gramming required. | |
| Plant engineers can work directly with these visual tools, no programming required. |
| **Function Nodes for Custom Logic** | ||
|
|
||
| Function nodes provide full JavaScript access for complex requirements. Write custom logic, install npm packages, and access the complete JavaScript standard library when Change nodes and JSONata reach their limits. | ||
| Function nodes vide full JavaScript access for complex requirements. Write custom logic, install npm packages, and access the complete JavaScript standard library when Change nodes and JSONata reach their limits. |
Contributor
There was a problem hiding this comment.
Suggested change
| Function nodes vide full JavaScript access for complex requirements. Write custom logic, install npm packages, and access the complete JavaScript standard library when Change nodes and JSONata reach their limits. | |
| Function nodes provide full JavaScript access for complex requirements. Write custom logic, install npm packages, and access the complete JavaScript standard library when Change nodes and JSONata reach their limits. |
| Function nodes vide full JavaScript access for complex requirements. Write custom logic, install npm packages, and access the complete JavaScript standard library when Change nodes and JSONata reach their limits. | ||
|
|
||
| *Tip: Use the [FlowFuse Expert](/blog/2025/07/flowfuse-ai-assistant-better-node-red-manufacturing/) to generate function nodes. Describe the transformation you need in plain English, and it will create the code for you. For best results, provide sample input data to ensure the output matches your requirements.* | ||
| *Tip: Use the [FlowFuse Expert](/blog/2025/07/flowfuse-ai-assistant-better-node-red-manufacturing/) to generate function nodes. Describe the transformation you need in plain English, and it will create the code for you. For best results, vide sample input data to ensure the output matches your requirements.* |
Contributor
There was a problem hiding this comment.
Suggested change
| *Tip: Use the [FlowFuse Expert](/blog/2025/07/flowfuse-ai-assistant-better-node-red-manufacturing/) to generate function nodes. Describe the transformation you need in plain English, and it will create the code for you. For best results, vide sample input data to ensure the output matches your requirements.* | |
| *Tip: Use the [FlowFuse Expert](/blog/2025/07/flowfuse-ai-assistant-better-node-red-manufacturing/) to generate function nodes. Describe the transformation you need in plain English, and it will create the code for you. For best results, provide sample input data to ensure the output matches your requirements.* |
| Before building custom solutions, check the palette manager. The Node-RED ecosystem includes thousands of nodes for data aggregation, statistical analysis, time-series buffering, and unit conversions. Many common transformation tasks already have ready-made solutions. | ||
|
|
||
| For example, a popular node I'm using in my demo for parsing and transforming data is `node-red-contrib-buffer-parser`. This node is especially useful when working with Modbus or PLC outputs, as it converts raw data into structured formats that can be easily processed further. | ||
| For example, a popular node I'm using in my demo for parsing and transforming data is `node-red-contrib-buffer-parser`. This node is especially useful when working with Modbus or PLC outputs, as it converts raw data into structured formats that can be easily cessed further. |
Contributor
There was a problem hiding this comment.
Suggested change
| For example, a popular node I'm using in my demo for parsing and transforming data is `node-red-contrib-buffer-parser`. This node is especially useful when working with Modbus or PLC outputs, as it converts raw data into structured formats that can be easily cessed further. | |
| For example, a popular node I'm using in my demo for parsing and transforming data is `node-red-contrib-buffer-parser`. This node is especially useful when working with Modbus or PLC outputs, as it converts raw data into structured formats that can be easily processed further. |
| Most MQTT implementations require setting up a separate broker either paying for a managed service or hosting your own. FlowFuse includes a managed MQTT broker built directly into the platform, eliminating this extra step. | ||
|
|
||
| Traditional PLC-to-cloud setups typically involve several moving parts: edge gateways running protocol drivers, a separate MQTT broker (cloud-hosted or self-managed), and your destination cloud services. Each layer adds configuration work, licensing costs, and potential failure points. When data stops flowing, you end up troubleshooting across multiple systems to locate the issue. | ||
| Traditional PLC-to-cloud setups typically involve several moving parts: edge gateways running tocol drivers, a separate MQTT broker (cloud-hosted or self-managed), and your destination cloud services. Each layer adds configuration work, licensing costs, and potential failure points. When data stops flowing, you end up troubleshooting across multiple systems to locate the issue. |
Contributor
There was a problem hiding this comment.
Suggested change
| Traditional PLC-to-cloud setups typically involve several moving parts: edge gateways running tocol drivers, a separate MQTT broker (cloud-hosted or self-managed), and your destination cloud services. Each layer adds configuration work, licensing costs, and potential failure points. When data stops flowing, you end up troubleshooting across multiple systems to locate the issue. | |
| Traditional PLC-to-cloud setups typically involve several moving parts: edge gateways running protocol drivers, a separate MQTT broker (cloud-hosted or self-managed), and your destination cloud services. Each layer adds configuration work, licensing costs, and potential failure points. When data stops flowing, you end up troubleshooting across multiple systems to locate the issue. |
| Traditional PLC-to-cloud setups typically involve several moving parts: edge gateways running tocol drivers, a separate MQTT broker (cloud-hosted or self-managed), and your destination cloud services. Each layer adds configuration work, licensing costs, and potential failure points. When data stops flowing, you end up troubleshooting across multiple systems to locate the issue. | ||
|
|
||
| FlowFuse consolidates those layers into a single integrated platform. It provides enterprise-grade features for management, scaling, deployment, and security, all handled by the FlowFuse infrastructure. You retain full control over configuration settings through a clean, intuitive interface, without needing to maintain multiple external systems. | ||
| FlowFuse consolidates those layers into a single integrated platform. It vides enterprise-grade features for management, scaling, deployment, and security, all handled by the FlowFuse infrastructure. You retain full control over configuration settings through a clean, intuitive interface, without needing to maintain multiple external systems. |
Contributor
There was a problem hiding this comment.
Suggested change
| FlowFuse consolidates those layers into a single integrated platform. It vides enterprise-grade features for management, scaling, deployment, and security, all handled by the FlowFuse infrastructure. You retain full control over configuration settings through a clean, intuitive interface, without needing to maintain multiple external systems. | |
| FlowFuse consolidates those layers into a single integrated platform. It provides enterprise-grade features for management, scaling, deployment, and security, all handled by the FlowFuse infrastructure. You retain full control over configuration settings through a clean, intuitive interface, without needing to maintain multiple external systems. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Related Issue(s)
Checklist
Working List