From 1328ca527217498756711eab2a6b7230490d2a7e Mon Sep 17 00:00:00 2001
From: sumitshinde-84 <shindesumit217@gmail.com>
Date: Fri, 14 Aug 2026 19:46:40 +0530
Subject: [PATCH 1/3] Add inline CTA images to next 50 blog posts by traffic

---
 src/blog/2023/01/environment-variables-in-node-red.md         | 3 +++
 src/blog/2023/03/3-quick-node-red-tips-4.md                   | 3 +++
 src/blog/2023/03/comparing-node-red-dashboards.md             | 3 +++
 src/blog/2023/06/import-modules.md                            | 3 +++
 .../07/how-to-build-a-opc-client-dashboard-in-node-red.md     | 3 +++
 .../07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md     | 3 +++
 src/blog/2023/07/influxdb-historical-data.md                  | 3 +++
 src/blog/2023/08/flowforge-is-now-flowfuse.md                 | 3 +++
 src/blog/2023/12/device-agent-as-a-windows-service.md         | 3 +++
 src/blog/2024/01/dashboard-2-multi-user.md                    | 3 +++
 src/blog/2024/02/connect-node-red-to-kepware-opc.md           | 2 ++
 src/blog/2024/03/dashboard-getting-started.md                 | 3 +++
 src/blog/2024/03/using-kafka-with-node-red.md                 | 3 +++
 src/blog/2024/04/displaying-logged-in-users-on-dashboard.md   | 3 +++
 src/blog/2024/05/exploring-node-red-dashboard-2-widgets.md    | 3 +++
 src/blog/2024/05/mapping-location-on-dashboard-2.md           | 3 +++
 src/blog/2024/06/dashboard-1-deprecated.md                    | 3 +++
 src/blog/2024/08/comparing-dashboard-2-with-uibuilder.md      | 3 +++
 src/blog/2024/08/customise-theming-in-your-dashboards.md      | 3 +++
 src/blog/2024/08/opc-ua-to-mqtt-with-node-red.md              | 3 +++
 src/blog/2024/08/opentelemetry-with-node-red.md               | 3 +++
 src/blog/2024/09/how-to-scrape-web-data-with-node-red.md      | 3 +++
 src/blog/2024/09/how-to-use-subflow-in-node-red.md            | 3 +++
 src/blog/2024/12/flowfuse-release-2-12.md                     | 3 +++
 src/blog/2024/12/publishing-modbus-data-to-uns.md             | 3 +++
 src/blog/2025/02/interacting-with-arduino-using-node-red.md   | 3 +++
 src/blog/2025/02/node-red-academy-announcement.md             | 4 +++-
 ...gning-flexible-cron-schedules-in-flowfuse-with-node-red.md | 3 +++
 .../2025/05/how-to-generate-pdf-reports-using-node-red.md     | 3 +++
 src/blog/2025/06/what-is-mes.md                               | 3 +++
 ...ed-opcua-real-time-subscriptions-alarms-historical-data.md | 3 +++
 src/blog/2025/09/poka-yoke-mistake-proofing.md                | 3 +++
 src/blog/2025/09/what-is-takt-time.md                         | 3 +++
 src/blog/2025/10/building-mcp-server-using-flowfuse.md        | 3 +++
 src/blog/2025/10/node-red-vs-flowfuse.md                      | 3 +++
 src/blog/2025/10/plc-to-mqtt-using-flowfuse.md                | 3 +++
 src/blog/2025/10/using-ethernet-ip-with-flowfuse.md           | 3 +++
 src/blog/2025/11/building-hmi-for-equipment-control.md        | 3 +++
 src/blog/2025/12/kafka-vs-mqtt.md                             | 3 +++
 src/blog/2025/12/node-red-buffer-parser-industrial-data.md    | 3 +++
 src/blog/2025/12/node-red-timer.md                            | 3 +++
 src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md     | 3 +++
 src/blog/2025/12/what-is-teep.md                              | 3 +++
 src/blog/2026/01/opcua-vs-mqtt.md                             | 3 +++
 src/blog/2026/01/why-modbus-still-exist.md                    | 3 +++
 src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md                  | 3 +++
 src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md     | 3 +++
 src/blog/2026/04/diagnosing-modbus-degradation.md             | 3 +++
 src/blog/2026/04/modbus-polling-best-practices.md             | 3 +++
 src/blog/2026/06/node-red-5-on-flowfuse.md                    | 3 +++
 50 files changed, 149 insertions(+), 1 deletion(-)

diff --git a/src/blog/2023/01/environment-variables-in-node-red.md b/src/blog/2023/01/environment-variables-in-node-red.md
index 3e4dd70fde..41eee26f10 100644
--- a/src/blog/2023/01/environment-variables-in-node-red.md
+++ b/src/blog/2023/01/environment-variables-in-node-red.md
@@ -63,6 +63,9 @@ Leveraging environment variables can also be done with other nodes, like for exa
 
 Node-RED allows you to set environment variables, but not to change them when executing flows. If you want to update data during execution, look into using [persistent context](/docs/user/persistent-context/). Node-RED doesn’t support Environment Variables like other programming environments do. When the flow is deployed the environment variables are replaced with the known values at that time. This is the biggest gotcha for most developers.
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ### Predefined variables
 
 Our first example was using a predefined variable, exposed by Node-RED. As of 3.0 it exposes a few environment variables among which `NR_NODE_NAME`, `NR_GROUP_NAME`, and `NR_FLOW_NAME`.
diff --git a/src/blog/2023/03/3-quick-node-red-tips-4.md b/src/blog/2023/03/3-quick-node-red-tips-4.md
index 8aac577960..32022b5d63 100644
--- a/src/blog/2023/03/3-quick-node-red-tips-4.md
+++ b/src/blog/2023/03/3-quick-node-red-tips-4.md
@@ -28,6 +28,9 @@ You can in turn use this to ignore values that deviate too far from the sample.
 [{"id":"9484c25a0120bd48","type":"group","z":"dd95c0bca1101c86","name":"Automatically outputs random value (temperature in Celcius) between 0 & 25 every second","style":{"label":!0},"nodes":["e4f972f9daad6246","c7fc075a1915e87b","966a772c46dc2888"],"x":34,"y":59,"w":574,"h":82},{"id":"e4f972f9daad6246","type":"link out","z":"dd95c0bca1101c86","g":"9484c25a0120bd48","name":"link out 1","mode":"link","links":["33594c64783cdc45","e6bf7b494b48861e"],"x":355,"y":100,"wires":[]},{"id":"c7fc075a1915e87b","type":"inject","z":"dd95c0bca1101c86","g":"9484c25a0120bd48","name":"","props":[],"repeat":"1","crontab":"","once":!1,"onceDelay":0.1,"topic":"","x":130,"y":100,"wires":[["966a772c46dc2888"]]},{"id":"966a772c46dc2888","type":"random","z":"dd95c0bca1101c86","g":"9484c25a0120bd48","name":"","low":"0","high":"25","inte":"true","property":"payload","x":260,"y":100,"wires":[["e4f972f9daad6246"]]},{"id":"37380f26e8bfc98a","type":"group","z":"dd95c0bca1101c86","name":"Calculate average, high and low, save to flow","style":{"label":!0},"nodes":["cc3978c7c4ea56ed","e1819526a5f365c8","33594c64783cdc45","fea261a15b3b7683","e28a69232f1cac53","aecb1727be523240","e30039ee13e480a8"],"x":34,"y":259,"w":552,"h":142},{"id":"cc3978c7c4ea56ed","type":"change","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"","rules":[{"t":"set","p":"high","pt":"flow","to":"payload","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":!1,"x":310,"y":300,"wires":[["aecb1727be523240"]]},{"id":"e1819526a5f365c8","type":"change","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"","rules":[{"t":"set","p":"low","pt":"flow","to":"payload","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":!1,"x":310,"y":360,"wires":[["e30039ee13e480a8"]]},{"id":"33594c64783cdc45","type":"link in","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"link in 1","links":["c07b2e101cecbd3b","e4f972f9daad6246"],"x":75,"y":320,"wires":[["e28a69232f1cac53","fea261a15b3b7683"]]},{"id":"fea261a15b3b7683","type":"smooth","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"Min","property":"payload","action":"min","count":"100","round":"2","mult":"single","reduce":!1,"x":170,"y":360,"wires":[["e1819526a5f365c8"]]},{"id":"e28a69232f1cac53","type":"smooth","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"Max","property":"payload","action":"max","count":"100","round":"2","mult":"single","reduce":!1,"x":170,"y":300,"wires":[["cc3978c7c4ea56ed"]]},{"id":"aecb1727be523240","type":"debug","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"debug 23","active":!0,"tosidebar":!1,"console":!1,"tostatus":!0,"complete":"payload","targetType":"msg","statusVal":"payload","statusType":"auto","x":480,"y":300,"wires":[]},{"id":"e30039ee13e480a8","type":"debug","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"debug 25","active":!0,"tosidebar":!1,"console":!1,"tostatus":!0,"complete":"payload","targetType":"msg","statusVal":"payload","statusType":"auto","x":480,"y":360,"wires":[]},{"id":"ec11a9ee9148b0b5","type":"group","z":"dd95c0bca1101c86","name":"Evaluate if an incoming value is between flow.high and flow.low, if it is not, send the message down a different wire and show an alert in debug","style":{"label":!0},"nodes":["9393c22b2e3c1ec8","1cd18307cb919159","7c1f474e646765a7","a209cd10f33ec401","f4b15283e55babf4","e6bf7b494b48861e"],"x":34,"y":419,"w":1032,"h":162},{"id":"9393c22b2e3c1ec8","type":"switch","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"Was the value between flow.high and flow.low?","property":"payload","propertyType":"msg","rules":[{"t":"btwn","v":"high","vt":"flow","v2":"low","v2t":"flow"},{"t":"else"}],"checkall":"true","repair":!1,"outputs":2,"x":300,"y":480,"wires":[["1cd18307cb919159"],["7c1f474e646765a7","a209cd10f33ec401"]]},{"id":"1cd18307cb919159","type":"debug","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"debug 15","active":!0,"tosidebar":!0,"console":!1,"tostatus":!1,"complete":"false","statusVal":"","statusType":"auto","x":560,"y":460,"wires":[]},{"id":"7c1f474e646765a7","type":"debug","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"debug 16","active":!1,"tosidebar":!0,"console":!1,"tostatus":!1,"complete":"false","statusVal":"","statusType":"auto","x":560,"y":540,"wires":[]},{"id":"a209cd10f33ec401","type":"change","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"Alert to debug when value is outside of the range","rules":[{"t":"set","p":"payload","pt":"msg","to":"The value was outside of the range","tot":"str"}],"action":"","property":"","from":"","to":"","reg":!1,"x":690,"y":500,"wires":[["f4b15283e55babf4"]]},{"id":"f4b15283e55babf4","type":"debug","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"debug 17","active":!0,"tosidebar":!0,"console":!1,"tostatus":!1,"complete":"false","statusVal":"","statusType":"auto","x":960,"y":500,"wires":[]},{"id":"e6bf7b494b48861e","type":"link in","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"link in 2","links":["e4f972f9daad6246","c07b2e101cecbd3b"],"x":75,"y":480,"wires":[["9393c22b2e3c1ec8"]]},{"id":"caf4214602d5f2c9","type":"group","z":"dd95c0bca1101c86","name":"Manually send a spurious value","style":{"label":!0},"nodes":["14097fb7ba3a9ecc","c07b2e101cecbd3b"],"x":34,"y":159,"w":232,"h":82},{"id":"14097fb7ba3a9ecc","type":"inject","z":"dd95c0bca1101c86","g":"caf4214602d5f2c9","name":"","props":[{"p":"payload"}],"repeat":"","crontab":"","once":!1,"onceDelay":0.1,"topic":"","payload":"75","payloadType":"num","x":130,"y":200,"wires":[["c07b2e101cecbd3b"]]},{"id":"c07b2e101cecbd3b","type":"link out","z":"dd95c0bca1101c86","g":"caf4214602d5f2c9","name":"link out 2","mode":"link","links":["33594c64783cdc45","e6bf7b494b48861e"],"x":225,"y":200,"wires":[]}]
 ```
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ### 2. Perform simple maths functions using JSONata in Change nodes
 
 You can perform basic maths functions using the Change node and JSONata. Let's say you wanted to take a payload and multiply it by a value. You could use a custom node such as [node-red-contrib-calc](https://flows.nodered.org/node/node-red-contrib-calc) but you can also easily complete the same task within a change node. 
diff --git a/src/blog/2023/03/comparing-node-red-dashboards.md b/src/blog/2023/03/comparing-node-red-dashboards.md
index 10a52bae9f..468ff2e0a9 100644
--- a/src/blog/2023/03/comparing-node-red-dashboards.md
+++ b/src/blog/2023/03/comparing-node-red-dashboards.md
@@ -74,6 +74,9 @@ There is also an [ongoing discussion](https://github.com/node-red/node-red/issue
 
 I believe a few improvements to the install process could make FlexDash a much more popular custom node.
 
+:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 ## How easy is it to get your first demo dashboard running?
 
 ### FlexDash - 1st place
diff --git a/src/blog/2023/06/import-modules.md b/src/blog/2023/06/import-modules.md
index ad0ec3bffc..e057095d13 100644
--- a/src/blog/2023/06/import-modules.md
+++ b/src/blog/2023/06/import-modules.md
@@ -87,6 +87,9 @@ Recently we wanted to use [moment](https://www.npmjs.com/package/moment) for som
 
 So, all we needed to do was import the module into a function node, and define our comparison there instead, here's a working example:
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ## Example: Easy CRC
 
 <video width="560" height="315" controls>
diff --git a/src/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md b/src/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md
index bc48c55f41..05a360b2f6 100644
--- a/src/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md
+++ b/src/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md
@@ -128,6 +128,9 @@ You can import this flow into Node-RED using the code below:
 
 To understand what is going on in this flow, we must refer back to the OPC UA Simulation Server `Address Space` tab.  
 
+:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 When we browse the OPC Server base folder structure in Node-RED, we will be browsing everything included under the `Objects` tree.  
 
 ![address-space.png](./images/opc-ua-3/address-space.png){data-zoomable}
diff --git a/src/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md b/src/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md
index 256dc92918..2e77006d2a 100644
--- a/src/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md
+++ b/src/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md
@@ -152,6 +152,9 @@ We can confirm the values are being stored in memory by checking the flow contex
 ![Screenshot showing the flow variables in the context data tab](./images/opc-ua-1/context-data-2.png "Screenshot showing the flow variables in the context data tab")
 Each time we hit refresh, the values change, confirming that the values are randomly changing every second.
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 The last, and most important part of the flow, is the `Compact-Server` node, which actually stands alone without any incoming or outgoing connections.
 
 !["Compact Server Node"](./images/opc-ua-1/compact-server-node.png "Compact Server Node")
diff --git a/src/blog/2023/07/influxdb-historical-data.md b/src/blog/2023/07/influxdb-historical-data.md
index 01e96d381a..662d3ae793 100644
--- a/src/blog/2023/07/influxdb-historical-data.md
+++ b/src/blog/2023/07/influxdb-historical-data.md
@@ -93,6 +93,9 @@ I selected “Generate All Access API Token,” but eventually you will want a c
 
 Copy your token and do not share it!  (mine will be deleted later)
 
+:::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::
+
 ## Connecting Node-RED to InfluxDB
 
 Navigate to “Manage Palette” in the Node-RED hamburger menu in the upper right corner of the flow editor.  I did a search for InfluxDB and selected the most popular one, “node-red-contrib-influxdb” by looking at the number of downloads per week at [https://flows.nodered.org/node/node-red-contrib-influxdb](https://flows.nodered.org/node/node-red-contrib-influxdb).  When you are just starting out, it can be a smart decision to go with the popular option. The popularity indicates a level of trust and adoption within the community, making it a reliable choice for beginners
diff --git a/src/blog/2023/08/flowforge-is-now-flowfuse.md b/src/blog/2023/08/flowforge-is-now-flowfuse.md
index c9e0c96d6b..36184bdf03 100644
--- a/src/blog/2023/08/flowforge-is-now-flowfuse.md
+++ b/src/blog/2023/08/flowforge-is-now-flowfuse.md
@@ -40,6 +40,9 @@ We are happy to announce that FlowForge is changing its name to FlowFuse. Changi
 
 We believe that this new name better reflects our core mission and aspirations. Just as electricity fuses elements to create energy, the FlowFuse platform fuses together data, ideas, processes, and technologies to generate a powerful force of innovation and transformation.
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 Selecting a new name for a company or product is never easy. Some of the requirements we set for a new name were: 1) it should be reasonably close to FlowForge so it will be easier to transition the brand identity, 2) it should even better reflect our mission, and 3) keeping the FF acronym will help with environment variable prefixes :-). I think we have accomplished all the above and am delighted to move forward as FlowFuse.
 
 **What to Expect Next**
diff --git a/src/blog/2023/12/device-agent-as-a-windows-service.md b/src/blog/2023/12/device-agent-as-a-windows-service.md
index ae1c31db6f..da29406263 100644
--- a/src/blog/2023/12/device-agent-as-a-windows-service.md
+++ b/src/blog/2023/12/device-agent-as-a-windows-service.md
@@ -88,6 +88,9 @@ icacls c:\opt\flowfuse-device /grant "user":F /T
 ```
 _where `"user"` is the service account (not the admin account)_
 
+:::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::
+
 ## Install nssm
 `nssm` can simply be downloaded and executed from any path.
 We will download it to the `c:\opt` directory, extract the files and copy the 64 bit version to the current directory.
diff --git a/src/blog/2024/01/dashboard-2-multi-user.md b/src/blog/2024/01/dashboard-2-multi-user.md
index 5d8245df5e..311e3f2f69 100644
--- a/src/blog/2024/01/dashboard-2-multi-user.md
+++ b/src/blog/2024/01/dashboard-2-multi-user.md
@@ -52,6 +52,9 @@ For all our Teams and Enterprise Self-Hosted customers who also want to use the
 
 Alternatively, if you're looking to elevate your Node-RED infrastructure, [book in a chat with us](/contact-us) to talk about how FlowFuse can help.
 
+:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 ### Using the Plugin
 
 Once enabled, any messages emitted by a Dashboard 2.0 node will contain a new `msg._client.user` object, e.g:
diff --git a/src/blog/2024/02/connect-node-red-to-kepware-opc.md b/src/blog/2024/02/connect-node-red-to-kepware-opc.md
index 8dec68f0c4..6dee80a08a 100644
--- a/src/blog/2024/02/connect-node-red-to-kepware-opc.md
+++ b/src/blog/2024/02/connect-node-red-to-kepware-opc.md
@@ -57,6 +57,8 @@ Next, let's configure the **OPC UA Client**.  Click the **pencil** to add a new
 
 For the endpoint, **copy** the endpoint definition from the KepserverEX OPC UA Configuration Manager.  In our example, it is ```opc.tcp://127.0.0.1:49320```, and paste it into the Endpoint.  For SecurityPolicy select **Basic256Sha256**. For SecurityMode, select **Sign&Encrypt**.  Lastly, we will be selecting **Anonymous**.  Click **Update**, then **Deploy**.  
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
 
 Trigger the flow by **clicking** on the inject node.  The server may not connect at this time, and it is expected.
 
diff --git a/src/blog/2024/03/dashboard-getting-started.md b/src/blog/2024/03/dashboard-getting-started.md
index 90c0700810..406a8c2e6d 100644
--- a/src/blog/2024/03/dashboard-getting-started.md
+++ b/src/blog/2024/03/dashboard-getting-started.md
@@ -60,6 +60,9 @@ Notice too that Dashboard will automatically setup some underlying configuration
 - `ui-group`: Each group contains a collection of widgets, and can be used to organize your Dashboard into logical sections.
 - `ui-theme`: Each `ui-page` can be assigned a given theme. Your "Themes" provide control over the aesthetic of your Dashboard like color, padding and margins.
 
+:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 ## Configuring your layout
 
 Dashboard 2.0 adds a dedicated sidebar to Node-RED to provide a centralized view of your pages, groups and widgets. From here you can add new pages and groups, modify existing settings, and re-order content to your liking.
diff --git a/src/blog/2024/03/using-kafka-with-node-red.md b/src/blog/2024/03/using-kafka-with-node-red.md
index 2250c95861..022ee6155c 100644
--- a/src/blog/2024/03/using-kafka-with-node-red.md
+++ b/src/blog/2024/03/using-kafka-with-node-red.md
@@ -50,6 +50,9 @@ During the writing of this tutorial, I utilized [Aiven’s cloud data platform](
 ## Installing Dashboard 2.0
 We will be installing Dashboard 2.0 to display real-time temperature data of various regions on a chart. If you are new to Dashboard 2.0, we recommend referring to [Getting started with Dashboard 2.0](/blog/2024/03/dashboard-getting-started/)\, which covers everything from basic concepts to installation and creating your first dashboard seamlessly.
 
+:::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::
+
 ## Installing and configuring Kafka custom node
 
 1. Install `node-red-kafka-manager` by the palette manager.
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 72ee6e3856..f865b146c8 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
@@ -109,6 +109,9 @@ Behind the scenes, the user addon is appending the user object to the `msg`, via
 
 When running Node-RED Dashboard 2.0 on FlowFuse, you'll have a new tab available in the "Dashboard 2.0" sidebar in the Node-RED Editor, you just have to navigate to the "FF Auth" tab and you’ll see two options.
 
+:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 **Option 1: Include Client Data**
 
 By default, this option is enabled. When this option is enabled, an object with user information will be added to the “msg” emitted by any widget of the Node-RED Dashboard 2.0.
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 5ea2f89a20..0214da44c7 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
@@ -76,6 +76,9 @@ return msg;
 
 Similarly, you can do this for storing expense data submitted using the expense submission form.
 
+:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 ### Displaying Notifications
 
 For displaying notifications on the dashboard, we'll utilize the **ui-notification** widget, which emits notifications to the user's dashboard. It accepts `msg.payload` which should be a string format or raw HTML/JavaScript for custom formatting.
diff --git a/src/blog/2024/05/mapping-location-on-dashboard-2.md b/src/blog/2024/05/mapping-location-on-dashboard-2.md
index e679996ac1..8830fe98f1 100644
--- a/src/blog/2024/05/mapping-location-on-dashboard-2.md
+++ b/src/blog/2024/05/mapping-location-on-dashboard-2.md
@@ -97,6 +97,9 @@ Before plotting locations, we need to obtain the data first. For this purpose, w
 
 To ensure compatibility with the Worldmap custom node, we need to format the location data appropriately. 
 
+:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 1. Drag the **Change** node onto the canvas, and set the `msg.payload` to `msg.payload.vehicles`, and give it name **Set payload**.
 
 ![Screenshot of the Change node setting the payload to the vehicles JSON array containing actual vehicle location data](./images/mapping-location-on-dashboard-2-change-node.png "Screenshot of the Change node setting the payload to the vehicles JSON array containing actual vehicle location data"){data-zoomable}
diff --git a/src/blog/2024/06/dashboard-1-deprecated.md b/src/blog/2024/06/dashboard-1-deprecated.md
index 0c247084cb..a51c353626 100644
--- a/src/blog/2024/06/dashboard-1-deprecated.md
+++ b/src/blog/2024/06/dashboard-1-deprecated.md
@@ -42,6 +42,9 @@ We are actively investing into the development of FlowFuse Dashboard, and releas
 
 If there are any other features you'd like to see, please do open a [Feature Request](https://github.com/FlowFuse/node-red-dashboard/issues/new/choose), and we'll do our best to accommodate.
 
+:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 ## Getting Started with FlowFuse Dashboard
 
 If you're ready to get started with FlowFuse Dashboard, you can install it directly from the Node-RED Palette Manager. Simply search for `@flowfuse/node-red-dashboard` and install the latest version.
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 34cec763ef..d37629c463 100644
--- a/src/blog/2024/08/comparing-dashboard-2-with-uibuilder.md
+++ b/src/blog/2024/08/comparing-dashboard-2-with-uibuilder.md
@@ -85,6 +85,9 @@ FlowFuse Dashboard offers an extensive set of UI elements, including forms, drop
 
 UI-Builder also offers a number of widgets, but these are not as user-friendly as those in FlowFuse Dashboard. Users must send a JSON config object, which can be complex for new users who lack knowledge of HTML/CSS. Additionally, handling widget data requires using UI-Builder's methods, which can further increase complexity. However, UI-Builder's strength lies in its flexibility, allowing any HTML element to be used as a component, and it also supports the W3C standard web components. Despite this, users need to perform a lot of additional tasks to get everything set up and will have the hassle of writing things.
 
+:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 ## Changing the UI at Runtime
 
 ### FlowFuse Dashboard
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 bd862b690f..3f5fda3c40 100644
--- a/src/blog/2024/08/customise-theming-in-your-dashboards.md
+++ b/src/blog/2024/08/customise-theming-in-your-dashboards.md
@@ -152,6 +152,9 @@ You can replace the URL with your logo's URL or set it using the `msg.payload` a
 !["Screenshot of the Dashboard displaying the added logo in the header"](./images/logo-added-dashboard.png "Screenshot of the Dashboard displaying the added logo in the header"){data-zoomable}
 _Screenshot of the Dashboard displaying the added logo in the header_
 
+:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 ### Right Side of the Header
 
 To render elements on the right side of the header, you can use the empty div element having the `#app-bar-actions` ID, in which we can add elements.
diff --git a/src/blog/2024/08/opc-ua-to-mqtt-with-node-red.md b/src/blog/2024/08/opc-ua-to-mqtt-with-node-red.md
index 2ad395dcdc..dc6296e1a8 100644
--- a/src/blog/2024/08/opc-ua-to-mqtt-with-node-red.md
+++ b/src/blog/2024/08/opc-ua-to-mqtt-with-node-red.md
@@ -95,6 +95,9 @@ In this section, I'll demonstrate how to bridge OPC UA data to MQTT using Node-R
 
 - MQTT Broker: We’ll need an MQTT broker for data communication. FlowFuse offers an integrated MQTT Broker Service within Platform for easy setup. For more details, check out [FlowFuse's MQTT Broker Announcement](/blog/2024/10/announcement-mqtt-broker/).
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 ### Retrieving Data from the OPC UA Server
 
 To begin retrieving data from your OPC UA server using Node-RED, follow these steps:
diff --git a/src/blog/2024/08/opentelemetry-with-node-red.md b/src/blog/2024/08/opentelemetry-with-node-red.md
index deb9278023..2bc0901370 100644
--- a/src/blog/2024/08/opentelemetry-with-node-red.md
+++ b/src/blog/2024/08/opentelemetry-with-node-red.md
@@ -87,6 +87,9 @@ For demonstration purposes, we will use a flow that simulates sensor reading and
 
 Deploy the flow above, and you might see a delay in the data shown on the debug panel. For this example, we added a Delay node before the Change node that converts temperature data from Kelvin to Celsius. While this delay is visible here, finding such delays in larger flows with many nodes can be difficult and time-consuming. Open Telemetry makes this easier by giving you detailed traces that show where delays or issues are happening
 
+:::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::
+
 ### Prerequisite
 
 Before you start, ensure you have the following:
diff --git a/src/blog/2024/09/how-to-scrape-web-data-with-node-red.md b/src/blog/2024/09/how-to-scrape-web-data-with-node-red.md
index 0a9733c1d2..5e39836854 100644
--- a/src/blog/2024/09/how-to-scrape-web-data-with-node-red.md
+++ b/src/blog/2024/09/how-to-scrape-web-data-with-node-red.md
@@ -49,6 +49,9 @@ To start scraping data, follow these steps to send an HTTP GET request to the we
 
 Once deployed, click the **inject** button. You will see the raw HTML printed in the debug panel.
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ### Parsing and Extracting Data from HTML
 
 Next, we need to process the raw HTML to extract meaningful data. This involves parsing the HTML content and identifying the specific information you want. To do this, first analyze the HTML structure of the webpage by opening the browser’s developer tools (press Ctrl + I or F12) and inspecting the elements to locate where the data is and in which HTML elements it resides.
diff --git a/src/blog/2024/09/how-to-use-subflow-in-node-red.md b/src/blog/2024/09/how-to-use-subflow-in-node-red.md
index ce45b47f55..ef5d7bd2f5 100644
--- a/src/blog/2024/09/how-to-use-subflow-in-node-red.md
+++ b/src/blog/2024/09/how-to-use-subflow-in-node-red.md
@@ -101,6 +101,9 @@ _Image showing subflow node added in the node palette_
 
 Once selected, the Subflow will be added to the node palette like other nodes. The selected flow will also be converted into a single node representing the Subflow.
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ### Adding Properties to the Subflow
 
 1. Double-click on the Subflow, then click on **"Edit Subflow template"**.
diff --git a/src/blog/2024/12/flowfuse-release-2-12.md b/src/blog/2024/12/flowfuse-release-2-12.md
index 5a5d5c1de4..788e19f836 100644
--- a/src/blog/2024/12/flowfuse-release-2-12.md
+++ b/src/blog/2024/12/flowfuse-release-2-12.md
@@ -70,6 +70,9 @@ _Screenshot showing the UI for selecting your Team's type, when onboarding throu
 
 <!-- <img width="438" alt="image" src="https://github.com/user-attachments/assets/da6fde55-27bc-42d7-afcc-19235661b558" /> -->
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ### Remote Instances
 
 When you create a Free team, an Application is created for you automatically. Applications in FlowFuse help you organise and group your resources, from Instances to DevOps Pipelines and Snapshots for Version Control. Within your new application, you can "register" your first Remote Instance. 
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 2761608a22..65a9972f6e 100644
--- a/src/blog/2024/12/publishing-modbus-data-to-uns.md
+++ b/src/blog/2024/12/publishing-modbus-data-to-uns.md
@@ -134,6 +134,9 @@ If you prefer a video explanation, [Kurt Braun](https://www.linkedin.com/in/wago
 
 After collecting data from your Modbus device, the next step is transforming it into a usable format for cloud-based IoT applications. Modbus data typically comes in raw register values, and you may need to convert these values into human-readable formats like temperature, pressure, or other measurements.
 
+:::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::
+
 Let's walk through the transformation process step by step.
 
 **Step 2.1: Parsing and Converting Raw Modbus Data**
diff --git a/src/blog/2025/02/interacting-with-arduino-using-node-red.md b/src/blog/2025/02/interacting-with-arduino-using-node-red.md
index 9bb70da03f..ae95eb532c 100644
--- a/src/blog/2025/02/interacting-with-arduino-using-node-red.md
+++ b/src/blog/2025/02/interacting-with-arduino-using-node-red.md
@@ -59,6 +59,9 @@ _Importing Standard Firmata setup sketch from examples in Arduino IDE_
 
 Once the upload is complete, the Arduino is ready to communicate via the Firmata protocol.
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ### Step 3: Connecting Node-RED to Arduino via Serial Communication
 
 As mentioned earlier, Firmata typically works over a serial connection (such as USB), enabling communication between the Arduino board and your Node-RED instance. The serial communication allows Node-RED to send commands to the Arduino and receive data from it.
diff --git a/src/blog/2025/02/node-red-academy-announcement.md b/src/blog/2025/02/node-red-academy-announcement.md
index 6f698493a6..cdaa65e42a 100644
--- a/src/blog/2025/02/node-red-academy-announcement.md
+++ b/src/blog/2025/02/node-red-academy-announcement.md
@@ -52,6 +52,9 @@ All courses completed through Node-RED Academy provide a formal certification up
 
 The credential will be evidence of your Node-RED knowledge and abilities, and will be a great way to demonstrate your expertise to potential employers or clients.
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ## What Courses are Included?
 
 Our first course, The [Node-RED Fundamentals](https://node-red-academy.learnworlds.com/), takes about 90 minutes to complete, is free and available now. [Check it out!](https://node-red-academy.learnworlds.com/).
@@ -70,7 +73,6 @@ We also have plans for the following courses to follow in the future:
 
 This list will likely grow beyond this too. We will be evolving our courses based on feedback and ideas from the community too!
 
-
 ## Who's behind the Node-RED Academy?
 
 There are many great resources for Node-RED education out there, but the Node-RED Academy has been curated by the authors and developers behind Node-RED and covers everything you'll need to know from building your first flow to integrating with industrial hardware.
diff --git a/src/blog/2025/05/designing-flexible-cron-schedules-in-flowfuse-with-node-red.md b/src/blog/2025/05/designing-flexible-cron-schedules-in-flowfuse-with-node-red.md
index 7ef1f0e2cf..0a8e9c069f 100644
--- a/src/blog/2025/05/designing-flexible-cron-schedules-in-flowfuse-with-node-red.md
+++ b/src/blog/2025/05/designing-flexible-cron-schedules-in-flowfuse-with-node-red.md
@@ -134,6 +134,9 @@ To make it even easier to create and customize cron patterns, the cron-plus node
 ![Image showing the easy builder feature](./images/easy-builder.gif){data-zoomable}
 _Image showing the easy builder feature_
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ### Solar Event Schedules
 
 Solar event-based triggers are a great feature in cron-plus for automating tasks based on sunlight events like sunrise, sunset, dawn, and dusk. You can fine-tune your triggers with offsets, like triggering an action 30 minutes after sunset.
diff --git a/src/blog/2025/05/how-to-generate-pdf-reports-using-node-red.md b/src/blog/2025/05/how-to-generate-pdf-reports-using-node-red.md
index 69a7930423..32ee228a32 100644
--- a/src/blog/2025/05/how-to-generate-pdf-reports-using-node-red.md
+++ b/src/blog/2025/05/how-to-generate-pdf-reports-using-node-red.md
@@ -191,6 +191,9 @@ This example creates a simple PDF featuring a centered logo, a title, a subtitle
 ![Example pdf result](./images/example-pdf.png){data-zoomable}
 _Example pdf result_
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ### Step 3: Creating a Flow to Generate a PDF
 
 Let's learn how to generate a PDF using dynamic inputs. For this, we’ll use the same example PDF report shown earlier, but this time, we’ll replace the hardcoded values with dynamic input data.
diff --git a/src/blog/2025/06/what-is-mes.md b/src/blog/2025/06/what-is-mes.md
index 31eea9d61b..f6e21f6979 100644
--- a/src/blog/2025/06/what-is-mes.md
+++ b/src/blog/2025/06/what-is-mes.md
@@ -38,6 +38,9 @@ The MES collects real-time information to tell you:
 
 This means you always know the exact status of your production, live. Such real-time insights and operational control are at the core of what a modern MES delivers, often leveraging flexible platforms like FlowFuse to connect diverse factory data and orchestrate workflows.
 
+:::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::
+
 ## What MES is NOT 
 
 It's easy to get confused about all the different computer systems in a factory. To really get what a MES does, it helps to know what it isn't.
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 e53e9d4d51..06feda1ae9 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
@@ -126,6 +126,9 @@ When using the "multiple" topic, each value update arrives in OPC UA's DataValue
 
 Subscribing to multiple tags with OpcUa-Item nodes returns just the value.
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 ### Stopping Subscriptions
 
 To stop receiving updates and free up server resources, you have two options:
diff --git a/src/blog/2025/09/poka-yoke-mistake-proofing.md b/src/blog/2025/09/poka-yoke-mistake-proofing.md
index e195b8816a..e73cd1963e 100644
--- a/src/blog/2025/09/poka-yoke-mistake-proofing.md
+++ b/src/blog/2025/09/poka-yoke-mistake-proofing.md
@@ -80,6 +80,9 @@ The impact of mistake-proofing extends far beyond just catching errors. By desig
 
 Errors in manual assembly lead to increased scrap rates, rework, and delays, all contributing to higher production costs. By eliminating errors at the source, the cost of mistakes within a company is reduced significantly. Companies implementing poka yoke techniques saw a 25% increase in productivity, with time previously spent correcting errors now available for value-added activities.
 
+:::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::
+
 Mistake-proofing creates safer processes by eliminating conditions that lead to accidents. When errors can literally mean life or death (as in pharmaceutical manufacturing), poka yoke becomes mission-critical. Workers experience less frustration from rework and greater confidence in their processes, leading to improved morale. Successful implementation leads to a 20% improvement in customer satisfaction through consistent product quality and reliability.
 
 The benefits of poka yoke in manufacturing deliver measurable business outcomes: defect elimination achieving near-zero defects, waste reduction across the eight forms identified in lean manufacturing, process simplification turning complex procedures into straightforward steps, real-time correction catching mistakes immediately rather than weeks later, scalable quality built into the system rather than dependent on individual heroics, and continuous improvement creating a foundation for ongoing kaizen activities.
diff --git a/src/blog/2025/09/what-is-takt-time.md b/src/blog/2025/09/what-is-takt-time.md
index c8f88e55d9..c15198fb10 100644
--- a/src/blog/2025/09/what-is-takt-time.md
+++ b/src/blog/2025/09/what-is-takt-time.md
@@ -130,6 +130,9 @@ Understanding the meaning of takt time in this result shows the production line
 
 This example illustrates why defining takt time correctly matters for matching cycle time to customer demand. Cycle times significantly exceeding takt time reveal capacity shortfalls requiring immediate attention. Cycle times falling well below takt time suggest excess capacity that might be redeployed elsewhere or indicate risk of overproduction if production control systems fail to prevent excess output.
 
+:::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::
+
 ### Example 2: Electronics Assembly (Multiple Shifts)
 
 An electronics manufacturer operates two shifts producing circuit boards, with weekly demand of 2,400 units across five operating days. Each eight-hour shift allocates 40 minutes for breaks and 20 minutes for changeovers.
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 3e1548b371..2b4169ebfd 100644
--- a/src/blog/2025/10/building-mcp-server-using-flowfuse.md
+++ b/src/blog/2025/10/building-mcp-server-using-flowfuse.md
@@ -81,6 +81,9 @@ http://192.168.1.100:1880/mcp
 
 This URL allows AI agents to discover resources, execute tools, and interact with your flows.
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ### Securing Your MCP Server
 
 To ensure your MCP server is protected from unauthorized access, enable FlowFuse User Authentication.
diff --git a/src/blog/2025/10/node-red-vs-flowfuse.md b/src/blog/2025/10/node-red-vs-flowfuse.md
index 808621b53f..8055302ae6 100644
--- a/src/blog/2025/10/node-red-vs-flowfuse.md
+++ b/src/blog/2025/10/node-red-vs-flowfuse.md
@@ -66,6 +66,9 @@ FlowFuse provides role-based access control (RBAC) to define who edits flows ver
 
 For supply chain security, FlowFuse generates a Software Bill of Materials (SBOM) listing every node and dependency across your instances. Security teams can scan for vulnerabilities and track what needs updating.
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ### Team Collaboration and Version Control
 
 Node-RED was built for individual developers. When two people edit the same instance, the last save wins. No version history exists. No way to review changes before deployment. No rollback option.
diff --git a/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md b/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md
index 79a20ed4e5..0cde8d511d 100644
--- a/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md
+++ b/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md
@@ -120,6 +120,9 @@ The Node-RED ecosystem that powers FlowFuse offers comprehensive protocol suppor
 
 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.
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 ## Convincing the IT Team
 
 When talking to people in the IIoT community, one recurring challenge always comes up, **convincing the IT team**.
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 9ad9cac12d..7cbec0a932 100644
--- a/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md
+++ b/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md
@@ -122,6 +122,9 @@ To communicate with Allen-Bradley PLCs from FlowFuse, use the popular node-red-c
 
 Once installed, you'll find the EtherNet/IP nodes in your palette under the "plc" category. The main nodes are `ethernet-ip in` for reading data and `ethernet-ip out` for writing data to the PLC.
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 ## Configuring the EtherNet/IP Node
 
 Now that you have installed the EtherNet/IP node, it is time to configure the connection to your Allen-Bradley PLC.
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 61a930ffc7..dc6e182b51 100644
--- a/src/blog/2025/11/building-hmi-for-equipment-control.md
+++ b/src/blog/2025/11/building-hmi-for-equipment-control.md
@@ -123,6 +123,9 @@ After saving the connection configuration, specify the **variable addresses that
 
 For sending commands (start motor, stop motor, setpoints), drag the corresponding output node onto your canvas. When configuring it, select the **same Server/Connection** from the dropdown instead of creating a new one. This shared connection approach means the IP address, port, and credentials only need to be configured once and can be reused across all your PLC/server nodes. You then only need to specify the variable addresses that control your equipment, and connect those nodes to your dashboard buttons or automation logic.
 
+:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 **Important Note:** Some PLCs require configuration in their engineering software before allowing external access. For example, Siemens S7 requires **PUT/GET communication** enabled in TIA Portal, and Allen-Bradley controllers may need **explicit messaging** enabled in Studio 5000. Refer to your PLC’s documentation for any communication prerequisites.
 
 **Test Your Connection:**
diff --git a/src/blog/2025/12/kafka-vs-mqtt.md b/src/blog/2025/12/kafka-vs-mqtt.md
index 8fedcd9edd..b836640946 100644
--- a/src/blog/2025/12/kafka-vs-mqtt.md
+++ b/src/blog/2025/12/kafka-vs-mqtt.md
@@ -83,6 +83,9 @@ Unlike MQTT, messages don't disappear after delivery. Everything writes to disk.
 
 Early Kafka needed Apache Zookeeper for cluster coordination, which added complexity. Recent versions support KRaft mode that removes this dependency, though many production systems still run Zookeeper.
 
+:::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::
+
 ## The Real Differences
 
 ### Architecture Philosophy
diff --git a/src/blog/2025/12/node-red-buffer-parser-industrial-data.md b/src/blog/2025/12/node-red-buffer-parser-industrial-data.md
index aabd6cf388..14acad4dbb 100644
--- a/src/blog/2025/12/node-red-buffer-parser-industrial-data.md
+++ b/src/blog/2025/12/node-red-buffer-parser-industrial-data.md
@@ -132,6 +132,9 @@ return msg;
 
 This works, but it's also fragile. When you need to add a pressure reading next month, you're editing code and hoping you don't break the offset calculations. When someone else looks at this flow, they have no idea what's happening without reading the function and if they don't understand JavaScript, they're stuck.
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 Buffer Parser turns this into configuration you can see and modify without touching code. Let's walk through a practical example.
 
 > But before you start, make sure you have a Node-RED instance running on your edge device. The fastest, easiest, and most production-ready way is using FlowFuse. If you don't have an account yet, create one with our [free trial](https://app.flowfuse.com/). FlowFuse simplifies managing remote instances and provides the ability to create hosted instances, no matter how many you need to manage, it makes it easy. There are no deployment headaches either; everything is managed by FlowFuse with built-in security. You'll also get access to tools such as DevOps pipelines, snapshots for recovery, audit logs, real-time collaboration with granular role-based access control (RBAC), and much more.
diff --git a/src/blog/2025/12/node-red-timer.md b/src/blog/2025/12/node-red-timer.md
index cc36053fd3..29494577d5 100644
--- a/src/blog/2025/12/node-red-timer.md
+++ b/src/blog/2025/12/node-red-timer.md
@@ -102,6 +102,9 @@ The hourglass node responds to control commands sent via `msg.command`. The avai
 
 These commands control timer behavior.
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ### Implementing a Stopwatch Timer
 
 Build a basic **stopwatch flow**:
diff --git a/src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md b/src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md
index 62dd001345..3edada3ad8 100644
--- a/src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md
+++ b/src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md
@@ -132,6 +132,9 @@ Before exposing variables, you need to create an OPC UA server interface in your
 
 If you're using an S7-1500 PLC with firmware version 2.5 or higher, you have the option to enable the standard SIMATIC server interface. Simply check **Enable standard SIMATIC server interface** in the OPC UA settings. This automatically makes all PLC tags that are marked as accessible available through OPC UA.
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 **For S7-1200 PLCs (or manual configuration for S7-1500):**
 
 For S7-1200 PLCs, you must manually create a server interface and add the tags you want to expose:
diff --git a/src/blog/2025/12/what-is-teep.md b/src/blog/2025/12/what-is-teep.md
index 4d8d78a88c..49259e5238 100644
--- a/src/blog/2025/12/what-is-teep.md
+++ b/src/blog/2025/12/what-is-teep.md
@@ -82,6 +82,9 @@ In many cases, TEEP reveals that the fastest and cheapest way to increase output
 
 Importantly, TEEP is not about pushing equipment to run 24/7 at all costs. Instead, it provides the data needed to make **intentional, informed decisions** about scheduling, staffing, maintenance, and growth.
 
+:::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::
+
 ## TEEP vs OEE: Key Differences
 
 OEE and TEEP both measure equipment performance, but they look at different things. The big difference is what time period they measure against.
diff --git a/src/blog/2026/01/opcua-vs-mqtt.md b/src/blog/2026/01/opcua-vs-mqtt.md
index da65c5e38e..bef6366a6d 100644
--- a/src/blog/2026/01/opcua-vs-mqtt.md
+++ b/src/blog/2026/01/opcua-vs-mqtt.md
@@ -135,6 +135,9 @@ Implementing an OPC UA server requires managing an address space, handling multi
 
 This overhead is impractical for battery-powered sensors with infrequent reporting requirements. It's appropriate for a $2M manufacturing cell where understanding that a temperature reading represents "bearing temperature on the output shaft of motor 3, measured in Celsius, with a normal operating range of 40-65°C and critical alarm at 85°C" matters.
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 ### The Layer Mismatch
 
 Think about the OSI model, that seven-layer networking abstraction everyone learns and immediately forgets:
diff --git a/src/blog/2026/01/why-modbus-still-exist.md b/src/blog/2026/01/why-modbus-still-exist.md
index d9c4d3eba8..85d85f312b 100644
--- a/src/blog/2026/01/why-modbus-still-exist.md
+++ b/src/blog/2026/01/why-modbus-still-exist.md
@@ -77,6 +77,9 @@ Industrial automation is full of protocol wars where vendors push their preferre
 
 Modbus doesn't care. It works with everyone's equipment. This vendor neutrality has enormous practical value in facilities running mixed automation systems. A typical factory floor might have Rockwell PLCs, ABB drives, Schneider Electric power meters, and Siemens HMIs all talking to each other. Getting all those vendors' preferred protocols to coexist would be a nightmare. Getting them all to speak Modbus is trivial.
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 This creates competitive pressure that keeps Modbus relevant. Device manufacturers can't afford to skip Modbus support because doing so immediately excludes them from projects with heterogeneous automation systems. Even vendors with their own sophisticated protocols implement Modbus as a fallback, ensuring interoperability when nothing else works.
 
 The open nature also prevents the protocol from becoming a competitive weapon. Nobody can leverage Modbus to lock customers into their platform. Nobody can obsolete older Modbus devices by dropping support in newer products. The protocol's longevity is guaranteed by the fact that no single entity controls its fate.
diff --git a/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md b/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md
index 4a24357216..6c7b66f960 100644
--- a/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md
+++ b/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md
@@ -51,6 +51,9 @@ The catch is that Ethernet latency is not flat. It varies with network load, swi
 
 RTU offers better worst-case latency. TCP offers better average latency. In industrial control, worst-case is usually what you design for.
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 ## Failure Modes: What Breaks, How It Breaks, and Whether You Will Know
 
 This is where the two protocols diverge most sharply, and where choosing wrong costs the most.
diff --git a/src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md b/src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md
index f98c0a6204..a6cf799d12 100644
--- a/src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md
+++ b/src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md
@@ -54,6 +54,9 @@ For device manufacturers, the math is punishing. A Modbus RTU interface costs ro
 
 Certificate management alone has quietly killed more OPC UA deployments than any technical limitation. Certificates expire. They need to be provisioned, rotated, and trusted across every client and server. In an IT environment with dedicated security teams, this is manageable. In a plant where the automation engineer also handles PLC programming, HMI design, and network troubleshooting, it becomes an ongoing burden that nobody budgeted for and nobody wants to own.
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 The OPC Foundation recognized this. Companion specifications like OPC UA FX and the Field Level Communications initiative are genuine attempts to bring the protocol closer to the field device layer. Progress is real but slow, and in the meantime, device manufacturers continue defaulting to Modbus because it ships today without a compliance checklist.
 
 Complexity isn't a dealbreaker when the problem demands it. Nobody complains that OPC UA is too complex when it's modeling an entire production line in a SCADA system. The complexity tax only becomes fatal when the problem is simple and a simpler tool is sitting right there, already understood by the team, already working.
diff --git a/src/blog/2026/04/diagnosing-modbus-degradation.md b/src/blog/2026/04/diagnosing-modbus-degradation.md
index 66f8f4f224..afb5d8d3dd 100644
--- a/src/blog/2026/04/diagnosing-modbus-degradation.md
+++ b/src/blog/2026/04/diagnosing-modbus-degradation.md
@@ -64,6 +64,9 @@ Those connection slots release when the idle-connection timeout or the TCP FIN/R
 
 That regularity is the diagnostic signal. A device with intermittent hardware faults fails unpredictably. A device whose connection table is being exhausted fails on a clock. If you're seeing periodic offline events with suspiciously consistent timing, check your connection handling before you assume the device is faulty.
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 **Transaction ID handling** is worth checking in high-concurrency polling configurations. The [Modbus application protocol specification](https://www.modbus.org/file/secure/modbusprotocolspecification.pdf) defines Transaction IDs to match requests with responses. A polling stack that reuses Transaction IDs before receiving a response to the previous one can match incoming responses to the wrong pending request. When this occurs, the symptom is correct values appearing in the wrong registers. It doesn't show up as an error at all, which makes it unusually difficult to diagnose. If you're seeing values that are off by a plausible amount but never produce error codes, check whether your stack's Transaction ID handling is correct under concurrent load.
 
 The second TCP failure mode that's become more common as industrial networks gain remote access infrastructure is latency on routed network paths pushing transaction times past configured timeouts. This applies to any routed path: site-to-site VPNs, SD-WAN appliances, MPLS links with QoS misconfiguration, or firewalls with deep-packet inspection enabled for industrial protocols. Modbus TCP on a dedicated plant-floor LAN has round-trip latency in single-digit milliseconds. The same configuration over a site-to-site VPN or through a stateful firewall can see 80 to 200ms per transaction. If your timeouts were calculated against a local network and you've since added any routing hops, your effective timeout margin may now be zero under any congestion. The failures are load-dependent: worse during business hours, cleaner overnight, invisible when you run a manual test. The fix is the same as in the last article: measure actual round-trip time under realistic load, then set your timeout to 1.5 to 2x that value.
diff --git a/src/blog/2026/04/modbus-polling-best-practices.md b/src/blog/2026/04/modbus-polling-best-practices.md
index bb2cff8911..7b52aac707 100644
--- a/src/blog/2026/04/modbus-polling-best-practices.md
+++ b/src/blog/2026/04/modbus-polling-best-practices.md
@@ -55,6 +55,9 @@ This tiered approach does something important beyond just reducing bus load: it
 
 The pushback you'll hear is that tiered polling is harder to configure and harder to document. That's true. A single scan rate is simple to explain and simple to hand off. But simple to configure and correct are different things, and a polling architecture that silently misses events or saturates a serial bus isn't simple. It's a problem that hasn't surfaced yet.
 
+:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 One more thing worth stating plainly: your scan rate has to account for the device's actual response capability, not just the rate you want data. Some field devices, including older PLCs, low-cost sensors, and anything running on an 8-bit microcontroller with slow UART handling, need 50 to 150ms just to process a request and formulate a response. If your fast-tier scan rate is 100ms and your device needs 120ms to respond, you're not getting 100ms data. You're getting collisions, timeouts, and a maintenance headache. Measure actual device response times before setting your fast-tier interval. The device datasheet will give you a starting point; a protocol analyzer will give you the truth.
 
 ## How Timeout Misconfiguration Kills Stability
diff --git a/src/blog/2026/06/node-red-5-on-flowfuse.md b/src/blog/2026/06/node-red-5-on-flowfuse.md
index a55bf1cae2..7b7a22c1f5 100644
--- a/src/blog/2026/06/node-red-5-on-flowfuse.md
+++ b/src/blog/2026/06/node-red-5-on-flowfuse.md
@@ -64,6 +64,9 @@ The **redesigned sidebars** now behave the same on both sides of the editor. Con
 
 Underneath the visual changes are functional and security improvements across debugging, authentication, and TLS, the parts that matter most once Node-RED is running in production. If previous releases expanded what it could do, this one sharpens how it feels to use. For the full list, read the [release blog](https://nodered.org/blog/2026/06/09/version-5-0-released).
 
+:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ## What it means for industrial teams
 
 The editor is where your team spends its day, so changes here add up fast across a working week.

From 7dfcdbb3271561c59e2d5d3f004c9aa05a39b17f Mon Sep 17 00:00:00 2001
From: sumitshinde-84 <shindesumit217@gmail.com>
Date: Fri, 14 Aug 2026 20:53:40 +0530
Subject: [PATCH 2/3] fix broken links

---
 src/blog/2023/01/environment-variables-in-node-red.md           | 2 +-
 src/blog/2023/03/3-quick-node-red-tips-4.md                     | 2 +-
 src/blog/2023/03/comparing-node-red-dashboards.md               | 2 +-
 src/blog/2023/06/import-modules.md                              | 2 +-
 .../2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md  | 2 +-
 .../2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md  | 2 +-
 src/blog/2023/07/influxdb-historical-data.md                    | 2 +-
 src/blog/2023/08/flowforge-is-now-flowfuse.md                   | 2 +-
 src/blog/2023/12/device-agent-as-a-windows-service.md           | 2 +-
 src/blog/2024/01/dashboard-2-multi-user.md                      | 2 +-
 src/blog/2024/02/connect-node-red-to-kepware-opc.md             | 2 +-
 src/blog/2024/03/dashboard-getting-started.md                   | 2 +-
 src/blog/2024/03/using-kafka-with-node-red.md                   | 2 +-
 src/blog/2024/04/displaying-logged-in-users-on-dashboard.md     | 2 +-
 src/blog/2024/05/exploring-node-red-dashboard-2-widgets.md      | 2 +-
 src/blog/2024/05/mapping-location-on-dashboard-2.md             | 2 +-
 src/blog/2024/06/dashboard-1-deprecated.md                      | 2 +-
 src/blog/2024/08/comparing-dashboard-2-with-uibuilder.md        | 2 +-
 src/blog/2024/08/customise-theming-in-your-dashboards.md        | 2 +-
 src/blog/2024/08/opc-ua-to-mqtt-with-node-red.md                | 2 +-
 src/blog/2024/08/opentelemetry-with-node-red.md                 | 2 +-
 src/blog/2024/09/how-to-scrape-web-data-with-node-red.md        | 2 +-
 src/blog/2024/09/how-to-use-subflow-in-node-red.md              | 2 +-
 src/blog/2024/12/flowfuse-release-2-12.md                       | 2 +-
 src/blog/2024/12/publishing-modbus-data-to-uns.md               | 2 +-
 src/blog/2025/02/interacting-with-arduino-using-node-red.md     | 2 +-
 src/blog/2025/02/node-red-academy-announcement.md               | 2 +-
 ...signing-flexible-cron-schedules-in-flowfuse-with-node-red.md | 2 +-
 src/blog/2025/05/how-to-generate-pdf-reports-using-node-red.md  | 2 +-
 src/blog/2025/06/what-is-mes.md                                 | 2 +-
 ...nced-opcua-real-time-subscriptions-alarms-historical-data.md | 2 +-
 src/blog/2025/09/poka-yoke-mistake-proofing.md                  | 2 +-
 src/blog/2025/09/what-is-takt-time.md                           | 2 +-
 src/blog/2025/10/building-mcp-server-using-flowfuse.md          | 2 +-
 src/blog/2025/10/node-red-vs-flowfuse.md                        | 2 +-
 src/blog/2025/10/plc-to-mqtt-using-flowfuse.md                  | 2 +-
 src/blog/2025/10/using-ethernet-ip-with-flowfuse.md             | 2 +-
 src/blog/2025/11/building-hmi-for-equipment-control.md          | 2 +-
 src/blog/2025/12/kafka-vs-mqtt.md                               | 2 +-
 src/blog/2025/12/node-red-buffer-parser-industrial-data.md      | 2 +-
 src/blog/2025/12/node-red-timer.md                              | 2 +-
 src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md       | 2 +-
 src/blog/2025/12/what-is-teep.md                                | 2 +-
 src/blog/2026/01/opcua-vs-mqtt.md                               | 2 +-
 src/blog/2026/01/why-modbus-still-exist.md                      | 2 +-
 src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md                    | 2 +-
 src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md       | 2 +-
 src/blog/2026/04/diagnosing-modbus-degradation.md               | 2 +-
 src/blog/2026/04/modbus-polling-best-practices.md               | 2 +-
 src/blog/2026/06/node-red-5-on-flowfuse.md                      | 2 +-
 50 files changed, 50 insertions(+), 50 deletions(-)

diff --git a/src/blog/2023/01/environment-variables-in-node-red.md b/src/blog/2023/01/environment-variables-in-node-red.md
index 41eee26f10..d69957c6f8 100644
--- a/src/blog/2023/01/environment-variables-in-node-red.md
+++ b/src/blog/2023/01/environment-variables-in-node-red.md
@@ -63,7 +63,7 @@ Leveraging environment variables can also be done with other nodes, like for exa
 
 Node-RED allows you to set environment variables, but not to change them when executing flows. If you want to update data during execution, look into using [persistent context](/docs/user/persistent-context/). Node-RED doesn’t support Environment Variables like other programming environments do. When the flow is deployed the environment variables are replaced with the known values at that time. This is the biggest gotcha for most developers.
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ### Predefined variables
diff --git a/src/blog/2023/03/3-quick-node-red-tips-4.md b/src/blog/2023/03/3-quick-node-red-tips-4.md
index 32022b5d63..2ceaeeee20 100644
--- a/src/blog/2023/03/3-quick-node-red-tips-4.md
+++ b/src/blog/2023/03/3-quick-node-red-tips-4.md
@@ -28,7 +28,7 @@ You can in turn use this to ignore values that deviate too far from the sample.
 [{"id":"9484c25a0120bd48","type":"group","z":"dd95c0bca1101c86","name":"Automatically outputs random value (temperature in Celcius) between 0 & 25 every second","style":{"label":!0},"nodes":["e4f972f9daad6246","c7fc075a1915e87b","966a772c46dc2888"],"x":34,"y":59,"w":574,"h":82},{"id":"e4f972f9daad6246","type":"link out","z":"dd95c0bca1101c86","g":"9484c25a0120bd48","name":"link out 1","mode":"link","links":["33594c64783cdc45","e6bf7b494b48861e"],"x":355,"y":100,"wires":[]},{"id":"c7fc075a1915e87b","type":"inject","z":"dd95c0bca1101c86","g":"9484c25a0120bd48","name":"","props":[],"repeat":"1","crontab":"","once":!1,"onceDelay":0.1,"topic":"","x":130,"y":100,"wires":[["966a772c46dc2888"]]},{"id":"966a772c46dc2888","type":"random","z":"dd95c0bca1101c86","g":"9484c25a0120bd48","name":"","low":"0","high":"25","inte":"true","property":"payload","x":260,"y":100,"wires":[["e4f972f9daad6246"]]},{"id":"37380f26e8bfc98a","type":"group","z":"dd95c0bca1101c86","name":"Calculate average, high and low, save to flow","style":{"label":!0},"nodes":["cc3978c7c4ea56ed","e1819526a5f365c8","33594c64783cdc45","fea261a15b3b7683","e28a69232f1cac53","aecb1727be523240","e30039ee13e480a8"],"x":34,"y":259,"w":552,"h":142},{"id":"cc3978c7c4ea56ed","type":"change","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"","rules":[{"t":"set","p":"high","pt":"flow","to":"payload","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":!1,"x":310,"y":300,"wires":[["aecb1727be523240"]]},{"id":"e1819526a5f365c8","type":"change","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"","rules":[{"t":"set","p":"low","pt":"flow","to":"payload","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":!1,"x":310,"y":360,"wires":[["e30039ee13e480a8"]]},{"id":"33594c64783cdc45","type":"link in","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"link in 1","links":["c07b2e101cecbd3b","e4f972f9daad6246"],"x":75,"y":320,"wires":[["e28a69232f1cac53","fea261a15b3b7683"]]},{"id":"fea261a15b3b7683","type":"smooth","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"Min","property":"payload","action":"min","count":"100","round":"2","mult":"single","reduce":!1,"x":170,"y":360,"wires":[["e1819526a5f365c8"]]},{"id":"e28a69232f1cac53","type":"smooth","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"Max","property":"payload","action":"max","count":"100","round":"2","mult":"single","reduce":!1,"x":170,"y":300,"wires":[["cc3978c7c4ea56ed"]]},{"id":"aecb1727be523240","type":"debug","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"debug 23","active":!0,"tosidebar":!1,"console":!1,"tostatus":!0,"complete":"payload","targetType":"msg","statusVal":"payload","statusType":"auto","x":480,"y":300,"wires":[]},{"id":"e30039ee13e480a8","type":"debug","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"debug 25","active":!0,"tosidebar":!1,"console":!1,"tostatus":!0,"complete":"payload","targetType":"msg","statusVal":"payload","statusType":"auto","x":480,"y":360,"wires":[]},{"id":"ec11a9ee9148b0b5","type":"group","z":"dd95c0bca1101c86","name":"Evaluate if an incoming value is between flow.high and flow.low, if it is not, send the message down a different wire and show an alert in debug","style":{"label":!0},"nodes":["9393c22b2e3c1ec8","1cd18307cb919159","7c1f474e646765a7","a209cd10f33ec401","f4b15283e55babf4","e6bf7b494b48861e"],"x":34,"y":419,"w":1032,"h":162},{"id":"9393c22b2e3c1ec8","type":"switch","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"Was the value between flow.high and flow.low?","property":"payload","propertyType":"msg","rules":[{"t":"btwn","v":"high","vt":"flow","v2":"low","v2t":"flow"},{"t":"else"}],"checkall":"true","repair":!1,"outputs":2,"x":300,"y":480,"wires":[["1cd18307cb919159"],["7c1f474e646765a7","a209cd10f33ec401"]]},{"id":"1cd18307cb919159","type":"debug","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"debug 15","active":!0,"tosidebar":!0,"console":!1,"tostatus":!1,"complete":"false","statusVal":"","statusType":"auto","x":560,"y":460,"wires":[]},{"id":"7c1f474e646765a7","type":"debug","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"debug 16","active":!1,"tosidebar":!0,"console":!1,"tostatus":!1,"complete":"false","statusVal":"","statusType":"auto","x":560,"y":540,"wires":[]},{"id":"a209cd10f33ec401","type":"change","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"Alert to debug when value is outside of the range","rules":[{"t":"set","p":"payload","pt":"msg","to":"The value was outside of the range","tot":"str"}],"action":"","property":"","from":"","to":"","reg":!1,"x":690,"y":500,"wires":[["f4b15283e55babf4"]]},{"id":"f4b15283e55babf4","type":"debug","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"debug 17","active":!0,"tosidebar":!0,"console":!1,"tostatus":!1,"complete":"false","statusVal":"","statusType":"auto","x":960,"y":500,"wires":[]},{"id":"e6bf7b494b48861e","type":"link in","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"link in 2","links":["e4f972f9daad6246","c07b2e101cecbd3b"],"x":75,"y":480,"wires":[["9393c22b2e3c1ec8"]]},{"id":"caf4214602d5f2c9","type":"group","z":"dd95c0bca1101c86","name":"Manually send a spurious value","style":{"label":!0},"nodes":["14097fb7ba3a9ecc","c07b2e101cecbd3b"],"x":34,"y":159,"w":232,"h":82},{"id":"14097fb7ba3a9ecc","type":"inject","z":"dd95c0bca1101c86","g":"caf4214602d5f2c9","name":"","props":[{"p":"payload"}],"repeat":"","crontab":"","once":!1,"onceDelay":0.1,"topic":"","payload":"75","payloadType":"num","x":130,"y":200,"wires":[["c07b2e101cecbd3b"]]},{"id":"c07b2e101cecbd3b","type":"link out","z":"dd95c0bca1101c86","g":"caf4214602d5f2c9","name":"link out 2","mode":"link","links":["33594c64783cdc45","e6bf7b494b48861e"],"x":225,"y":200,"wires":[]}]
 ```
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ### 2. Perform simple maths functions using JSONata in Change nodes
diff --git a/src/blog/2023/03/comparing-node-red-dashboards.md b/src/blog/2023/03/comparing-node-red-dashboards.md
index 468ff2e0a9..f83c57e9ff 100644
--- a/src/blog/2023/03/comparing-node-red-dashboards.md
+++ b/src/blog/2023/03/comparing-node-red-dashboards.md
@@ -74,7 +74,7 @@ There is also an [ongoing discussion](https://github.com/node-red/node-red/issue
 
 I believe a few improvements to the install process could make FlexDash a much more popular custom node.
 
-:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
 ::
 
 ## How easy is it to get your first demo dashboard running?
diff --git a/src/blog/2023/06/import-modules.md b/src/blog/2023/06/import-modules.md
index e057095d13..d534f4b403 100644
--- a/src/blog/2023/06/import-modules.md
+++ b/src/blog/2023/06/import-modules.md
@@ -87,7 +87,7 @@ Recently we wanted to use [moment](https://www.npmjs.com/package/moment) for som
 
 So, all we needed to do was import the module into a function node, and define our comparison there instead, here's a working example:
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ## Example: Easy CRC
diff --git a/src/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md b/src/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md
index 05a360b2f6..f365458fd2 100644
--- a/src/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md
+++ b/src/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md
@@ -128,7 +128,7 @@ You can import this flow into Node-RED using the code below:
 
 To understand what is going on in this flow, we must refer back to the OPC UA Simulation Server `Address Space` tab.  
 
-:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
 ::
 
 When we browse the OPC Server base folder structure in Node-RED, we will be browsing everything included under the `Objects` tree.  
diff --git a/src/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md b/src/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md
index 2e77006d2a..53dfe7e0e4 100644
--- a/src/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md
+++ b/src/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md
@@ -152,7 +152,7 @@ We can confirm the values are being stored in memory by checking the flow contex
 ![Screenshot showing the flow variables in the context data tab](./images/opc-ua-1/context-data-2.png "Screenshot showing the flow variables in the context data tab")
 Each time we hit refresh, the values change, confirming that the values are randomly changing every second.
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 The last, and most important part of the flow, is the `Compact-Server` node, which actually stands alone without any incoming or outgoing connections.
diff --git a/src/blog/2023/07/influxdb-historical-data.md b/src/blog/2023/07/influxdb-historical-data.md
index 662d3ae793..c897b6e739 100644
--- a/src/blog/2023/07/influxdb-historical-data.md
+++ b/src/blog/2023/07/influxdb-historical-data.md
@@ -93,7 +93,7 @@ I selected “Generate All Access API Token,” but eventually you will want a c
 
 Copy your token and do not share it!  (mine will be deleted later)
 
-:::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
 ::
 
 ## Connecting Node-RED to InfluxDB
diff --git a/src/blog/2023/08/flowforge-is-now-flowfuse.md b/src/blog/2023/08/flowforge-is-now-flowfuse.md
index 36184bdf03..985d8615ba 100644
--- a/src/blog/2023/08/flowforge-is-now-flowfuse.md
+++ b/src/blog/2023/08/flowforge-is-now-flowfuse.md
@@ -40,7 +40,7 @@ We are happy to announce that FlowForge is changing its name to FlowFuse. Changi
 
 We believe that this new name better reflects our core mission and aspirations. Just as electricity fuses elements to create energy, the FlowFuse platform fuses together data, ideas, processes, and technologies to generate a powerful force of innovation and transformation.
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 Selecting a new name for a company or product is never easy. Some of the requirements we set for a new name were: 1) it should be reasonably close to FlowForge so it will be easier to transition the brand identity, 2) it should even better reflect our mission, and 3) keeping the FF acronym will help with environment variable prefixes :-). I think we have accomplished all the above and am delighted to move forward as FlowFuse.
diff --git a/src/blog/2023/12/device-agent-as-a-windows-service.md b/src/blog/2023/12/device-agent-as-a-windows-service.md
index da29406263..e366173554 100644
--- a/src/blog/2023/12/device-agent-as-a-windows-service.md
+++ b/src/blog/2023/12/device-agent-as-a-windows-service.md
@@ -88,7 +88,7 @@ icacls c:\opt\flowfuse-device /grant "user":F /T
 ```
 _where `"user"` is the service account (not the admin account)_
 
-:::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
 ::
 
 ## Install nssm
diff --git a/src/blog/2024/01/dashboard-2-multi-user.md b/src/blog/2024/01/dashboard-2-multi-user.md
index 311e3f2f69..92df711471 100644
--- a/src/blog/2024/01/dashboard-2-multi-user.md
+++ b/src/blog/2024/01/dashboard-2-multi-user.md
@@ -52,7 +52,7 @@ For all our Teams and Enterprise Self-Hosted customers who also want to use the
 
 Alternatively, if you're looking to elevate your Node-RED infrastructure, [book in a chat with us](/contact-us) to talk about how FlowFuse can help.
 
-:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
 ::
 
 ### Using the Plugin
diff --git a/src/blog/2024/02/connect-node-red-to-kepware-opc.md b/src/blog/2024/02/connect-node-red-to-kepware-opc.md
index 6dee80a08a..6bb5b18714 100644
--- a/src/blog/2024/02/connect-node-red-to-kepware-opc.md
+++ b/src/blog/2024/02/connect-node-red-to-kepware-opc.md
@@ -57,7 +57,7 @@ Next, let's configure the **OPC UA Client**.  Click the **pencil** to add a new
 
 For the endpoint, **copy** the endpoint definition from the KepserverEX OPC UA Configuration Manager.  In our example, it is ```opc.tcp://127.0.0.1:49320```, and paste it into the Endpoint.  For SecurityPolicy select **Basic256Sha256**. For SecurityMode, select **Sign&Encrypt**.  Lastly, we will be selecting **Anonymous**.  Click **Update**, then **Deploy**.  
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 Trigger the flow by **clicking** on the inject node.  The server may not connect at this time, and it is expected.
diff --git a/src/blog/2024/03/dashboard-getting-started.md b/src/blog/2024/03/dashboard-getting-started.md
index 406a8c2e6d..ea86c11286 100644
--- a/src/blog/2024/03/dashboard-getting-started.md
+++ b/src/blog/2024/03/dashboard-getting-started.md
@@ -60,7 +60,7 @@ Notice too that Dashboard will automatically setup some underlying configuration
 - `ui-group`: Each group contains a collection of widgets, and can be used to organize your Dashboard into logical sections.
 - `ui-theme`: Each `ui-page` can be assigned a given theme. Your "Themes" provide control over the aesthetic of your Dashboard like color, padding and margins.
 
-:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
 ::
 
 ## Configuring your layout
diff --git a/src/blog/2024/03/using-kafka-with-node-red.md b/src/blog/2024/03/using-kafka-with-node-red.md
index 022ee6155c..8e829297b9 100644
--- a/src/blog/2024/03/using-kafka-with-node-red.md
+++ b/src/blog/2024/03/using-kafka-with-node-red.md
@@ -50,7 +50,7 @@ During the writing of this tutorial, I utilized [Aiven’s cloud data platform](
 ## Installing Dashboard 2.0
 We will be installing Dashboard 2.0 to display real-time temperature data of various regions on a chart. If you are new to Dashboard 2.0, we recommend referring to [Getting started with Dashboard 2.0](/blog/2024/03/dashboard-getting-started/)\, which covers everything from basic concepts to installation and creating your first dashboard seamlessly.
 
-:::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
 ::
 
 ## Installing and configuring Kafka custom node
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 f865b146c8..f8b945bd84 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
@@ -109,7 +109,7 @@ Behind the scenes, the user addon is appending the user object to the `msg`, via
 
 When running Node-RED Dashboard 2.0 on FlowFuse, you'll have a new tab available in the "Dashboard 2.0" sidebar in the Node-RED Editor, you just have to navigate to the "FF Auth" tab and you’ll see two options.
 
-:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
 ::
 
 **Option 1: Include Client Data**
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 0214da44c7..8f0be34d83 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
@@ -76,7 +76,7 @@ return msg;
 
 Similarly, you can do this for storing expense data submitted using the expense submission form.
 
-:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
 ::
 
 ### Displaying Notifications
diff --git a/src/blog/2024/05/mapping-location-on-dashboard-2.md b/src/blog/2024/05/mapping-location-on-dashboard-2.md
index 8830fe98f1..cbba2dfc35 100644
--- a/src/blog/2024/05/mapping-location-on-dashboard-2.md
+++ b/src/blog/2024/05/mapping-location-on-dashboard-2.md
@@ -97,7 +97,7 @@ Before plotting locations, we need to obtain the data first. For this purpose, w
 
 To ensure compatibility with the Worldmap custom node, we need to format the location data appropriately. 
 
-:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
 ::
 
 1. Drag the **Change** node onto the canvas, and set the `msg.payload` to `msg.payload.vehicles`, and give it name **Set payload**.
diff --git a/src/blog/2024/06/dashboard-1-deprecated.md b/src/blog/2024/06/dashboard-1-deprecated.md
index a51c353626..bbfa3f5fbc 100644
--- a/src/blog/2024/06/dashboard-1-deprecated.md
+++ b/src/blog/2024/06/dashboard-1-deprecated.md
@@ -42,7 +42,7 @@ We are actively investing into the development of FlowFuse Dashboard, and releas
 
 If there are any other features you'd like to see, please do open a [Feature Request](https://github.com/FlowFuse/node-red-dashboard/issues/new/choose), and we'll do our best to accommodate.
 
-:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
 ::
 
 ## Getting Started with FlowFuse Dashboard
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 d37629c463..c6915c2585 100644
--- a/src/blog/2024/08/comparing-dashboard-2-with-uibuilder.md
+++ b/src/blog/2024/08/comparing-dashboard-2-with-uibuilder.md
@@ -85,7 +85,7 @@ FlowFuse Dashboard offers an extensive set of UI elements, including forms, drop
 
 UI-Builder also offers a number of widgets, but these are not as user-friendly as those in FlowFuse Dashboard. Users must send a JSON config object, which can be complex for new users who lack knowledge of HTML/CSS. Additionally, handling widget data requires using UI-Builder's methods, which can further increase complexity. However, UI-Builder's strength lies in its flexibility, allowing any HTML element to be used as a component, and it also supports the W3C standard web components. Despite this, users need to perform a lot of additional tasks to get everything set up and will have the hassle of writing things.
 
-:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
 ::
 
 ## Changing the UI at Runtime
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 3f5fda3c40..1ff666588d 100644
--- a/src/blog/2024/08/customise-theming-in-your-dashboards.md
+++ b/src/blog/2024/08/customise-theming-in-your-dashboards.md
@@ -152,7 +152,7 @@ You can replace the URL with your logo's URL or set it using the `msg.payload` a
 !["Screenshot of the Dashboard displaying the added logo in the header"](./images/logo-added-dashboard.png "Screenshot of the Dashboard displaying the added logo in the header"){data-zoomable}
 _Screenshot of the Dashboard displaying the added logo in the header_
 
-:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
 ::
 
 ### Right Side of the Header
diff --git a/src/blog/2024/08/opc-ua-to-mqtt-with-node-red.md b/src/blog/2024/08/opc-ua-to-mqtt-with-node-red.md
index dc6296e1a8..a70138b891 100644
--- a/src/blog/2024/08/opc-ua-to-mqtt-with-node-red.md
+++ b/src/blog/2024/08/opc-ua-to-mqtt-with-node-red.md
@@ -95,7 +95,7 @@ In this section, I'll demonstrate how to bridge OPC UA data to MQTT using Node-R
 
 - MQTT Broker: We’ll need an MQTT broker for data communication. FlowFuse offers an integrated MQTT Broker Service within Platform for easy setup. For more details, check out [FlowFuse's MQTT Broker Announcement](/blog/2024/10/announcement-mqtt-broker/).
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 ### Retrieving Data from the OPC UA Server
diff --git a/src/blog/2024/08/opentelemetry-with-node-red.md b/src/blog/2024/08/opentelemetry-with-node-red.md
index 2bc0901370..bd2b6a43c1 100644
--- a/src/blog/2024/08/opentelemetry-with-node-red.md
+++ b/src/blog/2024/08/opentelemetry-with-node-red.md
@@ -87,7 +87,7 @@ For demonstration purposes, we will use a flow that simulates sensor reading and
 
 Deploy the flow above, and you might see a delay in the data shown on the debug panel. For this example, we added a Delay node before the Change node that converts temperature data from Kelvin to Celsius. While this delay is visible here, finding such delays in larger flows with many nodes can be difficult and time-consuming. Open Telemetry makes this easier by giving you detailed traces that show where delays or issues are happening
 
-:::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
 ::
 
 ### Prerequisite
diff --git a/src/blog/2024/09/how-to-scrape-web-data-with-node-red.md b/src/blog/2024/09/how-to-scrape-web-data-with-node-red.md
index 5e39836854..2d63bc33c5 100644
--- a/src/blog/2024/09/how-to-scrape-web-data-with-node-red.md
+++ b/src/blog/2024/09/how-to-scrape-web-data-with-node-red.md
@@ -49,7 +49,7 @@ To start scraping data, follow these steps to send an HTTP GET request to the we
 
 Once deployed, click the **inject** button. You will see the raw HTML printed in the debug panel.
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ### Parsing and Extracting Data from HTML
diff --git a/src/blog/2024/09/how-to-use-subflow-in-node-red.md b/src/blog/2024/09/how-to-use-subflow-in-node-red.md
index ef5d7bd2f5..ecf5b1f153 100644
--- a/src/blog/2024/09/how-to-use-subflow-in-node-red.md
+++ b/src/blog/2024/09/how-to-use-subflow-in-node-red.md
@@ -101,7 +101,7 @@ _Image showing subflow node added in the node palette_
 
 Once selected, the Subflow will be added to the node palette like other nodes. The selected flow will also be converted into a single node representing the Subflow.
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ### Adding Properties to the Subflow
diff --git a/src/blog/2024/12/flowfuse-release-2-12.md b/src/blog/2024/12/flowfuse-release-2-12.md
index 788e19f836..1152bb9a29 100644
--- a/src/blog/2024/12/flowfuse-release-2-12.md
+++ b/src/blog/2024/12/flowfuse-release-2-12.md
@@ -70,7 +70,7 @@ _Screenshot showing the UI for selecting your Team's type, when onboarding throu
 
 <!-- <img width="438" alt="image" src="https://github.com/user-attachments/assets/da6fde55-27bc-42d7-afcc-19235661b558" /> -->
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ### Remote Instances
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 65a9972f6e..a4bafffa47 100644
--- a/src/blog/2024/12/publishing-modbus-data-to-uns.md
+++ b/src/blog/2024/12/publishing-modbus-data-to-uns.md
@@ -134,7 +134,7 @@ If you prefer a video explanation, [Kurt Braun](https://www.linkedin.com/in/wago
 
 After collecting data from your Modbus device, the next step is transforming it into a usable format for cloud-based IoT applications. Modbus data typically comes in raw register values, and you may need to convert these values into human-readable formats like temperature, pressure, or other measurements.
 
-:::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
 ::
 
 Let's walk through the transformation process step by step.
diff --git a/src/blog/2025/02/interacting-with-arduino-using-node-red.md b/src/blog/2025/02/interacting-with-arduino-using-node-red.md
index ae95eb532c..31b38d2449 100644
--- a/src/blog/2025/02/interacting-with-arduino-using-node-red.md
+++ b/src/blog/2025/02/interacting-with-arduino-using-node-red.md
@@ -59,7 +59,7 @@ _Importing Standard Firmata setup sketch from examples in Arduino IDE_
 
 Once the upload is complete, the Arduino is ready to communicate via the Firmata protocol.
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ### Step 3: Connecting Node-RED to Arduino via Serial Communication
diff --git a/src/blog/2025/02/node-red-academy-announcement.md b/src/blog/2025/02/node-red-academy-announcement.md
index cdaa65e42a..5b3002b0c2 100644
--- a/src/blog/2025/02/node-red-academy-announcement.md
+++ b/src/blog/2025/02/node-red-academy-announcement.md
@@ -52,7 +52,7 @@ All courses completed through Node-RED Academy provide a formal certification up
 
 The credential will be evidence of your Node-RED knowledge and abilities, and will be a great way to demonstrate your expertise to potential employers or clients.
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ## What Courses are Included?
diff --git a/src/blog/2025/05/designing-flexible-cron-schedules-in-flowfuse-with-node-red.md b/src/blog/2025/05/designing-flexible-cron-schedules-in-flowfuse-with-node-red.md
index 0a8e9c069f..daa9b52f96 100644
--- a/src/blog/2025/05/designing-flexible-cron-schedules-in-flowfuse-with-node-red.md
+++ b/src/blog/2025/05/designing-flexible-cron-schedules-in-flowfuse-with-node-red.md
@@ -134,7 +134,7 @@ To make it even easier to create and customize cron patterns, the cron-plus node
 ![Image showing the easy builder feature](./images/easy-builder.gif){data-zoomable}
 _Image showing the easy builder feature_
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ### Solar Event Schedules
diff --git a/src/blog/2025/05/how-to-generate-pdf-reports-using-node-red.md b/src/blog/2025/05/how-to-generate-pdf-reports-using-node-red.md
index 32ee228a32..5765920b50 100644
--- a/src/blog/2025/05/how-to-generate-pdf-reports-using-node-red.md
+++ b/src/blog/2025/05/how-to-generate-pdf-reports-using-node-red.md
@@ -191,7 +191,7 @@ This example creates a simple PDF featuring a centered logo, a title, a subtitle
 ![Example pdf result](./images/example-pdf.png){data-zoomable}
 _Example pdf result_
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ### Step 3: Creating a Flow to Generate a PDF
diff --git a/src/blog/2025/06/what-is-mes.md b/src/blog/2025/06/what-is-mes.md
index f6e21f6979..7092de8480 100644
--- a/src/blog/2025/06/what-is-mes.md
+++ b/src/blog/2025/06/what-is-mes.md
@@ -38,7 +38,7 @@ The MES collects real-time information to tell you:
 
 This means you always know the exact status of your production, live. Such real-time insights and operational control are at the core of what a modern MES delivers, often leveraging flexible platforms like FlowFuse to connect diverse factory data and orchestrate workflows.
 
-:::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
 ::
 
 ## What MES is NOT 
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 06feda1ae9..cc3ed3b104 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
@@ -126,7 +126,7 @@ When using the "multiple" topic, each value update arrives in OPC UA's DataValue
 
 Subscribing to multiple tags with OpcUa-Item nodes returns just the value.
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 ### Stopping Subscriptions
diff --git a/src/blog/2025/09/poka-yoke-mistake-proofing.md b/src/blog/2025/09/poka-yoke-mistake-proofing.md
index e73cd1963e..247e1ff377 100644
--- a/src/blog/2025/09/poka-yoke-mistake-proofing.md
+++ b/src/blog/2025/09/poka-yoke-mistake-proofing.md
@@ -80,7 +80,7 @@ The impact of mistake-proofing extends far beyond just catching errors. By desig
 
 Errors in manual assembly lead to increased scrap rates, rework, and delays, all contributing to higher production costs. By eliminating errors at the source, the cost of mistakes within a company is reduced significantly. Companies implementing poka yoke techniques saw a 25% increase in productivity, with time previously spent correcting errors now available for value-added activities.
 
-:::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
 ::
 
 Mistake-proofing creates safer processes by eliminating conditions that lead to accidents. When errors can literally mean life or death (as in pharmaceutical manufacturing), poka yoke becomes mission-critical. Workers experience less frustration from rework and greater confidence in their processes, leading to improved morale. Successful implementation leads to a 20% improvement in customer satisfaction through consistent product quality and reliability.
diff --git a/src/blog/2025/09/what-is-takt-time.md b/src/blog/2025/09/what-is-takt-time.md
index c15198fb10..a9f9b96e6a 100644
--- a/src/blog/2025/09/what-is-takt-time.md
+++ b/src/blog/2025/09/what-is-takt-time.md
@@ -130,7 +130,7 @@ Understanding the meaning of takt time in this result shows the production line
 
 This example illustrates why defining takt time correctly matters for matching cycle time to customer demand. Cycle times significantly exceeding takt time reveal capacity shortfalls requiring immediate attention. Cycle times falling well below takt time suggest excess capacity that might be redeployed elsewhere or indicate risk of overproduction if production control systems fail to prevent excess output.
 
-:::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
 ::
 
 ### Example 2: Electronics Assembly (Multiple Shifts)
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 2b4169ebfd..99f01ad9bd 100644
--- a/src/blog/2025/10/building-mcp-server-using-flowfuse.md
+++ b/src/blog/2025/10/building-mcp-server-using-flowfuse.md
@@ -81,7 +81,7 @@ http://192.168.1.100:1880/mcp
 
 This URL allows AI agents to discover resources, execute tools, and interact with your flows.
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ### Securing Your MCP Server
diff --git a/src/blog/2025/10/node-red-vs-flowfuse.md b/src/blog/2025/10/node-red-vs-flowfuse.md
index 8055302ae6..2e0a177f2d 100644
--- a/src/blog/2025/10/node-red-vs-flowfuse.md
+++ b/src/blog/2025/10/node-red-vs-flowfuse.md
@@ -66,7 +66,7 @@ FlowFuse provides role-based access control (RBAC) to define who edits flows ver
 
 For supply chain security, FlowFuse generates a Software Bill of Materials (SBOM) listing every node and dependency across your instances. Security teams can scan for vulnerabilities and track what needs updating.
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ### Team Collaboration and Version Control
diff --git a/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md b/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md
index 0cde8d511d..60f9724d25 100644
--- a/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md
+++ b/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md
@@ -120,7 +120,7 @@ The Node-RED ecosystem that powers FlowFuse offers comprehensive protocol suppor
 
 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.
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 ## Convincing the IT Team
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 7cbec0a932..19b16cdf77 100644
--- a/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md
+++ b/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md
@@ -122,7 +122,7 @@ To communicate with Allen-Bradley PLCs from FlowFuse, use the popular node-red-c
 
 Once installed, you'll find the EtherNet/IP nodes in your palette under the "plc" category. The main nodes are `ethernet-ip in` for reading data and `ethernet-ip out` for writing data to the PLC.
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 ## Configuring the EtherNet/IP Node
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 dc6e182b51..0f7db15c49 100644
--- a/src/blog/2025/11/building-hmi-for-equipment-control.md
+++ b/src/blog/2025/11/building-hmi-for-equipment-control.md
@@ -123,7 +123,7 @@ After saving the connection configuration, specify the **variable addresses that
 
 For sending commands (start motor, stop motor, setpoints), drag the corresponding output node onto your canvas. When configuring it, select the **same Server/Connection** from the dropdown instead of creating a new one. This shared connection approach means the IP address, port, and credentials only need to be configured once and can be reused across all your PLC/server nodes. You then only need to specify the variable addresses that control your equipment, and connect those nodes to your dashboard buttons or automation logic.
 
-:::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
 ::
 
 **Important Note:** Some PLCs require configuration in their engineering software before allowing external access. For example, Siemens S7 requires **PUT/GET communication** enabled in TIA Portal, and Allen-Bradley controllers may need **explicit messaging** enabled in Studio 5000. Refer to your PLC’s documentation for any communication prerequisites.
diff --git a/src/blog/2025/12/kafka-vs-mqtt.md b/src/blog/2025/12/kafka-vs-mqtt.md
index b836640946..e83b2688c6 100644
--- a/src/blog/2025/12/kafka-vs-mqtt.md
+++ b/src/blog/2025/12/kafka-vs-mqtt.md
@@ -83,7 +83,7 @@ Unlike MQTT, messages don't disappear after delivery. Everything writes to disk.
 
 Early Kafka needed Apache Zookeeper for cluster coordination, which added complexity. Recent versions support KRaft mode that removes this dependency, though many production systems still run Zookeeper.
 
-:::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
 ::
 
 ## The Real Differences
diff --git a/src/blog/2025/12/node-red-buffer-parser-industrial-data.md b/src/blog/2025/12/node-red-buffer-parser-industrial-data.md
index 14acad4dbb..952ded715e 100644
--- a/src/blog/2025/12/node-red-buffer-parser-industrial-data.md
+++ b/src/blog/2025/12/node-red-buffer-parser-industrial-data.md
@@ -132,7 +132,7 @@ return msg;
 
 This works, but it's also fragile. When you need to add a pressure reading next month, you're editing code and hoping you don't break the offset calculations. When someone else looks at this flow, they have no idea what's happening without reading the function and if they don't understand JavaScript, they're stuck.
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 Buffer Parser turns this into configuration you can see and modify without touching code. Let's walk through a practical example.
diff --git a/src/blog/2025/12/node-red-timer.md b/src/blog/2025/12/node-red-timer.md
index 29494577d5..13becd51a8 100644
--- a/src/blog/2025/12/node-red-timer.md
+++ b/src/blog/2025/12/node-red-timer.md
@@ -102,7 +102,7 @@ The hourglass node responds to control commands sent via `msg.command`. The avai
 
 These commands control timer behavior.
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ### Implementing a Stopwatch Timer
diff --git a/src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md b/src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md
index 3edada3ad8..3474261ae1 100644
--- a/src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md
+++ b/src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md
@@ -132,7 +132,7 @@ Before exposing variables, you need to create an OPC UA server interface in your
 
 If you're using an S7-1500 PLC with firmware version 2.5 or higher, you have the option to enable the standard SIMATIC server interface. Simply check **Enable standard SIMATIC server interface** in the OPC UA settings. This automatically makes all PLC tags that are marked as accessible available through OPC UA.
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 **For S7-1200 PLCs (or manual configuration for S7-1500):**
diff --git a/src/blog/2025/12/what-is-teep.md b/src/blog/2025/12/what-is-teep.md
index 49259e5238..63a342935f 100644
--- a/src/blog/2025/12/what-is-teep.md
+++ b/src/blog/2025/12/what-is-teep.md
@@ -82,7 +82,7 @@ In many cases, TEEP reveals that the fastest and cheapest way to increase output
 
 Importantly, TEEP is not about pushing equipment to run 24/7 at all costs. Instead, it provides the data needed to make **intentional, informed decisions** about scheduling, staffing, maintenance, and growth.
 
-:::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
 ::
 
 ## TEEP vs OEE: Key Differences
diff --git a/src/blog/2026/01/opcua-vs-mqtt.md b/src/blog/2026/01/opcua-vs-mqtt.md
index bef6366a6d..6df9ce439b 100644
--- a/src/blog/2026/01/opcua-vs-mqtt.md
+++ b/src/blog/2026/01/opcua-vs-mqtt.md
@@ -135,7 +135,7 @@ Implementing an OPC UA server requires managing an address space, handling multi
 
 This overhead is impractical for battery-powered sensors with infrequent reporting requirements. It's appropriate for a $2M manufacturing cell where understanding that a temperature reading represents "bearing temperature on the output shaft of motor 3, measured in Celsius, with a normal operating range of 40-65°C and critical alarm at 85°C" matters.
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 ### The Layer Mismatch
diff --git a/src/blog/2026/01/why-modbus-still-exist.md b/src/blog/2026/01/why-modbus-still-exist.md
index 85d85f312b..2b60355f0c 100644
--- a/src/blog/2026/01/why-modbus-still-exist.md
+++ b/src/blog/2026/01/why-modbus-still-exist.md
@@ -77,7 +77,7 @@ Industrial automation is full of protocol wars where vendors push their preferre
 
 Modbus doesn't care. It works with everyone's equipment. This vendor neutrality has enormous practical value in facilities running mixed automation systems. A typical factory floor might have Rockwell PLCs, ABB drives, Schneider Electric power meters, and Siemens HMIs all talking to each other. Getting all those vendors' preferred protocols to coexist would be a nightmare. Getting them all to speak Modbus is trivial.
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 This creates competitive pressure that keeps Modbus relevant. Device manufacturers can't afford to skip Modbus support because doing so immediately excludes them from projects with heterogeneous automation systems. Even vendors with their own sophisticated protocols implement Modbus as a fallback, ensuring interoperability when nothing else works.
diff --git a/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md b/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md
index 6c7b66f960..9c57310729 100644
--- a/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md
+++ b/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md
@@ -51,7 +51,7 @@ The catch is that Ethernet latency is not flat. It varies with network load, swi
 
 RTU offers better worst-case latency. TCP offers better average latency. In industrial control, worst-case is usually what you design for.
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 ## Failure Modes: What Breaks, How It Breaks, and Whether You Will Know
diff --git a/src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md b/src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md
index a6cf799d12..4d0966729d 100644
--- a/src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md
+++ b/src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md
@@ -54,7 +54,7 @@ For device manufacturers, the math is punishing. A Modbus RTU interface costs ro
 
 Certificate management alone has quietly killed more OPC UA deployments than any technical limitation. Certificates expire. They need to be provisioned, rotated, and trusted across every client and server. In an IT environment with dedicated security teams, this is manageable. In a plant where the automation engineer also handles PLC programming, HMI design, and network troubleshooting, it becomes an ongoing burden that nobody budgeted for and nobody wants to own.
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 The OPC Foundation recognized this. Companion specifications like OPC UA FX and the Field Level Communications initiative are genuine attempts to bring the protocol closer to the field device layer. Progress is real but slow, and in the meantime, device manufacturers continue defaulting to Modbus because it ships today without a compliance checklist.
diff --git a/src/blog/2026/04/diagnosing-modbus-degradation.md b/src/blog/2026/04/diagnosing-modbus-degradation.md
index afb5d8d3dd..8d10fb3e00 100644
--- a/src/blog/2026/04/diagnosing-modbus-degradation.md
+++ b/src/blog/2026/04/diagnosing-modbus-degradation.md
@@ -64,7 +64,7 @@ Those connection slots release when the idle-connection timeout or the TCP FIN/R
 
 That regularity is the diagnostic signal. A device with intermittent hardware faults fails unpredictably. A device whose connection table is being exhausted fails on a clock. If you're seeing periodic offline events with suspiciously consistent timing, check your connection handling before you assume the device is faulty.
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 **Transaction ID handling** is worth checking in high-concurrency polling configurations. The [Modbus application protocol specification](https://www.modbus.org/file/secure/modbusprotocolspecification.pdf) defines Transaction IDs to match requests with responses. A polling stack that reuses Transaction IDs before receiving a response to the previous one can match incoming responses to the wrong pending request. When this occurs, the symptom is correct values appearing in the wrong registers. It doesn't show up as an error at all, which makes it unusually difficult to diagnose. If you're seeing values that are off by a plausible amount but never produce error codes, check whether your stack's Transaction ID handling is correct under concurrent load.
diff --git a/src/blog/2026/04/modbus-polling-best-practices.md b/src/blog/2026/04/modbus-polling-best-practices.md
index 7b52aac707..95e81013e3 100644
--- a/src/blog/2026/04/modbus-polling-best-practices.md
+++ b/src/blog/2026/04/modbus-polling-best-practices.md
@@ -55,7 +55,7 @@ This tiered approach does something important beyond just reducing bus load: it
 
 The pushback you'll hear is that tiered polling is harder to configure and harder to document. That's true. A single scan rate is simple to explain and simple to hand off. But simple to configure and correct are different things, and a polling architecture that silently misses events or saturates a serial bus isn't simple. It's a problem that hasn't surfaced yet.
 
-:::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
 ::
 
 One more thing worth stating plainly: your scan rate has to account for the device's actual response capability, not just the rate you want data. Some field devices, including older PLCs, low-cost sensors, and anything running on an 8-bit microcontroller with slow UART handling, need 50 to 150ms just to process a request and formulate a response. If your fast-tier scan rate is 100ms and your device needs 120ms to respond, you're not getting 100ms data. You're getting collisions, timeouts, and a maintenance headache. Measure actual device response times before setting your fast-tier interval. The device datasheet will give you a starting point; a protocol analyzer will give you the truth.
diff --git a/src/blog/2026/06/node-red-5-on-flowfuse.md b/src/blog/2026/06/node-red-5-on-flowfuse.md
index 7b7a22c1f5..0d0f1a7a27 100644
--- a/src/blog/2026/06/node-red-5-on-flowfuse.md
+++ b/src/blog/2026/06/node-red-5-on-flowfuse.md
@@ -64,7 +64,7 @@ The **redesigned sidebars** now behave the same on both sides of the editor. Con
 
 Underneath the visual changes are functional and security improvements across debugging, authentication, and TLS, the parts that matter most once Node-RED is running in production. If previous releases expanded what it could do, this one sharpens how it feels to use. For the full list, read the [release blog](https://nodered.org/blog/2026/06/09/version-5-0-released).
 
-:::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
 ## What it means for industrial teams

From a0694d7fc2671304f9286a9e4d63e6ed5872031f Mon Sep 17 00:00:00 2001
From: sumitshinde-84 <shindesumit217@gmail.com>
Date: Sat, 15 Aug 2026 01:33:55 +0530
Subject: [PATCH 3/3] bring cta earlier

---
 .../2023/01/environment-variables-in-node-red.md   |  6 +++---
 src/blog/2023/03/3-quick-node-red-tips-4.md        |  6 +++---
 src/blog/2023/03/comparing-node-red-dashboards.md  |  6 +++---
 src/blog/2023/06/import-modules.md                 |  6 +++---
 ...-to-build-a-opc-client-dashboard-in-node-red.md |  8 +++-----
 ...-to-deploy-a-basic-opc-ua-server-in-node-red.md |  9 +++------
 src/blog/2023/07/influxdb-historical-data.md       |  9 +++------
 src/blog/2023/08/flowforge-is-now-flowfuse.md      |  4 ++--
 .../2023/12/device-agent-as-a-windows-service.md   | 10 +++-------
 src/blog/2024/01/dashboard-2-multi-user.md         |  6 +++---
 .../2024/02/connect-node-red-to-kepware-opc.md     | 14 +++-----------
 src/blog/2024/03/dashboard-getting-started.md      |  8 +++-----
 src/blog/2024/03/using-kafka-with-node-red.md      |  6 +++---
 .../04/displaying-logged-in-users-on-dashboard.md  |  6 +++---
 .../05/exploring-node-red-dashboard-2-widgets.md   |  6 +++---
 .../2024/05/mapping-location-on-dashboard-2.md     |  6 +++---
 src/blog/2024/06/dashboard-1-deprecated.md         |  6 +++---
 .../08/comparing-dashboard-2-with-uibuilder.md     |  7 +++----
 .../08/customise-theming-in-your-dashboards.md     |  6 +++---
 src/blog/2024/08/opentelemetry-with-node-red.md    |  6 +++---
 src/blog/2024/09/how-to-use-subflow-in-node-red.md |  6 +++---
 src/blog/2024/12/flowfuse-release-2-12.md          |  7 +++----
 src/blog/2024/12/publishing-modbus-data-to-uns.md  |  6 +++---
 .../02/interacting-with-arduino-using-node-red.md  |  6 +++---
 src/blog/2025/02/node-red-academy-announcement.md  |  6 +++---
 .../how-to-generate-pdf-reports-using-node-red.md  |  6 +++---
 ...al-time-subscriptions-alarms-historical-data.md | 12 +++---------
 src/blog/2025/09/poka-yoke-mistake-proofing.md     |  6 +++---
 src/blog/2025/09/what-is-takt-time.md              |  6 +++---
 .../2025/10/building-mcp-server-using-flowfuse.md  |  6 +++---
 src/blog/2025/10/node-red-vs-flowfuse.md           |  6 +++---
 src/blog/2025/10/plc-to-mqtt-using-flowfuse.md     |  6 +++---
 .../2025/10/using-ethernet-ip-with-flowfuse.md     |  6 +++---
 .../2025/11/building-hmi-for-equipment-control.md  |  6 +++---
 src/blog/2025/12/kafka-vs-mqtt.md                  |  6 +++---
 .../12/node-red-buffer-parser-industrial-data.md   |  6 +++---
 src/blog/2025/12/node-red-timer.md                 |  6 +++---
 .../12/read-s7-optimized-datablocks-flowfuse.md    |  6 +++---
 src/blog/2025/12/what-is-teep.md                   |  6 +++---
 src/blog/2026/01/opcua-vs-mqtt.md                  |  6 +++---
 src/blog/2026/01/why-modbus-still-exist.md         |  6 +++---
 src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md       |  6 +++---
 .../03/why-opcua-is-not-replacing-modbus-yet.md    |  6 +++---
 src/blog/2026/04/diagnosing-modbus-degradation.md  |  6 +++---
 src/blog/2026/04/modbus-polling-best-practices.md  |  6 +++---
 src/blog/2026/06/node-red-5-on-flowfuse.md         |  6 +++---
 46 files changed, 137 insertions(+), 167 deletions(-)

diff --git a/src/blog/2023/01/environment-variables-in-node-red.md b/src/blog/2023/01/environment-variables-in-node-red.md
index d69957c6f8..4698dcebff 100644
--- a/src/blog/2023/01/environment-variables-in-node-red.md
+++ b/src/blog/2023/01/environment-variables-in-node-red.md
@@ -57,15 +57,15 @@ Contextual data like configuration, which user is executing the code, differenti
 
 One of the options for the `inject` node is to inject a `env variable`, short for; you guessed it: Environment Variable. In this case we’re going to one that’s pre-defined by Node-RED: `NR_FLOW_NAME`. The name of each variable is in all caps by convention. When connecting this inject to a debug it prints “Flow 1” for me.
 
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ![Using an environment variable in Node-RED](./images/node-red-use-env-var.png "Using an environment variable in Node-RED")
 
 Leveraging environment variables can also be done with other nodes, like for example `change`, `switch`. Note however; you can set the `inject` node to output the value for `FOO` even when it doesn’t exist, but it doesn’t allow you to check in the switch node for example if `FOO` exists.
 
 Node-RED allows you to set environment variables, but not to change them when executing flows. If you want to update data during execution, look into using [persistent context](/docs/user/persistent-context/). Node-RED doesn’t support Environment Variables like other programming environments do. When the flow is deployed the environment variables are replaced with the known values at that time. This is the biggest gotcha for most developers.
 
-::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
-::
-
 ### Predefined variables
 
 Our first example was using a predefined variable, exposed by Node-RED. As of 3.0 it exposes a few environment variables among which `NR_NODE_NAME`, `NR_GROUP_NAME`, and `NR_FLOW_NAME`.
diff --git a/src/blog/2023/03/3-quick-node-red-tips-4.md b/src/blog/2023/03/3-quick-node-red-tips-4.md
index 07145a00a2..29976ea14e 100644
--- a/src/blog/2023/03/3-quick-node-red-tips-4.md
+++ b/src/blog/2023/03/3-quick-node-red-tips-4.md
@@ -22,15 +22,15 @@ When taking data in from sensors sometimes a spurious value can be sent into you
 
 ![Using the Smooth node to return highest value from the last 100 payloads](./images/smooth.png "Using the Smooth node to return highest value from the last 100 payloads")
 
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 You can in turn use this to ignore values that deviate too far from the sample. To help demonstrate the Smooth node, I've created a flow you can import into Node-RED.
 
 ```json
 [{"id":"9484c25a0120bd48","type":"group","z":"dd95c0bca1101c86","name":"Automatically outputs random value (temperature in Celcius) between 0 & 25 every second","style":{"label":!0},"nodes":["e4f972f9daad6246","c7fc075a1915e87b","966a772c46dc2888"],"x":34,"y":59,"w":574,"h":82},{"id":"e4f972f9daad6246","type":"link out","z":"dd95c0bca1101c86","g":"9484c25a0120bd48","name":"link out 1","mode":"link","links":["33594c64783cdc45","e6bf7b494b48861e"],"x":355,"y":100,"wires":[]},{"id":"c7fc075a1915e87b","type":"inject","z":"dd95c0bca1101c86","g":"9484c25a0120bd48","name":"","props":[],"repeat":"1","crontab":"","once":!1,"onceDelay":0.1,"topic":"","x":130,"y":100,"wires":[["966a772c46dc2888"]]},{"id":"966a772c46dc2888","type":"random","z":"dd95c0bca1101c86","g":"9484c25a0120bd48","name":"","low":"0","high":"25","inte":"true","property":"payload","x":260,"y":100,"wires":[["e4f972f9daad6246"]]},{"id":"37380f26e8bfc98a","type":"group","z":"dd95c0bca1101c86","name":"Calculate average, high and low, save to flow","style":{"label":!0},"nodes":["cc3978c7c4ea56ed","e1819526a5f365c8","33594c64783cdc45","fea261a15b3b7683","e28a69232f1cac53","aecb1727be523240","e30039ee13e480a8"],"x":34,"y":259,"w":552,"h":142},{"id":"cc3978c7c4ea56ed","type":"change","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"","rules":[{"t":"set","p":"high","pt":"flow","to":"payload","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":!1,"x":310,"y":300,"wires":[["aecb1727be523240"]]},{"id":"e1819526a5f365c8","type":"change","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"","rules":[{"t":"set","p":"low","pt":"flow","to":"payload","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":!1,"x":310,"y":360,"wires":[["e30039ee13e480a8"]]},{"id":"33594c64783cdc45","type":"link in","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"link in 1","links":["c07b2e101cecbd3b","e4f972f9daad6246"],"x":75,"y":320,"wires":[["e28a69232f1cac53","fea261a15b3b7683"]]},{"id":"fea261a15b3b7683","type":"smooth","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"Min","property":"payload","action":"min","count":"100","round":"2","mult":"single","reduce":!1,"x":170,"y":360,"wires":[["e1819526a5f365c8"]]},{"id":"e28a69232f1cac53","type":"smooth","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"Max","property":"payload","action":"max","count":"100","round":"2","mult":"single","reduce":!1,"x":170,"y":300,"wires":[["cc3978c7c4ea56ed"]]},{"id":"aecb1727be523240","type":"debug","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"debug 23","active":!0,"tosidebar":!1,"console":!1,"tostatus":!0,"complete":"payload","targetType":"msg","statusVal":"payload","statusType":"auto","x":480,"y":300,"wires":[]},{"id":"e30039ee13e480a8","type":"debug","z":"dd95c0bca1101c86","g":"37380f26e8bfc98a","name":"debug 25","active":!0,"tosidebar":!1,"console":!1,"tostatus":!0,"complete":"payload","targetType":"msg","statusVal":"payload","statusType":"auto","x":480,"y":360,"wires":[]},{"id":"ec11a9ee9148b0b5","type":"group","z":"dd95c0bca1101c86","name":"Evaluate if an incoming value is between flow.high and flow.low, if it is not, send the message down a different wire and show an alert in debug","style":{"label":!0},"nodes":["9393c22b2e3c1ec8","1cd18307cb919159","7c1f474e646765a7","a209cd10f33ec401","f4b15283e55babf4","e6bf7b494b48861e"],"x":34,"y":419,"w":1032,"h":162},{"id":"9393c22b2e3c1ec8","type":"switch","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"Was the value between flow.high and flow.low?","property":"payload","propertyType":"msg","rules":[{"t":"btwn","v":"high","vt":"flow","v2":"low","v2t":"flow"},{"t":"else"}],"checkall":"true","repair":!1,"outputs":2,"x":300,"y":480,"wires":[["1cd18307cb919159"],["7c1f474e646765a7","a209cd10f33ec401"]]},{"id":"1cd18307cb919159","type":"debug","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"debug 15","active":!0,"tosidebar":!0,"console":!1,"tostatus":!1,"complete":"false","statusVal":"","statusType":"auto","x":560,"y":460,"wires":[]},{"id":"7c1f474e646765a7","type":"debug","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"debug 16","active":!1,"tosidebar":!0,"console":!1,"tostatus":!1,"complete":"false","statusVal":"","statusType":"auto","x":560,"y":540,"wires":[]},{"id":"a209cd10f33ec401","type":"change","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"Alert to debug when value is outside of the range","rules":[{"t":"set","p":"payload","pt":"msg","to":"The value was outside of the range","tot":"str"}],"action":"","property":"","from":"","to":"","reg":!1,"x":690,"y":500,"wires":[["f4b15283e55babf4"]]},{"id":"f4b15283e55babf4","type":"debug","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"debug 17","active":!0,"tosidebar":!0,"console":!1,"tostatus":!1,"complete":"false","statusVal":"","statusType":"auto","x":960,"y":500,"wires":[]},{"id":"e6bf7b494b48861e","type":"link in","z":"dd95c0bca1101c86","g":"ec11a9ee9148b0b5","name":"link in 2","links":["e4f972f9daad6246","c07b2e101cecbd3b"],"x":75,"y":480,"wires":[["9393c22b2e3c1ec8"]]},{"id":"caf4214602d5f2c9","type":"group","z":"dd95c0bca1101c86","name":"Manually send a spurious value","style":{"label":!0},"nodes":["14097fb7ba3a9ecc","c07b2e101cecbd3b"],"x":34,"y":159,"w":232,"h":82},{"id":"14097fb7ba3a9ecc","type":"inject","z":"dd95c0bca1101c86","g":"caf4214602d5f2c9","name":"","props":[{"p":"payload"}],"repeat":"","crontab":"","once":!1,"onceDelay":0.1,"topic":"","payload":"75","payloadType":"num","x":130,"y":200,"wires":[["c07b2e101cecbd3b"]]},{"id":"c07b2e101cecbd3b","type":"link out","z":"dd95c0bca1101c86","g":"caf4214602d5f2c9","name":"link out 2","mode":"link","links":["33594c64783cdc45","e6bf7b494b48861e"],"x":225,"y":200,"wires":[]}]
 ```
 
-::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
-::
-
 ### 2. Perform simple maths functions using JSONata in Change nodes
 
 You can perform basic maths functions using the Change node and JSONata. Let's say you wanted to take a payload and multiply it by a value. You could use a custom node such as [node-red-contrib-calc](https://flows.nodered.org/node/node-red-contrib-calc) but you can also easily complete the same task within a change node. 
diff --git a/src/blog/2023/03/comparing-node-red-dashboards.md b/src/blog/2023/03/comparing-node-red-dashboards.md
index f83c57e9ff..1ba7213036 100644
--- a/src/blog/2023/03/comparing-node-red-dashboards.md
+++ b/src/blog/2023/03/comparing-node-red-dashboards.md
@@ -50,6 +50,9 @@ I am assuming the user is a low-code developer. They may have limited experience
 
 So, that's the methodology, let's get on with looking at the strengths of each project.
 
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 ## How easy is it to install?
 
 ### uibuilder - 1st place
@@ -74,9 +77,6 @@ There is also an [ongoing discussion](https://github.com/node-red/node-red/issue
 
 I believe a few improvements to the install process could make FlexDash a much more popular custom node.
 
-::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
-::
-
 ## How easy is it to get your first demo dashboard running?
 
 ### FlexDash - 1st place
diff --git a/src/blog/2023/06/import-modules.md b/src/blog/2023/06/import-modules.md
index d534f4b403..ff15ea26de 100644
--- a/src/blog/2023/06/import-modules.md
+++ b/src/blog/2023/06/import-modules.md
@@ -69,6 +69,9 @@ Historically in Node-RED, you would have needed to manually `npm install` module
 
 ![Location of the "add" button in order to import an npm module intoa  function node](./images/npmimport-add.jpg "Location of the 'add' button in order to import an npm module intoa  function node")
 
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 All you need is the name of the module you want to import, then:
 
 1. Drop in a new "function" node & double-click it
@@ -87,9 +90,6 @@ Recently we wanted to use [moment](https://www.npmjs.com/package/moment) for som
 
 So, all we needed to do was import the module into a function node, and define our comparison there instead, here's a working example:
 
-::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
-::
-
 ## Example: Easy CRC
 
 <video width="560" height="315" controls>
diff --git a/src/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md b/src/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md
index e589681940..0faafd4cb8 100644
--- a/src/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md
+++ b/src/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md
@@ -114,6 +114,9 @@ Rather than building the flow step-by-step, the flow source code will be present
 
 ## Browse Hierarchical Server Address Space Structure With OPC UA Browser Node
 
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 The first flow will browse the hierarchical OPC UA Server address space structure and display it on the dashboard.
 
 ![image-20230727-085611.png](./images/opc-ua-3/image-20230727-085611.png){data-zoomable}
@@ -128,9 +131,6 @@ You can import this flow into Node-RED using the code below:
 
 To understand what is going on in this flow, we must refer back to the OPC UA Simulation Server `Address Space` tab.  
 
-::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
-::
-
 When we browse the OPC Server base folder structure in Node-RED, we will be browsing everything included under the `Objects` tree.  
 
 ![address-space.png](./images/opc-ua-3/address-space.png){data-zoomable}
@@ -141,7 +141,6 @@ The configuration of the endpoint properties includes no security credentials, a
 
 ![endpoint-configure.png](./images/opc-ua-3/endpoint-configure.png){data-zoomable}
 
-
 Using the output of a debug node, we get from the OPC UA Browser yield a payload with an array of 5 objects.  
 
 ![address-debug.png](./images/opc-ua-3/address-debug.png){data-zoomable}
@@ -208,7 +207,6 @@ Going back to our OPC Server, we can see that exactly where that value is derive
 
 ![sim-counter-server.png](./images/opc-ua-3/sim-counter-server.png){data-zoomable}
 
-
 Now we add a `gauge` dashboard node to visualize the counter on the dashboard.  In the OPC Server, it is shown that the counter increments in a range of 0-30 in 1 count increments.  
 
 ![counter-properties.png](./images/opc-ua-3/counter-propertie.png){data-zoomable}
diff --git a/src/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md b/src/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md
index 53dfe7e0e4..862037e0ae 100644
--- a/src/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md
+++ b/src/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md
@@ -77,7 +77,6 @@ Because of OPC-UA’s wide industry acceptance, it is increasingly becoming nati
 !["Automation Pyramid"](./images/opc-ua-1/automation-pyramid.jpg "Automation Pyramid")
 *Image reference - [imagecontroltips.com](https://www.motioncontroltips.com/what-is-opc-ua-and-how-does-it-compare-with-industrial-ethernet/)*
 
-
 ## Fieldbus Model vs OPC-UA Information Model
 
 As of today, industrial ethernet fieldbuses dominate the field/device-level (level 0) and controller/PLC-level (level 1) of the automation pyramid. 
@@ -90,7 +89,6 @@ Traditionally, fieldbus protocols transmit only raw data from field devices (ie,
 
 !["Fieldbus Model"](./images/opc-ua-1/fieldbus-model.png "Fieldbus Model")
 
-
 In contrast to fieldbus protocols, OPC-UA represents automation data in the form of nodes. The framework for constructing nodes is referred to as the [OPC Information model](https://reference.opcfoundation.org/Core/Part5/v104/docs/), and consists of pre-defined classes and methods that are programmed in the OPC Server address space.  
 
 !["OPC Information Model"](./images/opc-ua-1/opc-information-model.png "OPC Information Model")
@@ -112,6 +110,9 @@ The OPC client simply needs to subscribe to the OPC Server endpoint url (ex. opc
 
 With some background on OPC-UA and how information is modeled in mind, we can take a look at the [node-red-contrib-opcua-server](https://flows.nodered.org/node/node-red-contrib-opcua-server) node, which is merely a compact version of the [node-red-contrib-opcua](https://flows.nodered.org/node/node-red-contrib-opcua) node that only focuses on the OPC-UA server and hence requires less dependencies.  
 
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
  An [example flow](https://github.com/BiancoRoyal/node-red-contrib-opcua-server/blob/master/examples/server-with-context.json) is provided on github that can serve as a basis for understanding how a OPC-UA server is constructed.  Let’s get the example server up and running.  
 
 Deploying the example flow yields the following result - 
@@ -148,13 +149,9 @@ We can confirm the values are being stored in memory by checking the flow contex
 
 !["Screenshot showing the Context Data option"](./images/opc-ua-1/context-data-1.png "Screenshot showing the Context Data option")
 
-
 ![Screenshot showing the flow variables in the context data tab](./images/opc-ua-1/context-data-2.png "Screenshot showing the flow variables in the context data tab")
 Each time we hit refresh, the values change, confirming that the values are randomly changing every second.
 
-::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
-::
-
 The last, and most important part of the flow, is the `Compact-Server` node, which actually stands alone without any incoming or outgoing connections.
 
 !["Compact Server Node"](./images/opc-ua-1/compact-server-node.png "Compact Server Node")
diff --git a/src/blog/2023/07/influxdb-historical-data.md b/src/blog/2023/07/influxdb-historical-data.md
index c897b6e739..5125e47ecd 100644
--- a/src/blog/2023/07/influxdb-historical-data.md
+++ b/src/blog/2023/07/influxdb-historical-data.md
@@ -58,6 +58,9 @@ Unfortunately, these values are not in a friendly form to work with.  Ideally, w
 
  <br>
 
+::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::
+
 We need to extract the numeric part of the string using a regular expression with a “change” node and the JSONata expression `$number($match(msg.payload, /-?(\d+(\.\d+)?)/, 10).match)`.  `$match` and `/-?(\d+(\.\d+)?)/` help the function pull out the numeric components of the string and `$number` parses these components to be an actual number data type.
 
 Here are the properties of the “change” node.
@@ -70,7 +73,6 @@ When we look in the debugger we see the payload specified as a “number” and
 
 Now we have some live data, let’s store it using InfluxDB. Below are the steps to set up an account with the InfluxDB free service.  Navigate to [https://www.influxdata.com/products/influxdb-overview/](https://www.influxdata.com/products/influxdb-overview/) and let’s begin.  Click on “Get Started for Free” under Cloud, InfluxDB Cloud Serverless.
 
-
 !["Screenshot showing the Influxdb cloud 'Getting started' button"](images/influxdb-historical-data/run-influxdb-8.png "Screenshot showing the Influxdb cloud 'Getting started' button")
 
 For this example the Free plan will work fine.
@@ -93,9 +95,6 @@ I selected “Generate All Access API Token,” but eventually you will want a c
 
 Copy your token and do not share it!  (mine will be deleted later)
 
-::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
-::
-
 ## Connecting Node-RED to InfluxDB
 
 Navigate to “Manage Palette” in the Node-RED hamburger menu in the upper right corner of the flow editor.  I did a search for InfluxDB and selected the most popular one, “node-red-contrib-influxdb” by looking at the number of downloads per week at [https://flows.nodered.org/node/node-red-contrib-influxdb](https://flows.nodered.org/node/node-red-contrib-influxdb).  When you are just starting out, it can be a smart decision to go with the popular option. The popularity indicates a level of trust and adoption within the community, making it a reliable choice for beginners
@@ -168,7 +167,6 @@ Here is the code from the “time/date” function node.  A bit of juggling of l
 
 Here is the “change” node used to create the msg.rangeEnd.  The JSONatta expression is `$fromMillis($toMillis(msg.rangeStart) + msg.payload.window * 60 * 1000)`.  The expression combines the milliseconds from the `msg.rangeStart` with the calculated milliseconds in the “Window (minutes)” from the GUI.
 
-
 !["Screenshot of the change node properties tab"](images/influxdb-historical-data/change-node-26.png "Screenshot of the change node properties tab")
 
 <br>
@@ -223,7 +221,6 @@ The “join” node just needs to be set to “Combine each” msg.chartData obj
 
 The final “change” node, “format,” is where we prescribe the format needed for the “chart” node, [{"series":[""],"data":[[]],"labels":[""]}], and finally we insert our `msg.chartData` array into that structure.  Notice `msg.title` is now set to “Data Received.”
 
-
 !["Screenshot of the change node properties tab"](images/influxdb-historical-data/change-node-33.png "Screenshot of the change node properties tab")
 
 <br>
diff --git a/src/blog/2023/08/flowforge-is-now-flowfuse.md b/src/blog/2023/08/flowforge-is-now-flowfuse.md
index 985d8615ba..3bd9b147b5 100644
--- a/src/blog/2023/08/flowforge-is-now-flowfuse.md
+++ b/src/blog/2023/08/flowforge-is-now-flowfuse.md
@@ -38,11 +38,11 @@ We are happy to announce that FlowForge is changing its name to FlowFuse. Changi
 
 <!--more-->
 
-We believe that this new name better reflects our core mission and aspirations. Just as electricity fuses elements to create energy, the FlowFuse platform fuses together data, ideas, processes, and technologies to generate a powerful force of innovation and transformation.
-
 ::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
 ::
 
+We believe that this new name better reflects our core mission and aspirations. Just as electricity fuses elements to create energy, the FlowFuse platform fuses together data, ideas, processes, and technologies to generate a powerful force of innovation and transformation.
+
 Selecting a new name for a company or product is never easy. Some of the requirements we set for a new name were: 1) it should be reasonably close to FlowForge so it will be easier to transition the brand identity, 2) it should even better reflect our mission, and 3) keeping the FF acronym will help with environment variable prefixes :-). I think we have accomplished all the above and am delighted to move forward as FlowFuse.
 
 **What to Expect Next**
diff --git a/src/blog/2023/12/device-agent-as-a-windows-service.md b/src/blog/2023/12/device-agent-as-a-windows-service.md
index e366173554..9678fca395 100644
--- a/src/blog/2023/12/device-agent-as-a-windows-service.md
+++ b/src/blog/2023/12/device-agent-as-a-windows-service.md
@@ -49,7 +49,6 @@ Finally, we set the service to run under the **service** account.
 
 _NOTE: The instructions in this how to were written on **Windows 11 Pro 22H2**_
 
-
 ### TIP: Using domain accounts
 If the account is a domain account, append the domain name to the **user** e.g. `user@domain` whenever the **user** name is used in the instructions below.
 
@@ -59,6 +58,9 @@ If the account is a domain account, append the domain name to the **user** e.g.
 powershell -Command "Start-Process 'cmd' -Verb runAs
 ```
 
+::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::
+
 ### TIP: Launching an elevated powershell prompt window (e.g. as the admin user)
 
 ```bash
@@ -88,9 +90,6 @@ icacls c:\opt\flowfuse-device /grant "user":F /T
 ```
 _where `"user"` is the service account (not the admin account)_
 
-::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
-::
-
 ## Install nssm
 `nssm` can simply be downloaded and executed from any path.
 We will download it to the `c:\opt` directory, extract the files and copy the 64 bit version to the current directory.
@@ -110,7 +109,6 @@ del nssm-2.24.zip
 rmdir /s /q nssm-2.24
 ```
 
-
 ### `powershell` version [elevated](#tip%3A-launching-an-elevated-powershell-prompt-window-(e.g.-as-the-admin-user)) powershell prompt
 If you don't have `cURL` installed, then powershell can be used to download the file. Here is how to do it:
 
@@ -133,7 +131,6 @@ If you prefer, you can download the nssm zip file manually from [https://nssm.cc
 
 Ultimately, you should end up with a file named `nssm.exe` in the `c:\opt\` directory.
 
-
 ## Install and configure the device-agent
 
 As the **service** account, to do so open a command prompt window and run the following and authenticate:
@@ -229,7 +226,6 @@ Click the "Edit Service" button to save the changes.
 
 Now you have a service that will run the device-agent as the **service** account 🎉
 
-
 ### Controlling the service
 
 You can start the service with the command:
diff --git a/src/blog/2024/01/dashboard-2-multi-user.md b/src/blog/2024/01/dashboard-2-multi-user.md
index 92df711471..471ed7a7f7 100644
--- a/src/blog/2024/01/dashboard-2-multi-user.md
+++ b/src/blog/2024/01/dashboard-2-multi-user.md
@@ -38,6 +38,9 @@ All instances on FlowFuse can be configured with _"FlowFuse User Authentication"
 
 ##### FlowFuse Cloud
 
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 _Note: Every instance created from today onwards automatically comes with the necessary configuration. Already created instances need to be manually restarted._
 
 The Personalised Multi-User Dashboard plugin, `@flowfuse/node-red-dashboard-2-user-addon`, is available in our [Certified Nodes](/integrations/?certified=1) catalogue, accessible to our Teams and Enterprise customers.
@@ -52,9 +55,6 @@ For all our Teams and Enterprise Self-Hosted customers who also want to use the
 
 Alternatively, if you're looking to elevate your Node-RED infrastructure, [book in a chat with us](/contact-us) to talk about how FlowFuse can help.
 
-::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
-::
-
 ### Using the Plugin
 
 Once enabled, any messages emitted by a Dashboard 2.0 node will contain a new `msg._client.user` object, e.g:
diff --git a/src/blog/2024/02/connect-node-red-to-kepware-opc.md b/src/blog/2024/02/connect-node-red-to-kepware-opc.md
index 6bb5b18714..513f5ad492 100644
--- a/src/blog/2024/02/connect-node-red-to-kepware-opc.md
+++ b/src/blog/2024/02/connect-node-red-to-kepware-opc.md
@@ -31,11 +31,12 @@ The first thing we need to do is check our **OPC UA Configuration Manager** for
 
 ![kepware tray](./images/kepserverex-tray.png)
 
-
 If your Node-RED instance lives on the same server that your KepserverEX is on, pick accordingly or click add if you need to define by ip address. This is for setting different credential requirements for localhost vs remote host access.  Also note, that if you have multiple network adapters, make sure to select the adapter that is in use. 
 
-![kepware endpoint definition](./images/kep-endpoint-definition.png)
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
 
+![kepware endpoint definition](./images/kep-endpoint-definition.png)
 
 We are testing locally on the server, so we will use the one selected for loopback addressing.  We will be leaving the OPC server port as default and select **Basic256Sha256** with **Sign and Encrypt**.
 
@@ -49,34 +50,26 @@ Import the flow below into your Node-RED environment.
 
 <iframe width="100%" height="225px" src="https://flows.nodered.org/flow/04a84fe5b0db7cda9e74ba811e7b0ca5/share?height=250" allow="clipboard-read; clipboard-write" style="border: none;"></iframe>
 
-
 Next, let's configure the **OPC UA Client**.  Click the **pencil** to add a new OPCUA-Endpoint.
 
 ![kepware node-red encrypted opc ua node](./images/opcua-endpoint-node-red-encrypted.png)
 
-
 For the endpoint, **copy** the endpoint definition from the KepserverEX OPC UA Configuration Manager.  In our example, it is ```opc.tcp://127.0.0.1:49320```, and paste it into the Endpoint.  For SecurityPolicy select **Basic256Sha256**. For SecurityMode, select **Sign&Encrypt**.  Lastly, we will be selecting **Anonymous**.  Click **Update**, then **Deploy**.  
 
-::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
-::
-
 Trigger the flow by **clicking** on the inject node.  The server may not connect at this time, and it is expected.
 
 ![kepware node-red invalid endpoint](./images/node-red-opc-ua-invalid-endpoint.png)
 
-
 #### Step 3: KepserverEX
 
 Moving back over to KepserverEX,  Click on the tray again in the bottom of the screen and select **Configuration**, then select **Edit** from the file menu, then **Properties**.  Next, Select **OPC UA** and ensure that **Allow Anonymous login** is set to **Yes**.  Click **OK**.  
 
 ![kepware node-red anonymous login](./images/node-red-kepware-anonymous-login.png)
 
-
 Select the tray at the bottom of the screen again, and select **OPC UA Configuration**. Select the **Trusted Clients** tab.
 
 ![kepware node-red trusted client before](./images/kepserverex-trusted-client-before.png)
 
-
 Now select the **NodeOPCUA-Client** and then **click** Trust.  ***If you don't have the client option, trigger the inject node again from the Node-RED flow and check the logs***
 
 ![kepware node-red trusted client after](./images/kepserverex-trusted-client-after.png)
@@ -93,7 +86,6 @@ We will be leveraging the default Simulated Examples for reading tags from Kepse
 
 ![kepware node-red read tags](./images/node-red-kepware-read-tag.png)
 
-
 Edit the OPCUa-Item node and note the item.
 
 ```
diff --git a/src/blog/2024/03/dashboard-getting-started.md b/src/blog/2024/03/dashboard-getting-started.md
index 6634b1f152..23c18c42dd 100644
--- a/src/blog/2024/03/dashboard-getting-started.md
+++ b/src/blog/2024/03/dashboard-getting-started.md
@@ -46,6 +46,9 @@ So, with that in mind, we wanted to offer a new "Getting Started" guide that wil
 
 ## Adding your first widgets
 
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 With the nodes installed, getting started is as easy as choosing a node from the Palette (the left-hand side list of nodes) in Node-RED, and dropping it onto your canvas.
 
 <video autoplay loop muted playsinline aria-label="Screen recording to show how easy it is to deploy your first Dashboard 2.0 application." width="800" height="460" preload="none"><source src="/blog/2024/03/images/dashboard-getting-started-add-widget.webm" type="video/webm" /></video>
@@ -60,9 +63,6 @@ Notice too that Dashboard will automatically setup some underlying configuration
 - `ui-group`: Each group contains a collection of widgets, and can be used to organize your Dashboard into logical sections.
 - `ui-theme`: Each `ui-page` can be assigned a given theme. Your "Themes" provide control over the aesthetic of your Dashboard like color, padding and margins.
 
-::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
-::
-
 ## Configuring your layout
 
 Dashboard 2.0 adds a dedicated sidebar to Node-RED to provide a centralized view of your pages, groups and widgets. From here you can add new pages and groups, modify existing settings, and re-order content to your liking.
@@ -86,7 +86,6 @@ Currently, we have three different options for page layout:
 - **Fixed:** ([docs](https://dashboard.flowfuse.com/layouts/types/fixed.html)) Each component will render at a _fixed_ width, no matter what the screen size is. The "width" property is converted a fixed pixel value (multiples of 48px by default).
 - **Notebook:** ([docs](https://dashboard.flowfuse.com/layouts/types/notebook.html)) This layout will stretch to 100% width, up to a maximum width of 1024px, and will centrally align. It's particularly useful for storytelling (e.g. articles/blogs) or analysis type user interfaces (e.g. Jupyter Notebooks), where you want the user to digest content in a particular order through scrolling.
 
-
 ### Navigation Sidebar
 
 Dashboard 2.0 offers various options on the appearance of the navigation sidebar:
@@ -97,7 +96,6 @@ Dashboard 2.0 offers various options on the appearance of the navigation sidebar
 - **Appear over Content:** When the sidebar is opened, the page is given an overlay, and the sidebar sits on top.
 - **Always Hide:** The sidebar will never show, and navigation between pages can instead be driven by [`ui-control`](https://dashboard.flowfuse.com/nodes/widgets/ui-control.html).
 
-
 ### Define Your Layout
 
 In our example, we're going to switch to a "Notebook" layout, with a "Collapse to Icons" sidebar:
diff --git a/src/blog/2024/03/using-kafka-with-node-red.md b/src/blog/2024/03/using-kafka-with-node-red.md
index 310d7ec80c..dcb74736a3 100644
--- a/src/blog/2024/03/using-kafka-with-node-red.md
+++ b/src/blog/2024/03/using-kafka-with-node-red.md
@@ -42,6 +42,9 @@ docker run -p 9092:9092 `
 confluentinc/cp-kafka
 ```
 
+::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::
+
 ## Running Kafka on the cloud
 To run Kafka on the cloud, you can consider utilizing any cloud service according to your preferences. For a guide on running Kafka on a cloud platform, the procedures may differ. You can refer to the documentation provided by your preferred cloud service for detailed instructions.
 
@@ -50,9 +53,6 @@ During the writing of this tutorial, I utilized [Aiven’s cloud data platform](
 ## Installing Dashboard 2.0
 We will be installing Dashboard 2.0 to display real-time temperature data of various regions on a chart. If you are new to Dashboard 2.0, we recommend referring to [Getting started with Dashboard 2.0](/blog/2024/03/dashboard-getting-started/)\, which covers everything from basic concepts to installation and creating your first dashboard seamlessly.
 
-::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
-::
-
 ## Installing and configuring Kafka custom node
 
 1. Install `node-red-kafka-manager` by the palette manager.
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 f8b945bd84..f637eaebdc 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
@@ -85,6 +85,9 @@ The FlowFuse User Addon is a plugin developed for Dashboard 2.0, leveraging the
 
 ### Installing Flowfuse user addon
 
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 1. Click the Node-RED Settings (top-right)
 2. Click "Manage Palette"
 3. Switch to the "Install" tab
@@ -109,9 +112,6 @@ Behind the scenes, the user addon is appending the user object to the `msg`, via
 
 When running Node-RED Dashboard 2.0 on FlowFuse, you'll have a new tab available in the "Dashboard 2.0" sidebar in the Node-RED Editor, you just have to navigate to the "FF Auth" tab and you’ll see two options.
 
-::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
-::
-
 **Option 1: Include Client Data**
 
 By default, this option is enabled. When this option is enabled, an object with user information will be added to the “msg” emitted by any widget of the Node-RED Dashboard 2.0.
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 2420727f02..8d0c3bfc38 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
@@ -54,6 +54,9 @@ The **ui-form** widget emits a payload object with key-value pairs of form eleme
 
 1. Drag a **function** node onto the canvas and add the following code. This will store the submission in the `income` global context variable, and then modify `msg.payload` to pass on a notification to any further connected nodes.
 
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 ```javascript
 // Retrieve the existing 'income' array from the global context, or initialize it as an empty array if it doesn't exist
 let income = global.get('income') || [];
@@ -76,9 +79,6 @@ return msg;
 
 Similarly, you can do this for storing expense data submitted using the expense submission form.
 
-::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
-::
-
 ### Displaying Notifications
 
 For displaying notifications on the dashboard, we'll utilize the **ui-notification** widget, which emits notifications to the user's dashboard. It accepts `msg.payload` which should be a string format or raw HTML/JavaScript for custom formatting.
diff --git a/src/blog/2024/05/mapping-location-on-dashboard-2.md b/src/blog/2024/05/mapping-location-on-dashboard-2.md
index a6c57cf4b3..39d9cfbf7f 100644
--- a/src/blog/2024/05/mapping-location-on-dashboard-2.md
+++ b/src/blog/2024/05/mapping-location-on-dashboard-2.md
@@ -86,6 +86,9 @@ To render an interactive world map webpage for plotting location data, we will u
 
 Before plotting locations, we need to obtain the data first. For this purpose, we will utilize the [Edenburg Open Public Transportation API](https://tfe-opendata.readme.io/docs/getting-started). This API provides the live locations of all of Edenburg's public buses and trams, enabling us to access the necessary data for plotting on Worldmap within Dashboard 2.0.
 
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 1. Drag an **Inject** node onto the canvas and set the repeat property to a 20-second interval.
 2. Drag an HTTP request node onto the canvas, Dobule-click on it and choose **GET** method, and enter `https://tfe-opendata.com/api/v1/vehicle_locations` in the URL field and select return  as **a parsed json object**. This API is public, so no need for environment variables. For private APIs, consider using [environment variables](/blog/2023/01/environment-variables-in-node-red) for security.
 
@@ -97,9 +100,6 @@ Before plotting locations, we need to obtain the data first. For this purpose, w
 
 To ensure compatibility with the Worldmap custom node, we need to format the location data appropriately. 
 
-::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
-::
-
 1. Drag the **Change** node onto the canvas, and set the `msg.payload` to `msg.payload.vehicles`, and give it name **Set payload**.
 
 ![Screenshot of the Change node setting the payload to the vehicles JSON array containing actual vehicle location data](./images/mapping-location-on-dashboard-2-change-node.png "Screenshot of the Change node setting the payload to the vehicles JSON array containing actual vehicle location data"){data-zoomable}
diff --git a/src/blog/2024/06/dashboard-1-deprecated.md b/src/blog/2024/06/dashboard-1-deprecated.md
index bbfa3f5fbc..7896b0ac9b 100644
--- a/src/blog/2024/06/dashboard-1-deprecated.md
+++ b/src/blog/2024/06/dashboard-1-deprecated.md
@@ -32,6 +32,9 @@ Not only have we made significant efforts to ensure that FlowFuse Dashboard has
 - **Directly Install on Mobile:** FlowFuse Dashboard is built as a Progressive Web App (PWA), this means that you're able to install it directly onto your mobile device as if it were a native mobile application.
 - **Vuetify Framework:** FlowFuse Dashboard is built on VueJS, and with that, we made the decision to integrate in [Vuetify](https://vuetifyjs.com/en/components/all/#containment), a very rich collection of functional UI widgets. All of these widgets are available, by default when you want to build your own custom widgets in a `ui-template` node.
 
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 ## What we have planned
 
 We are actively investing into the development of FlowFuse Dashboard, and releasing new features and updates on a regular basis. We have a public [Project Management Board](https://github.com/orgs/FlowFuse/projects/15/views/1) that show exactly what we're working on, and what we have planned in the near future. Some particular highlights include:
@@ -42,9 +45,6 @@ We are actively investing into the development of FlowFuse Dashboard, and releas
 
 If there are any other features you'd like to see, please do open a [Feature Request](https://github.com/FlowFuse/node-red-dashboard/issues/new/choose), and we'll do our best to accommodate.
 
-::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
-::
-
 ## Getting Started with FlowFuse Dashboard
 
 If you're ready to get started with FlowFuse Dashboard, you can install it directly from the Node-RED Palette Manager. Simply search for `@flowfuse/node-red-dashboard` and install the latest version.
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 c6915c2585..4bf6e475d4 100644
--- a/src/blog/2024/08/comparing-dashboard-2-with-uibuilder.md
+++ b/src/blog/2024/08/comparing-dashboard-2-with-uibuilder.md
@@ -63,6 +63,9 @@ Users will need to recreate their dashboards from scratch, as UI-Builder relies
 
 ### FlowFuse Dashboard
 
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 [FlowFuse Dashboard](https://github.com/FlowFuse/node-red-dashboard/graphs/contributors), which replaced Node-RED Dashboard 1.0 in 2023, has shown consistent and high development activity. The project benefits from a dedicated team that regularly updates and improves it, ensuring it remains current with user needs and technological advancements.
 
 ![Screenshot of the FlowFuse Dashboard GitHub commit chart](./images/dashboard-2-commits.png)  
@@ -85,9 +88,6 @@ FlowFuse Dashboard offers an extensive set of UI elements, including forms, drop
 
 UI-Builder also offers a number of widgets, but these are not as user-friendly as those in FlowFuse Dashboard. Users must send a JSON config object, which can be complex for new users who lack knowledge of HTML/CSS. Additionally, handling widget data requires using UI-Builder's methods, which can further increase complexity. However, UI-Builder's strength lies in its flexibility, allowing any HTML element to be used as a component, and it also supports the W3C standard web components. Despite this, users need to perform a lot of additional tasks to get everything set up and will have the hassle of writing things.
 
-::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
-::
-
 ## Changing the UI at Runtime
 
 ### FlowFuse Dashboard
@@ -217,7 +217,6 @@ UI-Builder does not have a publicly accessible project roadmap or a dedicated pl
 
 ## Summary Table
 
-
 | Feature                                  | FlowFuse Dashboard                          | UI-Builder                                       |
 |------------------------------------------|--------------------------------------------------|--------------------------------------------------|
 | **Ease of Installation**                 | **Moderately easy**: Search for `flowfuse/node-red-dashboard` can be confusing due to multiple nodes; useful documentation available | **Easy**: Clear package name `node-red-ui-builder` makes it straightforward to find |
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 bc8adc942e..b92b0b0247 100644
--- a/src/blog/2024/08/customise-theming-in-your-dashboards.md
+++ b/src/blog/2024/08/customise-theming-in-your-dashboards.md
@@ -104,6 +104,9 @@ _Screenshot showing the 'Show page name in the header bar' option in the dashboa
 3. Choose the page on which you want to render the buttons if you selected `page-scope`, or choose correct ui if `ui-scope` is selected.
 4. Paste the following Vue snippet into the template widget. In this snippet, note how we specify the "to" attribute targeting the `#app-bar-title` ID in the teleport tag:
 
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 ```html
 <template>
     <!-- Teleport the button to the #app-bar-actions area when mounted -->
@@ -152,9 +155,6 @@ You can replace the URL with your logo's URL or set it using the `msg.payload` a
 !["Screenshot of the Dashboard displaying the added logo in the header"](./images/logo-added-dashboard.png "Screenshot of the Dashboard displaying the added logo in the header"){data-zoomable}
 _Screenshot of the Dashboard displaying the added logo in the header_
 
-::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
-::
-
 ### Right Side of the Header
 
 To render elements on the right side of the header, you can use the empty div element having the `#app-bar-actions` ID, in which we can add elements.
diff --git a/src/blog/2024/08/opentelemetry-with-node-red.md b/src/blog/2024/08/opentelemetry-with-node-red.md
index bd2b6a43c1..cb61597b20 100644
--- a/src/blog/2024/08/opentelemetry-with-node-red.md
+++ b/src/blog/2024/08/opentelemetry-with-node-red.md
@@ -75,6 +75,9 @@ In Node-RED The Open Telemetry module helps track messages by creating "spans" t
 
 ## Tracing in Node-RED Flows using Opentelemetry
 
+::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::
+
 In a manufacturing plant, Node-RED manages different machines and sensors. Suppose there's a problem with the production line, such as a delay in processing or a GPIO node experiencing issues reading data. With Open Telemetry integrated, you can trace the data flow through the system to see exactly where the issue is happening. This helps you quickly identify whether the problem is with a specific node that is reading the machine data or a delay in data processing, allowing you to fix the issue faster and keep the production line running smoothly.
 
 For demonstration purposes, we will use a flow that simulates sensor reading and data processing. We will monitor this flow using Open Telemetry to track data across the system, identify bottlenecks, and optimize performance.
@@ -87,9 +90,6 @@ For demonstration purposes, we will use a flow that simulates sensor reading and
 
 Deploy the flow above, and you might see a delay in the data shown on the debug panel. For this example, we added a Delay node before the Change node that converts temperature data from Kelvin to Celsius. While this delay is visible here, finding such delays in larger flows with many nodes can be difficult and time-consuming. Open Telemetry makes this easier by giving you detailed traces that show where delays or issues are happening
 
-::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
-::
-
 ### Prerequisite
 
 Before you start, ensure you have the following:
diff --git a/src/blog/2024/09/how-to-use-subflow-in-node-red.md b/src/blog/2024/09/how-to-use-subflow-in-node-red.md
index b358379191..c95c019c4c 100644
--- a/src/blog/2024/09/how-to-use-subflow-in-node-red.md
+++ b/src/blog/2024/09/how-to-use-subflow-in-node-red.md
@@ -93,6 +93,9 @@ To follow along, import the following flow into your Node-RED instance.
 <video autoplay loop muted playsinline aria-label="Video showing process of creating subflow from the selection" width="800" height="354" preload="none"><source src="/blog/2024/09/images/selecting-and-converting-subflow.webm" type="video/webm" /></video>
 _Video showing process of creating subflow from the selection_
 
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 1. Select the flow you want to convert into a Subflow.
 2. Open the main menu by clicking the top-right menu icon, and select "Selection to Subflow" under the Subflows option.
 
@@ -101,9 +104,6 @@ _Image showing subflow node added in the node palette_
 
 Once selected, the Subflow will be added to the node palette like other nodes. The selected flow will also be converted into a single node representing the Subflow.
 
-::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
-::
-
 ### Adding Properties to the Subflow
 
 1. Double-click on the Subflow, then click on **"Edit Subflow template"**.
diff --git a/src/blog/2024/12/flowfuse-release-2-12.md b/src/blog/2024/12/flowfuse-release-2-12.md
index 1152bb9a29..9cead37ce0 100644
--- a/src/blog/2024/12/flowfuse-release-2-12.md
+++ b/src/blog/2024/12/flowfuse-release-2-12.md
@@ -42,7 +42,6 @@ The new Free plan on FlowFuse Cloud will allow you to manage two remote instance
 
 FlowFuse is an industrial data platform that enables engineers to build, manage, scale, and secure their Node-RED solutions for digitalizing processes and operations. More fundamentally though, it's a great platform to manage multiple instances of Node-RED.
 
-
 <div class="blog-update-notes">
     <p>After careful consideration, we've decided to withdraw the free plan. You can still sign up for a 30-day trial to experience all that FlowFuse has to offer.</p>
 </div>
@@ -59,6 +58,9 @@ In our new free tier on FlowFuse Cloud you get:
 
 ## Getting Started
 
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ### Create Your Free Team
 
 To create a free team, simply [sign up to FlowFuse Cloud](https://app.flowfuse.com/create).
@@ -70,9 +72,6 @@ _Screenshot showing the UI for selecting your Team's type, when onboarding throu
 
 <!-- <img width="438" alt="image" src="https://github.com/user-attachments/assets/da6fde55-27bc-42d7-afcc-19235661b558" /> -->
 
-::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
-::
-
 ### Remote Instances
 
 When you create a Free team, an Application is created for you automatically. Applications in FlowFuse help you organise and group your resources, from Instances to DevOps Pipelines and Snapshots for Version Control. Within your new application, you can "register" your first Remote Instance. 
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 a4bafffa47..41420a3ed3 100644
--- a/src/blog/2024/12/publishing-modbus-data-to-uns.md
+++ b/src/blog/2024/12/publishing-modbus-data-to-uns.md
@@ -92,6 +92,9 @@ While Node-RED doesn't include Modbus nodes by default, adding them to your pale
 
 Next, you'll need to configure the Modbus connection based on your device type. Modbus devices can communicate using two primary protocols: **Modbus RTU** (over serial) or **Modbus TCP** (over Ethernet/Wi-Fi). The specific choice depends on the type of Device you are working with.
 
+::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::
+
 1. Drag a **Modbus Read** node onto your Node-RED Canvas.
 2. Double-click on the **Modbus Read** node to open its configuration.
 3. In the configuration window:
@@ -134,9 +137,6 @@ If you prefer a video explanation, [Kurt Braun](https://www.linkedin.com/in/wago
 
 After collecting data from your Modbus device, the next step is transforming it into a usable format for cloud-based IoT applications. Modbus data typically comes in raw register values, and you may need to convert these values into human-readable formats like temperature, pressure, or other measurements.
 
-::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
-::
-
 Let's walk through the transformation process step by step.
 
 **Step 2.1: Parsing and Converting Raw Modbus Data**
diff --git a/src/blog/2025/02/interacting-with-arduino-using-node-red.md b/src/blog/2025/02/interacting-with-arduino-using-node-red.md
index 31b38d2449..323ff8a743 100644
--- a/src/blog/2025/02/interacting-with-arduino-using-node-red.md
+++ b/src/blog/2025/02/interacting-with-arduino-using-node-red.md
@@ -47,6 +47,9 @@ For a step-by-step guide on installing and running the FlowFuse device agent, re
 
 Now, let's download the setup to the Arduino. Before proceeding, ensure your Arduino is connected to your laptop or computer via the correct USB cable. The USB connection is essential for uploading the code (sketch) to the Arduino and will also be used by Firmata for communication later.
 
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 **Setting up Arduino IDE and Download the setup from examples:**
 
 1. Open the Arduino IDE on your computer.
@@ -59,9 +62,6 @@ _Importing Standard Firmata setup sketch from examples in Arduino IDE_
 
 Once the upload is complete, the Arduino is ready to communicate via the Firmata protocol.
 
-::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
-::
-
 ### Step 3: Connecting Node-RED to Arduino via Serial Communication
 
 As mentioned earlier, Firmata typically works over a serial connection (such as USB), enabling communication between the Arduino board and your Node-RED instance. The serial communication allows Node-RED to send commands to the Arduino and receive data from it.
diff --git a/src/blog/2025/02/node-red-academy-announcement.md b/src/blog/2025/02/node-red-academy-announcement.md
index 5b3002b0c2..7a24fba9a6 100644
--- a/src/blog/2025/02/node-red-academy-announcement.md
+++ b/src/blog/2025/02/node-red-academy-announcement.md
@@ -46,15 +46,15 @@ The [Node-RED Academy](https://node-red-academy.learnworlds.com/) provides Node-
 
 Node-RED Academy is a brand new learning portal for Node-RED. Whether you're a complete beginner to Node-RED or have been building applications for years, Node-RED Academy courses will take your expertise to the next level, and provide you with formal certification that are evidence of your Node-RED knowledge and skills.
 
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ## Can I Earn a Credential?
 
 All courses completed through Node-RED Academy provide a formal certification upon successful course completion. You can share this certificate on LinkedIn, add it to your CV or show it off anywhere else you like.
 
 The credential will be evidence of your Node-RED knowledge and abilities, and will be a great way to demonstrate your expertise to potential employers or clients.
 
-::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
-::
-
 ## What Courses are Included?
 
 Our first course, The [Node-RED Fundamentals](https://node-red-academy.learnworlds.com/), takes about 90 minutes to complete, is free and available now. [Check it out!](https://node-red-academy.learnworlds.com/).
diff --git a/src/blog/2025/05/how-to-generate-pdf-reports-using-node-red.md b/src/blog/2025/05/how-to-generate-pdf-reports-using-node-red.md
index 5765920b50..54702e522c 100644
--- a/src/blog/2025/05/how-to-generate-pdf-reports-using-node-red.md
+++ b/src/blog/2025/05/how-to-generate-pdf-reports-using-node-red.md
@@ -115,6 +115,9 @@ For additional attributes and information, refer to the [pdfmake documentation](
 
 Here’s a simple example of how you can use these attributes to create a basic PDF:
 
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ```json
 {
   "content": [
@@ -191,9 +194,6 @@ This example creates a simple PDF featuring a centered logo, a title, a subtitle
 ![Example pdf result](./images/example-pdf.png){data-zoomable}
 _Example pdf result_
 
-::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
-::
-
 ### Step 3: Creating a Flow to Generate a PDF
 
 Let's learn how to generate a PDF using dynamic inputs. For this, we’ll use the same example PDF report shown earlier, but this time, we’ll replace the hardcoded values with dynamic input data.
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 cc3ed3b104..c39b5823eb 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
@@ -38,14 +38,12 @@ To follow this guide, you'll need:
 - A working OPC UA server connection
 - The basics from our [previous tutorial](/blog/2025/07/reading-and-writing-plc-data-using-opc-ua/)
 
-
 > Managing and scaling Node-RED instances is easy with FlowFuse, offering DevOps pipelines, audit logs, snapshots, high availability, and much more. [Start your free trial today!](https://app.flowfuse.com/account/create)
 
 Before proceeding, check which features your OPC UA server supports, most handle subscriptions and events, but historical data and methods vary by vendor.
 
 Let's get started.
 
-
 ## Real-Time Monitoring with Subscriptions
 
 OPC UA subscriptions monitor values on the server side and notify you only when they change. This is fundamentally different from polling, where you repeatedly ask for values whether they've changed or not.
@@ -62,7 +60,6 @@ To create your first subscription:
 
 > 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/).
 
-
 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.
 
 3. Place an OpcUa-Client node on the canvas. Open its Configuration, select your OPC UA server endpoint configuration, and change the Action dropdown to "SUBSCRIBE". Set the interval to how often you want updates.
@@ -71,16 +68,17 @@ To create your first subscription:
 
 5. Deploy your flow and click the Inject button. 
 
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 ::render-flow{:height="300"}
 ```json
 [{"id":"c62e8dab346d62bb","type":"inject","z":"7008401a.b94db","name":"","props":[{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","x":490,"y":740,"wires":[["cce9159a656858b9"]]},{"id":"cce9159a656858b9","type":"OpcUa-Item","z":"7008401a.b94db","item":"ns=3;i=1003","datatype":"Int32","value":"","name":"","x":700,"y":740,"wires":[["042a5d016ce879c6"]]},{"id":"1c1d56834b8d3373","type":"debug","z":"7008401a.b94db","name":"Result","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload","targetType":"msg","statusVal":"","statusType":"auto","x":1130,"y":720,"wires":[]},{"id":"bccca1356626f117","type":"debug","z":"7008401a.b94db","name":"Errors","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload","targetType":"msg","statusVal":"","statusType":"auto","x":1130,"y":760,"wires":[]},{"id":"042a5d016ce879c6","type":"OpcUa-Client","z":"7008401a.b94db","endpoint":"","action":"subscribe","deadbandtype":"a","deadbandvalue":1,"time":"2","timeUnit":"s","certificate":"n","localfile":"","localkeyfile":"","securitymode":"None","securitypolicy":"None","useTransport":false,"maxChunkCount":1,"maxMessageSize":8192,"receiveBufferSize":8192,"sendBufferSize":8192,"setstatusandtime":false,"keepsessionalive":false,"name":"","x":940,"y":740,"wires":[["1c1d56834b8d3373"],["bccca1356626f117"],[]]}]
 ```
 ::
 
-
 When clicked, the OpcUa-Item node sends the tag to the OpcUa-Client and creates the subscription. The node’s status will update to “subscribed” once the subscription is active. When values change, they appear in the debug panel. If no value changes occur within the interval time, the status will show “keep alive” to confirm that the connection is still active.
 
-
 ### Subscribing to Multiple Tags
 
 To monitor multiple tags, simply create multiple OpcUa-Item nodes and connect them all to the OpcUa-Client node. Each item node should have its own NodeId configured. When you trigger the flow, all tags start updating simultaneously.
@@ -126,9 +124,6 @@ When using the "multiple" topic, each value update arrives in OPC UA's DataValue
 
 Subscribing to multiple tags with OpcUa-Item nodes returns just the value.
 
-::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
-::
-
 ### Stopping Subscriptions
 
 To stop receiving updates and free up server resources, you have two options:
@@ -295,7 +290,6 @@ The historical data returns with timestamps and quality codes. Use this for shif
 
 You've now mastered the advanced features that make OPC UA essential for industrial systems. With subscriptions, you're monitoring values in real-time without wasting bandwidth. With events and alarms, you're capturing critical alerts the moment they happen. With method calls, you're executing complex operations with a single command. And with historical access, you have the data trail needed for analysis and compliance.
 
-
 ## Scale Your OPC UA Implementation
 
 Managing OPC UA flows across multiple sites? FlowFuse helps teams deploy Node-RED to hundreds of edge devices with one click, monitor everything from a central dashboard, and roll back instantly if something goes wrong. Built-in team collaboration, audit logs, and enterprise security keep your industrial data safe.
diff --git a/src/blog/2025/09/poka-yoke-mistake-proofing.md b/src/blog/2025/09/poka-yoke-mistake-proofing.md
index 247e1ff377..34f43208f2 100644
--- a/src/blog/2025/09/poka-yoke-mistake-proofing.md
+++ b/src/blog/2025/09/poka-yoke-mistake-proofing.md
@@ -66,6 +66,9 @@ Shingo made a key distinction between human mistakes and production defects. Mis
 
 Poka yoke is a systematic approach that uses automatic devices or methods to either make errors impossible or make them immediately obvious once they occur. It's any mechanism that helps equipment operators avoid mistakes by preventing, correcting, or drawing attention to human errors as they happen.
 
+::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::
+
 The poka yoke meaning extends beyond simple error prevention. Rather than treating errors as moral failures or training deficiencies, it treats them as design problems. This lean manufacturing approach recognizes that even the most skilled workers experience moments of distraction, fatigue, or cognitive overload.
 
 Traditional quality control detects defects after they occur, requiring inspection, rework, and often scrapping of materials. The poka yoke approach prevents defects during production by making errors physically impossible or immediately visible. This prevention-first approach creates a cascading effect: quality control teams focus on complex issues rather than basic errors, workers gain confidence in their processes, customer satisfaction improves through consistent product quality, and excellence becomes the natural outcome rather than a heroic achievement.
@@ -80,9 +83,6 @@ The impact of mistake-proofing extends far beyond just catching errors. By desig
 
 Errors in manual assembly lead to increased scrap rates, rework, and delays, all contributing to higher production costs. By eliminating errors at the source, the cost of mistakes within a company is reduced significantly. Companies implementing poka yoke techniques saw a 25% increase in productivity, with time previously spent correcting errors now available for value-added activities.
 
-::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
-::
-
 Mistake-proofing creates safer processes by eliminating conditions that lead to accidents. When errors can literally mean life or death (as in pharmaceutical manufacturing), poka yoke becomes mission-critical. Workers experience less frustration from rework and greater confidence in their processes, leading to improved morale. Successful implementation leads to a 20% improvement in customer satisfaction through consistent product quality and reliability.
 
 The benefits of poka yoke in manufacturing deliver measurable business outcomes: defect elimination achieving near-zero defects, waste reduction across the eight forms identified in lean manufacturing, process simplification turning complex procedures into straightforward steps, real-time correction catching mistakes immediately rather than weeks later, scalable quality built into the system rather than dependent on individual heroics, and continuous improvement creating a foundation for ongoing kaizen activities.
diff --git a/src/blog/2025/09/what-is-takt-time.md b/src/blog/2025/09/what-is-takt-time.md
index e6be2b6cde..4a2cc44908 100644
--- a/src/blog/2025/09/what-is-takt-time.md
+++ b/src/blog/2025/09/what-is-takt-time.md
@@ -92,6 +92,9 @@ This **formula of takt time** contains two critical components that require care
 
 ### Available Production Time
 
+::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::
+
 This is the net time available for production during your planning period (typically one shift or one day). When applying the takt formula, available production time includes only planned production time. It excludes planned breaks, meetings, shift changes, and scheduled maintenance, but does not include unplanned downtime such as breakdowns or minor stoppages. It excludes scheduled breaks and lunch periods, shift changeovers, planned maintenance windows, and scheduled meetings or training.
 
 Consider an example calculation of takt time. An eight-hour shift equals 480 minutes. Subtract a 10-minute break to yield 470 minutes. Subtract a 20-minute lunch to yield 450 minutes. Subtract a 30-minute planned changeover to yield 420 minutes. The available production time equals 420 minutes.
@@ -130,9 +133,6 @@ Understanding the meaning of takt time in this result shows the production line
 
 This example illustrates why defining takt time correctly matters for matching cycle time to customer demand. Cycle times significantly exceeding takt time reveal capacity shortfalls requiring immediate attention. Cycle times falling well below takt time suggest excess capacity that might be redeployed elsewhere or indicate risk of overproduction if production control systems fail to prevent excess output.
 
-::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
-::
-
 ### Example 2: Electronics Assembly (Multiple Shifts)
 
 An electronics manufacturer operates two shifts producing circuit boards, with weekly demand of 2,400 units across five operating days. Each eight-hour shift allocates 40 minutes for breaks and 20 minutes for changeovers.
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 5bffbecd59..222569aae6 100644
--- a/src/blog/2025/10/building-mcp-server-using-flowfuse.md
+++ b/src/blog/2025/10/building-mcp-server-using-flowfuse.md
@@ -63,6 +63,9 @@ Before defining resources or tools, the MCP Server must be configured. This serv
 
 Once the server is configured, clients can connect using a URL. The URL to connect with is your instance URL plus the MCP path you configured, for example:
 
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 ```
 https://your-instance.flowfuse.cloud/mcp
 ```
@@ -81,9 +84,6 @@ http://192.168.1.100:1880/mcp
 
 This URL allows AI agents to discover resources, execute tools, and interact with your flows.
 
-::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
-::
-
 ### Securing Your MCP Server
 
 To ensure your MCP server is protected from unauthorized access, enable FlowFuse User Authentication.
diff --git a/src/blog/2025/10/node-red-vs-flowfuse.md b/src/blog/2025/10/node-red-vs-flowfuse.md
index 2e0a177f2d..a6ab737285 100644
--- a/src/blog/2025/10/node-red-vs-flowfuse.md
+++ b/src/blog/2025/10/node-red-vs-flowfuse.md
@@ -48,6 +48,9 @@ Your Node-RED flow works. It monitors equipment, processes data, and displays da
 
 That question exposes the limitations of standalone Node-RED:
 
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 You need to deploy to 50 sites across three continents without manual setup at each location. Five engineers need to work on improvements without conflicts. You need alerts when any instance goes down because downtime stops production and costs money. Your security team requires SSO integration, role-based access control, and audit trails. You need to push updates to all sites at once, not travel to each location over weeks. When someone deploys a breaking change on Friday afternoon, you need to roll it back in seconds.
 
 This is where Node-RED ends and FlowFuse begins.
@@ -66,9 +69,6 @@ FlowFuse provides role-based access control (RBAC) to define who edits flows ver
 
 For supply chain security, FlowFuse generates a Software Bill of Materials (SBOM) listing every node and dependency across your instances. Security teams can scan for vulnerabilities and track what needs updating.
 
-::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
-::
-
 ### Team Collaboration and Version Control
 
 Node-RED was built for individual developers. When two people edit the same instance, the last save wins. No version history exists. No way to review changes before deployment. No rollback option.
diff --git a/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md b/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md
index 60f9724d25..8b0556c858 100644
--- a/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md
+++ b/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md
@@ -102,6 +102,9 @@ Now, let's get started. First, watch this demo, where I have built a FlowFuse fl
 
 This flow standardizes data from each protocol into a consistent JSON format, enriches it with contextual metadata, and publishes everything to the FlowFuse MQTT Broker, all within a single instance. The following guide explains how to replicate this setup for any PLC on your factory floor.
 
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 ## Step 1: Extract Data from Your PLC
 
 As mentioned earlier, extracting data is the first and most complex step. Get this wrong, and the complexity and costs can spiral out of control. FlowFuse simplifies this process. Its pre-built connectors handle Modbus, OPC UA, EtherNet/IP, and other protocols right out of the box, no custom coding, expensive proprietary gateways, or per-tag licensing fees required. You can configure your connections visually and have data flowing within minutes.
@@ -120,9 +123,6 @@ The Node-RED ecosystem that powers FlowFuse offers comprehensive protocol suppor
 
 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.
 
-::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
-::
-
 ## Convincing the IT Team
 
 When talking to people in the IIoT community, one recurring challenge always comes up, **convincing the IT team**.
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 2d814ca758..73b7db5a4d 100644
--- a/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md
+++ b/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md
@@ -96,6 +96,9 @@ Used for PLCs that connect directly via Ethernet without backplane routing, such
 **With Routing:**
 Used for chassis-based PLCs like ControlLogix and CompactLogix, where the processor sits in a backplane slot. In this case, the slot number must be specified, as it automatically creates a routing path through the backplane to reach the processor.
 
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 ### Unconnected Messaging
 
 Unconnected messaging sends individual requests without maintaining a persistent connection. Each transaction is standalone, request, response, done.
@@ -122,9 +125,6 @@ To communicate with Allen-Bradley PLCs from FlowFuse, use the popular node-red-c
 
 Once installed, you'll find the EtherNet/IP nodes in your palette under the "plc" category. The main nodes are `ethernet-ip in` for reading data and `ethernet-ip out` for writing data to the PLC.
 
-::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
-::
-
 ## Configuring the EtherNet/IP Node
 
 Now that you have installed the EtherNet/IP node, it is time to configure the connection to your Allen-Bradley PLC.
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 0f7db15c49..06fbff2130 100644
--- a/src/blog/2025/11/building-hmi-for-equipment-control.md
+++ b/src/blog/2025/11/building-hmi-for-equipment-control.md
@@ -96,6 +96,9 @@ Start by creating a [FlowFuse account](https://app.flowfuse.com/account/create).
 
 Your HMI needs to talk to your PLC to read equipment status and send control commands. FlowFuse handles this through Node-RED's protocol nodes, which support every major industrial controller. No proprietary gateways, no per-tag licensing, no vendor lock-in, just direct communication with your PLC.
 
+::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
+::
+
 Choose the node that matches your PLC:
 
 - **[node-red-contrib-modbus](/node-red/protocol/modbus/)** – Modbus RTU/TCP PLCs and devices
@@ -123,9 +126,6 @@ After saving the connection configuration, specify the **variable addresses that
 
 For sending commands (start motor, stop motor, setpoints), drag the corresponding output node onto your canvas. When configuring it, select the **same Server/Connection** from the dropdown instead of creating a new one. This shared connection approach means the IP address, port, and credentials only need to be configured once and can be reused across all your PLC/server nodes. You then only need to specify the variable addresses that control your equipment, and connect those nodes to your dashboard buttons or automation logic.
 
-::cta-image{src="/images/cta/wenco-book-demo.png" alt="Wenco deploys new dashboard pages in days with FlowFuse - book a demo" cta="demo"}
-::
-
 **Important Note:** Some PLCs require configuration in their engineering software before allowing external access. For example, Siemens S7 requires **PUT/GET communication** enabled in TIA Portal, and Allen-Bradley controllers may need **explicit messaging** enabled in Studio 5000. Refer to your PLC’s documentation for any communication prerequisites.
 
 **Test Your Connection:**
diff --git a/src/blog/2025/12/kafka-vs-mqtt.md b/src/blog/2025/12/kafka-vs-mqtt.md
index e83b2688c6..16f529f189 100644
--- a/src/blog/2025/12/kafka-vs-mqtt.md
+++ b/src/blog/2025/12/kafka-vs-mqtt.md
@@ -67,6 +67,9 @@ MQTT has three Quality of Service levels:
 
 **QoS 2** - Exactly once through a four-way handshake. Slowest but guaranteed.
 
+::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
+::
+
 Pick based on what you're sending. Temperature readings every 10 seconds? QoS 0 is fine. Critical alarm messages? QoS 2.
 
 ## How Kafka Works
@@ -83,9 +86,6 @@ Unlike MQTT, messages don't disappear after delivery. Everything writes to disk.
 
 Early Kafka needed Apache Zookeeper for cluster coordination, which added complexity. Recent versions support KRaft mode that removes this dependency, though many production systems still run Zookeeper.
 
-::cta-image{src="/images/cta/power-workplace-book-demo.png" alt="Power Workplace relies on FlowFuse for scalability, reliability and security audits - book a demo" cta="demo"}
-::
-
 ## The Real Differences
 
 ### Architecture Philosophy
diff --git a/src/blog/2025/12/node-red-buffer-parser-industrial-data.md b/src/blog/2025/12/node-red-buffer-parser-industrial-data.md
index 952ded715e..f0d5738cef 100644
--- a/src/blog/2025/12/node-red-buffer-parser-industrial-data.md
+++ b/src/blog/2025/12/node-red-buffer-parser-industrial-data.md
@@ -112,6 +112,9 @@ The device manual says this buffer breaks down as:
 - Bytes 5-6: Humidity reading
 - Bytes 7-8: CRC checksum
 
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 You need to extract temperature and humidity. Everything else is Modbus protocol overhead.
 
 The manual also specifies:
@@ -132,9 +135,6 @@ return msg;
 
 This works, but it's also fragile. When you need to add a pressure reading next month, you're editing code and hoping you don't break the offset calculations. When someone else looks at this flow, they have no idea what's happening without reading the function and if they don't understand JavaScript, they're stuck.
 
-::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
-::
-
 Buffer Parser turns this into configuration you can see and modify without touching code. Let's walk through a practical example.
 
 > But before you start, make sure you have a Node-RED instance running on your edge device. The fastest, easiest, and most production-ready way is using FlowFuse. If you don't have an account yet, create one with our [free trial](https://app.flowfuse.com/). FlowFuse simplifies managing remote instances and provides the ability to create hosted instances, no matter how many you need to manage, it makes it easy. There are no deployment headaches either; everything is managed by FlowFuse with built-in security. You'll also get access to tools such as DevOps pipelines, snapshots for recovery, audit logs, real-time collaboration with granular role-based access control (RBAC), and much more.
diff --git a/src/blog/2025/12/node-red-timer.md b/src/blog/2025/12/node-red-timer.md
index 13becd51a8..59c2077fa0 100644
--- a/src/blog/2025/12/node-red-timer.md
+++ b/src/blog/2025/12/node-red-timer.md
@@ -80,6 +80,9 @@ Let's start with installing and building a stopwatch.
 
 ### Installing the Hourglass Node
 
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 First, install the **hourglass node** in your Node-RED instance:
 
 1. Open the Node-RED editor
@@ -102,9 +105,6 @@ The hourglass node responds to control commands sent via `msg.command`. The avai
 
 These commands control timer behavior.
 
-::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
-::
-
 ### Implementing a Stopwatch Timer
 
 Build a basic **stopwatch flow**:
diff --git a/src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md b/src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md
index 3474261ae1..72648194b9 100644
--- a/src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md
+++ b/src/blog/2025/12/read-s7-optimized-datablocks-flowfuse.md
@@ -97,6 +97,9 @@ Siemens S7-1200 and S7-1500 PLCs have built-in OPC UA server. Activate it in TIA
 
 When you modify your data block or recompile, your flows keep working because they reference variable names, not memory locations that might shift.
 
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 ## Prerequisites
 
 Before you begin, make sure you have:
@@ -132,9 +135,6 @@ Before exposing variables, you need to create an OPC UA server interface in your
 
 If you're using an S7-1500 PLC with firmware version 2.5 or higher, you have the option to enable the standard SIMATIC server interface. Simply check **Enable standard SIMATIC server interface** in the OPC UA settings. This automatically makes all PLC tags that are marked as accessible available through OPC UA.
 
-::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
-::
-
 **For S7-1200 PLCs (or manual configuration for S7-1500):**
 
 For S7-1200 PLCs, you must manually create a server interface and add the tags you want to expose:
diff --git a/src/blog/2025/12/what-is-teep.md b/src/blog/2025/12/what-is-teep.md
index 63a342935f..1fd5694a9f 100644
--- a/src/blog/2025/12/what-is-teep.md
+++ b/src/blog/2025/12/what-is-teep.md
@@ -69,6 +69,9 @@ But availability now means operating time divided by total calendar time, not ju
 
 TEEP matters because it connects operational performance to **business value**, not just shop-floor efficiency. While OEE shows how well equipment runs during scheduled shifts, it says nothing about how much of the asset you're actually using relative to what you paid for it. TEEP fills that gap.
 
+::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
+::
+
 For capital-intensive manufacturing, this difference is critical. Equipment often represents millions in investment, yet much of that capacity may sit idle due to scheduling choices, demand patterns, labor availability, or maintenance strategy. TEEP makes this visible. It answers the executive-level question: **"Are we getting a return on our equipment, or is capacity hiding in plain sight?"**
 
 TEEP is especially valuable when:
@@ -82,9 +85,6 @@ In many cases, TEEP reveals that the fastest and cheapest way to increase output
 
 Importantly, TEEP is not about pushing equipment to run 24/7 at all costs. Instead, it provides the data needed to make **intentional, informed decisions** about scheduling, staffing, maintenance, and growth.
 
-::cta-image{src="/images/cta/arch-systems-book-demo.png" alt="Arch Systems scales automation across complex manufacturing environments with FlowFuse - book a demo" cta="demo"}
-::
-
 ## TEEP vs OEE: Key Differences
 
 OEE and TEEP both measure equipment performance, but they look at different things. The big difference is what time period they measure against.
diff --git a/src/blog/2026/01/opcua-vs-mqtt.md b/src/blog/2026/01/opcua-vs-mqtt.md
index 6df9ce439b..a8e809e8ac 100644
--- a/src/blog/2026/01/opcua-vs-mqtt.md
+++ b/src/blog/2026/01/opcua-vs-mqtt.md
@@ -91,6 +91,9 @@ The broker is a single point of failure unless you architect clustering separate
 
 MQTT is deliberately minimal. This simplicity at the transport layer enables its flexibility and efficiency.
 
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 ### OPC UA: The Semantic Framework
 
 OPC UA (Unified Architecture) isn't primarily about moving data; it's about describing what data means, how it relates to other data, and what operations are valid.
@@ -135,9 +138,6 @@ Implementing an OPC UA server requires managing an address space, handling multi
 
 This overhead is impractical for battery-powered sensors with infrequent reporting requirements. It's appropriate for a $2M manufacturing cell where understanding that a temperature reading represents "bearing temperature on the output shaft of motor 3, measured in Celsius, with a normal operating range of 40-65°C and critical alarm at 85°C" matters.
 
-::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
-::
-
 ### The Layer Mismatch
 
 Think about the OSI model, that seven-layer networking abstraction everyone learns and immediately forgets:
diff --git a/src/blog/2026/01/why-modbus-still-exist.md b/src/blog/2026/01/why-modbus-still-exist.md
index 2b60355f0c..b20c089fcc 100644
--- a/src/blog/2026/01/why-modbus-still-exist.md
+++ b/src/blog/2026/01/why-modbus-still-exist.md
@@ -61,6 +61,9 @@ The numbers show how big this problem is. [The Modbus TCP market alone was $1.35
 
 ## It Costs Almost Nothing
 
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 The economics of Modbus implementation are absurdly compelling. A basic Modbus RTU interface costs manufacturers maybe $5-10 in components. Software licensing? Zero. The protocol is completely open, no royalties, no certification fees, no vendor lock-in. Compare that to implementing industrial Ethernet protocols where you might pay thousands for stack licenses, certification processes, and conformance testing.
 
 For device manufacturers, this matters enormously. A sensor company can add Modbus support for trivial cost and immediately become compatible with millions of existing installations. The development effort is minimal: the protocol specification fits in a few dozen pages, implementations are straightforward, and countless reference designs exist. You don't need specialized silicon or complex firmware. A basic microcontroller with a UART can speak Modbus RTU. Add an Ethernet chip and you've got Modbus TCP.
@@ -77,9 +80,6 @@ Industrial automation is full of protocol wars where vendors push their preferre
 
 Modbus doesn't care. It works with everyone's equipment. This vendor neutrality has enormous practical value in facilities running mixed automation systems. A typical factory floor might have Rockwell PLCs, ABB drives, Schneider Electric power meters, and Siemens HMIs all talking to each other. Getting all those vendors' preferred protocols to coexist would be a nightmare. Getting them all to speak Modbus is trivial.
 
-::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
-::
-
 This creates competitive pressure that keeps Modbus relevant. Device manufacturers can't afford to skip Modbus support because doing so immediately excludes them from projects with heterogeneous automation systems. Even vendors with their own sophisticated protocols implement Modbus as a fallback, ensuring interoperability when nothing else works.
 
 The open nature also prevents the protocol from becoming a competitive weapon. Nobody can leverage Modbus to lock customers into their platform. Nobody can obsolete older Modbus devices by dropping support in newer products. The protocol's longevity is guaranteed by the fact that no single entity controls its fate.
diff --git a/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md b/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md
index 9c57310729..bbea8bf034 100644
--- a/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md
+++ b/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md
@@ -33,6 +33,9 @@ That architecture imposes hard constraints. Only one device can transmit at a ti
 
 ![Image showing Modbus RTU on RS-485 and Modbus TCP on Ethernet.](./images/modbus-rtu-and-tcp-physical-layer.png "Image showing Modbus RTU on RS-485 and Modbus TCP on Ethernet.")
 
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 Modbus TCP moves the same application layer onto Ethernet and wraps it in a TCP socket. The serial constraints disappear. Multiple masters can coexist, transactions can be pipelined, and the physical layer handles collision detection and retransmission. What you gain in flexibility, you trade for a different set of assumptions. TCP guarantees delivery, but not timing. A retransmission storm on a busy network can stretch response times in ways that RTU, for all its limitations, never would.
 
 ## Latency: What the Numbers Actually Mean on the Floor
@@ -51,9 +54,6 @@ The catch is that Ethernet latency is not flat. It varies with network load, swi
 
 RTU offers better worst-case latency. TCP offers better average latency. In industrial control, worst-case is usually what you design for.
 
-::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
-::
-
 ## Failure Modes: What Breaks, How It Breaks, and Whether You Will Know
 
 This is where the two protocols diverge most sharply, and where choosing wrong costs the most.
diff --git a/src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md b/src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md
index 4d0966729d..6fa5d274fc 100644
--- a/src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md
+++ b/src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md
@@ -40,6 +40,9 @@ None of that happened.
 
 The [Modbus TCP market was valued at $1.35 billion in 2024 and is projected to reach $2.55 billion by 2032](https://www.futuremarketreport.com/industry-report/modbus-communication-module-market). That isn't legacy drag. That's active investment. New Modbus devices are being designed, manufactured, purchased, and installed in 2026, not as fallback options, but as deliberate first choices. Meanwhile, OPC UA adoption, while genuinely growing, remains concentrated in specific layers of the automation stack: SCADA systems, MES integrations, and IT/OT gateways. At the field device level, Modbus still dominates.
 
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 The gap between expectation and reality isn't a failure of OPC UA's design. The protocol does what it promises. The gap exists because adoption in industrial automation doesn't follow software industry timelines. A protocol doesn't win by being technically superior. It wins by becoming the path of least resistance across every layer of the ecosystem simultaneously: device manufacturers, integrators, maintenance teams, procurement departments, and plant managers all have to move together. That has never happened with OPC UA, and understanding why requires looking at each layer honestly.
 
 ## The Complexity Tax Nobody Talks About
@@ -54,9 +57,6 @@ For device manufacturers, the math is punishing. A Modbus RTU interface costs ro
 
 Certificate management alone has quietly killed more OPC UA deployments than any technical limitation. Certificates expire. They need to be provisioned, rotated, and trusted across every client and server. In an IT environment with dedicated security teams, this is manageable. In a plant where the automation engineer also handles PLC programming, HMI design, and network troubleshooting, it becomes an ongoing burden that nobody budgeted for and nobody wants to own.
 
-::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
-::
-
 The OPC Foundation recognized this. Companion specifications like OPC UA FX and the Field Level Communications initiative are genuine attempts to bring the protocol closer to the field device layer. Progress is real but slow, and in the meantime, device manufacturers continue defaulting to Modbus because it ships today without a compliance checklist.
 
 Complexity isn't a dealbreaker when the problem demands it. Nobody complains that OPC UA is too complex when it's modeling an entire production line in a SCADA system. The complexity tax only becomes fatal when the problem is simple and a simpler tool is sitting right there, already understood by the team, already working.
diff --git a/src/blog/2026/04/diagnosing-modbus-degradation.md b/src/blog/2026/04/diagnosing-modbus-degradation.md
index 8d10fb3e00..320ee3ea59 100644
--- a/src/blog/2026/04/diagnosing-modbus-degradation.md
+++ b/src/blog/2026/04/diagnosing-modbus-degradation.md
@@ -49,6 +49,9 @@ One failure mode that gets far less attention than it deserves: bus contention f
 
 RS-485 is half-duplex. After sending a request, the master must de-assert its transmit driver before the device can respond. If the driver stays asserted even a few hundred microseconds too long (firmware timing bug, misconfigured enable pin, USB adapter with incorrect turnaround handling) the device's response overlaps with the master's still-active driver. The result is frame corruption on every transaction, every time, and it's indistinguishable from a severely damaged cable.
 
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 A [protocol analyzer](https://en.wikipedia.org/wiki/Protocol_analyzer) confirms it immediately by showing both signals active simultaneously. Before you pull cable on a segment where every transaction is corrupted, swap the serial adapter or test with a different master. It takes ten minutes and it's right more often than people expect.
 
 ### Modbus TCP: connection management and latency
@@ -64,9 +67,6 @@ Those connection slots release when the idle-connection timeout or the TCP FIN/R
 
 That regularity is the diagnostic signal. A device with intermittent hardware faults fails unpredictably. A device whose connection table is being exhausted fails on a clock. If you're seeing periodic offline events with suspiciously consistent timing, check your connection handling before you assume the device is faulty.
 
-::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
-::
-
 **Transaction ID handling** is worth checking in high-concurrency polling configurations. The [Modbus application protocol specification](https://www.modbus.org/file/secure/modbusprotocolspecification.pdf) defines Transaction IDs to match requests with responses. A polling stack that reuses Transaction IDs before receiving a response to the previous one can match incoming responses to the wrong pending request. When this occurs, the symptom is correct values appearing in the wrong registers. It doesn't show up as an error at all, which makes it unusually difficult to diagnose. If you're seeing values that are off by a plausible amount but never produce error codes, check whether your stack's Transaction ID handling is correct under concurrent load.
 
 The second TCP failure mode that's become more common as industrial networks gain remote access infrastructure is latency on routed network paths pushing transaction times past configured timeouts. This applies to any routed path: site-to-site VPNs, SD-WAN appliances, MPLS links with QoS misconfiguration, or firewalls with deep-packet inspection enabled for industrial protocols. Modbus TCP on a dedicated plant-floor LAN has round-trip latency in single-digit milliseconds. The same configuration over a site-to-site VPN or through a stateful firewall can see 80 to 200ms per transaction. If your timeouts were calculated against a local network and you've since added any routing hops, your effective timeout margin may now be zero under any congestion. The failures are load-dependent: worse during business hours, cleaner overnight, invisible when you run a manual test. The fix is the same as in the last article: measure actual round-trip time under realistic load, then set your timeout to 1.5 to 2x that value.
diff --git a/src/blog/2026/04/modbus-polling-best-practices.md b/src/blog/2026/04/modbus-polling-best-practices.md
index 95e81013e3..e08acd8c17 100644
--- a/src/blog/2026/04/modbus-polling-best-practices.md
+++ b/src/blog/2026/04/modbus-polling-best-practices.md
@@ -42,6 +42,9 @@ Consider what's actually living in a typical Modbus device: a temperature readin
 
 **Polling too slow loses events.** A motor fault flag that goes high for 800ms and then clears on its own will be completely invisible to a 1-second polling interval. Not occasionally invisible, reliably invisible. The bit flipped, the motor logged an internal fault, the fault self-cleared, and your polling cycle saw nothing but normal values on both sides of the event. You'll hear about that fault months later when the motor fails completely and maintenance pulls the device logs.
 
+::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
+::
+
 The fix isn't complicated, but it requires making a deliberate decision you've probably been deferring: **categorize your data by how fast it actually changes, then assign poll rates to match.**
 
 A practical starting framework for most industrial installations:
@@ -55,9 +58,6 @@ This tiered approach does something important beyond just reducing bus load: it
 
 The pushback you'll hear is that tiered polling is harder to configure and harder to document. That's true. A single scan rate is simple to explain and simple to hand off. But simple to configure and correct are different things, and a polling architecture that silently misses events or saturates a serial bus isn't simple. It's a problem that hasn't surfaced yet.
 
-::cta-image{src="/images/cta/aperia-book-demo.png" alt="Aperia Technologies stopped reprogramming controllers station by station with FlowFuse - book a demo" cta="demo"}
-::
-
 One more thing worth stating plainly: your scan rate has to account for the device's actual response capability, not just the rate you want data. Some field devices, including older PLCs, low-cost sensors, and anything running on an 8-bit microcontroller with slow UART handling, need 50 to 150ms just to process a request and formulate a response. If your fast-tier scan rate is 100ms and your device needs 120ms to respond, you're not getting 100ms data. You're getting collisions, timeouts, and a maintenance headache. Measure actual device response times before setting your fast-tier interval. The device datasheet will give you a starting point; a protocol analyzer will give you the truth.
 
 ## How Timeout Misconfiguration Kills Stability
diff --git a/src/blog/2026/06/node-red-5-on-flowfuse.md b/src/blog/2026/06/node-red-5-on-flowfuse.md
index 0d0f1a7a27..d75220cfbd 100644
--- a/src/blog/2026/06/node-red-5-on-flowfuse.md
+++ b/src/blog/2026/06/node-red-5-on-flowfuse.md
@@ -57,6 +57,9 @@ Node-RED 5 is the first release built around the editor itself. Previous major v
 ![The redesigned Node-RED 5 editor showing the new sidebars and Explorer panel.](./images/node-red-5.png)
 *The Node-RED 5 editor, redesigned around the place teams spend their whole day.*
 
+::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
+::
+
 The **redesigned sidebars** now behave the same on both sides of the editor. Controls are grouped together instead of buried in a menu, and you can split one vertically to keep two panels open at once. A new **Explorer panel** gives you a structured view of your flows, making large projects with dozens of tabs far easier to navigate. And a **built-in dark theme** now ships in core, with no custom packages needed, alongside an accessibility review of the default theme.
 
 ![The Node-RED 5 editor in its built-in dark theme.](./images/nr-dark-theme.png)
@@ -64,9 +67,6 @@ The **redesigned sidebars** now behave the same on both sides of the editor. Con
 
 Underneath the visual changes are functional and security improvements across debugging, authentication, and TLS, the parts that matter most once Node-RED is running in production. If previous releases expanded what it could do, this one sharpens how it feels to use. For the full list, read the [release blog](https://nodered.org/blog/2026/06/09/version-5-0-released).
 
-::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
-::
-
 ## What it means for industrial teams
 
 The editor is where your team spends its day, so changes here add up fast across a working week.