diff --git a/nuxt/assets/css/getting-started.css b/nuxt/assets/css/getting-started.css
new file mode 100644
index 0000000000..ce49532a43
--- /dev/null
+++ b/nuxt/assets/css/getting-started.css
@@ -0,0 +1,232 @@
+/* Shared styles for the /getting-started guide. Imported once by the
+ getting-started layout so every section page is pure content (no per-page
diff --git a/nuxt/components/GsFlow.vue b/nuxt/components/GsFlow.vue
new file mode 100644
index 0000000000..aaedb9237c
--- /dev/null
+++ b/nuxt/components/GsFlow.vue
@@ -0,0 +1,49 @@
+
+
+
+ {{ current.lead }} Ready to build? Start a free trial, or get a guided walkthrough from our team. Find the product that fits how you work, then follow a step-by-step guide to your first application. New to FlowFuse? There's a quick tour of how it all works further down. FlowFuse comes in three products for three jobs. Answer four quick questions and we'll point you to the right one — then take you straight to its get-started guide. Already know? Skip ahead and pick it below. Pick your product and follow the steps to your first running application. Each guide points to the exact starting materials for that path. A five-minute tour of what FlowFuse is and how the pieces fit together — handy before you build, and here whenever you want it. FlowFuse is the industrial application platform — the place you build the applications that actually run your operation. It sits on top of the data and machines you already have, and unlike a closed product, it's open and yours to own. Every FlowFuse application — however big — is assembled from the same six pieces. Learn these and you understand the whole platform. The plant floor, the business systems, and the devices in the field are different worlds — but the same platform and the same building blocks serve all three. That's how one company standardizes on FlowFuse instead of a tool per team. Anyone can connect a PLC to a dashboard once. The reason teams standardize on FlowFuse is what happens next — shipping fast, governing centrally, scaling everywhere, and never getting locked in. Here's every piece working together in one real application: OEE — how much good product a line makes versus its potential — from the machine at the edge to a live dashboard in the cloud. Four pieces, two connections — and you can see how the same pattern powers everything from energy monitoring to full MES. Ready to build? Open FlowFuse and get going. Jump into the platform and start your first application, or bring a use case and we'll walk it through with you.
+
+
+
+
+ Get Started with FlowFuse — Fast
+ Find Your Product
+ Get Started
+ How It All Works
+ What FlowFuse Is
+ Why That's Different
+ The Pieces You Build With
+ The Six Pieces
+ It Fits Every Team
+
+
+ Why It Pays Off
+ See It in Action
+
Leveraging enterprise-grade development, deployment, and governance solutions, you can build faster, scale more efficiently, and secure deployments of any size.
+Every application is assembled from the same core pieces — managed Node-RED instances running in the cloud or at the edge, a built-in Team Broker for your Unified Namespace, shared Tables for operational data, operator dashboards, and fleet-wide device management. The same building blocks arrange into the IT, OT, and IIoT architectures that fit how you run — wherever the work happens.
+