[{"data":1,"prerenderedAt":178},["ShallowReactive",2],{"application-guide-nav":3,"application-guide-node-red-foundations":101},[4,11,15,21,24,30,35,41,46,52,57,63,68,74,79,85,91,97],{"guide":5,"slug":6,"title":7,"navOrder":8,"blurb":9,"path":10},"flowfuse","overview","Overview",1,"Turn an app idea into FlowFuse pieces you can name and say in one sentence.","\u002Fapplication-guide\u002Fflowfuse\u002Foverview\u002F",{"guide":12,"slug":6,"title":7,"navOrder":8,"blurb":13,"path":14},"node-red","Turn an architecture sentence into a clean flow shape you can read at a glance.","\u002Fapplication-guide\u002Fnode-red\u002Foverview\u002F",{"guide":5,"slug":16,"title":17,"navOrder":18,"blurb":19,"path":20},"foundations","Foundations",2,"The foundation to build on: what FlowFuse is, its core pieces, and how code is shared across teams.","\u002Fapplication-guide\u002Fflowfuse\u002Ffoundations\u002F",{"guide":12,"slug":16,"title":17,"navOrder":18,"blurb":22,"path":23},"The handful of concepts you need to build with Node-RED, and how they fit together.","\u002Fapplication-guide\u002Fnode-red\u002Ffoundations\u002F",{"guide":5,"slug":25,"title":26,"navOrder":27,"blurb":28,"path":29},"app-delivery-methods","App delivery methods",3,"Two different units of code, delivered two ways: ship the whole app, or publish one reusable piece.","\u002Fapplication-guide\u002Fflowfuse\u002Fapp-delivery-methods\u002F",{"guide":12,"slug":31,"title":32,"navOrder":27,"blurb":33,"path":34},"flow-shape","Flow shape","Turn an architecture sentence into a flow you can read at a glance.","\u002Fapplication-guide\u002Fnode-red\u002Fflow-shape\u002F",{"guide":5,"slug":36,"title":37,"navOrder":38,"blurb":39,"path":40},"hardware-apps","Hardware apps",4,"The three shapes a FlowFuse app takes when it runs on a device.","\u002Fapplication-guide\u002Fflowfuse\u002Fhardware-apps\u002F",{"guide":12,"slug":42,"title":43,"navOrder":38,"blurb":44,"path":45},"design-patterns","Design patterns","The moves that turn a flow into something you can reuse, test and hand off.","\u002Fapplication-guide\u002Fnode-red\u002Fdesign-patterns\u002F",{"guide":5,"slug":47,"title":48,"navOrder":49,"blurb":50,"path":51},"software-apps","Software apps",5,"The three shapes a FlowFuse app takes when it runs on the platform.","\u002Fapplication-guide\u002Fflowfuse\u002Fsoftware-apps\u002F",{"guide":12,"slug":53,"title":54,"navOrder":49,"blurb":55,"path":56},"handling-data","Handling data","Sort data by what it is for before you tune anything.","\u002Fapplication-guide\u002Fnode-red\u002Fhandling-data\u002F",{"guide":5,"slug":58,"title":59,"navOrder":60,"blurb":61,"path":62},"data-plane","Data plane",6,"Before you pick where things run, decide how data is handled.","\u002Fapplication-guide\u002Fflowfuse\u002Fdata-plane\u002F",{"guide":12,"slug":64,"title":65,"navOrder":60,"blurb":66,"path":67},"operating-flows","Operating flows","Four operational habits that keep a flow running when the real world pushes back.","\u002Fapplication-guide\u002Fnode-red\u002Foperating-flows\u002F",{"guide":5,"slug":69,"title":70,"navOrder":71,"blurb":72,"path":73},"architectures","Architectures",7,"The same building blocks, arranged for where they run.","\u002Fapplication-guide\u002Fflowfuse\u002Farchitectures\u002F",{"guide":12,"slug":75,"title":76,"navOrder":71,"blurb":77,"path":78},"worked-example","Worked example","The shape rules and patterns applied end to end.","\u002Fapplication-guide\u002Fnode-red\u002Fworked-example\u002F",{"guide":5,"slug":80,"title":81,"navOrder":82,"blurb":83,"path":84},"it-architectures","IT architectures",8,"Hosting the platform and serving the wider organisation.","\u002Fapplication-guide\u002Fflowfuse\u002Fit-architectures\u002F",{"guide":5,"slug":86,"title":87,"navOrder":88,"blurb":89,"path":90},"ot-architectures","OT architectures",9,"How FlowFuse deploys in operational-technology environments, near the equipment.","\u002Fapplication-guide\u002Fflowfuse\u002Fot-architectures\u002F",{"guide":5,"slug":92,"title":93,"navOrder":94,"blurb":95,"path":96},"iiot-architectures","IIoT architectures",10,"Distributed edge nodes, each doing one small job, feeding one central system.","\u002Fapplication-guide\u002Fflowfuse\u002Fiiot-architectures\u002F",{"guide":5,"slug":75,"title":76,"navOrder":98,"blurb":99,"path":100},11,"OEE, end to end — two packages, two connections.","\u002Fapplication-guide\u002Fflowfuse\u002Fworked-example\u002F",{"id":102,"title":17,"blocks":103,"blurb":22,"extension":174,"guide":12,"meta":175,"navOrder":18,"slug":16,"stem":176,"__hash__":177},"applicationGuide\u002Fapplication-guide\u002Fnode-red\u002F02-foundations.yml",[104,108,139,141,167],{"type":105,"kicker":106,"body":107},"prose","Foundations — start here","The handful of concepts you need to build with Node-RED, and how they fit together. You wire pre-built nodes into flows and spend your effort on the logic — what the system should do — while the platform handles the syntax and the connectivity. Learn these and you can build real integrations in Node-RED with only a little JavaScript — the structure carries most of the weight.",{"type":109,"heading":110,"lanes":111,"legend":136},"diagram","How it fits together",[112,127,129],{"label":113,"tone":114,"nodes":115},"Node-RED runtime","neutral",[116,119,122,124],{"title":117,"sub":118},"Message in","http in \u002F inject",{"title":120,"sub":121},"Node","transform",{"title":120,"sub":123},"route",{"title":125,"sub":126},"Sink","no routing",{"link":128},"read \u002F write state",{"label":130,"tone":114,"nodes":131},"Shared state",[132],{"title":133,"sub":134,"tone":135},"Context","shared state","muted",[137],{"label":138,"tone":114},"msg travels the wires",{"type":105,"body":140},"A message enters a flow and passes from node to node, transformed along the way, until it reaches a sink that sends and routes nothing. Reuse comes from subflows and link nodes; shared state lives in context; new capabilities come from installing nodes off the palette.",{"type":142,"heading":143,"columns":18,"items":144},"cards","The core pieces",[145,147,150,153,156,159,161,164],{"title":120,"body":146},"A single processing block: it receives a message, does one thing — read, transform, call, route — and passes it on.",{"title":148,"body":149},"Flow","Nodes wired left-to-right on a tab; a message enters, is transformed, and exits. One working unit of automation.",{"title":151,"body":152},"Message (msg)","The object that travels the wires, carrying msg.payload plus metadata between nodes.",{"title":154,"body":155},"Subflow","A block you define once and drop in many places, with its own inputs, outputs and per-instance config.",{"title":157,"body":158},"Link nodes","link in \u002F link out \u002F link call wire flows together across tabs with no visible wires — your in-process service calls.",{"title":133,"body":160},"Storage that keeps state between messages — flow and global scope, in memory or persisted.",{"title":162,"body":163},"Palette","The library of installable nodes (npm) you add new capabilities from.",{"title":165,"body":166},"Editor & runtime","The browser editor where you wire flows, and the runtime that executes them continuously.",{"type":168,"heading":169,"body":170,"link":171},"note","In the Node-RED docs","That's the working model. For the full glossary — every core term and node type, straight from the Node-RED project — see the official Node-RED documentation instead of a glossary here.",{"label":172,"to":173},"nodered.org\u002Fdocs →","https:\u002F\u002Fnodered.org\u002Fdocs\u002F","yml",{},"application-guide\u002Fnode-red\u002F02-foundations","Sp9QPsZB6k5TyHSs3Vj7TLWINQVx4hUQ_DlA2OIEJh8",1786132521732]