diff --git a/nuxt/nuxt.config.ts b/nuxt/nuxt.config.ts
index 5b7dd6e6e6..72f6bfbc50 100644
--- a/nuxt/nuxt.config.ts
+++ b/nuxt/nuxt.config.ts
@@ -492,6 +492,11 @@ export default defineNuxtConfig({
'/landing/tulip/',
'/landing/plc/',
'/landing/factory-efficiency/',
+ // The partner pages are .vue files; only the listing is linked from the nav.
+ '/partners/',
+ '/partners/certify-hardware/',
+ '/partners/ctrlx/',
+ '/partners/referral-sign-up/',
// The six architecture pages are .vue files with no listing that links to them all, so the crawler never reaches them.
'/use-cases/data-integration/',
'/use-cases/edge-connectivity/',
diff --git a/nuxt/pages/partners/certify-hardware.vue b/nuxt/pages/partners/certify-hardware.vue
new file mode 100644
index 0000000000..6442013960
--- /dev/null
+++ b/nuxt/pages/partners/certify-hardware.vue
@@ -0,0 +1,96 @@
+
+
+
+
+
+
+
How to Certify Your Hardware
+
+
Follow these steps to get your hardware certified for compatibility with FlowFuse and Node-RED.
+
+
+
+
+
Technical Qualification in 3 Steps
+
+
+
+
+
+
+
+
+
+
+
+ Explore the FlowFuse Device Agent
+ Repository and
+ Documentation.
+
+ {{ step.text }}
+
+
+
+
+
+
+
Certification
+
+
After successfully navigating the technical qualification, take the next step by booking a meeting with our team. Together, we'll work towards ensuring your device is fully compatible with FlowFuse and Node-RED.
+
+
+
+
+
+
+
+
+
+
Marketing and Publications
+
+
+
+
+
+
In a joint meeting, we will discuss marketing activities on a case-by-case basis.
+
+
+
+
+
+
Upon successful technical qualification, you will be granted the right to use the "FlowFuse Certified" logo.
+ FlowFuse reduces the risk of using Node-RED in production. We offer professional support for
+ Node-RED deployments on the crtlX platform. Customers have direct access to Node-RED experts who can
+ help with development and production deployment issues.
+
+
+
+
+
+
+
+
Support for Third Party Nodes
+
+
+ The Node-RED package for ctrlX includes pre-installs third party nodes for
+ popular industrial protocols, including OMRON, MC Protocol, Modbus and S7. FlowFuse will support the
+ use of these nodes in production.
+
+
+
+
+
+
+
+
+
+
+
For CtrlX Customers
+
+
+
+
+
+
+
+
+
+
Customer Support
+
+
+ Get in touch with us to access expert guidance and comprehensive assistance for your Node-RED
+ deployments. Our team will support you every step of the way, ensuring seamless integration and
+ successful implementation.
+
+
+
+
+ CONTACT SUPPORT
+
+
+
+
+
+
+
+
+
+
Upgrade to FlowFuse
+
+
+ CtrlX customers can update their Node-RED deployments to use the FlowFuse platform to take
+ advantage of our device management, team collaboration, software delivery pipelines and other
+ enterprise features. Book a demo to discover the FlowFuse platform.
+
+ Many companies are realizing the benefits of using FlowFuse for their Node-RED development. We want to
+ encourage them to recommend FlowFuse to other potential users. That's why we're excited to offer a referral
+ program that rewards others for spreading the word about our platform.
+
+
diff --git a/nuxt/public/images/flowfuse-icon.png b/nuxt/public/images/flowfuse-icon.png
new file mode 100644
index 0000000000..33474d5c0d
Binary files /dev/null and b/nuxt/public/images/flowfuse-icon.png differ
diff --git a/nuxt/public/images/partners/ff-certified-device.svg b/nuxt/public/images/partners/ff-certified-device.svg
new file mode 100644
index 0000000000..1b50f6a9c6
--- /dev/null
+++ b/nuxt/public/images/partners/ff-certified-device.svg
@@ -0,0 +1,61 @@
+
+
\ No newline at end of file
diff --git a/nuxt/public/images/partners/logo-40hero.png b/nuxt/public/images/partners/logo-40hero.png
new file mode 100644
index 0000000000..c99281ef86
Binary files /dev/null and b/nuxt/public/images/partners/logo-40hero.png differ
diff --git a/nuxt/public/images/partners/logo-aws.png b/nuxt/public/images/partners/logo-aws.png
new file mode 100644
index 0000000000..116355add7
Binary files /dev/null and b/nuxt/public/images/partners/logo-aws.png differ
diff --git a/nuxt/public/images/partners/logo-digital-o.png b/nuxt/public/images/partners/logo-digital-o.png
new file mode 100644
index 0000000000..e49ef5a9de
Binary files /dev/null and b/nuxt/public/images/partners/logo-digital-o.png differ
diff --git a/nuxt/public/images/partners/logo-gallarus.png b/nuxt/public/images/partners/logo-gallarus.png
new file mode 100644
index 0000000000..4c402f7aff
Binary files /dev/null and b/nuxt/public/images/partners/logo-gallarus.png differ
diff --git a/nuxt/public/images/partners/logo-idoneos.png b/nuxt/public/images/partners/logo-idoneos.png
new file mode 100644
index 0000000000..8285d71cd8
Binary files /dev/null and b/nuxt/public/images/partners/logo-idoneos.png differ
diff --git a/nuxt/public/images/partners/logo-iniationware.png b/nuxt/public/images/partners/logo-iniationware.png
new file mode 100644
index 0000000000..ef28dc5c6c
Binary files /dev/null and b/nuxt/public/images/partners/logo-iniationware.png differ
diff --git a/nuxt/public/images/partners/logo-mayker.png b/nuxt/public/images/partners/logo-mayker.png
new file mode 100644
index 0000000000..ca05d185bc
Binary files /dev/null and b/nuxt/public/images/partners/logo-mayker.png differ
diff --git a/nuxt/public/images/partners/logo-ncd-io.png b/nuxt/public/images/partners/logo-ncd-io.png
new file mode 100644
index 0000000000..fcb7fea422
Binary files /dev/null and b/nuxt/public/images/partners/logo-ncd-io.png differ
diff --git a/nuxt/public/images/partners/logo-rexroth.png b/nuxt/public/images/partners/logo-rexroth.png
new file mode 100644
index 0000000000..f636cefe6d
Binary files /dev/null and b/nuxt/public/images/partners/logo-rexroth.png differ
diff --git a/nuxt/public/images/partners/logo-wago.png b/nuxt/public/images/partners/logo-wago.png
new file mode 100644
index 0000000000..fa675a580f
Binary files /dev/null and b/nuxt/public/images/partners/logo-wago.png differ
diff --git a/nuxt/public/images/partners/nr-ctrlx.png b/nuxt/public/images/partners/nr-ctrlx.png
new file mode 100644
index 0000000000..51e4e786fa
Binary files /dev/null and b/nuxt/public/images/partners/nr-ctrlx.png differ
diff --git a/nuxt/public/images/pictograms/browser_blue.png b/nuxt/public/images/pictograms/browser_blue.png
new file mode 100644
index 0000000000..42c0d72baf
Binary files /dev/null and b/nuxt/public/images/pictograms/browser_blue.png differ
diff --git a/nuxt/public/images/pictograms/results_blue.png b/nuxt/public/images/pictograms/results_blue.png
new file mode 100644
index 0000000000..ad0478156e
Binary files /dev/null and b/nuxt/public/images/pictograms/results_blue.png differ
diff --git a/nuxt/public/images/pictograms/security_blue.png b/nuxt/public/images/pictograms/security_blue.png
new file mode 100644
index 0000000000..1768ca98ae
Binary files /dev/null and b/nuxt/public/images/pictograms/security_blue.png differ
diff --git a/nuxt/public/images/pictograms/support_blue.png b/nuxt/public/images/pictograms/support_blue.png
new file mode 100644
index 0000000000..4faa6a3e09
Binary files /dev/null and b/nuxt/public/images/pictograms/support_blue.png differ
diff --git a/nuxt/public/images/pictograms/time_blue.png b/nuxt/public/images/pictograms/time_blue.png
new file mode 100644
index 0000000000..2549745598
Binary files /dev/null and b/nuxt/public/images/pictograms/time_blue.png differ
diff --git a/nuxt/server/middleware/legacy.ts b/nuxt/server/middleware/legacy.ts
index 5606284c33..e2597a422a 100644
--- a/nuxt/server/middleware/legacy.ts
+++ b/nuxt/server/middleware/legacy.ts
@@ -15,12 +15,12 @@ const NUXT_ROUTE_PREFIXES = ['/integrations/', '/raw/']
// left once its one referring blog post pointed at /contact-us/ instead) - but they stay
// listed so their 301s in nuxt/redirects.ts are served by Nitro in dev rather than being
// proxied to 11ty, which has nothing there either.
-const NUXT_PREFIXES = ['/handbook', '/ebooks', '/whitepaper', '/pricing', '/docs', '/changelog', '/application-guide', '/blog', '/product', '/customer-stories', '/thank-you', '/resources', '/webinars', '/free-consultation', '/vs', '/landing', '/use-cases']
+const NUXT_PREFIXES = ['/handbook', '/ebooks', '/whitepaper', '/pricing', '/docs', '/changelog', '/application-guide', '/blog', '/product', '/customer-stories', '/thank-you', '/resources', '/webinars', '/free-consultation', '/vs', '/landing', '/use-cases', '/partners']
// Top-level routes still on 11ty, not yet ported to Nuxt (everything not listed above
// already falls through to the 11ty proxy by default). Remove entries here as they migrate:
// /blueprints, /careers, /community, /events
-// /free-consultation, /industries, /node-red, /partners, /platform, /webinars
+// /free-consultation, /industries, /node-red, /platform, /webinars
// New pages should never grow that fallback set: nuxt/lib/legacy-pages.test.mjs fails
// `npm test` if a PR adds a new .njk file under src/ that doesn't already exist on main,
diff --git a/src/partners/certify-hardware.njk b/src/partners/certify-hardware.njk
deleted file mode 100644
index baad53d7ff..0000000000
--- a/src/partners/certify-hardware.njk
+++ /dev/null
@@ -1,89 +0,0 @@
----
-layout: layouts/page.njk
-meta:
- title: How to Certify Your Hardware
- description: Follow these steps to get your hardware certified for compatibility with FlowFuse and Node-RED
----
-{% from "components/cta/cta-contact-us.njk" import ctaContactUs %}
-
-
How to Certify Your Hardware
-
-
Follow these steps to get your hardware certified for compatibility with FlowFuse and Node-RED.
Ensure that the Device Agent comes pre-installed on your device. Alternatively, it should be available from a store or marketplace as a "one-click" installer.
-
-
-
-
-
-
{% include "components/icons/document-arrow-up.svg" %}
-
-
-
-
Users can easily upload their device configuration either through a custom user interface (e.g., file upload or input mask) or via the built-in Device Agent UI.
-
-
-
-
-
-
Certification
-
-
After successfully navigating the technical qualification, take the next step by booking a meeting with our team. Together, we'll work towards ensuring your device is fully compatible with FlowFuse and Node-RED.
- FlowFuse reduces the risk of using Node-RED in production. We offer professional support for Node-RED deployments on the crtlX platform. Customers have direct access to Node-RED experts who can help with development and production deployment issues.
-
- The Node-RED package for ctrlX includes pre-installs third party nodes for popular industrial protocols, including OMRON, MC Protocol, Modbus and S7. FlowFuse will support the use of these nodes in production.
-
- Get in touch with us to access expert guidance and comprehensive assistance for your Node-RED deployments. Our team will support you every step of the way, ensuring seamless integration and successful implementation.
-
- CtrlX customers can update their Node-RED deployments to use the FlowFuse platform to take advantage of our device management, team collaboration, software delivery pipelines and other enterprise features. Book a demo to discover the FlowFuse platform.
-
\ No newline at end of file
diff --git a/src/partners/referral-sign-up.njk b/src/partners/referral-sign-up.njk
deleted file mode 100644
index 13a4d6a5cc..0000000000
--- a/src/partners/referral-sign-up.njk
+++ /dev/null
@@ -1,59 +0,0 @@
----
-layout: layouts/page.njk
-title: Introducing the FlowFuse Referral Program
-description: "
Many companies are realizing the benefits of using FlowFuse for
-their Node-RED development. We want to encourage them to recommend FlowFuse to
-other potential users. That's why we're excited to offer a referral program that
-rewards others for spreading the word about our platform.