Easy instance management, easily suspend and tear down projects. FlowForge makes keeping track of multiple Node-RED projects a breeze.
FlowForge also provides Single-Sign On to ensure that increased scale, also comes with trusted security.
" -}, { - "icon": "edge_red.png", - "title": "Device Management & Remote Deployment", - "description": "One-click deploy to thousands of devices.
Effortlessly upgrade flows remotely to your edge devices and get an overview of device health and connectivity.
" -}, { - "icon": "collaboration_red.png", - "title": "Advanced Collaboration", - "description": "FlowForge provides intuitive tools to help control access to your Node-RED projects and grow your team without fear of development conflicts.
Team Libraries for your own flows and nodes also make it easy to share code with your team across your Node-RED projects.
" -}, { - "icon": "orchestration_red.png", - "title": "Frictionless Orchestration", - "description": "FlowForge takes away the headache of having to manage your many Node-RED instances.
FlowForge continues to grow and gain further enhancements to assist in your IT and OT integration story.
" -}, { - "icon": "enterprise_red.png", - "title": "Standardized Environments", - "description": "Project Templates accelerate getting started on new flows, with configuration of Node-RED versions and pre-installed third-party nodes.
FlowForge provides stacks for easy upgrading to the latest versions of Node-RED as soon as it's available.
" -}, { - "icon": "time_red.png", - "title": "Reduced Operational Overheads", - "description": "Backed by consistent security across the platform, FlowForge makes hosting, deployment, and management easy.
FlowForge provides centralised audit logging too - bringing you peace of mind and compliance in your production environment
" -}] \ No newline at end of file diff --git a/src/_data/mainFeatures.json b/src/_data/mainFeatures.json new file mode 100644 index 0000000000..342f695a57 --- /dev/null +++ b/src/_data/mainFeatures.json @@ -0,0 +1,56 @@ +[{ + "id": "feature1", + "buttonText": "LOW-CODE NODE-RED", + "buttonTextMobile": "LOW-CODE", + "title": "Low-code Node-RED", + "imageFolder": "./images/features/", + "imageFile": "feature-low-code-nr.png", + "imageAlt": " low-code programming.", + "content": "Node-RED is at the core of the FlowFuse platform. The low-code visually programming environment is the development experience you enjoy when using FlowFuse. This includes having access to the sizeable community of Node-RED nodes for connecting with different protocols, hardware platforms, databases, services, and much more." + }, + { + "id": "feature2", + "buttonText": "Scalable Node-RED", + "buttonTextMobile": "Scalable", + "title": "Scalable and Reliable Node-RED Hosting", + "imageFolder": "./images/features/", + "imageFile": "feature-scalable.png", + "imageAlt": " scalable Node-RED.", + "content": "FlowFuse makes it possible to host Node-RED applications in a reliable and scalable manner.", + "list": [ + "The FlowFuse platform allows for multiple Node-RED applications to be run simultaneously on the platform.", + "Node-RED applications can be run in high availability mode to allow the applications to scale up to meet spikes in demand.", + "High availability mode also allows for failover of application traffic from a failed instance to another Node-RED instance thereby keeping the application running." + ] + }, + { + "id": "feature3", + "buttonText": "DATA SHARING & STORAGE", + "buttonTextMobile": "DATA", + "title": "Data sharing and storage", + "imageFolder": "./images/pictograms/", + "imageFile": "feature-data-sharing.png", + "imageAlt": " data sharing and storage.", + "content": "FlowFuse adds to a Node-RED environment the ability to share information between instances and persistent data, including:", + "list": [ + "Persistent file storage allows Node-RED flows to read and write files from storage. These files can be shared between instances, persist beyond instance restarts and containers.", + "In-memory variables defined in a Node-RED flow can persist across instance restarts and upgrades.", + "New FlowFuse Project Nodes enable the passing of data and messages between your Node-RED projects, ideal for communicating between Node-RED instances deployed at the edge and Node-RED instances deployed in the cloud." + ] + }, + { + "id": "feature4", + "buttonText": "EDGE MANAGEMENT", + "buttonTextMobile": "EDGE", + "title": "Remote device management at the edge", + "imageFolder": "./images/pictograms/", + "imageFile": "edge_red.png", + "imageAlt": " edge management.", + "content": "FlowFuse allows you to deploy and manage Node-RED instances out to edge devices. This allows you to deploy the exact same instance out to hundreds or thousands of edge devices and monitor their status.", + "list": [ + "Easy onboarding of new devices through an administrative UI or an automated process.", + "Management interface to monitor the status of your Node-RED deployment on each device.", + "Consistent deployment of Node-RED instance snapshots out to all of you devices that allow for quick deployment and redeployment of versions of flows.", + "The ability to remotely access the Node-RED editor on remote devices to debug, troubleshoot and correct production errors." + ] + }] \ No newline at end of file diff --git a/src/_data/nodeRed/faqs.json b/src/_data/nodeRed/faqs.json index 3896cebec2..a3583587a1 100644 --- a/src/_data/nodeRed/faqs.json +++ b/src/_data/nodeRed/faqs.json @@ -3,7 +3,7 @@ "answer": "Node-RED is a low-code programming environment that allows developers to connect a wide variety of endpoints, such as industrial PLCs, APIs, databases, enterprise applications and online services.
Users of Node-RED visually drag ānodesā from a palette that represent the end points and then connect them together into flows to accomplish the desired task. Node-RED applications are accessible via a web browser.
" },{ "question": "How do I deploy Node-RED online or in the Cloud?", - "answer": "FlowForge Cloud is a hosted Node-RED service that developers can use to access Node-RED online. This makes it much quicker to get started using Node-RED since you don't need to install it locally" + "answer": "FlowFuse Cloud is a hosted Node-RED service that developers can use to access Node-RED online. This makes it much quicker to get started using Node-RED since you don't need to install it locally" },{ "question": "What is Node-RED used for?", "answer": "Node-RED can be used for a wide variety of use cases, including:
- The manufacturing industry uses Node-RED for collecting data from different pieces of factory equipment.
- Creating dashboards that visualize data and allow for event triggers to occur based on the data.
- Developing chatbot platforms that can collect interactions of a wide variety of social media platforms.
- Extract, transform and integrate data from many different sources in the enterprise.
- Lots of hobbyists use Node-RED for home automation.
- Integrating data with machine learning models
FlowForge Cloud offers the easiest way to get started with Node-RED. After signing into FlowForge Cloud users have immediate access to a Node-RED instance.
For those who prefer to install Node-RED themselves, there are many tutorials that help people to get started with Node-RED. A recommended starting point is the Getting Started found on nodered.org. Other tutorials from the community include Steveās Node-RED Guide and Raspberry Pi Getting Started with Node-RED.
" + "answer": "FlowFuse Cloud offers the easiest way to get started with Node-RED. After signing into FlowFuse Cloud users have immediate access to a Node-RED instance.
For those who prefer to install Node-RED themselves, there are many tutorials that help people to get started with Node-RED. A recommended starting point is the Getting Started found on nodered.org. Other tutorials from the community include Steveās Node-RED Guide and Raspberry Pi Getting Started with Node-RED.
" },{ "question": "What port number does Node-RED use?", "answer": "Node-RED is accessed via port 1880. You can access the Node-RED editor running locally at http://localhost:1880 or on another computer at http://domain name:1880." @@ -24,5 +24,5 @@ "answer": "There are three aspects of Node-RED that need to be secured.
- Node-RED is a web application so you need to enable HTTPS access to the Node-RED runtime. The default Node-RED settings include a commented out section that can be used for local certificates.
- The Node-RED editor and administration requires authentication to access it. Node-RED supports username/password and OAuth/OpenID authentication. The adminAuth property in the setting file is used to specify the authentication credentials.
- Securing the HTTP Node can be done using basic authentication. This can be set using the httpNodeAuth property in the settings file.
You can also follow our guide on how to secure Node-RED." },{ "question": "How is Node-RED used in IoT?", - "answer": "
Node-RED is very popular in the manufacturing and industrial automation industries (IIoT) as an edge computing solution. Often deployed on PLCs and IoT gateways, Node-RED supports collecting data from legacy and proprietary systems (Siemens S7, Modbus, OPC-UA, etc), integrating the industrial data with other data sources (weather data, enterprise data), filtering data on the edge, and then sending the data to the cloud. FlowForge offers remote device deployment to IIoT edge devices.
Node-RED is also very popular with DIY home automation enthusiasts, in particular the Home Assistant community." + "answer": "
Node-RED is very popular in the manufacturing and industrial automation industries (IIoT) as an edge computing solution. Often deployed on PLCs and IoT gateways, Node-RED supports collecting data from legacy and proprietary systems (Siemens S7, Modbus, OPC-UA, etc), integrating the industrial data with other data sources (weather data, enterprise data), filtering data on the edge, and then sending the data to the cloud. FlowFuse offers remote device deployment to IIoT edge devices.
Node-RED is also very popular with DIY home automation enthusiasts, in particular the Home Assistant community." }] diff --git a/src/_data/site.json b/src/_data/site.json index 9177319663..0c6d1d0116 100644 --- a/src/_data/site.json +++ b/src/_data/site.json @@ -1,9 +1,10 @@ { - "title": "FlowForge", + "title": "FlowFuse", "baseURL": "https://flowforge.com", - "jobBoard": "https://boards.greenhouse.io/flowforge", + "jobBoard": "https://boards.greenhouse.io/flowfuse", "openings": { - "sales": "https://boards.greenhouse.io/flowforge/jobs/4843566004", - "devadvocate": "https://boards.greenhouse.io/flowforge/jobs/4843566004" + "sales": "https://boards.greenhouse.io/flowfuse/jobs/4843566004", + "devadvocate": "https://boards.greenhouse.io/flowfuse/jobs/4843566004", + "frontenddash": "https://boards.greenhouse.io/flowfuse/jobs/4911532004" } } diff --git a/src/_data/team/marian-demme.json b/src/_data/team/marian-demme.json index 404640d369..0a77bf6d80 100644 --- a/src/_data/team/marian-demme.json +++ b/src/_data/team/marian-demme.json @@ -6,11 +6,11 @@ "github": "MarianRaphael", "linkedin": "marian-demme", "country": "DE", - "email": "marian@flowforge.com", + "email": "marian@flowfuse.com", "headshot": "marian.png", "facts": [ "IIoT connoisseur: with countless assembly lines and factories explored, reveling in digitalizing and transforming them.", "Two-wheeled adventurer: has pedaled through scenic routes from Berlin to Copenhagen, from Munich to Venice, and beyond.", - "Chasing new hobbies: the love for Node-RED turned into a professional adventure at FlowForge." + "Chasing new hobbies: the love for Node-RED turned into a professional adventure at FlowFuse." ] } \ No newline at end of file diff --git a/src/_data/team/piotr-pawlowski.json b/src/_data/team/piotr-pawlowski.json new file mode 100644 index 0000000000..59b82b6781 --- /dev/null +++ b/src/_data/team/piotr-pawlowski.json @@ -0,0 +1,14 @@ +{ + "order": 13, + "name": "Piotr Pawlowski", + "title": "DevOps Engineer", + "github": "ppawlowski", + "country": "PL", + "email": "piotr@flowfuse.com", + "headshot": "piotr.png", + "facts": [ + "DevOps/Cloud Engineer with 10+ years of experience and solid background in Linux/Unix administration", + "Huge automation enthusiast, automate all the boring stuff around me", + "Dog lover, owner of Figa - 4 year old female beagle" + ] +} \ No newline at end of file diff --git a/src/_data/team/richard-meyer.json b/src/_data/team/richard-meyer.json deleted file mode 100644 index 519a8d6d98..0000000000 --- a/src/_data/team/richard-meyer.json +++ /dev/null @@ -1,15 +0,0 @@ -{ - "order": 12, - "name": "Richard Meyer", - "title": "Developer Advocate", - "github": "Hisma", - "linkedin": "richard-meyer-5b606122", - "country": "USA", - "email": "richard@flowforge.com", - "headshot": "richard.png", - "facts": [ - "15 years of industrial automation with experience in turnkey project engineering, functional safety, commissioning, and R&D", - "US Navy Veteran, ODU Alum with BSc in Electromechanical Engineering Technology", - "Lived in 4 different countries to quench my insatiable thirst for adventure. If not traveling, I'm obsessively tinkering with computers and electronics" - ] -} \ No newline at end of file diff --git a/src/_data/team/rob-marcer.json b/src/_data/team/rob-marcer.json index d8120a2840..4515323a91 100644 --- a/src/_data/team/rob-marcer.json +++ b/src/_data/team/rob-marcer.json @@ -4,7 +4,7 @@ "title": "Customer Success Manager", "github": "robmarcer", "linkedin": "rob-marcer-b414b910", - "email": "rob@flowforge.com", + "email": "rob@flowfuse.com", "country": "GB", "headshot": "rob.png", "facts": [ diff --git a/src/_data/team/tracy-anthony.json b/src/_data/team/tracy-anthony.json index 1e8fafba55..9e40a16477 100644 --- a/src/_data/team/tracy-anthony.json +++ b/src/_data/team/tracy-anthony.json @@ -5,7 +5,7 @@ "github": "Tracy-Anthony", "linkedin": "tracyanthonyfernandez", "country": "IN", - "email": "tracy@flowforge.com", + "email": "tracy@flowfuse.com", "headshot": "tracy.png", "facts": [ "Almost a decade of experience with all things People, Talent Acquisition and Operations", diff --git a/src/_data/team/yndira-escobar.json b/src/_data/team/yndira-escobar.json index 017c49a666..46fb743ba9 100644 --- a/src/_data/team/yndira-escobar.json +++ b/src/_data/team/yndira-escobar.json @@ -5,7 +5,7 @@ "github": "Yndira-FlowForge", "linkedin": "yndira-escobar-es", "country": "ES", - "email": "yndira@flowforge.com", + "email": "yndira@flowfuse.com", "headshot": "yndira.png", "facts": [ "Over 15 years of experience in graphic design and art direction", diff --git a/src/_data/team/zack-wasli.json b/src/_data/team/zack-wasli.json new file mode 100644 index 0000000000..fcb1d1db0f --- /dev/null +++ b/src/_data/team/zack-wasli.json @@ -0,0 +1,15 @@ +{ + "order": 14, + "name": "Zack Wasli", + "title": "Account Executive", + "github": "zackwasli", + "linkedin": "zack-wasli", + "country": "USA", + "email": "zack@flowfuse.com", + "headshot": "zack.png", + "facts": [ + "5+ years selling open-source software, from SDR to Enterprise", + "Digital nomad", + "Love outdoor sports and getting off-grid" + ] +} \ No newline at end of file diff --git a/src/_data/team/zeger-jan-van-de-weg.json b/src/_data/team/zeger-jan-van-de-weg.json index 151fa1bef6..0e7e155e5c 100644 --- a/src/_data/team/zeger-jan-van-de-weg.json +++ b/src/_data/team/zeger-jan-van-de-weg.json @@ -7,7 +7,7 @@ "linkedin": "zegerjan", "blog": "https://www.zjvandeweg.nl", "country": "NL", - "email": "zj@flowforge.com", + "email": "zj@flowfuse.com", "headshot": "zj.png", "facts": [ "Early GitLab employee, still knows too much about Git for his own good", diff --git a/src/_includes/blog/template.njk b/src/_includes/blog/template.njk index 419bd13761..8f50396899 100644 --- a/src/_includes/blog/template.njk +++ b/src/_includes/blog/template.njk @@ -1,11 +1,11 @@ -
+
-
-
@@ -180,33 +121,4 @@ date: git Last Modified
})
-
-
-
-
-
-{% initClipboardJS %}
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
+{% include "./common-js.njk" %}
\ No newline at end of file
diff --git a/src/_includes/layouts/left-nav.njk b/src/_includes/layouts/left-nav.njk
new file mode 100644
index 0000000000..c87c304719
--- /dev/null
+++ b/src/_includes/layouts/left-nav.njk
@@ -0,0 +1,66 @@
+
+
Blog
{% include "components/divider-grey-wires-right.njk" %}
+
+
{{ content | safe }}
@@ -234,21 +214,21 @@
{%- for tag in blogTags -%}
{% if tag.value !== "posts" %}
diff --git a/src/_includes/components/dividers/divider-flow--top-grey.svg b/src/_includes/components/dividers/divider-flow--top-grey.svg
new file mode 100644
index 0000000000..5440c54f1e
--- /dev/null
+++ b/src/_includes/components/dividers/divider-flow--top-grey.svg
@@ -0,0 +1,3 @@
+
\ No newline at end of file
diff --git a/src/_includes/components/events-banner.njk b/src/_includes/components/events-banner.njk
index 7d458e5af9..b946f63b43 100644
--- a/src/_includes/components/events-banner.njk
+++ b/src/_includes/components/events-banner.njk
@@ -2,15 +2,11 @@
-
- Join our Webinar
- -
-
-Building Node-RED Applications for Scalability and High Availability
-
+ FlowForge is now FlowFuse
-
- Register Today {% include "components/icons/chevron-right-sm.svg" %}
+ Check out the story {% include "components/icons/chevron-right-sm.svg" %}
\ No newline at end of file
diff --git a/src/_includes/components/flowforge-logo.njk b/src/_includes/components/flowforge-logo.njk
deleted file mode 100644
index 0a7d6ed294..0000000000
--- a/src/_includes/components/flowforge-logo.njk
+++ /dev/null
@@ -1,6 +0,0 @@
-
-
diff --git a/src/_includes/components/flowforge-square.svg b/src/_includes/components/flowforge-square.svg
deleted file mode 100644
index ea6f7258cb..0000000000
--- a/src/_includes/components/flowforge-square.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/src/_includes/components/flowforge-wordmark.njk b/src/_includes/components/flowforge-wordmark.njk
deleted file mode 100644
index 957513473c..0000000000
--- a/src/_includes/components/flowforge-wordmark.njk
+++ /dev/null
@@ -1,8 +0,0 @@
-
-
-
diff --git a/src/_includes/components/flowforge-wordmark.svg b/src/_includes/components/flowforge-wordmark.svg
deleted file mode 100644
index b8d43028c4..0000000000
--- a/src/_includes/components/flowforge-wordmark.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/src/_includes/components/flowforge.njk b/src/_includes/components/flowforge.njk
deleted file mode 100644
index ff99141464..0000000000
--- a/src/_includes/components/flowforge.njk
+++ /dev/null
@@ -1,5 +0,0 @@
-
diff --git a/src/_includes/components/flowfuse-logo--wordmark--dark.svg b/src/_includes/components/flowfuse-logo--wordmark--dark.svg
new file mode 100644
index 0000000000..2204b72b8a
--- /dev/null
+++ b/src/_includes/components/flowfuse-logo--wordmark--dark.svg
@@ -0,0 +1,5 @@
+
diff --git a/src/_includes/components/flowfuse-square.svg b/src/_includes/components/flowfuse-square.svg
new file mode 100644
index 0000000000..f117e04e8b
--- /dev/null
+++ b/src/_includes/components/flowfuse-square.svg
@@ -0,0 +1,2 @@
+
\ No newline at end of file
diff --git a/src/_includes/components/flowfuse-wordmark.njk b/src/_includes/components/flowfuse-wordmark.njk
new file mode 100644
index 0000000000..4f8077804f
--- /dev/null
+++ b/src/_includes/components/flowfuse-wordmark.njk
@@ -0,0 +1,7 @@
+
+
+
diff --git a/src/_includes/components/icons/arrow-small-down.svg b/src/_includes/components/icons/arrow-small-down.svg
new file mode 100644
index 0000000000..fd464d8a19
--- /dev/null
+++ b/src/_includes/components/icons/arrow-small-down.svg
@@ -0,0 +1,3 @@
+
\ No newline at end of file
diff --git a/src/_includes/components/icons/arrow-top-right-on-square.svg b/src/_includes/components/icons/arrow-top-right-on-square.svg
index afefe86171..ea9f0bc1ad 100644
--- a/src/_includes/components/icons/arrow-top-right-on-square.svg
+++ b/src/_includes/components/icons/arrow-top-right-on-square.svg
@@ -1,3 +1,3 @@
-
-
- {% image "./images/flowforge-logo-wordmark-white.svg", "FlowForge Logo in White", [150] %}
+ {% image "./images/flowfuse-logo-wordmark-white.svg", "FlowFuse Logo in White", [150] %}
Copyright 2023 FlowForge Inc.
All Rights Reserved
This site uses cookies. Click here to manage your preferences.
+ This site uses cookies. Click here to manage your preferences.
Social
diff --git a/src/_includes/layouts/common-js.njk b/src/_includes/layouts/common-js.njk new file mode 100644 index 0000000000..e46b234c74 --- /dev/null +++ b/src/_includes/layouts/common-js.njk @@ -0,0 +1,29 @@ + + + + + + +{% initClipboardJS %} + + + + + + + + diff --git a/src/_includes/layouts/handbook.njk b/src/_includes/layouts/handbook.njk index ac29ddce84..6014d044a6 100644 --- a/src/_includes/layouts/handbook.njk +++ b/src/_includes/layouts/handbook.njk @@ -19,71 +19,9 @@ date: git Last Modified } -
-
-
-
-
+-
-
- - {{ nav }} - - {# {{ collections.nav.handbook.children | console | safe }} #} - {% for group in collections.nav[nav].groups %} - {% if group.children.length > 0 %} -
- {{ group.name }} - {% for entry in group.children %} -
- - - {{ entry.name }} - - {% if entry.children %} - - {% endif %} - - {% if entry.children %} -
- - - {{ child.name }} - - {% if child.children %} - - {% endif %} - - {% if child.children %} -
- - - {{ grandchild.name }} - - - {% endfor %} -
-
- {% for child in entry.children %}
-
-
- {% for grandchild in child.children %}
-
+ {% include "./left-nav.njk" %}
+
+
@@ -125,7 +66,7 @@ date: git Last Modified
{% renderTeamMember maintainer %}
{%- endfor -%}
-
@@ -91,9 +29,12 @@ date: git Last Modified
{% if version %}
v{{ version }}
{% endif %}
- {{ page.filePathStem | handbookBreadcrumbs |safe }}
+ {{ page.url | handbookBreadcrumbs | safe }}
+
+
@@ -110,7 +51,7 @@ date: git Last Modified
{% if version %}
v{{ version }}
{% endif %}
- {{ page.filePathStem | handbookBreadcrumbs | safe }}
+ {{ page.url | handbookBreadcrumbs | safe }}
Updated: {{ page.date }}
+ Updated: {% filter shortDate %}{{ updated if updated else page.date }}{% endfilter %}
+
\ No newline at end of file
diff --git a/src/_includes/layouts/node-docs.njk b/src/_includes/layouts/node-docs.njk
new file mode 100644
index 0000000000..fc5efa2ec2
--- /dev/null
+++ b/src/_includes/layouts/node-docs.njk
@@ -0,0 +1,72 @@
+---
+layout: nohero
+date: git Last Modified
+---
+
+
+-
+ {% set path = (["node-red/", nav] | join) if nav == "core-nodes" else nav %}
+
+
- + {{ nav }} + + {% for group in collections + .nav[nav] + .groups %} + {% if group.children.length > 0 %} +
- {{ group.name }} + {% for entry in group.children %} +
- + + {{ entry.name }} + + {% if entry.children %} + + {% endif %} + + {% if entry.children %} +
- + + {{ child.name }} + + {% if child.children %} + + {% endif %} + + {% if child.children %} +
- + + {{ grandchild.name }} + + + {% endfor %} +
-
+ {% for child in entry.children %}
+
-
+ {% for grandchild in child.children %}
+
+ {% include "./left-nav.njk" %}
+
+
+
+{% include "./common-js.njk" %}
\ No newline at end of file
diff --git a/src/_includes/layouts/nohero.njk b/src/_includes/layouts/nohero.njk
index 8da84c0efc..69805cf1f6 100644
--- a/src/_includes/layouts/nohero.njk
+++ b/src/_includes/layouts/nohero.njk
@@ -2,6 +2,6 @@
layout: layouts/page.njk
nohero: true
---
-
+
+
+
+
+
+ {% if version %}
+ v{{ version }}
+ {% endif %}
+ {{ page.url | handbookBreadcrumbs | safe }}
+
+
+
+
+
+
+
+
+
+
+ {{ content | rewriteHandbookLinks(page) | safe }}
+
+
+
+
+
+
+
+
+ {% if version %}
+ v{{ version }}
+ {% endif %}
+ {{ page.url | handbookBreadcrumbs | safe }}
+
+
+ {%- for maintainer in page | pageOwners | ghUsersToTeamMembers(team) -%}
+ {%- if loop.first -%}
+
+ Page maintainer
+ {%- endif -%} + + {% renderTeamMember maintainer %} + {%- endfor -%} + +Updated: {{ page.date | shortDate }}
+
+
{{ content | safe }}
diff --git a/src/_includes/layouts/page.njk b/src/_includes/layouts/page.njk
index af8b9ea8d6..aa393b20b4 100644
--- a/src/_includes/layouts/page.njk
+++ b/src/_includes/layouts/page.njk
@@ -2,10 +2,11 @@
layout: layouts/base.njk
---
-
+
{% if title %}
+
{% if nohero %}
-
+
@@ -27,12 +28,15 @@ layout: layouts/base.njk
{% endif %}
{% else %}
-
{{ title }}
+
{% endif %}
+
{% endif %}
{{ title }}
+{{ subtitle | safe }}
+{{ description | safe }}
{{ content | safe }}
diff --git a/src/_includes/layouts/post.njk b/src/_includes/layouts/post.njk
index 478a4ebcfc..5a6bae8da4 100644
--- a/src/_includes/layouts/post.njk
+++ b/src/_includes/layouts/post.njk
@@ -43,7 +43,7 @@ layout: layouts/base.njk
diff --git a/src/careers.njk b/src/careers.njk
index 3b0db9e005..3d86eefbd7 100644
--- a/src/careers.njk
+++ b/src/careers.njk
@@ -1,7 +1,7 @@
---
layout: "nohero"
title: Careers
-description: Check out our openings at FlowForge and join the team reliably delivering Node-RED applications in a continuous, collaborative, and secure manner.
+description: Check out our openings at FlowFuse and join the team reliably delivering Node-RED applications in a continuous, collaborative, and secure manner.
sitemapPriority: 0.8
skipIndex: true
image: /images/careers/hiring.jpeg
diff --git a/src/community/newsletter.njk b/src/community/newsletter.njk
index 987c483f60..c4fdc7a845 100644
--- a/src/community/newsletter.njk
+++ b/src/community/newsletter.njk
@@ -3,7 +3,7 @@ layout: nohero
sitemapPriority: 0.9
---
-
+
Newsletter
diff --git a/src/contact-us.njk b/src/contact-us.njk
index 2d5b0e6a40..06757fcdcd 100644
--- a/src/contact-us.njk
+++ b/src/contact-us.njk
@@ -3,7 +3,7 @@ layout: layouts/nohero.njk
title: Contact us
sitemapPriority: 0.8
meta:
- description: Get in touch with FlowForge
+ description: Get in touch with FlowFuse
---
diff --git a/src/css/algolia-theme.css b/src/css/algolia-theme.css
index 97b592a9f2..490ef6950f 100644
--- a/src/css/algolia-theme.css
+++ b/src/css/algolia-theme.css
@@ -1,5 +1,4 @@
#algolia-search {
- @apply sticky top-0;
--aa-search-input-height: 42px;
--aa-input-border-color-rgb: none;
--aa-spacing: 12px;
diff --git a/src/css/roadmap.css b/src/css/roadmap.css
index 90256007d5..05ede566a2 100644
--- a/src/css/roadmap.css
+++ b/src/css/roadmap.css
@@ -5,7 +5,6 @@
.left {
display: flex;
justify-content: left;
- width: 100%;
}
.left-headline {
@@ -38,10 +37,9 @@
.reaction-count {
align-items: center;
- color: #9ca3af;
display: flex;
margin-left: 8px;
- margin-right: 8px;
+ font-weight: bold;
}
.roadmap-feedback {
@@ -53,23 +51,46 @@
}
.roadmap-item {
- align-items: flex-start;
border-top: 1px solid #e5e7ed;
+ min-height: 88px;
+ align-items: center;
display: flex;
- flex-direction: column;
- margin-bottom: 8px;
- padding: 16px 0;
+ flex-grow: 1;
}
-.roadmap-item-container {
+.roadmap-item a {
+ align-items: center;
display: flex;
+ flex-direction: row;
+ justify-content: space-between;
+ padding: 16px 1.5rem;
+ width: 100%;
+ height: 100%;
flex-grow: 1;
+ font-weight: 400;
+ color: theme(colors.gray.500);
+}
+
+.roadmap-item a:hover {
+ text-decoration: none;
+ background-color: theme(colors.gray.100);
+ color: theme(colors.gray.800);
+}
+
+.roadmap-item-container {
+ display: flex;
+ /* flex-grow: 1; */
+ width: 100%;
+}
+
+.roadmap-item-container ul {
+ width: 100%;
+ display: flex;
+ flex-direction: column;
}
.roadmap-item-text {
- color: #374151;
flex-grow: 1;
- font-weight: bold;
text-align: left;
}
@@ -82,44 +103,28 @@
align-items: flex-start;
display: flex;
flex-direction: column;
- justify-content: space-between;
+}
+
+.roadmap-section h4 {
+ color: white;
}
.title-number-container {
align-items: center;
display: flex;
- margin-bottom: 16px;
}
.vote-btn {
align-items: center;
- background-color: #E4E7E0;
- border-radius: 8px;
- color: #000;
display: flex;
- font-weight: bold;
justify-content: center;
- padding: 8px 16px;
+ padding: 12px 0px 12px 4px;
text-decoration: none;
transition: 0.3s;
}
-.vote-btn a {
- color: #000;
-}
-
-.vote-btn:hover {
- background-color: #c9ccc6;
- text-decoration: none;
-}
-
.vote-btn img {
height: 16px;
margin-right: 4px;
width: 16px;
-}
-
-.vote-btn span {
- color: #000;
- margin-right: 4px;
-}
+}
\ No newline at end of file
diff --git a/src/css/style.css b/src/css/style.css
index 4dcc0461e0..ae673c583d 100644
--- a/src/css/style.css
+++ b/src/css/style.css
@@ -23,7 +23,7 @@ html, body {
}
/*
- Standard FlowForge Sizings
+ Standard FlowFuse Sizings
*/
h1 {
font-size: 2.25rem;
@@ -94,14 +94,40 @@ h1, h2, h3, h4, h5, p {
background-color: theme(colors.gray.800);
}
-.base {
- background-color: theme(colors.gray.800);
- background-image: url('/images/ff-cloud_50.svg');
- background-repeat: no-repeat;
+.ff-bg-flows {
+ background-image: url('/images/ff-bg-flows.svg');
+ background-repeat: repeat-x;
background-position-x: 50%;
- background-position-y: 150px;
+ background-position-y: calc(100% + 50px);
background-size: contain;
}
+
+.hero .ff-bg-flows {
+ background-size: 100%;
+ background-position-y: calc(100% + 100px);
+}
+
+@media (max-width: 1250px) {
+ .ff-bg-flows {
+ background-size: 100%;
+ background-position-y: bottom;
+ }
+ .hero .ff-bg-flows {
+ background-size: 100%;
+ background-position-y: calc(100% + 25px);
+ }
+}
+
+.gradient-bg {
+ background: radial-gradient(circle 50vw at center 500px,theme(colors.gray.700),transparent);
+ background-size: 100vw;
+}
+
+.pricing .gradient-bg {
+ background: radial-gradient(circle 50vw at center -100px,rgba(55, 65, 81, 0.2),theme(colors.gray.800));
+ background-size: 100vw;
+}
+
main a {
color: theme(colors.teal.300);
}
@@ -134,6 +160,49 @@ pre code {
padding-right: 0.25rem;
}
+.nodered table {
+ text-align: center;
+}
+
+dl.message-properties {
+ border-radius: 2px;
+ /* margin: 5px auto 10px; */
+ }
+
+ dl.message-properties > dt {
+ padding: 0px 6px 2px 6px;
+ font-family: ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,"Liberation Mono","Courier New",monospace;
+ font-size: 0.875em;
+ font-weight: 500;
+ margin: 5px 3px 1px;
+ color: theme(colors.red.600);
+ white-space: nowrap;
+ background-color: theme(colors.gray.100);
+ }
+
+ dl.message-properties > dt.optional {
+ font-style: italic;
+ }
+
+ dl.message-properties > dt .property-type {
+ color: theme(colors.gray.400);
+ font-style: italic;
+ font-size: 11px;
+ float: right;
+ padding-top: 4px;
+ }
+
+ dl.message-properties > dt:after {
+ content: "";
+ display: table;
+ clear: both;
+ }
+
+ dl.message-properties > dd {
+ margin: 0px 8px 12px 13px;
+ vertical-align: top;
+ }
+
/*
Blog
*/
@@ -551,6 +620,39 @@ h4:hover .header-anchor {
}
}
+.red-gradient {
+ background: linear-gradient(127.44deg, #C63A3A 32.29%, #3A2828 100%);
+ -webkit-background-clip: text;
+ -webkit-text-fill-color: transparent;
+ background-clip: text;
+ text-fill-color: transparent;
+}
+
+.features-card{
+ @apply flex flex-wrap flex-col justify-between h-full bg-gray-50 rounded-3xl px-5 pb-5;
+}
+
+.feature-button {
+ background-color: none;
+ color: theme(colors.gray.800);
+ text-transform: uppercase;
+ display: inline-block;
+ padding: 8px 12px;
+ font-weight: 600;
+}
+
+.feature-button.active {
+ background-color: theme(colors.blue.800);
+ color: white;
+}
+
+.feature {
+ display: none;
+ }
+
+ .feature.active {
+ display: block;
+ }
/*
Footer
*/
@@ -1070,7 +1172,7 @@ pre.mermaid {
background-color: #ffffff
}
/*
- FlowForge markdown-it rendered footnote styles
+ FlowFuse markdown-it rendered footnote styles
*/
div.content hr.footnotes-sep {
margin-top: 3em;
@@ -1092,6 +1194,14 @@ div.content section.footnotes ol li p {
background-position-y: bottom;
}
+.features-bg {
+ background-image: url('../images/features/features-bg.png');
+ background-size: cover;
+ background-repeat: no-repeat;
+ background-position-y: bottom;
+ background-position-x: center;
+}
+
/*
Overwrite HubSpot Z Index
*/
diff --git a/src/css/style.handbook.css b/src/css/style.handbook.css
index 9b3fef0429..0c4aab9db8 100644
--- a/src/css/style.handbook.css
+++ b/src/css/style.handbook.css
@@ -17,11 +17,10 @@
--nav-bg: theme(colors.gray.50);
--nav-pl: 1rem;
background-color: theme(colors.gray.50);
- padding-left: 0.5rem;
padding-top: 0.25rem;
max-height: calc(100vh - 1.5rem);
overflow-y: auto;
- @apply sticky top-12;
+ @apply sticky top-12 pl-2 sm:pl-6 xl:pl-0;
}
.handbook-nav-nested {
diff --git a/src/css/style.page.css b/src/css/style.page.css
index 0f4b7c6e8a..334e494f55 100644
--- a/src/css/style.page.css
+++ b/src/css/style.page.css
@@ -83,6 +83,18 @@
padding: 0 24px;
}
+.about-team h4 {
+ color: theme(colors.gray.800);
+}
+
+.about-team a:hover,
+.about-team h4:hover,
+.about-team path:hover {
+ color: theme(colors.blue.600);
+ text-decoration: none;
+ --tdur: 0;
+}
+
/*
PRODUCT
*/
@@ -164,7 +176,6 @@
position: relative;
grid-template-columns: 1fr 1fr 1fr;
gap: 30px;
- z-index: 2;
margin-left: auto;
margin-right: auto;
}
@@ -317,6 +328,54 @@
margin-bottom: 3rem;
@apply px-2 md:px-0
}
+
+ .about-values .company-value {
+ display: flex;
+ align-items: center;
+ margin-bottom: 2rem;
+ @apply w-1/2 md:w-1/3 gap-y-3 justify-start md:justify-center px-6 flex-col md:flex-row;
+ }
+
+ .about-values .company-value img {
+ width: 60px;
+ min-width: 60px;
+ }
+
+ .about-values .company-value h5 {
+ color: theme(colors.teal.300);
+ font-weight: 500;
+ margin-top: 0;
+ margin-bottom: 0;
+ font-size: 1.2rem;
+ line-height: 1.3rem;
+ @apply px-2 md:px-0 text-center md:text-left md:ml-4;
+ }
+}
+
+/* INVESTORS */
+
+@layer components {
+ .investors {
+ display: flex;
+ flex-direction:row;
+ flex-wrap: wrap;
+ align-items: center;
+ justify-content: space-between;
+ @apply md:px-3;
+ }
+
+ .investors .logos {
+ display: flex;
+ flex-direction: row;
+ flex-wrap: nowrap;
+ margin-bottom: 10px;
+ align-items: center;
+ @apply gap-3 w-full justify-center gap-6 md:gap-0 md:justify-between;
+ }
+
+ .investors img {
+ @apply px-3 max-h-[48px] md:max-h-[41px];
+ }
}
/* MEET THE TEAM */
diff --git a/src/customer-stories.njk b/src/customer-stories.njk
index 2152fc1b20..ed057485e3 100644
--- a/src/customer-stories.njk
+++ b/src/customer-stories.njk
@@ -4,7 +4,7 @@ sitemapPriority: 0.8
meta:
title: Customer Stories
---
-
+
diff --git a/src/customer-stories/manufacturing-digital-transformation.md b/src/customer-stories/manufacturing-digital-transformation.md
index deb1217255..1662c172f8 100644
--- a/src/customer-stories/manufacturing-digital-transformation.md
+++ b/src/customer-stories/manufacturing-digital-transformation.md
@@ -8,10 +8,10 @@ story:
url:
quote: Overall, the project leader sees Node-RED as the future of software development. The low code paradigm makes it possible for companies to decentralize innovation within an organization
challenge: Maintain and track the thousands of Node-RED developed instances and versions of these instances.
- solution: Using the FlowForge platform to address these challenges.
+ solution: Using the FlowFuse platform to address these challenges.
results:
- Managing the deployment of Node-RED instances out to thousands of remote devices and maintain multiple versions of the instances.
- - Using FlowForge delivery pipelines and collaboration tools to improve the reliability and efficiency of their development processes.
+ - Using FlowFuse delivery pipelines and collaboration tools to improve the reliability and efficiency of their development processes.
---
A **large US based manufacturing company is using Node-RED** to enable the digital transformation of their entire manufacturing operations. The company has a global footprint with dozens of different locations and over ten thousand employees.
@@ -30,6 +30,6 @@ According to the Node-RED project leader **the key benefit of using Node-RED for
Some limitations they have noticed of Node-RED is the ability to orchestrate software delivery pipelines, version control and tools for teams of developers. It has become very difficult to maintain and track the thousands of Node-RED instances and versions of these instances that they have developed.
-The company is using the FlowForge platform to address these challenges. **They are using FlowForge to manage the deployment of Node-RED instances out to thousands of remote devices and maintain multiple versions of the instances**. In addition, they use FlowForge delivery pipelines and collaboration tools to improve the reliability and efficiency of their development processes.
+The company is using the FlowFuse platform to address these challenges. **They are using FlowFuse to manage the deployment of Node-RED instances out to thousands of remote devices and maintain multiple versions of the instances**. In addition, they use FlowFuse delivery pipelines and collaboration tools to improve the reliability and efficiency of their development processes.
Overall, **the project leader sees Node-RED as the future of software development**. The low code paradigm makes it possible for companies to decentralize innovation within an organization. Allowing subject matter experts to build digital systems that drive innovation.
diff --git a/src/features.njk b/src/features.njk
index 6fd5bd7f45..fedb408542 100644
--- a/src/features.njk
+++ b/src/features.njk
@@ -1,76 +1,172 @@
---
-title: Features
-layout: layouts/page.njk
-description:
Customer Stories
From device management to running Node-RED at scale, FlowForge reduces operational overheads for running your integration infrastructure.
FlowForge is an open-source platform for managing IT and OT integration at scale.
-heroimg: "./images/features.png" -heroWide: true -sitemapPriority: 0.9 +layout: page +nohero: true meta: - description: Explore the features available in the FlowForge platform. + title: FlowFuse Features +description: + FlowFuse provides the features companies require to reliably deliver Node-RED applications to devices and cloud in a collaborative, secure manner. +sitemapPriority: 0.8 --- -
- {% include "components/divider-flow--default.njk" %}
-
-
-
-
-
-
Enterprise Ready Node-RED
-If you're interested in what we are working on, or what may come soon,
check out our Development Board and our Product Roadmap.
+
+
+
+
-
-
+
+ {% include "feature_lists/main-features.njk" %}
+ FlowFuse Features +
++ FlowFuse provides the features companies require to reliably deliver Node-RED applications to devices and cloud in a collaborative, secure manner. +
+
- {%- for f in features -%}
-
-
-
-{% include "components/divider-flow--top-red--dark.njk" %}
+
- {% set imageSrc = ["./images/pictograms/", f.icon] | join %}
- {% set imageDescription = ["Icon depicting", description] | join %}
- {% image imageSrc, imageDescription, [64] %}
+
+
+ {% include "components/divider-flow--top-red--light.njk" %}
+
+
+
-
+
+
- {%- endfor -%}
+
+
+
+
+
+ Software Delivery Pipelines and Version History
+
+
+ + FlowFuse allows software development teams to establish software delivery pipelines that are common for teams that have embraced DevOps practices.Ā +
+-
+
- DevOps pipelines can be set up to stage Node-RED instances that have different development stages, ex. Test, development and production. +
- Snapshots of Node-RED instances can be taken to create a version history of the development work. Previous snapshot versions can be rolled back at any time. +
+
-
+
- {{ f.title }}
{{ f.description | safe }}
+ {% include "components/dividers/light-grey-curve.svg" %}
+
-
-
-
-
- Benefits of FlowForge
-Get started with FlowForge Cloud, or install FlowForge for free on your own infrastructure.
-
-
- {% image "./images/pictograms/time.png", "Graphic of a clock, depicting 'Time'.", [128] %}
-
- One-Minute Setup
-
- {% image "./images/pictograms/security.png", "Graphic of a padlock, depicting 'Security'.", [128] %}
-
- Enterprise Ready
-
- {% image "./images/pictograms/ticket.png", "Graphic of a ticket, depicting 'Ticket-Based Support'.", [128] %}
-
- Ticket-Based Support
-
- {% image "./images/pictograms/community.png", "Graphic depicting 'Flexibility'.", [128] %}
-
Flexible Deployment
+
+ ` - for short thank you messages
@@ -146,7 +150,7 @@ All feedback is then sent directly to the relevant user via the Slack App, meani
## 1:1 meetings
-Each employee at FlowForge will have regular one to one meetings with their
+Each employee at FlowFuse will have regular one to one meetings with their
manager. The primary goal of this meeting is for the report to set the agenda
and tone. It's important to understand what's going on in ones life, how they're
feeling, and what their challenges are.
@@ -172,5 +176,5 @@ also communicate with the manager's manager to keep in touch with the strategy a
communicate feedback on what they observe directly.
The advised cadance to have these meetings depends on the wants of the report,
-but generally advised once every 6-8 weeks. As FlowForge scales, the number of
+but generally advised once every 6-8 weeks. As FlowFuse scales, the number of
weeks between these meetings is likely increasing.
diff --git a/src/handbook/company/decisions.md b/src/handbook/company/decisions.md
index 4f4c596d3b..bf81c7d27a 100644
--- a/src/handbook/company/decisions.md
+++ b/src/handbook/company/decisions.md
@@ -13,7 +13,7 @@ particular undertaking.
When decisions need to be made regarding a DRI's area of responsibility, the DRI
is the person who has the final say and is empowered to make those decisions.
This allows for efficient decision-making and prevents decision paralysis or
-ambiguity within FlowForge. The DRI is expected to gather relevant input and
+ambiguity within FlowFuse. The DRI is expected to gather relevant input and
feedback from other stakeholders but is ultimately responsible for making the
final call. Other stakeholders might need to
Disagree and Commit. Regular
@@ -28,7 +28,7 @@ or project successfully.
Note that both the CEO and CTO retain the right to veto decisions. This should very seldomly happen.
-DRI's weren't invented by FlowForge, we stand on the shoulder of giants that
+DRI's weren't invented by FlowFuse, we stand on the shoulder of giants that
championed the term and iterated before us. Read about the prior art:
1. [Apple](http://fortune.com/2011/08/25/how-apple-works-inside-the-worlds-biggest-startup/)
1. [GitLab](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/)
diff --git a/src/handbook/company/index.md b/src/handbook/company/index.md
index 613d4e71a7..edffc41f24 100644
--- a/src/handbook/company/index.md
+++ b/src/handbook/company/index.md
@@ -5,7 +5,7 @@ navGroup: Company
# Company
-FlowForge allows organizations to reliably deliver Node-RED applications in a
+FlowFuse allows organizations to reliably deliver Node-RED applications in a
continuous, collaborative, and secure manner.
- [Board meetings](./board.md)
@@ -30,4 +30,4 @@ Upon request wiring details can be provided by the CEO.
### Dun & Bradstreet
-FlowForge's Dun and Bradstreet ID is: 11-899-4742
+FlowFuse's Dun and Bradstreet ID is: 11-899-4742
diff --git a/src/handbook/company/remote.md b/src/handbook/company/remote.md
index 9680d870a2..593f2da0d6 100644
--- a/src/handbook/company/remote.md
+++ b/src/handbook/company/remote.md
@@ -2,7 +2,7 @@
navTitle: Remote Work
---
-FlowForge is fully remote and our team spans multiple countries and timezones.
+FlowFuse is fully remote and our team spans multiple countries and timezones.
Working remotely can require some changes.
### Working from a Coworking space
@@ -18,6 +18,6 @@ less of a physical barrier, it's more important to create this barrier on the
digital world. Turn off notification outside of your intended working hours for
email, Slack, and GitHub where possible.
-While FlowForge allows you to use your work devices for private purposes, this
+While FlowFuse allows you to use your work devices for private purposes, this
is another venue to explore. It might work out better to have a private devices
without any work related data to have access to work when not working.
diff --git a/src/handbook/company/security/access-control.md b/src/handbook/company/security/access-control.md
index bc6b3fecf4..6db17a06c3 100644
--- a/src/handbook/company/security/access-control.md
+++ b/src/handbook/company/security/access-control.md
@@ -15,11 +15,11 @@ with business objectives.
## Scope
-This policy applies to all FlowForge information systems that process, store, or
-transmit confidential data as defined in the FlowForge [Data Management Policy](./data-management.md).
+This policy applies to all FlowFuse information systems that process, store, or
+transmit confidential data as defined in the FlowFuse [Data Management Policy](./data-management.md).
-It applies to all employees of FlowForge and to all external parties with access
-to FlowForge system resources.
+It applies to all employees of FlowFuse and to all external parties with access
+to FlowFuse system resources.
## Access Control Policy
@@ -97,7 +97,7 @@ absolute minimum.
## Access to Source Code
-FlowForge defaults to developing in the open, without restriction on who can
+FlowFuse defaults to developing in the open, without restriction on who can
view the source code.
Exceptions will be made for business reasons to keep particular repositories
@@ -106,7 +106,7 @@ and role.
## Password Policy
-All FlowForge system passwords must meet industry standards and best practices.
+All FlowFuse system passwords must meet industry standards and best practices.
Where possible, systems shall be configured to enforce these standards.
- Minimum length of 8 characters, with a mix of letters, numbers, symbols and case.
diff --git a/src/handbook/company/security/asset-management.md b/src/handbook/company/security/asset-management.md
new file mode 100644
index 0000000000..50f2ef17c7
--- /dev/null
+++ b/src/handbook/company/security/asset-management.md
@@ -0,0 +1,81 @@
+---
+navTitle: Asset Management Policy
+---
+
+# Asset Management Policy
+
+| Policy owner | Effective date |
+| -------------- | -------------- |
+| @knolleary | 2023-06-01 |
+
+## Purpose
+
+To identify organizational assets and define appropriate protection responsibilities.
+To ensure that information receives an appropriate level of protection in accordance
+with its importance to the organization. To prevent unauthorized disclosure,
+modification, removal, or destruction of information stored on media.
+
+
+## Scope
+
+This policy applies to all FlowFuse owned or managed information systems.
+
+##Ā Policy
+
+### Inventory of Assets
+
+Assets associated with information and information processing facilities that
+store, process, or transmit classified information shall be identified and an
+inventory of these assets shall be created and maintained.
+
+### Ownership of Assets
+
+Assets maintained in the inventory shall be owned by a specific individual or
+group within the company.
+
+### Acceptable Use of Assets
+
+Rules for the acceptable use of information, assets, and information processing
+facilities shall be identified and documented in the [Information Security Policy](./information-security.md).
+
+### Loss or Theft of Assets
+
+All personnel must immediately report the loss of any information systems,
+including portable or laptop computers, smartphones, PDAs, authentication tokens
+(keyfobs, one-time-password generators, or personally owned smartphones or
+devices with access to FlowFuse systems) or other devices that can store and
+process or help grant access to FlowFuse data.
+
+### Return of Assets
+
+All employees and third-party users of FlowFuse equipment shall return all of
+the organizational assets within their possession upon termination of their
+employment, contract, or agreement in accordance with the [off-boarding process](../../peopleops/hiring.md#offboarding).
+
+### Handling of Assets
+
+Employees and users who are issued or handle FlowFuse equipment are expected to
+use reasonable judgment and exercise due care in protecting and maintaining the
+equipment.
+
+Employees are responsible for ensuring that company equipment is secured and
+properly attended to whenever it is transported or stored. Equipment must be
+secured in accordance with the [Access Control](./access-control.md) policy and
+must not be left unattended in public locations.
+
+All mobile devices shall be handled in accordance with the [Information Security Policy](./information-security.md).
+
+## Exceptions
+
+Requests for an exception to this policy must be submitted via email to the
+CEO or CTO for approval.
+
+## Violations & Enforcement
+
+Any known violations of this policy should be reported to the CEO or CTO.
+Violations of this policy can result in immediate withdrawal or suspension of
+system access and/or disciplinary action in accordance with company procedures
+up to and including termination of employment.
+
+---
+Policy derived from [JupiterOne/security-policy-templates](https://github.com/JupiterOne/security-policy-templates) ([CC BY-SA 4 license](https://creativecommons.org/licenses/by-sa/4.0/)) and [Vanta](https://vanta.com)
diff --git a/src/handbook/company/security/business-continuity.md b/src/handbook/company/security/business-continuity.md
new file mode 100644
index 0000000000..8837afb079
--- /dev/null
+++ b/src/handbook/company/security/business-continuity.md
@@ -0,0 +1,76 @@
+---
+navTitle: Business Continuity & Disaster Recovery Policy
+---
+
+# Business Continuity & Disaster Recovery Policy
+
+| Policy owner | Effective date |
+| -------------- | -------------- |
+| @knolleary | 2023-07-01 |
+
+## Purpose
+
+The purpose of this business continuity plan is to prepare FlowFuse in the
+event of service outages caused by factors beyond our control (e.g., natural
+disasters, man-made events), and to restore services to the widest extent
+possible in a minimum time frame.
+
+## Scope
+
+This policy applies to the FlowFuse Cloud production environment, and any
+individual instances of the platform FlowFuse manages on behalf of customers.
+
+It also applies to any systems used in support of the business critical operations
+of the company.
+
+## Continuity of Critical Services
+
+As an all-remote company, our business-critical systems are provided by third-party
+vendors and we rely on their SLAs in the event of any outage.
+
+## FlowFuse Platform General Disaster Recovery Procedures
+
+In the event of a situation that has material impact to the FlowFuse Cloud platform,
+or any equivalent system managed by FlowFuse on behalf of our customers, the following
+procedures apply.
+
+### Notification Phase
+
+This phase deals with the initial identification of a situation that impacts a
+production system. The procedure is as follows:
+
+1. An incident is identified. Full details are relayed to the CTO.
+2. The CTO announces an incident in Slack and directs the engineering/devops teams
+ to gather information and assess the impact and estimated recovery time.
+3. If the incident will result in a prolonged outage or otherwise, the CTO will
+ activate the Recovery phase.
+4. The CTO will notify the necessary teams of this decision, including the CEO.
+
+### Recovery Phase
+
+The goal is to fully restore the affected system within 24 hours of the outage and
+to minimise further disruption for the affected users.
+
+The following steps should be taken. The CTO will coordinate these actions with
+the required teams.
+
+1. Notify affected users to begin initial communication
+2. Assess damage to the environment
+3. Create a new production environment
+4. Ensure new environment is properly secured
+5. Deploy platform code to new environment
+6. Restore data backup to new environment
+7. Verify platform deployment
+8. Verify logging, monitoring and alerting functionality
+9. Update DNS and other necessary records to point to the new environment
+10. Notify affected users through established channels
+
+### Resolution Phase
+
+Once the system has been restored, the CTO will initiate a post mortem of the event
+to ensure any lessons from the outage and subsequent recovery can be reviewed and
+captured.
+
+
+---
+Policy derived from [JupiterOne/security-policy-templates](https://github.com/JupiterOne/security-policy-templates) ([CC BY-SA 4 license](https://creativecommons.org/licenses/by-sa/4.0/)) and [Vanta](https://vanta.com)
diff --git a/src/handbook/company/security/cryptography.md b/src/handbook/company/security/cryptography.md
index 37e38cec9a..e652f9b9d8 100644
--- a/src/handbook/company/security/cryptography.md
+++ b/src/handbook/company/security/cryptography.md
@@ -17,12 +17,12 @@ throughout the entire encryption lifecycle.
## Scope
-All FlowForge data, information and information systems that handle confidential
+All FlowFuse data, information and information systems that handle confidential
or critical information.
## Cryptography Policy
-FlowForge requires all team members apply appropriate cryptographic controls in
+FlowFuse requires all team members apply appropriate cryptographic controls in
handling of data. Where encryption is in use, strong cryptography with associated
key management processes and procedures shall be implemented. All encryption
shall be performed in accordance with industry standards, including NIST SP 800-57.
@@ -32,7 +32,7 @@ in accordance with vendor recommendations and industry best practices including
[NIST when stored or transferred over a public network](https://csrc.nist.gov/projects/cryptographic-standards-and-guidelines).
-FlowForge requires all team members to comply with the cryptography policy, such that:
+FlowFuse requires all team members to comply with the cryptography policy, such that:
- All Production Data at rest is stored on encrypted volumes.
diff --git a/src/handbook/company/security/data-management.md b/src/handbook/company/security/data-management.md
index cf797c7733..6bee9354f8 100644
--- a/src/handbook/company/security/data-management.md
+++ b/src/handbook/company/security/data-management.md
@@ -15,11 +15,11 @@ disposed of in accordance with its importance to the organization.
## Scope
-All FlowForge data, information and information systems.
+All FlowFuse data, information and information systems.
## Data Management Policy
-FlowForge classifies data and information systems in accordance with legal
+FlowFuse classifies data and information systems in accordance with legal
requirements, sensitivity, and business criticality in order to ensure that
information is given the appropriate level of protection. Data owners are
responsible for identifying any additional requirements for specific data or
@@ -30,7 +30,7 @@ classification of data that they store or process.
## Data Classification
-To help FlowForge and its employees easily understand requirements associated
+To help FlowFuse and its employees easily understand requirements associated
with different kinds of information, the company has created four classes of data.
- Critical
@@ -38,7 +38,7 @@ with different kinds of information, the company has created four classes of dat
- Internal
- Public
-As FlowForge is an open company by default, most of our data falls into **public**.
+As FlowFuse is an open company by default, most of our data falls into **public**.
But it is important to recognise when a higher classification is required.
### Definitions and Examples
@@ -90,11 +90,11 @@ waived on a case-by-case basis.
- Legal documents
**Public** data is data intended for public consumption and can be freely distributed
-outside of FlowForge.
+outside of FlowFuse.
*Example Public Data* Types include
- - FlowForge source code, unless classified otherwise
+ - FlowFuse source code, unless classified otherwise
- Marketing material
- Product documentation
- The company handbook
@@ -132,9 +132,9 @@ outside of FlowForge.
classified data is not accidentally included in public data. For example, access
tokens in source code.
-##Ā Data Retention
+## Data Retention
-FlowForge shall retain data as long as the company has a need for its use, or to
+FlowFuse shall retain data as long as the company has a need for its use, or to
meet regulatory or contractual requirements. Once data is no longer needed, it
shall be securely disposed of or archived. Data owners, in consultation with
legal counsel, may determine retention periods for their data.
@@ -142,12 +142,12 @@ legal counsel, may determine retention periods for their data.
Personally identifiable information (PII) shall be deleted or de-identified as
soon as it no longer has a business use.
-##Ā Data Disposal
+## Data Disposal
Data classified as critical, confidential or internal shall be securely deleted
when no longer needed.
-FlowForge will ensure any third-party system used in the operations of the company
+FlowFuse will ensure any third-party system used in the operations of the company
will meet the requires for secure data disposal.
Personally identifiable information (PII) shall be collected, used and retained
@@ -160,13 +160,13 @@ other legal obligation to retain the data.
## Legal Requirements
-Under certain circumstances, FlowForge may become subject to legal proceedings
+Under certain circumstances, FlowFuse may become subject to legal proceedings
requiring retention of data associated with legal holds, lawsuits, or other
-matters as stipulated by FlowForge legal counsel. Such records and information
+matters as stipulated by FlowFuse legal counsel. Such records and information
are exempt from any other requirements specified within this Data Management Policy
and are to be retained in accordance with requirements identified by the Legal
department. All such holds and special retention requirements are subject to
-annual review with FlowForge's legal counsel to evaluate continuing requirements
+annual review with FlowFuse's legal counsel to evaluate continuing requirements
and scope.
## Exceptions
diff --git a/src/handbook/company/security/human-resources.md b/src/handbook/company/security/human-resources.md
new file mode 100644
index 0000000000..f715cc88fa
--- /dev/null
+++ b/src/handbook/company/security/human-resources.md
@@ -0,0 +1,124 @@
+---
+navTitle: Human Resources Security Policy
+---
+
+# Human Resources Security Policy
+
+| Policy owner | Effective date |
+| -------------- | -------------- |
+| @Tracy-Anthony | 2023-06-01 |
+
+## Purpose
+
+To ensure that employees and contractors meet security requirements, understand
+their responsibilities, and are suitable for their roles.
+
+## Scope
+
+This policy applies to all employees of FlowFuse, consultants, contractors and
+other third-party entities with access to FlowFuse production networks and
+system resources.
+
+## Policy
+
+### Screening
+
+Background verification checks on FlowFuse personnel shall be carried out in
+accordance with relevant laws, regulations, and shall be proportional to the
+business requirements, the classification of the information to be accessed, and
+the perceived risks.
+
+All third-parties with technical privileged or administrative access to FlowFuse
+production systems or networks are subject to a background check or requirement
+to provide evidence of an acceptable background, based on their level of access
+and the perceived risk to FlowFuse.
+
+### Competence & Performance Assessment
+
+The skills and competence of employees and contractors shall be assessed as part
+of the [hiring process](../../peopleops/hiring.md). Required skills and competencies shall be listed in job
+descriptions and requisitions, and/or aligned with the responsibilities outlined
+in the Information Security Roles and Responsibilities Policy. Competency
+evaluations may include reference checks, education and certification verifications,
+technical testing, and interviews.
+
+All FlowFuse employees will undergo an [annual performance review](../../peopleops/performance-review.md) which will
+include an assessment of job performance, competence in the role, adherence to
+company policies and code of conduct, and achievement of role-specific objectives.
+
+
+### Terms & Conditions of Employment
+
+Company policies and information security roles and responsibilities shall be
+communicated to employees and third-parties at the time of hire or engagement,
+and employees and contractors are required to formally acknowledge their
+understanding and acceptance of their security responsibilities.
+
+Employees and relevant third-parties shall follow all FlowFuse information
+security policies.
+
+### Management Responsibilities
+
+Each policy owner shall be responsible for ensuring that information security policies
+and procedures are reviewed annually, available in the company handbook, and that
+employees and contractors abide by those policies and procedures for the duration
+of their employment or engagement.
+
+The primary source for the policies is the [company handbook](/handbook/company/security/).
+The review status of each policy is tracked in [Vanta](https://app.vanta.com).
+
+Annual policy reviews shall include a review of any linked or referenced procedures,
+standards or guidelines.
+
+PeopleOps shall ensure that information security responsibilities are
+communicated to individuals, through written job descriptions, policies or some
+other documented method which is accurately updated and maintained.
+
+Compliance with information security policies and procedures and fulfillment of
+information security responsibilities shall be evaluated as part of the performance
+review process wherever applicable.
+
+Management shall consider excessive pressures, and opportunities for fraud when
+establishing incentives and segregating roles, responsibilities, and authorities.
+
+
+### Information Security Awareness, Education & Training
+
+All FlowFuse employees and third-parties with administrative or privileged
+technical access to FlowFuse production systems and networks shall complete
+security awareness training at the time of hire and annually thereafter.
+
+This is managed via the [Vanta](https://app.vanta.com) platform.
+
+Management shall monitor training completion and shall take appropriate steps to
+ensure compliance with this policy. Employees and contractors shall be aware of
+relevant information security and data privacy policies and procedures. The
+company shall ensure that personnel receive security and data privacy training
+appropriate to their role and data handling responsibilities.
+
+In order to maintain a robust level of security awareness, the company will
+provide security-related updates and communications to company personnel on an
+on-going basis through the usual communication channels as needed.
+
+### Termination Process
+
+Employee and contractor termination and offboarding processes shall ensure that
+physical and logical access is promptly revoked in accordance with company SLAs
+and policies, and that all company issued equipment is returned.
+
+The full offboarding process is available [here](../../peopleops/hiring.md#offboarding)
+
+## Exceptions
+
+Requests for an exception to this policy must be submitted by email to the CEO
+or CTO for approval.
+
+## Violations & Enforcement
+
+Any known violations of this policy should be reported to the CEO or CTO.
+Violations of this policy can result in immediate withdrawal or suspension of
+system access and/or disciplinary action in accordance with company procedures
+up to and including termination of employment.
+
+---
+Policy derived from [JupiterOne/security-policy-templates](https://github.com/JupiterOne/security-policy-templates) ([CC BY-SA 4 license](https://creativecommons.org/licenses/by-sa/4.0/)) and [Vanta](https://vanta.com)
diff --git a/src/handbook/company/security/incident-response.md b/src/handbook/company/security/incident-response.md
new file mode 100644
index 0000000000..4401017d07
--- /dev/null
+++ b/src/handbook/company/security/incident-response.md
@@ -0,0 +1,167 @@
+---
+navTitle: Incident Response Plan
+---
+
+# Incident Response Plan
+
+| Policy owner | Effective date |
+| -------------- | -------------- |
+| @knolleary | 2023-07-01 |
+
+## Purpose
+
+This document establishes the plan for managing information security incidents
+and events, and offers guidance for employees or incident responders who believe
+they have discovered, or are responding to, a security incident.
+
+## Scope
+
+This policy covers all information security or data privacy events or incidents.
+
+## External Vulnerability Disclosures
+
+This policy relates to how we deal with security issues internally. For information
+on how to report potential vulnerabilities in the FlowFuse platform and associated
+components from outside the company, please refer to our [Vulnerability Reporting policy](/handbook/development/security).
+
+## Incident and Event Definitions
+
+A **security event** is an observable occurrence relevant to the confidentiality,
+availability, integrity, or privacy of company controlled data, systems or networks.
+
+A **security incident** is a *security event* which results in loss or damage to
+the confidentiality, availability, integrity, or privacy of company controlled
+data, systems or networks.
+
+## Security Incident Response Team
+
+The Security Incident Response Team (SIRT) is responsible for
+
+ - Reviewing analyzing, and logging all received reports and tracking their statuses.
+ - Performing investigations, creating and executing action plans, and post-incident activities.
+ - Collaboration with law enforcement agencies.
+
+Current members of the FlowFuse SIRT:
+
+ - CTO
+ - CEO
+ - Customer Success manager
+ - Product Manager
+
+## Incident Reporting & Documentation
+
+### Reporting
+
+If a FlowFuse employee, contractor, user, or customer becomes aware of an
+information security event or incident, possible incident, imminent incident,
+unauthorized access, policy violation, security weakness, or suspicious activity,
+then they shall immediately report the information using one of the following
+communication channels:
+
+ - Email security@flowfuse.com with information or reports about the event or
+ incident
+ - Raise an issue in [`flowforge/security`](https://github.com/flowforge/security){rel="nofollow"}
+ - Report it in #security channel in slack
+
+Reports should include specific details about what has been observed or discovered.
+
+### Severity
+
+The [SIRT](#security-incident-response-team) shall monitor incident and event
+issues and shall assign a severity (via label) based on the following categories:
+
+
+ - **P3/P4** - Low and Medium Severity
+ Issues meeting this severity are simply suspicions or odd behaviors. They
+ are not verified and require further investigation. There is no clear indicator
+ that systems have tangible risk and do not require emergency response. This
+ includes lost/stolen laptop with disk encryption, suspicious emails, outages,
+ strange activity on a laptop, etc.
+ - **P2** - High Severity
+ High severity issues relate to problems where an adversary or active
+ exploitation hasn't been proven yet, and may not have happened, but is likely
+ to happen. This may include lost/stolen laptop without encryption, vulnerabilities
+ with direct risk of exploitation, threats with risk or adversarial persistence
+ on our systems (e.g.: backdoors, malware), malicious access of business
+ data (e.g.: passwords, vulnerability data, payments information).
+ - **P1** - Critical Severity
+ Critical issues relate to actively exploited risks and involve a malicious
+ actor or threats that put any individual at risk of physical harm.
+ Identification of active exploitation is required to meet this severity category.
+
+### Escalation and Internal Reporting
+
+ - **P1** - Critical Severity
+ P1 issues require immediate notification to a member of the [SIRT](#security-incident-response-team)
+ - **P2** - High Severity
+ An issue should be raised in [`flowforge/security`](https://github.com/flowforge/security){rel="nofollow"}
+ and explicit notification in the #security channel
+ - **P3/P4** - Medium and Low Severity
+ An issue should be raised in [`flowforge/security`](https://github.com/flowforge/security){rel="nofollow"}
+
+### Documentation
+
+All reported security events, incidents, and response activities shall be documented
+and adequately protected in the `flowforge/security` repository.
+
+A root cause analysis (RCA) may be performed on all verified **P1** security incidents.
+It will be reference in the incident issue and reviewed by the SIRT.
+
+## Incident Response Process
+
+For critical issues, the response team will follow an iterative response process.
+
+This covers the following phases:
+
+1. **Investigate** - establish the known facts of the situation.
+2. **Contain** - limit the impact of the situation.
+3. **Eradicate** - remove the immediate cause of the situation.
+4. **Recover** - restore the affected systems and services.
+5. **Remediate** - apply necessary preventative measures to ensure the situation cannot happen again.
+6. **Document** - perform a post-mortem of the situation and a root-cause analysis (RCA). Document to ensure lessons can be learnt.
+
+
+## External Communications and Breach Reporting
+
+In the event of unauthorized access to company or customer systems, networks,
+and/or data, the CEO, with Legal advice, determine what external communications
+are required.
+
+Breaches shall be reported to customers, consumers, data subjects and regulators
+without undue delay and in accordance with all contractual commitments and
+applicable legislation.
+
+No personnel may disclose information regarding incident or potential breaches
+to any third party or unauthorized person without the approval of legal and/or
+executive management.
+
+## Mitigation and Remediation
+
+The CEO and CTO shall determine any immediate or long term mitigations or
+remedial actions that need to be taken as a result of an incident or breach.
+
+In the event that mitigations or remedial actions are needed, executive staff
+shall direct personnel with respect to planning, communicating and executing
+those activities.
+
+### Cooperation with Customers, Data Controller and Authorities
+
+As needed and determined by legal and executive staff, the company shall
+cooperate with customers, Data Controllers and regulators to fulfill all of its
+obligations in the event of an incident or data breach.
+
+
+## Exceptions
+
+Requests for an exception to this policy must be submitted to the CEO or CTO for
+approval.
+
+## Violations & Enforcement
+
+Any known violations of this policy should be reported to the CEO or CTO.
+Violations of this policy can result in immediate withdrawal or suspension of
+system access and/or disciplinary action in accordance with company procedures
+up to and including termination of employment.
+
+---
+Policy derived from [JupiterOne/security-policy-templates](https://github.com/JupiterOne/security-policy-templates) ([CC BY-SA 4 license](https://creativecommons.org/licenses/by-sa/4.0/)) and [Vanta](https://vanta.com)
diff --git a/src/handbook/company/security/index.md b/src/handbook/company/security/index.md
index 781f2d8e09..f65282d1de 100644
--- a/src/handbook/company/security/index.md
+++ b/src/handbook/company/security/index.md
@@ -4,7 +4,7 @@ navTitle: Security
# Security
-To ensure the safety and security of our company, employees, and customers, FlowForge
+To ensure the safety and security of our company, employees, and customers, FlowFuse
maintains a set of security policies that we all must follow.
It is important that every takes the time to understand their own responsibilities
@@ -17,6 +17,12 @@ in this area, which includes prompt reporting and resolution of any issues ident
- [Secure Development Policy](./secure-development.md)
- [Operations Security Policy](./operations-security.md)
- [Cryptography Policy](./cryptography.md)
+ - [Asset Management Policy](./asset-management.md)
+ - [Third Party Risk Management Policy](./third-party-risk-management.md)
+ - [Human Resources Policy](./human-resources.md)
+ - [Risk Management Policy](./risk-management.md)
+ - [Incident Response Plan](./incident-response.md)
+ - [Business Continuity and Disaster Recover Policy](./business-continuity.md)
## Credentials
@@ -26,7 +32,7 @@ The company provides a 1Password Vault account to all employees. When available,
sign in with your Google Workspace account. When this option is not available,
you must not reuse the same password between different application, but you must
generate a new one per application. Passwords are stored in 1Password for both
-individual user accounts and shared accounts (e.g. FlowForge npmjs account).
+individual user accounts and shared accounts (e.g. FlowFuse npmjs account).
Any shared accounts should be in an appropriate vault shared with those that
need it only, but always more than just one person.
@@ -37,7 +43,7 @@ For all services that support it, 2FA authentication should be enabled and if po
## Executive Fraud
-The CEO, CTO, and other executives at FlowForge will never email anyone to wire
+The CEO, CTO, and other executives at FlowFuse will never email anyone to wire
money, request you to buy gift cards, or request any other type of monitory
transaction. Transactions are started through [a set process](../../operations/vendors.md)
only. When in doubt, reach out through Slack and request a call with the executive
diff --git a/src/handbook/company/security/information-security-roles.md b/src/handbook/company/security/information-security-roles.md
index 9a98b2a21c..2c24a6d649 100644
--- a/src/handbook/company/security/information-security-roles.md
+++ b/src/handbook/company/security/information-security-roles.md
@@ -11,8 +11,8 @@ navTitle: Information Security Roles and Responsibilities
## Purpose
-FlowForge is committed to conducting business in compliance with all applicable laws,
-regulations, and company policies. FlowForge has adopted this policy to outline
+FlowFuse is committed to conducting business in compliance with all applicable laws,
+regulations, and company policies. FlowFuse has adopted this policy to outline
the security measures required to protect electronic information systems and
related equipment from unauthorized use.
@@ -21,7 +21,7 @@ related equipment from unauthorized use.
### Board of directors
- Oversight over risk and internal control for information security, privacy, and compliance.
- - Consults with executive leadership to understand FlowForge's security mission and risks and provides guidance to bring them into alignment
+ - Consults with executive leadership to understand FlowFuse's security mission and risks and provides guidance to bring them into alignment
### Executive Leadership
@@ -29,7 +29,7 @@ related equipment from unauthorized use.
- Approves Capital Expenditures for Information Security and Privacy programs and initiatives
- Oversight over the execution of the information security and Privacy risk management program and risk treatments
- Communication Path to the Board of Directors
- - Aligns [Information Security](./information-security.md) and [Privacy Policy](/privacy-policy/#privacy-policy) based on FlowForge's mission, strategic objectives and risk appetite
+ - Aligns [Information Security](./information-security.md) and [Privacy Policy](/privacy-policy/#privacy-policy) based on FlowFuse's mission, strategic objectives and risk appetite
### CTO
@@ -42,7 +42,7 @@ related equipment from unauthorized use.
### Systems Owners
- Maintain the confidentiality, integrity and availability of the information
- systems for which they are responsible in compliance with FlowForge's policies
+ systems for which they are responsible in compliance with FlowFuse's policies
on information security and privacy
- Approval of technical access and change requests for non-standard access to
systems under their control
diff --git a/src/handbook/company/security/information-security.md b/src/handbook/company/security/information-security.md
index 239c9c8014..0eff2d3560 100644
--- a/src/handbook/company/security/information-security.md
+++ b/src/handbook/company/security/information-security.md
@@ -11,52 +11,52 @@ navTitle: Information Security Policy and Acceptable Use Policy
## Overview
-This Information Security Policy is intended to protect FlowForgeās employees,
+This Information Security Policy is intended to protect FlowFuseās employees,
partners and the company from illegal or damaging actions by individuals, either
knowingly or unknowingly.
-FlowForge systems are to be used for business purposes in serving the interests of
+FlowFuse systems are to be used for business purposes in serving the interests of
the company, and of our clients and customers in the course of normal operations.
Effective security is a team effort involving the participation and support of
-every FlowForge employee or contractor who deals with information and/or
+every FlowFuse employee or contractor who deals with information and/or
information systems. It is the responsibility of every team member to read and
understand this policy, and to conduct their activities accordingly.
## Purpose
The purpose of this policy is to communicate our information security policies
-and outline the acceptable use and protection of FlowForgeās information and
-assets. These rules are in place to protect customers, employees, and FlowForge.
-Inappropriate use exposes FlowForge to risks including virus attacks, compromise
+and outline the acceptable use and protection of FlowFuseās information and
+assets. These rules are in place to protect customers, employees, and FlowFuse.
+Inappropriate use exposes FlowFuse to risks including virus attacks, compromise
of network systems and services, financial and reputational risk, and legal and
compliance issues.
-The FlowForge "Information Security Policy" is comprised of this policy and all
-FlowForge policies referenced and/or linked within this document.
+The FlowFuse "Information Security Policy" is comprised of this policy and all
+FlowFuse policies referenced and/or linked within this document.
## Scope
This policy applies to the use of information, electronic and computing devices,
-and network resources to conduct FlowForge business or interact with internal
-networks and business systems, whether owned or leased by FlowForge, the employee,
+and network resources to conduct FlowFuse business or interact with internal
+networks and business systems, whether owned or leased by FlowFuse, the employee,
or a third party. All employees, contractors, consultants, temporary, and other
-workers at FlowForge and its subsidiaries are responsible for exercising good
+workers at FlowFuse and its subsidiaries are responsible for exercising good
judgment regarding appropriate use of information, electronic devices, and
-network resources in accordance with FlowForge policies and standards, and local
+network resources in accordance with FlowFuse policies and standards, and local
laws and regulations.
This policy applies to employees, contractors, consultants, temporaries, and
-other workers at FlowForge, including all personnel affiliated with third
-parties. This policy applies to all FlowForge-controlled company and customer
+other workers at FlowFuse, including all personnel affiliated with third
+parties. This policy applies to all FlowFuse-controlled company and customer
data as well as all equipment, systems, networks and software owned or leased by
-FlowForge.
+FlowFuse.
## Security Incident Reporting
All users are required to report known or suspected security events or incidents,
including policy violations and observed security weaknesses. Incidents shall be
-reported immediately or as soon as possible by sending an email to security@flowforge.com.
+reported immediately or as soon as possible by sending an email to security@flowfuse.com.
In your email please describe the incident or observation along with any relevant
details.
@@ -74,7 +74,7 @@ comply with this policy.
2. Providing access to another individual, either deliberately or through failure
to secure a device is prohibited.
-3. All end-user, personal (BYOD) or company owned devices used to access FlowForge
+3. All end-user, personal (BYOD) or company owned devices used to access FlowFuse
information systems (i.e. email) must adhere to the following rules and requirements:
1. Devices must be secured with a password (or equivalent control such as biometric)
@@ -83,7 +83,7 @@ information systems (i.e. email) must adhere to the following rules and requirem
2. Devices must not be left unattended in public.
4. Users must report any suspected misuse or theft of a mobile device immediately
- to security@flowforge.com
+ to security@flowfuse.com
5. Avoid sharing credentials. Secrets must be stored safely, using features such
as GitHub Secrets. For accounts and other sensitive data that need to be shared
@@ -92,7 +92,7 @@ information systems (i.e. email) must adhere to the following rules and requirem
6. Confidential information must not be stored on portable media such as USB drives
-7. Accessing FlowForge systems on public "shared" computers, such as hotel kiosks
+7. Accessing FlowFuse systems on public "shared" computers, such as hotel kiosks
is strictly prohibited
8. Upon termination users agree to return all company owned devices and delete
@@ -100,9 +100,9 @@ information systems (i.e. email) must adhere to the following rules and requirem
## Acceptable Use Policy
-FlowForge proprietary and customer information stored on electronic and computing
-devices, whether owned or leased by FlowForge, the employee or a third party,
-remains the sole property of FlowForge for the purposes of this policy.
+FlowFuse proprietary and customer information stored on electronic and computing
+devices, whether owned or leased by FlowFuse, the employee or a third party,
+remains the sole property of FlowFuse for the purposes of this policy.
Employees and contractors must ensure through legal or technical means that
proprietary information is protected in accordance with the [Data Management Policy](./data-management.md).
@@ -111,16 +111,16 @@ Google Drive should be used to store and share files within the company, ensurin
proper access controls are applied.
You have a responsibility to promptly report the theft, loss, or unauthorized
-disclosure of FlowForge proprietary information or equipment. You may access,
-use or share FlowForge proprietary information only to the extent it is authorized
+disclosure of FlowFuse proprietary information or equipment. You may access,
+use or share FlowFuse proprietary information only to the extent it is authorized
and necessary to fulfill your assigned job duties.
Employees are responsible for exercising good judgment regarding the
reasonableness of personal use of company-provided devices.
For security and network maintenance purposes, authorized individuals within
-FlowForge may monitor equipment, systems and network traffic at any time.
-FlowForge reserves the right to audit networks and systems on a periodic basis
+FlowFuse may monitor equipment, systems and network traffic at any time.
+FlowFuse reserves the right to audit networks and systems on a periodic basis
to ensure compliance with this policy.
Employees must ensure the software they use is properly licensed and used as
@@ -128,9 +128,9 @@ intended.
## Unacceptable Use
-Under no circumstances is an employee of FlowForge authorized to engage in any
+Under no circumstances is an employee of FlowFuse authorized to engage in any
activity that is illegal under local, state, federal or international law while
-utilizing FlowForge-owned resources or while representing FlowForge in any capacity.
+utilizing FlowFuse-owned resources or while representing FlowFuse in any capacity.
## Additional Policies and Procedures Incorporated by Reference
@@ -145,22 +145,22 @@ get added to the handbook and adopted.
Role | Purpose
---|---
[Access Control Policy](./access-control.md) | To limit access to information and information processing systems to authorized parties in accordance with business objectives.
-Asset Management Policy | To identify organizational assets and define appropriate protection responsibilities.
-Business Continuity & Disaster Recovery Plan | To prepare FlowForge in the event of extended service outages caused by factors beyond our control (e.g., natural disasters, man-made events), and to restore services to the widest extent possible in a minimum time frame.
+[Asset Management Policy](./asset-management.md) | To identify organizational assets and define appropriate protection responsibilities.
+[Business Continuity & Disaster Recovery Plan](./business-continuity.md) | To prepare FlowFuse in the event of extended service outages caused by factors beyond our control (e.g., natural disasters, man-made events), and to restore services to the widest extent possible in a minimum time frame.
[Cryptography Policy](./cryptography.md) | To ensure proper and effective use of cryptography to protect the confidentiality, authenticity and/or integrity of information.
[Data Management Policy](./data-management.md) | To ensure that information is classified and protected in accordance with its importance to the organization.
-Human Resources Policy | To ensure that employees and contractors meet security requirements, understand their responsibilities, and are suitable for their roles.
-Incident Response Plan | Policy and procedures for suspected or confirmed information security incidents.
+[Human Resources Policy](./human-resources.md) | To ensure that employees and contractors meet security requirements, understand their responsibilities, and are suitable for their roles.
+[Incident Response Plan](./incident-response.md) | Policy and procedures for suspected or confirmed information security incidents.
[Operations Security Policy](./operations-security.md) | To ensure the correct and secure operation of information processing systems and facilities.
Physical Security Policy | To prevent unauthorized physical access or damage to the organizationās information and information processing facilities.
-Risk Management Policy | To define the process for assessing and managing FlowForge's information security risks in order to achieve the companyās business and information security objectives.
+[Risk Management Policy](./risk-management.md) | To define the process for assessing and managing FlowFuse's information security risks in order to achieve the companyās business and information security objectives.
[Secure Development Policy](./secure-development.md) | To ensure that information security is designed and implemented within the development lifecycle for applications and information systems.
-Third-Party Management Policy | To ensure protection of the organization's data and assets that are shared with, accessible to, or managed by suppliers, including external parties or third-party organizations such as service providers, vendors, and customers, and to maintain an agreed level of information security and service delivery in line with supplier agreements.
+[Third Party Risk Management Policy](./third-party-risk-management.md) | To ensure protection of the organization's data and assets that are shared with, accessible to, or managed by suppliers, including external parties or third-party organizations such as service providers, vendors, and customers, and to maintain an agreed level of information security and service delivery in line with supplier agreements.
## Policy Compliance
-FlowForge will measure and verify compliance to this policy through various
+FlowFuse will measure and verify compliance to this policy through various
methods, including but not limited to ongoing monitoring, and both internal and
external audits.
diff --git a/src/handbook/company/security/operations-security.md b/src/handbook/company/security/operations-security.md
index 402432c351..8381700e3d 100644
--- a/src/handbook/company/security/operations-security.md
+++ b/src/handbook/company/security/operations-security.md
@@ -14,7 +14,7 @@ To ensure the correct and secure operation of information processing systems and
## Scope
-All FlowForge data, information and information systems that are business critical
+All FlowFuse data, information and information systems that are business critical
and/or process, store, or transmit company data.
## Operations Security
@@ -73,7 +73,7 @@ periodically tested, not less than annually.
Backups must be stored separately from the production data location.
-FlowForge does not regularly backup user devices like laptops. Users are expected to
+FlowFuse does not regularly backup user devices like laptops. Users are expected to
store critical files and information in the commpany-provided Google Drive with
appropriate access controls applied.
diff --git a/src/handbook/company/security/risk-management.md b/src/handbook/company/security/risk-management.md
new file mode 100644
index 0000000000..cbcd38ba40
--- /dev/null
+++ b/src/handbook/company/security/risk-management.md
@@ -0,0 +1,114 @@
+---
+navTitle: Risk Management Policy
+---
+
+# Data Management Policy
+
+| Policy owner | Effective date |
+| -------------- | -------------- |
+| @knolleary | 2023-06-01 |
+
+## Purpose
+
+To define actions to address information security risks and opportunities. To
+define a plan for the achievement of information security and privacy objectives.
+
+## Scope
+
+All FlowFuse data, information and information systems.
+
+Risks that could affect the medium to long-term goals should be considered as
+well as risks that will be encountered in the day-to-day delivery of services.
+
+Risks will be targeted to achieve maximum benefit without increasing the
+bureaucratic burden and ultimately affecting core service delivery to the
+organization.
+
+## Risk Management Strategy
+
+A thorough risk assessment must be conducted to evaluate potential threats and
+vulnerabilities to the confidentiality, integrity, and availability of sensitive,
+confidential, and proprietary electronic information FlowFuse stores, transmits,
+and/or processes.
+
+Risk assessments must be performed with any major change to FlowFuse's business
+or technical operations and/or supporting infrastructure no less than once per year.
+
+Strategies shall be developed to mitigate or accept the risks identified in the
+risk assessment process.
+
+A [risk register](https://app.vanta.com/risk-management/risk-register) is maintained
+and monitored quarterly to assess compliance with the above policy, and document
+newly discovered or created risks.
+
+## Managing Risk
+
+Risks are assessed and ranked according to their impact and their likelihood of
+occurrence. A formal Risk Assessment, and network penetration tests, will be
+performed at least annually and shall take into consideration the results of any
+technical vulnerability management activities performed in accordance with the
+[Operations Security Policy](./operations-security.md).
+
+Each risk will be assessed as to its likelihood and impact. Both impact and
+likelihood are assessed on a scale of 1-5. Impact can range from 1 ("Very low impact")
+to 5 ("Very high impact") and likelihood can range from 1 ("Very unlikely") to 5 ("Very likely").
+
+The criteria for determining risk is the combined likelihood and impact of an
+event adversely affecting the confidentiality, availability, integrity, or
+privacy of organizational and customer information, personally identifiable
+information (PII), or business information systems.
+
+For all risk inputs such as risk assessments, vulnerability scans, penetration test,
+bug bounty programs, etc., FlowFuse management shall reserve the right to modify
+risk rankings based on its assessment of the nature and criticality of the system
+processing, as well as the nature, criticality and exploitability (or other
+relevant factors and considerations) of the identified vulnerability.
+
+## Risk Response, Treatment, and Tracking
+
+Risk will be prioritized and maintained in a risk register where they will be
+prioritized and mapped using the approach contained in this policy.
+
+The following responses to risk should be employed:
+
+ - **Modify**: take actions or employ strategies to reduce the risk.
+ - **Accept**: accept and monitor the risk at the present time. This may be necessary for some risks that arise from external events.
+ - **Transfer**: pass the risk on to another party. For example contractual terms may be agreed to ensure that the risk is not borne by FlowFuse or insurance may be appropriate for protection against financial loss.
+ - **Avoid**: cease the activity or to change it in such a way as to end the risk.
+
+Where FlowFuse chooses a risk response other than "Accept" or "Avoid" it shall
+develop a Risk Treatment Plan
+
+
+### Risk Management Procedures
+
+The procedure for managing risk will meet the following criteria:
+
+ - FlowFuse will maintain a [Risk Register](https://app.vanta.com/risk-management/risk-register) and Treatment Plan.
+ - Risks are ranked by "likelihood" and "severity/impact" as critical, high, medium, low, and negligible.
+ - Overall risk shall be determined through a combination of likelihood and impact.
+ - Risks may be evaluated to estimate potential monetary loss where possible.
+
+FlowFuse will respond to risks in a prioritized fashion. Remediation priority
+will consider the risk likelihood and impact, cost, work effort, and availability
+of resources. Multiple remediations may be undertaken simultaneously.
+
+Regular reports will be made to the senior leadership of FlowFuse to ensure
+risks are being mitigated appropriately, and in accordance with business
+priorities and objectives.
+
+
+## Exceptions
+
+Requests for an exception to this policy must be submitted to the CEO or CTO for
+approval.
+
+## Violations & Enforcement
+
+Any known violations of this policy should be reported to the CEO or CTO.
+Violations of this policy can result in immediate withdrawal or suspension of
+system access and/or disciplinary action in accordance with company procedures
+up to and including termination of employment.
+
+---
+Policy derived from [JupiterOne/security-policy-templates](https://github.com/JupiterOne/security-policy-templates) ([CC BY-SA 4 license](https://creativecommons.org/licenses/by-sa/4.0/)) and [Vanta](https://vanta.com)
diff --git a/src/handbook/company/security/secure-development.md b/src/handbook/company/security/secure-development.md
index 5bcdd8fe6f..d3acbbe7bc 100644
--- a/src/handbook/company/security/secure-development.md
+++ b/src/handbook/company/security/secure-development.md
@@ -15,16 +15,16 @@ development lifecycle for applications and information systems.
## Scope
-All FlowForge applications and information systems that are business critical
+All FlowFuse applications and information systems that are business critical
and/or process, store, or transmit Confidential data. This policy applies to all
-internal and external engineers and developers of FlowForge software and
+internal and external engineers and developers of FlowFuse software and
infrastructure.
## Secure Development Policy
-FlowForge policy requires that:
+FlowFuse policy requires that:
- 1. FlowForge software engineering and product development is required to follow
+ 1. FlowFuse software engineering and product development is required to follow
security best practices. Product should be "Secure by Design" and "Secure by
Default".
@@ -46,7 +46,7 @@ new product or major changes to an existing product.
4. Security requirements must be defined, tracked, and implemented.
5. Security analysis must be performed for any open source software and/or
- third-party components and dependencies included in FlowForge software products.
+ third-party components and dependencies included in FlowFuse software products.
6. Static application security testing (SAST) must be performed throughout
development and prior to each release.
@@ -63,9 +63,9 @@ be remediated in the next release or within the defined, predetermined timeframe
10. Any exception to the remediation of a finding must be documented and
approved by the CTO.
-##Ā Secure Development Environment
+## Secure Development Environment
-FlowForge uses separate Staging and Production systems. These are logically
+FlowFuse uses separate Staging and Production systems. These are logically
segregated environments in different AWS accounts.
The Production environment is classified Critical with suitable controls in place
diff --git a/src/handbook/company/security/third-party-risk-management.md b/src/handbook/company/security/third-party-risk-management.md
new file mode 100644
index 0000000000..4fd6f1aa9c
--- /dev/null
+++ b/src/handbook/company/security/third-party-risk-management.md
@@ -0,0 +1,58 @@
+---
+navTitle: Third-Party Risk Management Policy
+---
+
+# Third-Party Risk Management Policy
+
+| Policy owner | Effective date |
+| -------------- | -------------- |
+| @ZJvandeWeg | 2023-06-01 |
+
+## Purpose
+
+To ensure protection of the organization's data and assets that are shared with,
+accessible to, or managed by suppliers, including external parties or third-party
+organizations such as service providers, vendors, and customers, and to maintain
+an agreed level of information security and service delivery in line with supplier
+agreements.
+
+## Scope
+
+All data and information systems owned or used by FlowFuse that are business
+critical and/or process, store, or transmit data classified as [Confidential or Critical](./data-management.md).
+
+## Policy
+
+A list of approved vendors/partners must be maintained and reviewed annually. This
+list will be linked from the [Vendor section of the handbook](../../operations/vendors.md).
+
+Approval from management must be in place before onboarding any new vendor or
+contractor that impacts FlowFuse production systems. Additionally, all changes
+to existing contract agreements must be reviewed and approved before implementation.
+
+For any technology solution that needs to be integrated with FlowFuse production
+environment or operations, a review should be held to understand and approve the
+risk. Periodic compliance assessment and SLA review may be required.
+
+FlowFuse Customers or Partners should not be allowed access outside of their
+own environment, meaning they cannot access, modify, or delete any data belonging
+to other third parties.
+
+Additional vendor agreements should be obtained as required by applicable regulatory
+compliance requirements.
+
+
+## Exceptions
+
+Requests for an exception to this policy must be submitted via email to the
+CEO or CTO for approval.
+
+## Violations & Enforcement
+
+Any known violations of this policy should be reported to the CEO or CTO.
+Violations of this policy can result in immediate withdrawal or suspension of
+system access and/or disciplinary action in accordance with company procedures
+up to and including termination of employment.
+
+---
+Policy derived from [JupiterOne/security-policy-templates](https://github.com/JupiterOne/security-policy-templates) ([CC BY-SA 4 license](https://creativecommons.org/licenses/by-sa/4.0/)) and [Vanta](https://vanta.com)
diff --git a/src/handbook/company/strategy.md b/src/handbook/company/strategy.md
index 1920bdd1de..9f4268f12c 100644
--- a/src/handbook/company/strategy.md
+++ b/src/handbook/company/strategy.md
@@ -18,9 +18,9 @@ Node-RED is at the core of what we do. It is the reason the company exists. Our
success is fed by the success of the core project. Node-RED enables tens of
thousands to create and maintain workflows and logic of both physical devices
and digital services. Ensure their effectiveness grows, while new users are
-introduced to Node-RED is vital to the success of FlowForge.
+introduced to Node-RED is vital to the success of FlowFuse.
-FlowForge will drive the Node-RED project through:
+FlowFuse will drive the Node-RED project through:
- **Deliver features** to the core of Node-RED that are stable and provide value to the community
- **Actively participate** in the community to establish a positive reputation and level of engagement
@@ -30,18 +30,18 @@ FlowForge will drive the Node-RED project through:
#### Become the standard way of running any Node-RED at any scale
-There's a wide range of deployment scenarios and FlowForge aims to build a
-platform to help each of them to be successful. FlowForge will solve challenges
+There's a wide range of deployment scenarios and FlowFuse aims to build a
+platform to help each of them to be successful. FlowFuse will solve challenges
unsolved by Node-RED and push Low-Code beyond the capabilities of Node-RED.
Firstly, team collaboration. Allowing Flows to be developed by multiple
individuals, ensuring quality and correctness. Push the boundaries of Low-Code
to allow more people to collaborate.
-Secondly, Node-RED is deployed in many different environments. FlowForge will allow
+Secondly, Node-RED is deployed in many different environments. FlowFuse will allow
everyone to achieve the best results whatever the execution context.
-We believe these two points will make FlowForge synonymous with Node-RED, and
+We believe these two points will make FlowFuse synonymous with Node-RED, and
make it attractive to individual users as well as Enterprises. Value offered
will increase exponentially as the platform scales to teams of developers and
larger deployment scenarios.
@@ -84,21 +84,21 @@ Furthermore, we will continue our involvement with the Node-RED community.
### Key metrics
-At FlowForge we're engaged in many initiatives to grow our offering and assess
+At FlowFuse we're engaged in many initiatives to grow our offering and assess
product market fit. Currently we're measuring 2 key metrics which serve as
heuristic for company wide success.
#### Installed Platforms
-FlowForge is the key product we're verifying in the market currently. Each
+FlowFuse is the key product we're verifying in the market currently. Each
platform installed and running shows value is delivered to customers. Through
telemetry we know the number of instances that reported their unique instance ID.
Other than the number of unique instances reporting on telemetry the last 7 days
-we measure the number of managed instances of Node-RED through FlowForge. This
+we measure the number of managed instances of Node-RED through FlowFuse. This
is the sum of projects and devices.
Telemetry collection is opt-in, and dependant on an internet connection. As such
-it's anticipated to under report the true number of FlowForge managed instances.
+it's anticipated to under report the true number of FlowFuse managed instances.
Target growth for this metric is 10% week over week.
diff --git a/src/handbook/company/values.md b/src/handbook/company/values.md
index 5326d14bd4..4729792f1b 100644
--- a/src/handbook/company/values.md
+++ b/src/handbook/company/values.md
@@ -5,8 +5,8 @@ meta:
## Values
-FlowForge has a few core values. Values we aspire to live by in everything we do
-at FlowForge. With a shared set of values, norms that are created every day will
+FlowFuse has a few core values. Values we aspire to live by in everything we do
+at FlowFuse. With a shared set of values, norms that are created every day will
align with what company we want to be, and how we conduct business. Our values
are as follows:
diff --git a/src/handbook/company/vision.md b/src/handbook/company/vision.md
index fe2d71c934..5d6492b550 100644
--- a/src/handbook/company/vision.md
+++ b/src/handbook/company/vision.md
@@ -7,7 +7,7 @@ meta:
> We will only be successful if the whole Node-RED community is successful.
-Our company vision has four parts and captures what we want FlowForge to evolve
+Our company vision has four parts and captures what we want FlowFuse to evolve
into in the next 5 years. The vision is inspiration for the [product strategy](../product/strategy.md), which is updated continuously. Itās based on the four pillars. This allows us to adapt to changing market conditions so that we meet customer needs.
- Drive the growth and success of the [Node-RED](https://nodered.org) project
@@ -17,9 +17,9 @@ into in the next 5 years. The vision is inspiration for the [product strategy](.
#### Drive the growth and success of the Node-RED project
-Node-RED is at the core of what we do. Node-RED enables tens of thousands to create and maintain workflows and logic of both physical devices and digital services. Ensuring their effectiveness grows, while new users are introduced to Node-RED is vital to the success of FlowForge.
+Node-RED is at the core of what we do. Node-RED enables tens of thousands to create and maintain workflows and logic of both physical devices and digital services. Ensuring their effectiveness grows, while new users are introduced to Node-RED is vital to the success of FlowFuse.
-FlowForge will drive the Node-RED project through:
+FlowFuse will drive the Node-RED project through:
- **Deliver features** to the core of Node-RED that are stable and provide value to the community
- **Actively participate** in the community to establish a positive reputation and level of engagement
@@ -29,18 +29,18 @@ FlowForge will drive the Node-RED project through:
#### Become the standard way of running any Node-RED at any scale - Be DevOps for Node-RED
-There's a wide range of deployment scenarios and FlowForge aims to build a
-platform to help each of them to be successful. FlowForge will solve challenges
+There's a wide range of deployment scenarios and FlowFuse aims to build a
+platform to help each of them to be successful. FlowFuse will solve challenges
unsolved by Node-RED and push Low-Code beyond the capabilities of Node-RED.
Firstly, team collaboration. Allowing Flows to be developed by multiple
individuals, ensuring quality and correctness. Push the boundaries of Low-Code
to allow more people to collaborate.
-Secondly, Node-RED is deployed in many different environments. FlowForge will allow
+Secondly, Node-RED is deployed in many different environments. FlowFuse will allow
everyone to achieve the best results whatever the execution context.
-We believe these two points will make FlowForge synonymous with Node-RED, and
+We believe these two points will make FlowFuse synonymous with Node-RED, and
make it attractive to individual users as well as Enterprises. Value offered
will increase exponentially as the platform scales to teams of developers and
larger deployment scenarios.
diff --git a/src/handbook/design/art-requests.md b/src/handbook/design/art-requests.md
index b2ac48bb99..8b5a206d6e 100644
--- a/src/handbook/design/art-requests.md
+++ b/src/handbook/design/art-requests.md
@@ -4,7 +4,7 @@ navTitle: Art Requests
## Art Requests
-Across FlowForge it will be a common occurence that we need visual content created. These can be part of development tasks (where you're comfortable doing the development work, but less doing the graphic/illustrative design work) or social/marketing materials.
+Across FlowFuse it will be a common occurence that we need visual content created. These can be part of development tasks (where you're comfortable doing the development work, but less doing the graphic/illustrative design work) or social/marketing materials.
Likely places this will be required are:
@@ -17,7 +17,7 @@ Likely places this will be required are:
### Creating an Art Request
-You can create an issue on any of the FlowForge Repositories that best suits the asset required, e.g:
+You can create an issue on any of the FlowFuse Repositories that best suits the asset required, e.g:
- [flowforge/flowforge](https://github.com/flowforge/flowforge): In-Product Visuals (e.g. icons, diagrams, pictograms)
- [flowforge/website](https://github.com/flowforge/website): Markitechture Diagrams, Blog Tiles, Webinar & AMA Tiles
diff --git a/src/handbook/design/branding.md b/src/handbook/design/branding.md
index a8a4d47423..331d06c904 100644
--- a/src/handbook/design/branding.md
+++ b/src/handbook/design/branding.md
@@ -1,14 +1,14 @@
-# FlowForge Branding Guidelines
+# FlowFuse Branding Guidelines
-For FlowForge Assets (e.g. logos, pictograms, and raw design files), please look in the [`/design/Media`](https://drive.google.com/drive/u/1/folders/1guBnBUrIiRXuK6vsik_NIXIhtE1cZRRa) folder on Google Drive.
+For FlowFuse Assets (e.g. logos, pictograms, and raw design files), please look in the [`/design/Media`](https://drive.google.com/drive/u/1/folders/1guBnBUrIiRXuK6vsik_NIXIhtE1cZRRa) folder on Google Drive.
## Fonts
-In both the FlowForge application and on our website, we use [Tailwind CSS](https://tailwindcss.com/). With Tailwind, comes the `font-sans` class, which we use across FlowForge.
+In both the FlowFuse application and on our website, we use [Tailwind CSS](https://tailwindcss.com/). With Tailwind, comes the `font-sans` class, which we use across FlowFuse.
For branded materials such as videos and images we have two stylized fonts in-use:
- ["DIN Alternate Bold"](https://fontsgeek.com/fonts/DIN-Alternate-Bold): Used in videos & social media content.
-- ["Baloo Da 2"](https://fonts.google.com/specimen/Baloo+Da+2): Used in the FlowForge logo.
+- ["Baloo Da 2"](https://fonts.google.com/specimen/Baloo+Da+2): Used in the FlowFuse logo.
## Colour Palette
+
+
+
+
-
+
+
+
+
+
+ Team Development
+
+
+ + Node-RED team development is made possible with FlowFuse. Different development team members are able to share and collaborate on the same Node-RED instance. This makes for much easier collaboration between Node-RED developers.Ā +
+-
+
- Team membership and access control is controlled from a central administration console. +
- Role based access control allows for restrictions on what team members can access and do while using the FlowFuse platform. +
+
+ {% image "./images/pictograms/collaboration_red.png", "Graphics depicting a team.", [250] %}
+
+
- {% image "./images/pictograms/node_catalog.png", "Graphic of nodes & wires, depicting 'Node-RED'.", [128] %}
- Node-RED, Managed
+
+ Node-RED, Managed
For You
+
+ {% include "components/dividers/light-white-curve.svg" %}
+
+
+
+
+
diff --git a/src/handbook/.github/scripts/package.json b/src/handbook/.github/scripts/package.json
index 3b5bc8c343..65125646e5 100644
--- a/src/handbook/.github/scripts/package.json
+++ b/src/handbook/.github/scripts/package.json
@@ -1,7 +1,7 @@
{
"name": "flowforge-handbook",
"version": "1.0.0",
- "description": "Repository to manage and test all of the content for FlowForge's Company Handbook.",
+ "description": "Repository to manage and test all of the content for FlowFuse's Company Handbook.",
"private": true,
"devDependencies": {
"axios": "^1.2.2",
diff --git a/src/handbook/LICENSE b/src/handbook/LICENSE
index edc9e84146..02153db3c1 100644
--- a/src/handbook/LICENSE
+++ b/src/handbook/LICENSE
@@ -2,4 +2,4 @@ All documentation in this repository is licensed under a Creative Commons Attrib
https://creativecommons.org/licenses/by-sa/4.0/
-Copyright (c) 2021 FlowForge
+Copyright (c) 2021 FlowFuse
diff --git a/src/handbook/company/achieving-success.md b/src/handbook/company/achieving-success.md
index c705667f21..5fa568cd85 100644
--- a/src/handbook/company/achieving-success.md
+++ b/src/handbook/company/achieving-success.md
@@ -4,23 +4,23 @@ meta:
title: KPIs and OKRs
---
-# Achieving Success at FlowForge
+# Achieving Success at FlowFuse
-There's multiple ways to align a company around business goals, and at FlowForge
+There's multiple ways to align a company around business goals, and at FlowFuse
we've identified two ways to help us shape this. The core metric are captured in
the [KPI](#kpi). A KPI is a tool to identify problems and areas for improvement.
-The second tool employed at FlowForge to improve on the identfied problems are [OKR](#okrs)s.
+The second tool employed at FlowFuse to improve on the identfied problems are [OKR](#okrs)s.
## KPI
A KPI, or Key Point Indicator, is used as a heuristic metric for company wide
-success. At FlowForge we're engaged in many initiatives to grow our offering and
+success. At FlowFuse we're engaged in many initiatives to grow our offering and
assess product market fit. At this time there's one KPI to track progress.
### Annual Recurring Revenue (ARR)
-Now FlowForge has a stable and maturing product, we're trying to verify product
+Now FlowFuse has a stable and maturing product, we're trying to verify product
market fit. The market verification requires sales, and ARR is a good metric to
track this.
diff --git a/src/handbook/company/communication.md b/src/handbook/company/communication.md
index 81ec18b238..287f0dbf50 100644
--- a/src/handbook/company/communication.md
+++ b/src/handbook/company/communication.md
@@ -59,9 +59,9 @@ Slack to be matched automatically.
When using Slack, prefer to keep discussions in a thread. This reduces scroll
back, and focusses channels.
-Note that knowledge in Slack is ephemeral, it's not a great storage of information.
-As such knowledge on a decision made in Slack, or elsewhere, should always be recorded
-in the GitHub issue or Google Doc on that topic to keep a log that also works
+Note that knowledge in Slack is ephemeral, it's not storage for information or knowledge
+sharing. As such knowledge and decision made in Slack should always be recorded
+in the handbook, GitHub issue, or Google Doc on that topic to keep a log that also works
for asynchronous communication.
#### Recommended channels
@@ -70,21 +70,25 @@ Not all channels are joined by default when you join Slack. We've added a bunch
below so you get to decide if you want more channels or not.
- `#metrics` will output sales and engagement metrics
-- `#social-twitter` is a stream of engagement with @FlowForgeInc
+- `#social-twitter` is a stream of engagement with @FlowFuseInc
- `#virtual-coffee` to schedule coffee calls with other team members!
#### Channel name structure
-When a channel is created for projects; work that's scoped to a certain topic
-that's going to be completed at some time in the future, it might be valuable to
-collect all internal communications into one Slack channel. Please prefix the
-channel name with `proj-` to make grouping easier.
+To make it easier to find your way around in Slack, we have some rules for naming channels. This will help give everything some context and implicit sense of purpose.
-All team members are advised to put `proj-` channels into [their own section](https://slack.com/help/articles/360043207674-Organize-your-sidebar-with-custom-sections).
+|Type | Slack prefix | Purpose |
+|:--- |:--- |:---|
+| Department | `#dept-` | For each company department and ask them questions |
+| Project based work | `#proj-` | Work scoped to a project with an finite horizon |
+| GitHub notifications | `#gh-` | For many updates around the website and product development a notification is sent to the corresponding channel |
+| Ops notifications | `#ops-` | Channels receiving notifications from operations-related services |
+
+All team members are advised to put prefix type channels into [their own section](https://slack.com/help/articles/360043207674-Organize-your-sidebar-with-custom-sections).
### GitHub
-All code at FlowForge is stored in Git, and GitHub hosts our repositories. As
+All code at FlowFuse is stored in Git, and GitHub hosts our repositories. As
such all our changes, feature ideas/requests, etc. are stored there. It also
holds task lists for onboarding, [art requests](../design/art-requests.md), and
other projects not necessarily code related. It's important to stay in the loop
@@ -126,17 +130,17 @@ two weeks, and what results are expected to the company wide KPI.
## Node-RED community interactions.
-As an employee of FlowForge, when we interact with the OSS Node-RED community we
+As an employee of FlowFuse, when we interact with the OSS Node-RED community we
must be mindful of our position. For example, when offering advice on the Node-RED
forum or the Node-RED slack, the first answer we offer should be how a solution can
be achieved using Node-RED. If a native Node-RED solution is not possible or the
-user would benefit from the advantages that FlowForge offers, then, like any other
-person or company, we can offer FlowForge as a potential solution.
+user would benefit from the advantages that FlowFuse offers, then, like any other
+person or company, we can offer FlowFuse as a potential solution.
## Feedback and Thanks
-In FlowForge, we strongly encourage the sharing of feedback and thank you's. We have
-a custom-built SlackBot (built in Node-RED and hosted in FlowForge of course), that
+In FlowFuse, we strongly encourage the sharing of feedback and thank you's. We have
+a custom-built SlackBot (built in Node-RED and hosted in FlowFuse of course), that
enables users to message `@Feedback` with:
- `/give-thanks @to_user
+
+
+
-
+
+
+
+
+
+ Security Built-in to your Node-RED instances
+
+
+ + FlowFuse has built-in security for your Node-RED instances.Ā Ā +
+-
+
- All Node-RED instances are accessed using TLS/SSL. +
- Single Sign-on (SSO) allows for users to sign in to FlowFuse using an existing SAML identity provider. +
- Audit logs keep track of all changes that occur to a Node-RED instance and which user was responsible for the change. +
+
+ {% image "./images/pictograms/security_red.png", "Graphics depicting a lock.", [250] %}
+
+
- {% image "./images/pictograms/browser.png", "Graphic of a globe, depicting FlowForge being full browser-based.", [128] %}
-
+ Full Browser-Based
+
+ {% include "components/dividers/light-grey-curve.svg" %}
+
+
+
+
+
+
+
+
+ Adopt FlowFuse Today
+
+
+
+
+
+
+
+
+ +
+ Install FlowFuse on your own hardware for increased deployment flexibility. You can use the open source version of FlowFuse to install it on-premises and support the deployment yourselves.Ā
+
+
+
+ Install now
+
+
+
+
+
+
+ +
+ Our managed hosted solution, maintained and supported by the FlowFuse team. Experience flexibility, scalability, and expert assistance to drive your business forward.
+
+
+
+ TRY FOR FREE
+
+
+
+
+
+ +
+ Do you want to know what adopting FlowFuse could mean for your company?
+ Customers can purchase an enterprise license fo FlowFuse to install on premise and obtain support from FlowFuse.Ā
+
+
+
+ Book a demo
+
+
@@ -203,9 +203,23 @@ These larger images are used for stylistic purposes. We use pictograms to commun
If you wish to create your own Pictograms, you can use this Adobe Illustrator file as a template:
[pictogram.ai](https://drive.google.com/drive/u/1/folders/1guBnBUrIiRXuK6vsik_NIXIhtE1cZRRa)
-
+
Sizings:
- **128 x 128px**: Used when showing multiple pictograms in the same section of the website or application.
- **250 x 250 px:** Used as part of page headers, inline with the page title and page description.
+
+## Presentations
+
+There's a **branded theme** for Google Slides presentations available in the [FlowFuse template gallery](https://docs.google.com/presentation/u/0/?tgif=d&ftv=1). To access it, you need to be logged in to your FlowFuse account. Look for a theme called "FlowFuse Template".
+
+When you click on it, two things will happen:
+1. A new Google Slides file will be created in your Drive with the theme applied.
+2. The copy of the file will open for editing.
+
+You'll find a fully designed presentation as an example of how to use different layouts. To explore all the predefined options available, check the [Layout menu](https://support.google.com/docs/answer/1705254?hl=en&ref_topic=19434&sjid=8039782987794605660-EU#zippy=%2Cchange-layout:~:text=your%20theme%20colors-,Change%20layout,-A%20layout%20is).
+
+Feel free to edit the content, delete or add slides as needed. Any changes you make will only affect your copy in your Drive.
+
+Please note that the theme has predefined typography, margins, and colors. We kindly request that any changes made maintain these design elements as part of the overall composition and design of your presentation.
\ No newline at end of file
diff --git a/src/handbook/design/design-thinking.md b/src/handbook/design/design-thinking.md
index 22de40ef0b..23f83602ba 100644
--- a/src/handbook/design/design-thinking.md
+++ b/src/handbook/design/design-thinking.md
@@ -4,7 +4,7 @@ navTitle: Design Thinking
## Design Thinking
-At FlowForge, we practice Design Thinking when considering our UI design and wider decisions influencing the overall user experience of FlowForge.
+At FlowFuse, we practice Design Thinking when considering our UI design and wider decisions influencing the overall user experience of FlowFuse.
> Design Thinking is a non-linear, iterative process that teams use to understand users, challenge assumptions, redefine problems and create innovative solutions to prototype and test.
>
@@ -17,7 +17,7 @@ found within [FigJam](./tools#figjam-(more-info)), we have also written up some
### User Personas
-Personas are fictional characters that represent the different users we expect to interact with FlowForge as a brand and/or platform. At FlowForge, we have many personas that will evolve over time, we have written up some of our Personas [here](../product/personas/).
+Personas are fictional characters that represent the different users we expect to interact with FlowFuse as a brand and/or platform. At FlowFuse, we have many personas that will evolve over time, we have written up some of our Personas [here](../product/personas/).
+
Sizings:
- **128 x 128px**: Used when showing multiple pictograms in the same section of the website or application.
- **250 x 250 px:** Used as part of page headers, inline with the page title and page description.
+
+## Presentations
+
+There's a **branded theme** for Google Slides presentations available in the [FlowFuse template gallery](https://docs.google.com/presentation/u/0/?tgif=d&ftv=1). To access it, you need to be logged in to your FlowFuse account. Look for a theme called "FlowFuse Template".
+
+When you click on it, two things will happen:
+1. A new Google Slides file will be created in your Drive with the theme applied.
+2. The copy of the file will open for editing.
+
+You'll find a fully designed presentation as an example of how to use different layouts. To explore all the predefined options available, check the [Layout menu](https://support.google.com/docs/answer/1705254?hl=en&ref_topic=19434&sjid=8039782987794605660-EU#zippy=%2Cchange-layout:~:text=your%20theme%20colors-,Change%20layout,-A%20layout%20is).
+
+Feel free to edit the content, delete or add slides as needed. Any changes you make will only affect your copy in your Drive.
+
+Please note that the theme has predefined typography, margins, and colors. We kindly request that any changes made maintain these design elements as part of the overall composition and design of your presentation.
\ No newline at end of file
diff --git a/src/handbook/design/design-thinking.md b/src/handbook/design/design-thinking.md
index 22de40ef0b..23f83602ba 100644
--- a/src/handbook/design/design-thinking.md
+++ b/src/handbook/design/design-thinking.md
@@ -4,7 +4,7 @@ navTitle: Design Thinking
## Design Thinking
-At FlowForge, we practice Design Thinking when considering our UI design and wider decisions influencing the overall user experience of FlowForge.
+At FlowFuse, we practice Design Thinking when considering our UI design and wider decisions influencing the overall user experience of FlowFuse.
> Design Thinking is a non-linear, iterative process that teams use to understand users, challenge assumptions, redefine problems and create innovative solutions to prototype and test.
>
@@ -17,7 +17,7 @@ found within [FigJam](./tools#figjam-(more-info)), we have also written up some
### User Personas
-Personas are fictional characters that represent the different users we expect to interact with FlowForge as a brand and/or platform. At FlowForge, we have many personas that will evolve over time, we have written up some of our Personas [here](../product/personas/).
+Personas are fictional characters that represent the different users we expect to interact with FlowFuse as a brand and/or platform. At FlowFuse, we have many personas that will evolve over time, we have written up some of our Personas [here](../product/personas/).
diff --git a/src/handbook/design/index.md b/src/handbook/design/index.md
index fa2bf24181..d6fe35f534 100644
--- a/src/handbook/design/index.md
+++ b/src/handbook/design/index.md
@@ -6,7 +6,7 @@ navGroup: Development & Design Practices
## Design
This section of our handbook contains all details related to how we design content
-at FlowForge. From our Branding Guidelines, with logos and color palettes, through
+at FlowFuse. From our Branding Guidelines, with logos and color palettes, through
to how we plan design work and ensure empathy for users through Design Thinking.
- [Branding](./branding/)
diff --git a/src/handbook/design/process.md b/src/handbook/design/process.md
index 698d35bc11..c42592af8a 100644
--- a/src/handbook/design/process.md
+++ b/src/handbook/design/process.md
@@ -1,13 +1,15 @@
-## Process
+# Process
-### Art Requests
+## Art Requests
If you want something designed or drawn, then please follow the details in
[Art Requests](./art-requests.md) in order to have your request be picked up by an available designer.
-### Scheduling
+## Scheduling
-The Design process is bound by the [Development Cadence](../development/releases/planning#cadence),
+### Product design
+
+The Design process is bound by the [Development Cadence](../development/releases/planning#cadence).
Work begins on formal design (mid and high-fidelity UX and visual design assets)
two weeks prior to a release cycle beginning.
@@ -16,7 +18,23 @@ been conducted on the high-level UX, and development is not blocked at the start
of a release sprint. Both visual and UX design iterations will occur throughout the
first two weeks of a cycle, alongside development efforts.
-### Delivery of Art
+### Website and rest of design assets
+
+In contrast to the platform, changes and updates to the web design can be implemented independently and are not limited to specific release cycles. The timing and order of these changes, as well as the creation of other design assets such as blog images, open graphs, presentations, illustrations, etc., depend on prioritization aligned with the company's interests.
+
+## Design Review
+
+This phase aims to ensure that the designs not only look visually appealing, but also effectively communicate the intended message to the audience.
+
+To achieve this, please assess the organization of information, evaluate the readability and coherence of text, and verify the alignment with the project's objectives.
+
+All design proposals, including UX/UI and other design assets, will be presented and signed off in GitHub, ensuring one source of truth and centralizing the process for all design-related work.
+
+For UX/UI proposals, the design review concludes with the sign-off of Figma designs by the page owner, who is usually the DRI for the Website but may be another team member. As for the rest of the design assets, it's determined by the person who created the Art Request.
+
+While iterations can be made during the development phase for UX/UI design in terms of content and layout, it is recommended to facilitate feedback loops during the design phase. By getting early feedback, we aim to identify and address any potential issues before entering the development phase. This approach helps streamline the design workflow, allowing for quicker iterations and ultimately saving time.
+
+## Delivery of Art
While the art request will include a delivery method of the assets, please be
sure to also always export the asset to the [Design directory](https://drive.google.com/drive/folders/1PiuFwW3H8XuydolepmfQQ4BjcdNekVQg){rel="nofollow"}
diff --git a/src/handbook/design/tools.md b/src/handbook/design/tools.md
index 70eda6d24b..253c129925 100644
--- a/src/handbook/design/tools.md
+++ b/src/handbook/design/tools.md
@@ -9,7 +9,7 @@ Figma is used to construct mid- and high-fidelity designs. We have two primary w
- Website
- Platform
-Underlying each of these Figma files is a standardised component library, which coincides with FlowForge's `forge-ui-component` library.
+Underlying each of these Figma files is a standardised component library, which coincides with FlowFuse's `forge-ui-component` library.
### FigJam ([more info](https://www.figma.com/figjam/))
@@ -22,9 +22,9 @@ Any in-person whiteboard discussions should have a documented digital copy. Addi
For visual design elements of the user interface and public-facing material, we predominantly use Adobe Illustrator and Adobe After Effects.
-- **Illustrator** provides us tooling to create high-quality, static SVG assets to supplement the user experience on both the website and the FlowForge platform.
+- **Illustrator** provides us tooling to create high-quality, static SVG assets to supplement the user experience on both the website and the FlowFuse platform.
-- **After Effects** enables the generation of animated SVG elements. In particular, we work with [Lottie Files](https://lottiefiles.com/) for injection into both our website and FlowForge platform.
+- **After Effects** enables the generation of animated SVG elements. In particular, we work with [Lottie Files](https://lottiefiles.com/) for injection into both our website and FlowFuse platform.
Other tools included in the Creative Cloud suite that may be useful include:
diff --git a/src/handbook/development/ab-testing.md b/src/handbook/development/ab-testing.md
index cbd297b097..3d8d8c7fd7 100644
--- a/src/handbook/development/ab-testing.md
+++ b/src/handbook/development/ab-testing.md
@@ -8,7 +8,7 @@ A/B Testing is a very useful exercise by which we can distribution variants of a
## Defining a Test
-A/B Tests can be proposed via the "A/B Testing" issue template on the [FlowForge Website repository](https://github.com/flowforge/website/issues/new/choose). These issues are used to track findings. Results will be shared here from PostHog, and will provide a searchable source in the future if we want to reference historical A/B tests when proposiing new ideas that we may have already tried.
+A/B Tests can be proposed via the "A/B Testing" issue template on the [FlowFuse Website repository](https://github.com/flowforge/website/issues/new/choose). These issues are used to track findings. Results will be shared here from PostHog, and will provide a searchable source in the future if we want to reference historical A/B tests when proposiing new ideas that we may have already tried.
### What are your variants?
@@ -22,7 +22,7 @@ You must have a trackable metric that the variants can compete over. Example suc
- Clicks of a certain button, e.g. a primary or secondary CTA
- $pageview events of a certain URL
-- Number of Instances spun up on FlowForge
+- Number of Instances spun up on FlowFuse
## How we run A/B Tests
diff --git a/src/handbook/development/frontend/index.md b/src/handbook/development/frontend/index.md
index f2d834f719..7066cdbec8 100644
--- a/src/handbook/development/frontend/index.md
+++ b/src/handbook/development/frontend/index.md
@@ -4,7 +4,7 @@ navTitle: Front End
### Front-End
-A collection of how-to's and best practice guides for FlowForge's front-end development.
+A collection of how-to's and best practice guides for FlowFuse's front-end development.
- [Data Attributes](./data-attributes.md)
- [Services](./services.md)
diff --git a/src/handbook/development/frontend/services.md b/src/handbook/development/frontend/services.md
index a3a4ced8d1..b5085e39b0 100644
--- a/src/handbook/development/frontend/services.md
+++ b/src/handbook/development/frontend/services.md
@@ -7,7 +7,7 @@ meta:
The frontend contains two helper services that can be called anywhere in the UI. Each of the services control components built into the main `Platform.vue`.
Here we see an example of a `Dialog` being used to confirmed deletion of a snapshot, followed by confirmation of the deletion via an `Alert`.
diff --git a/src/handbook/development/frontend/testing.md b/src/handbook/development/frontend/testing.md
index 22c8a5c569..d2ac438c08 100644
--- a/src/handbook/development/frontend/testing.md
+++ b/src/handbook/development/frontend/testing.md
@@ -67,7 +67,7 @@ To make Cypress testing easier, we have created a collection of helper functions
```js
cy.login(, )
```
-This will log you into FlowForge as the given user. The test users are defined in the [test environment](https://github.com/flowforge/flowforge/blob/main/test/e2e/frontend/environments/standard.js).
+This will log you into FlowFuse as the given user. The test users are defined in the [test environment](https://github.com/flowforge/flowforge/blob/main/test/e2e/frontend/environments/standard.js).
```js
cy.home()
diff --git a/src/handbook/development/git-how-to.md b/src/handbook/development/git-how-to.md
index d8d091d719..d860e96a65 100644
--- a/src/handbook/development/git-how-to.md
+++ b/src/handbook/development/git-how-to.md
@@ -5,7 +5,7 @@ navTitle: Using Git
## Background
-[Git](#git) is a way for a team to create written content, track any changes to that content, and seek approval for any changes to become the [Published](#publish) version of that content on [Live](#live). [Git](#git) can be used in many ways, our developers use it to write the code which makes FlowForge work. In this guide we are focusing on the process of working with documents within our company [Handbook](#handbook) or website. We will use [Git](#git)'s terminology to describe how we are working. This guide also assumes you are using [Github](#github).com to edit the [Handbook](#handbook) and website.
+[Git](#git) is a way for a team to create written content, track any changes to that content, and seek approval for any changes to become the [Published](#publish) version of that content on [Live](#live). [Git](#git) can be used in many ways, our developers use it to write the code which makes FlowFuse work. In this guide we are focusing on the process of working with documents within our company [Handbook](#handbook) or website. We will use [Git](#git)'s terminology to describe how we are working. This guide also assumes you are using [Github](#github).com to edit the [Handbook](#handbook) and website.
When making changes to a [Project](#project) at least two people have to agree that the changes should be Published. In most cases those two people would be yourself and a [Reviewer](#reviewer).
@@ -47,7 +47,7 @@ If another person has opened a Pull Request or branch already, and asked you to
You may be asked to conduct a Pull Request Review. This means that someone else has contributed some work, and would like you to check whether it works, and whether you're happy with the contributions made. These are the steps by which you can do that:
1. Switch to their branch on your machine (if request to append to the Pull Request, that will have a branch associated to.)
-2. Run the code (e.g. website server or FlowForge platform) and ensure their changes work as expected.
+2. Run the code (e.g. website server or FlowFuse platform) and ensure their changes work as expected.
3. "Add your Review" on GitHub, offer comments and recommendatins where required.
4. Once you're happy, "Approve" the Pull Request
5. Merge the PR
@@ -74,7 +74,7 @@ You can now start the process of actually creating or editing content, any chang
### Create a new file (document)
-In this example I am going to create a new document in the [Handbook](#handbook) which will help non-technical FlowForge team members use [Git](#git).
+In this example I am going to create a new document in the [Handbook](#handbook) which will help non-technical FlowFuse team members use [Git](#git).
Firstly I will create a new document called git-how-to.md in the design folder.
@@ -104,7 +104,7 @@ I am now ready to request a [Review](#review) of my work from a colleague. To do
It's a good idea to provide your colleagues descriptive comments explaining the goals of the changes you have made as well as anything else you think would help them [review](#review) your work.
-Once you press the 'Create pull request' button an alert will be sent to one of FlowForge's Slack channels letting everyone know you'd like your work reviewed. You can also request a [review](#review) from a specific colleague using the [Reviewers](#reviewer) section of your [Pull Request](#pull-request) Click on [Reviewers](#reviewer) then select the colleague you think would be best placed to [review](#review) your work.
+Once you press the 'Create pull request' button an alert will be sent to one of FlowFuse's Slack channels letting everyone know you'd like your work reviewed. You can also request a [review](#review) from a specific colleague using the [Reviewers](#reviewer) section of your [Pull Request](#pull-request) Click on [Reviewers](#reviewer) then select the colleague you think would be best placed to [review](#review) your work.
@@ -154,7 +154,7 @@ A website which allows you to manage [Git](#git). Github also allows you to comm
### Handbook
-FlowForge's public document explaining how run the company.
+FlowFuse's public document explaining how run the company.
### Live
@@ -166,11 +166,11 @@ A method to add formatting to a document by adding additional characters around
### Markdown
-A [Markup](#markup) language for formatting content in documents. You can read more in this [guide](https://www.markdownguide.org/). FlowForge uses Markdown to format content for our website and [Handbook](#handbook)
+A [Markup](#markup) language for formatting content in documents. You can read more in this [guide](https://www.markdownguide.org/). FlowFuse uses Markdown to format content for our website and [Handbook](#handbook)
### Project
-A collection of documents and content which usually relate to a specific topic. In this guide we are discussing how to edit two FlowForge Projects, our website and our [Handbook](#handbook).
+A collection of documents and content which usually relate to a specific topic. In this guide we are discussing how to edit two FlowFuse Projects, our website and our [Handbook](#handbook).
### Publish
diff --git a/src/handbook/development/how-we-work/index.md b/src/handbook/development/how-we-work/index.md
index 77faee8292..c7faaa9273 100644
--- a/src/handbook/development/how-we-work/index.md
+++ b/src/handbook/development/how-we-work/index.md
@@ -2,7 +2,7 @@
navTitle: How We Work
---
-This section is useful to read if you are going to be contributing to FlowForge. It contains
+This section is useful to read if you are going to be contributing to FlowFuse. It contains
details on our development best practices, security practices and how to navigate and understand
our GitHub processes.
diff --git a/src/handbook/development/how-we-work/packaging.md b/src/handbook/development/how-we-work/packaging.md
index 6268dcec47..602a0860c9 100644
--- a/src/handbook/development/how-we-work/packaging.md
+++ b/src/handbook/development/how-we-work/packaging.md
@@ -172,7 +172,7 @@ The process for making a release is documented [here](../releases/process.md).
### Adding NPM packages to Stacks
-As we build more FlowForge specific nodes we will need to add these to the Stacks
+As we build more FlowFuse specific nodes we will need to add these to the Stacks
#### Localfs
diff --git a/src/handbook/development/how-we-work/security.md b/src/handbook/development/how-we-work/security.md
index 977b18662a..59de7ad14f 100644
--- a/src/handbook/development/how-we-work/security.md
+++ b/src/handbook/development/how-we-work/security.md
@@ -5,7 +5,7 @@ navTitle: Security Policy
## Reporting a Vulnerability
-Please report any vulnerabilities discovered in FlowForge products to security@flowforge.com.
+Please report any vulnerabilities discovered in FlowFuse products to security@flowfuse.com.
We will endeavour to acknowledge and fix any reported vulnerabilities ASAP based
on its severity and assessed impact to our users.
@@ -16,7 +16,7 @@ At our sole discretion, we offer rewards for responsibly disclosed issues accord
to their severity.
Please note the following are general guidelines and any reward decisions are up
-to the discretion of FlowForge. We keep these reward levels under review to ensure
+to the discretion of FlowFuse. We keep these reward levels under review to ensure
they provide a fair reflection of the issues being reported.
diff --git a/src/handbook/development/how-we-work/staging.md b/src/handbook/development/how-we-work/staging.md
index ea9a9a637c..e34e23e2eb 100644
--- a/src/handbook/development/how-we-work/staging.md
+++ b/src/handbook/development/how-we-work/staging.md
@@ -4,7 +4,7 @@ navTitle: Staging Environment
## Staging Environment
We have a staging environment running on AWS which is a scaled down replica of
-our managed FlowForge offering, with a separate domain. Staging URL and sign in
+our managed FlowFuse offering, with a separate domain. Staging URL and sign in
details can be found in the Developer Vault in 1Password.
### AWS Account
@@ -46,7 +46,7 @@ Currently there is no auto deployment to staging, this should be rectified in th
When setting up a team you'll need to enter billing details. For credit card
details, use [the Stripe mock data](https://stripe.com/docs/testing#testing-interactively).
-### Using the FlowForge Device Agent with staging
+### Using the FlowFuse Device Agent with staging
Staging uses pre-release npm packages stored in a GitHub npm repository. To be able to use these packages you will need to authenticate with the repository.
diff --git a/src/handbook/development/index.md b/src/handbook/development/index.md
index 7272b76826..77a29f4a4c 100644
--- a/src/handbook/development/index.md
+++ b/src/handbook/development/index.md
@@ -17,7 +17,7 @@ navGroup: Development & Design Practices
- [Process](./releases/process.md)
### Front-End
-A collection of how-to's and best practice guides for FlowForge's front-end development.
+A collection of how-to's and best practice guides for FlowFuse's front-end development.
- [Data Attributes](./frontend/data-attributes.md)
- [Services](./frontend/services.md)
- [Testing](./frontend/testing.md)
\ No newline at end of file
diff --git a/src/handbook/development/packaging.md b/src/handbook/development/packaging.md
index a8183af67d..b8eef7dfcf 100644
--- a/src/handbook/development/packaging.md
+++ b/src/handbook/development/packaging.md
@@ -2,7 +2,7 @@
originalPath: development/packaging.md
updated: 2022-11-24 22:12:28 +0000
---
-# FlowForge Packaging Guidelines
+# FlowFuse Packaging Guidelines
This section describes the requirements we have for all GitHub repositories,
and npm modules we maintain.
@@ -91,14 +91,16 @@ ensures we have a consistent approach to planning and tracking of work.
- Type: `epic`, `story`, `task`, `bug`
- Sizing: `1`, `2`, `3`, `5`, `8`, `13`
- - Area: `area:docs`, `area:db`, `area:migration`, `area:frontend`, `area:api`, `area:device`
- - Priority: `priority:high`, `priority:medium`, `priority:low`
+ - Area: `area:docs`, `area:db`, `area:migration`, `area:frontend`, `area:api`, `area:device`, `area:marketing`, `area:customer-success`
+ - Priority: `priority:high`, `priority:medium`, `priority:low`, `Customer Request`
- Status: `blocked`
- Product Scope: `scope:devices`, `scope:enterprise`, `scope:node-red`, `scope:collaboration`
- Other: `good first issue`, `upstream`, `needs-triage`
The labels are synchronized across the repositories via a GitHub Action in the [`.github`](https://github.com/flowforge/.github)
repository.
+
+The `Customer Request` label is intended solely for issues requested by an important enterprise customer, not for leads or individuals like [Harry the Hobbyist](../product/personas/).
New repositories must be added to the list in [`flowforge-repositories.yml`](https://github.com/flowforge/.github/blob/main/flowforge-repositories.yml),
and then the [Synchronize Labels](https://github.com/flowforge/.github/actions/workflows/sync-labels.yml) action manually run.
@@ -168,12 +170,12 @@ section of the handbook.
A Fix release can be made at any time, depending on the best judgement of the engineer making the fix but requires a review by another team member.
-The process for making a release is documented [here](./release.md).
+The process for making a release is documented [here](./releases/process/).
### Adding NPM packages to Stacks
-As we build more FlowForge specific nodes we will need to add these to the Stacks
+As we build more FlowFuse specific nodes we will need to add these to the Stacks
#### Localfs
diff --git a/src/handbook/development/releases/digital-ocean.md b/src/handbook/development/releases/digital-ocean.md
index 32faebe667..d9eabc35d4 100644
--- a/src/handbook/development/releases/digital-ocean.md
+++ b/src/handbook/development/releases/digital-ocean.md
@@ -10,7 +10,7 @@ repository a GitHub Action will run and rebuild the image.
Once complete the Release Manager should post to the #dev slack chanel to ask somebody with
Digital Ocean access to do the following steps.
- 1. Log into the FlowForge team on Digital Ocean
+ 1. Log into the FlowFuse team on Digital Ocean
2. Navigate to the "Images" section, from the "Manage" options in the left hand menu
3. Select the new image from the "Droplets" list and click on "More"
diff --git a/src/handbook/development/releases/planning.md b/src/handbook/development/releases/planning.md
index befc738a8c..322a22205f 100644
--- a/src/handbook/development/releases/planning.md
+++ b/src/handbook/development/releases/planning.md
@@ -8,7 +8,7 @@ Instructions for creating a release are [here](./process.md).
### Cadence
-FlowForge is released every four weeks, on a Thursday. We track releases using
+FlowFuse is released every four weeks, on a Thursday. We track releases using
GitHub Milestones. The current schedule of releases can be seen [here](https://github.com/flowforge/flowforge/milestones).
Our planning process is continually evolving as we find the right way to accommodate
@@ -20,6 +20,13 @@ We use GitHub issues for planning the work in a release. A Milestone should exis
for the current release (N) and the next one (N+1). We do not schedule work beyond
that as priorities can change through a release.
+---
+#### Week 2 - UX Planning
+
+##### Tuesday
+- UX Pre-Planning
+ - This meeting is conducted between the Product Manager (PM) and the Head of User Experience (UX), it is designed to discuss and identify potential UX issues and requirements that need to be addressed in the upcoming iteration. The goal is to be proactive in identifying and resolving UX-related challenges before the start of the development phase.
+
---
#### Week 3 - Planning Week
@@ -81,7 +88,7 @@ We label some items as `headline`. These are items we want to highlight in the r
announcement material and should clearly describe the value they bring to our users.
#### Effort Estimation
-To more accurately understand which tasks can be scheduled without overloading our team, everyone conducts an initial, high-level analysis when creating an issue to assign weight estimates. We recognize that these estimates might not be precise. If the person who creates an issue cannot provide an estimate, any FlowForge team member is welcome to contribute one.
+To more accurately understand which tasks can be scheduled without overloading our team, everyone conducts an initial, high-level analysis when creating an issue to assign weight estimates. We recognize that these estimates might not be precise. If the person who creates an issue cannot provide an estimate, any FlowFuse team member is welcome to contribute one.
If a developer, who is an expert in a field, wants to change an estimation, they are encouraged to do so immediately. There is no blame for "wrong" estimation; we all have to work together to achieve good planning. It is better to have a rough estimation than no estimation at all. The final decision on estimations in general lies with the CTO.
@@ -167,7 +174,7 @@ are thus required before the design sprint start.
### Retrospective/Kick-Off
-The day after each FlowForge release, always a Friday, a meeting is scheduled
+The day after each FlowFuse release, always a Friday, a meeting is scheduled
by the CTO. This meeting includes 2 parts:
1. A retrospective on the last release. This should capture feedback on what
diff --git a/src/handbook/development/releases/process.md b/src/handbook/development/releases/process.md
index 018919f4e5..d730289520 100644
--- a/src/handbook/development/releases/process.md
+++ b/src/handbook/development/releases/process.md
@@ -10,7 +10,7 @@ We do two types or releases:
## Scheduled Releases
-We publish a new release of FlowForge in line with our [release plan](./planning.md#cadence). Each
+We publish a new release of FlowFuse in line with our [release plan](./planning.md#cadence). Each
release has a Release Manager who oversees the process. This role rotates around
the team to ensure everyone is able to do it and that we don't have any single
points of failure in the process.
@@ -26,6 +26,7 @@ iteration:
- git command-line tools
- Ensure ssh key access is setup so git interactions do not require continual
password typing - `ssh -T git@github.com`
+ - Ensure you have git configured with an appropriate `user.name` and `user.email`
- [GitHub client](https://github.com/cli/cli)
- Ensure the client is logged in using `gh auth login`
- [jq](https://stedolan.github.io/jq/download/)
@@ -95,60 +96,43 @@ If any need to be updated, refer to the section [Unmanaged Releases](#unmanaged-
### Phase Two
-There are three scripts used run the release
+This phase is largely automated using the `create-release` script in the `admin` repository.
- - `checkout-release` - ensures a clean copy of all required code is checked out locally
- - `prepare-release` - publishes a PR against each repository that updates the version number and changelogs as needed
- - `create-release` - creates the GitHub Releases
-
-Follow these steps to run the scripts:
+Follow these steps to run the script:
1. Clone the [`flowforge/admin`](https://github.com/flowforge/admin) repository if you do not already have it.
Ensure you have the latest with a `git pull`.
2. In the *parent* directory to where you have the `admin` checked out, run the
following command, replace `1.x.y` with the proper release version.
```bash
- ./admin/checkout-release 1.x.y
- ```
- This will create a directory called `release-1.x.y` and checkout all of the releasable
- repositories under it.
- **NOTE:** If you do not have a global git configuration, you will need to set `user.name` and `user.email`
- in each of those repositories.
-3. Within the release directory run:
- ```bash
- cd release-1.x.y
- ../admin/prepare-release 1.x.y
- ```
- This will check all of the repositories are ready to be released. This includes
- listing any open pull-requests. The Release Manager should check nothing has been
- missed. The script will then update the `package.json` files to reflect the
- new version (including cross-package dependencies) and update the `CHANGELOG` files.
-
- It will then raise PRs against each repository with these changes in.
-
- **Note:** Some PRs will fail their tests at this stage because they want to
- install versions of packages that have not been published yet in the process.
- This is normal and will be dealt with in the next step.
-4. Run the next script in the process:
- ```bash
- ../admin/create-release 1.x.y
+ ./admin/create-release 1.x.y
```
- For each repository in the release process it:
- - Checks all npm dependencies have been published. If any are missing it blocks
- until the user asks it to check again.
- - Checks if there are any open PRs in the repository. This will include the
- Release PR created in the previous step.
- The Release Manager should get the Release PR (and any others that have been
- missed at this late state) reviewed and merged before allowing the script to continue.
- This includes ensuring the tests are passing cleanly.
- **Note:** This will require a second person to do the review as the RM cannot
- approve their own PRs.
- - The script will then create a *draft* GitHub release and provide its URL.
- The Release Manager should review the draft - check the changelog looks
- appropriate and take note of any first-time contributors to provide to the
- release blog post author.
- - The script will then publish the release and move onto the next repository.
-5. Digital Ocean Droplet requires a manual step once the GitHub Action has finished,
+
+ This will create a directory called `release-1.x.y`.
+
+ Then, for each managed repository in turn it will:
+
+ - Checks if a matching GitHub release already exists, if so it moves on to the next repo.
+ - Checks for any outstanding PRs and waits for confirmation to continue if it finds any.
+ - Checks to see if the repo has already been cloned into the release directory.
+ - if it has been, ensures it is on `main` and pulls from origin
+ - otherwise, clones it
+ - Checks that all @flowforge/* dependencies are on npm at the matching version
+ - If any dependency is missing, it waits for you to ask it to check again.
+ - Creates a clean `release-x.y.z` branch
+ - Updates CHANGELOG, package.json and package-lock.json files and commits changes
+ - Pushes changes back to GitHub
+ - Opens a PR
+ - At this point, the PR should be reviewed to ensure all updates look correct
+ and all tests are passing. Once merged, the process can continue.
+ - Checks the outstanding PRs again - waits for confirmation to continue
+ - Creates a *draft* GitHub release and provides its url.
+ - The Release Manager should review the draft - check the release notes look appropriate
+ and take note of any first-time contributors from outside the FF team.
+ - The script waits for you to confirm you have reviewed the draft
+ - Publishes the release and moves onto the next repo
+
+3. Digital Ocean Droplet requires a manual step once the GitHub Action has finished,
follow [these](./digital-ocean.md) steps to have the new image reviewed and published
### Phase Three
@@ -157,7 +141,7 @@ Once everything has been published, the Release Manager should:
1. Run the staging CI pipeline [Build for Staging](https://github.com/flowforge/CloudProject/actions/workflows/build-kube.yml) against the main branch, to ensure staging is running the latest release.
- Once that completes, verify it has deployed cleanly on Staging
-2. Raise a "FlowForge Cloud Change Requests" Issue in [CloudProject Project](https://github.com/flowforge/CloudProject/issues/new/choose) to request Production to be updated to the new version.
+2. Raise a "FlowFuse Cloud Change Requests" Issue in [CloudProject Project](https://github.com/flowforge/CloudProject/issues/new/choose) to request Production to be updated to the new version.
3. Notify the CTO/Senior Engineer that the release is ready to publish to production.
Once Production has been updated and verified, the Release Manager should announce
@@ -212,5 +196,5 @@ All release activity should be highlighted in #dev so the team is aware.
## Launch Lunch
-To celebrate the launch of a new version of FlowForge, we organize a lunch on
+To celebrate the launch of a new version of FlowFuse, we organize a lunch on
the release day. See also the [peopleops section](../../peopleops/compensation#launch-lunch).
diff --git a/src/handbook/development/security.md b/src/handbook/development/security.md
index 51039bf86d..8981fc3527 100644
--- a/src/handbook/development/security.md
+++ b/src/handbook/development/security.md
@@ -2,11 +2,17 @@
originalPath: development/security.md
updated: 2022-08-04 17:05:04 +0100
---
-#Ā Security Policy
+
+# Security Policy
+
+This policy relates to external disclosures of potential vulnerabilities in the
+FlowFuse platform and associated components.
+
+Our internal Incident Response plan is documented [here](../company/security/incident-response.md).
## Reporting a Vulnerability
-Please report any vulnerabilities discovered in FlowForge products to security@flowforge.com.
+Please report any vulnerabilities discovered in FlowFuse products to security@flowfuse.com.
We will endeavour to acknowledge and fix any reported vulnerabilities ASAP based
on its severity and assessed impact to our users.
@@ -17,7 +23,7 @@ At our sole discretion, we offer rewards for responsibly disclosed issues accord
to their severity.
Please note the following are general guidelines and any reward decisions are up
-to the discretion of FlowForge. We keep these reward levels under review to ensure
+to the discretion of FlowFuse. We keep these reward levels under review to ensure
they provide a fair reflection of the issues being reported.
diff --git a/src/handbook/development/staging.md b/src/handbook/development/staging.md
index 47bb628db8..f4e57c2689 100644
--- a/src/handbook/development/staging.md
+++ b/src/handbook/development/staging.md
@@ -5,7 +5,7 @@ updated: 2022-11-24 12:11:19 +0100
# Staging Environment
We have a staging environment running on AWS which is a scaled down replica of
-our managed FlowForge offering, with a separate domain. Staging URL and sign in
+our managed FlowFuse offering, with a separate domain. Staging URL and sign in
details can be found in the Developer Vault in 1Password.
## AWS Account
@@ -26,7 +26,7 @@ smallest instance that can be used with EKS.
The staging environment can only be used with a set of pre-approved email addresses. This currently includes:
- - All `@flowforge.com` addresses - with SSO enabled
+ - All `@flowfuse.com` addresses - with SSO enabled
- A collection of disposable email accounts that can be used to test user sign-up/invitations etc. Details of the available addresses are in [this issue](https://github.com/flowforge/CloudProject/issues/135). If you use one of these addresses for some testing, please delete the user once you are done so it is available for future use.
The list of valid email addresses is managed via the Amazon SES configuration in the staging acount.
@@ -40,7 +40,7 @@ Currently there is no auto deployment to staging, this should be rectified in th
When setting up a team you'll need to enter billing details. For credit card
details, use [the Stripe mock data](https://stripe.com/docs/testing#testing-interactively).
-## Using the FlowForge Device Agent with staging
+## Using the FlowFuse Device Agent with staging
Staging uses pre-release npm packages stored in a GitHub npm repository. To be able to use these packages you will need to authenticate with the repository.
diff --git a/src/handbook/index.md b/src/handbook/index.md
index 07718d57ae..0ae933dcb1 100644
--- a/src/handbook/index.md
+++ b/src/handbook/index.md
@@ -2,43 +2,56 @@
navTitle: Handbook
---
-## Introduction
+# FlowFuse Handbook
-This handbook contains all the information about how FlowForge Inc. is run.
-
-It's a living set of documents - they will evolve with time and expand as we learn
+This handbook contains all the information about how FlowFuse is run. It's a
+living set of documents - they will evolve with time and expand as we learn
and discover new things.
-The handbook is here for the whole company to help maintain. Pull-requests are welcome
-and strongly encouraged.
+Whilst instinctively we want to be open in all we do, there will inevitably be
+content that is [not appropriate to make public][data-class]. That content is not
+shared in this handbook.
+
+[data-class]: /handbook/company/security/data-management/#data-classification
-### Company
+The handbook is here for the whole company to help maintain. Pull-requests are welcome and [strongly encouraged](#contributing).
- - [Values](./company/values.md)
- - [Vision](./company/vision.md)
- - [Operations](./operations)
- - [Product](./product)
+## How FlowFuse is run
-### Development & Design Practices
+To run our company we provide a comprehensive guide outlining policies, procedures, and expectations, fostering consistency, clarity, and effective communication within the organisation.
- - [Design](./design)
- - [Development](./development)
- - [Videos](./marketing/videos.md)
+| | |
+|:----|:----|
+| [Values](/handbook/company/values.md)
----
-```
+---
+navTitle: Webinars
+navGroup: Sales & Marketing
+---
+
+## FlowFuse Webinars
+
+FlowFuse will organize two types of webinars: 1) Ask Me Anything session that is an ope mic for community members to ask questions of Node-RED and FlowFuse experts, and 2) Educational webinars that will educational topics. The current plan is to do an AMA session the second week of each month and an educational webinar the last week of the month.
+
+### Hosting Webinars
+FlowFuse will use the Zoom Webinar platform to host each webinar. This platform provides the automated recording, email reminders, calendar entries, Q&A and accommodate up to 500 attendees.
+
+Hubspot will be used to collect attendee registrations.
+
+### Steps to Schedule a Webinar
+
+1. Select a topic and speaker
+ * Create a title and abstract for the webinar and speaker bio
+2. Schedule webinar in Zoom
+ * Zoom will automatically send a confirmation email and a two reminder emails to all registrants.
+3. Create a webinar page for the website
+ * Follow the templates from previous months - more details can be found [below](#creating-a-webinar-page).
+4. Create a graphic to promote the webinar
+ * Follow the templates from previous months.
+5. Setup Hubspot for Webinar
+ * Create a static list to track the registrations
+ * Change the webinar workflow to point to the new static list
+ * Change the webinar workflow to point to the new Zoom Webinar ID. The ID can be found in the Zoom webinar page. NOTE: you need to use hyphens to replace the spaces in the ID number.
+
+### Promoting Webinars
+
+Each webinar should be available for promotion 2-4 weeks before the live date. Channels for promotion include:
+* Flowforge newsletter
+* Social media
+* Slack channels
+* Node-RED forums
+* FlowFuse website
+
+### Creating a Webinar Page
+
+Webinar pages follow a fixed structure, you can see plenty of examples [here](https://github.com/flowforge/website/tree/main/src/webinars) in our website repository. Importantly, they must define the following properties at the top of the `.md` file:
+
+#### Properties
+
+| Property | Description
+|-|-|
+| `title` | The title of the webinar, this will also be what shows as the "title" when shared on socials
+| `subtitle` | More context on what the webinar will involve
+| `video` | Once you have an available video recording of the session, you can include the videos' YouTube id here to include the recording in the webinar's page
+| `image` | Absolute file path to the image to show for the Webinar's tile
+| `date` | The date that the webinar will take place
+| `time` | The time that the webinar will take place, in both GMT & ET
+| `duration` | How long, in minutes with the webinar last for
+| `hosts` | A list of the webinar hosts, the names need to be formatted inline with the file names found [here](https://github.com/flowforge/website/tree/main/src/_data/team)
+| `hubspot.formId` | The formId from HubSpot to handle the event registration
+
+#### Example
+
+```yml
+---
+title: "DevOps for Node-RED: An Introduction to FlowFuse"
+subtitle: Join FlowFuse's CTO Nick O'Leary for an introduction to FlowFuse and how it provides DevOps for Node-RED.
+video: 47EvfmJji-k
+image: /images/webinars/webinar-nr-5mins.jpg
+date: YYYY-MM-DD
+time: HH:MM GMT (HH:MM ET)
+duration: MM
+hosts: ["rob-marcer"]
+hubspot:
+ formId:
+---
+```
diff --git a/src/handbook/marketing/website.md b/src/handbook/marketing/website.md
index aa63fe896b..b61e4f0b88 100644
--- a/src/handbook/marketing/website.md
+++ b/src/handbook/marketing/website.md
@@ -7,7 +7,7 @@ navTitle: Marketing - Website
- All written content should be in UK English.
- All page titles should summarise the content, keep the URL length as short as practical and use [Kebab Case](https://en.wiktionary.org/wiki/kebab_case).
- All images should use informative [alt tags](https://www.w3.org/WAI/tutorials/images/tips/) which clearly describe the point of an image rather than all the details. Alt tags should be no longer than 60 characters.
-- When mentioning [FlowForge Concepts](https://flowforge.com/docs/user/concepts/) (terminology) where possible we should link to an explanation of that concept.
+- When mentioning [FlowFuse Concepts](https://flowforge.com/docs/user/concepts/) (terminology) where possible we should link to an explanation of that concept.
- All written content should use the [Oxford Comma](https://en.wikipedia.org/wiki/Serial_comma). We believe the Oxford Comma reduces the ambiguity of written technical content.
#### Events Banner
diff --git a/src/handbook/operations/accounts.md b/src/handbook/operations/accounts.md
index c46ae8fce7..9ab58ddfa5 100644
--- a/src/handbook/operations/accounts.md
+++ b/src/handbook/operations/accounts.md
@@ -4,18 +4,18 @@ navTitle: Accounts
# Accounts
-These are the principles of how we setup and use accounts on the FlowForge.cloud platform.
+These are the principles of how we setup and use accounts on the FlowFuse.cloud platform.
Shared accounts should be avoided wherever possible, particularly on our own systems as this removes the ability to track which individual made a change.
## User Accounts
-All employees of Flowforge should have a user account on flowforge.cloud and be added to the `FlowForge Team` in order to access our own company projects.
-The email address for this account should be their normal @flowforge.com address
+All employees of Flowforge should have a user account on flowforge.cloud and be added to the `FlowFuse Team` in order to access our own company projects.
+The email address for this account should be their normal @flowfuse.com address
## Admin
Where their role requires it they should have a separate admin account on flowforge.cloud in the format `username-admin` This account should not be a member of any teams and should only be used to administrate the service.
-Because you can only have one account per email address on the platform admin accounts should have +admin added to the name eg `bob+admin@flowforge.com` Google will then automatically forward those emails to the `bob@flowforge.com` account.
+Because you can only have one account per email address on the platform admin accounts should have +admin added to the name eg `bob+admin@flowfuse.com` Google will then automatically forward those emails to the `bob@flowfuse.com` account.
diff --git a/src/handbook/operations/billing.md b/src/handbook/operations/billing.md
index 7fdf88c5bb..a3d30ba7c8 100644
--- a/src/handbook/operations/billing.md
+++ b/src/handbook/operations/billing.md
@@ -4,13 +4,13 @@ navTitle: Billing
# Billing
-We use Stripe to bill our customers and to manage subscriptions for FlowForge.
+We use Stripe to bill our customers and to manage subscriptions for FlowFuse.
Team members will be given a login to the Stripe dashboard as required for
their role with an appropriate level of access.
## Providing support
-The main use of the Stripe dashboard will be to answer queries on a customers subscription, this should only be in relation to a ticket raised by the customer and we *must* confirm that the customer team in question on the support ticket is the same one you are looking at it Stripe. Remember that the email address in Stripe may not match that of the FlowForge user as this is a "billing email". You should use the team ID numbers in the metadata field to confirm.
+The main use of the Stripe dashboard will be to answer queries on a customers subscription, this should only be in relation to a ticket raised by the customer and we *must* confirm that the customer team in question on the support ticket is the same one you are looking at it Stripe. Remember that the email address in Stripe may not match that of the FlowFuse user as this is a "billing email". You should use the team ID numbers in the metadata field to confirm.
## Invoices
@@ -35,12 +35,12 @@ on the [quote](../sales/pricing.md#generating-a-quote-and-order-form) and
When the invoice is generated and send to the customer you can go ahead with
providing them they [license for self-managed](../sales/pricing.md#generating-a-license),
-or [create a coupon](#coupons) and apply that to the FlowForge Cloud team.
+or [create a coupon](#coupons) and apply that to the FlowFuse Cloud team.
## Coupons
From time to time we may wish to provide a user with some free access to
-the managed FlowForge platform. In this situation we will create a coupon code
+the managed FlowFuse platform. In this situation we will create a coupon code
in Stripe which can be shared with the users.
To create a couple on Stripe:
diff --git a/src/handbook/operations/change.md b/src/handbook/operations/change.md
index 973a481702..0af4f6b6a6 100644
--- a/src/handbook/operations/change.md
+++ b/src/handbook/operations/change.md
@@ -1,10 +1,10 @@
---
-navTitle: FlowForge Cloud Change Control
+navTitle: FlowFuse Cloud Change Control
---
-# FlowForge Cloud Change Control
+# FlowFuse Cloud Change Control
-We track changes made to either the Staging or Production environments of FlowForge Cloud
+We track changes made to either the Staging or Production environments of FlowFuse Cloud
through issues on the CloudProject repository.
The issues should record the nature of the change required, which environment it applies to
diff --git a/src/handbook/operations/customer-success.md b/src/handbook/operations/customer-success.md
new file mode 100644
index 0000000000..751b91d41f
--- /dev/null
+++ b/src/handbook/operations/customer-success.md
@@ -0,0 +1,137 @@
+---
+navTitle: Customer Success
+---
+
+# Customer Success
+
+Customer Success (CS) helps our customers get value from FlowFuse. This should result in them continuing to use, make broader use of, and become advocates of FlowFuse.
+
+## Customer Success Methodology
+
+The basic principal of CS is to help customers succeed in their goals by getting value from our services. The assumption is, where customers get value they are likely to consciously recognise that value, be open to gaining more value, and recommending FlowFuse to potential customers. This should in turn result in customers remaining with FlowFuse for longer, delivering greater revenue, and encouraging more of their professional and personal networks to join FlowFuse.
+
+FlowFuse has a diverse customer-base. When devising a strategy to deliver CS it is important to recognise the key cohorts within our customers. They are grouped as follows:
+
+|Cohort|Key Traits|
+|-|-|
+|Trial|Not paying for services|
+|Starter|Low number of Node-RED instances|
+|Premium|Team of users, collaboration on applications|
+|Enterprise|Large scale applications, extensive use of FlowFuse's features|
+
+You can view our current customer-base and their cohorts in [this report](https://main.flowforge.cloud/ui/#!/1?socketid=rq-XlmWmn83upsPQAAAp){rel="nofollow}.
+
+CS activity is planned to manage each of the cohorts with appropriate support & communications. The support and communications will be in some cases fully automated and in others will involve individual actions by our CS team, such as holding regular review meetings with customers.
+
+The key goal of CS is to migrate customers from the trial status, down the table of cohorts above, and where appropriate onto being an Enterprise customer. It is however important to consider that some customers would not benefit from our broadest offerings of services. Appropriate resources should be put into customers who have found lasting value further up the cohorts table.
+
+## Customer Success Tools
+
+### Data Sources
+
+To drive CS, we need to utilise data across various platforms to understand what our customers need from us to succeed. the main platforms we use are as follows:
+
+|Platform|Key Data|
+|-|-|
+|FlowFuse Cloud's Database|Current usage of the platform and uptake of features|
+|Stripe|Expenditure|
+|Hubspot|Interaction with support and marketing content on our website and in emails|
+
+### Useful Customer Data
+
+- [Team, User, Instances & Devices Growth](https://main.flowforge.cloud/ui/#!/0?socketid=LPUnOyHnjGM_GqrnAAAd)
+- [Customer Cohorts](https://main.flowforge.cloud/ui/#!/1?socketid=LPUnOyHnjGM_GqrnAAAd)
+- [Device Agent Adoption](https://main.flowforge.cloud/ui/#!/2?socketid=LPUnOyHnjGM_GqrnAAAd)
+- [User Audit Interactions](https://main.flowforge.cloud/ui/#!/4?socketid=zuEy1h2ZhTjyhCnuAABB)
+
+### Communication
+
+To deliver automated and manual communication with customers, we use Hubspot CRM. Hubspot allows us to collaborate as a team. This is vital when manually communicating with customers as well as operating automated email campaigns based on a customer's current cohort and interaction with their account.
+
+We have built an integration in Node-RED which can extract data from our platforms then append it to a customer's record in Hubspot. The integration as well as any other CS resources built in Node-RED are hosted on FlowFuse Cloud and can be [accessed in this application](https://main.flowforge.cloud/){rel="nofollow}.
+
+## Inbound Support
+
+For FlowFuse customers, there are two ways to get support, through support tickets
+or go to the community forum. Where to go when is described below.
+
+| Topic | Support venue |
+|---|---|
+| Billing | [Support ticket][support-tickets] |
+| FlowFuse Application | [Support ticket][support-tickets] |
+| FlowFuse Feature Requests | [FlowFuse repository](https://github.com/flowforge/flowforge/issues) |
+| Node-RED Application | [Community Forum][support-forum] |
+| Node-RED flows | [Community Forum][support-forum] |
+| Custom nodes | [Community Forum][support-forum] |
+
+If you're not a FlowFuse customer, or in your trial phase, please go to the
+[community forum][support-forum].
+
+### Support Tickets
+
+#### HubSpot
+
+We use HubSpot to manage our customer support tickets for the managed FlowFuse platform. We can give each FlowFuse team member access to HubSpot by assigning them a seat.
+
+If you wish to be granted access to HubSpot please post in the FlowFuse
+[#support-tickets](https://flowforgeworkspace.slack.com/archives/C031K13FLDD) Slack channel.
+
+Whenever a customer raises a new ticket or replies with an update a message is
+posted into slack #support-tickets.
+This will allow the whole team visibility of customer issues, comments on the
+Slack thread will be added to the ticket as notes.
+
+When the customer has used the support widget you can communicate with that customer in real-time using the support-tickets Slack channel.
+
+When replying to the ticket one should have the intent to always reply with links
+to FlowFuse articles or documentation. If these resources are missing, please
+start or update where applicable.
+
+HubSpot uses notes and responses within the thread, notes are internal and not sent to the customer, responses are sent to the customer.
+
+We monitor the time since a ticket on HubSpot was last updated and send alerts to slack #support-tickets where those tickets have not been updated for longer than:
+
+ - 1 day for customer created support tickets.
+
+#### Scope of Support
+
+FlowFuse customers will only get support for issues relating to the FlowFuse
+application or their account & billing. Any questions around Node-RED
+itself or their flows should be redirected to the
+[FlowFuse Community forum][support-forum].
+
+3rd party nodes are not supported at this time. It is reasonable to point a
+customer direct to a repo for a 3rd party node question.
+
+#### SLA
+
+Support will be available between during business hours (Berlin time zones)
+Monday to Friday, with anything outside of those hours on a 'best effort' basis
+unless the customer and FlowFuse agreed otherwise.
+
+#### Escalation
+
+Where the issue relates to a bug in the FlowFuse application then the person
+dealing with the ticket should aim to reproduce that bug and then raise an
+appropriate issue in GitHub, The issue should reference the support ticket but
+not mention the customer by name. Once raised the issue URL should be added to
+the ticket and shared with the customer for visibility. The ticket should not be
+closed until the bug is resolved.
+
+## Community Forum
+
+As the Node-RED forums are intended to be vendor neutral, FlowFuse has a
+[community forum][support-forum] too.
+
+#### Scope of Support
+
+FlowFuse customers will only get support for issues relating to the FlowFuse
+application or their account & billing. Any questions around Node-RED
+itself or their flows should be redirected to the
+[FlowFuse Community forum][support-forum].
+
+3rd party nodes are not supported at this time. It is reasonable to point a
+customer direct to a repo for a 3rd party node question.
+
+[support-tickets]: ../../support/
+[support-forum]: https://community.flowfuse.com
diff --git a/src/handbook/operations/data.md b/src/handbook/operations/data.md
index 76abc4ad67..3d61b22dea 100644
--- a/src/handbook/operations/data.md
+++ b/src/handbook/operations/data.md
@@ -1,15 +1,15 @@
---
-navTitle: Data at FlowForge
+navTitle: Data at FlowFuse
---
-# Data at FlowForge
+# Data at FlowFuse
-At FlowForge we're trying to leverage data obtained to make better decisions.
+At FlowFuse we're trying to leverage data obtained to make better decisions.
### Data sources
Right now we're mostly using the Telemetry data from self-managed installs of
-FlowForge. Later we'll likely add data from Stripe and Hubspot.
+FlowFuse. Later we'll likely add data from Stripe and Hubspot.
### Data warehouse
@@ -21,7 +21,7 @@ Sheets and [Data Studio](https://datastudio.google.com/).
### Source to sink
We've adopted Meltano to obtain and transfer the data. See also the
-[FlowForge-Data](https://github.com/flowforge/flowforge-data){rel="nofollow"}
+[FlowFuse-Data](https://github.com/flowforge/flowforge-data){rel="nofollow"}
(Internal project)
on how we transfer the data. It's manually triggered for now.
diff --git a/src/handbook/operations/index.md b/src/handbook/operations/index.md
index 32479b376d..cf101e9961 100644
--- a/src/handbook/operations/index.md
+++ b/src/handbook/operations/index.md
@@ -7,15 +7,15 @@ navGroup: Company
This covers how we run our business and deliver service to our customers.
- [Data](../operations/data.md)
-- [Support](../operations/support.md)
+- [Customer Success](../operations/customer-success.md)
- [Billing](../operations/billing.md)
- [Accounts](../operations/accounts.md)
- [Change Control](../operations/change.md)
- [Vendors](../operations/vendors.md)
-### Services used at FlowForge
+### Services used at FlowFuse
-At FlowForge there's a couple of services that are vital to the operation of the
+At FlowFuse there's a couple of services that are vital to the operation of the
business. As a matter of having a plan before these services are taken offline
or go bankrupt a table is maintained with where to go in case of service disruption.
@@ -25,5 +25,5 @@ or go bankrupt a table is maintained with where to go in case of service disrupt
| Slack Huddles | Internal face to face commuication | Google Meet | - |
| Google Meet / Zoom | External video calls | Google Meet / Zoom | - |
| [Google Appointment Schedules](https://support.google.com/calendar/answer/10729749?hl=en) | Scheduling meetings with external parties | Calendly | - |
-| AWS | Hosting for FlowForge Cloud | ? | - |
+| AWS | Hosting for FlowFuse Cloud | ? | - |
diff --git a/src/handbook/operations/support.md b/src/handbook/operations/support.md
deleted file mode 100644
index 25ecc9e77c..0000000000
--- a/src/handbook/operations/support.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-navTitle: Support
----
-
-# Support
-
-For FlowForge customers, there are two ways to get support, through support tickets
-or go to the community forum. Where to go when is described below.
-
-| Topic | Support venue |
-|---|---|
-| Billing | [Support ticket][support-tickets] |
-| FlowForge Application | [Support ticket][support-tickets] |
-| FlowForge Feature Requests | [FlowForge repository](https://github.com/flowforge/flowforge/issues) |
-| Node-RED Application | [Community Forum][support-forum] |
-| Node-RED flows | [Community Forum][support-forum] |
-| Custom nodes | [Community Forum][support-forum] |
-
-If you're not a FlowForge customer, or in your trial phase, please go to the
-[community forum][support-forum].
-
-## Support Tickets
-
-### HubSpot
-
-We use HubSpot to manage our customer support tickets for the managed FlowForge platform. We can give each FlowForge team member access to HubSpot by assigning them a seat.
-
-If you wish to be granted access to HubSpot please post in the FlowForge
-[#support-tickets](https://flowforgeworkspace.slack.com/archives/C031K13FLDD) Slack channel.
-
-Whenever a customer raises a new ticket or replies with an update a message is
-posted into slack #support-tickets.
-This will allow the whole team visibility of customer issues, comments on the
-Slack thread will be added to the ticket as notes.
-
-When the customer has used the support widget you can communicate with that customer in real-time using the support-tickets Slack channel.
-
-When replying to the ticket one should have the intent to always reply with links
-to FlowForge articles or documentation. If these resources are missing, please
-start or update where applicable.
-
-HubSpot uses notes and responses within the thread, notes are internal and not sent to the customer, responses are sent to the customer.
-
-We monitor the time since a ticket on HubSpot was last updated and send alerts to slack #support-tickets where those tickets have not been updated for longer than:
-
- - 1 day for customer created support tickets.
-
-### Scope of Support
-
-FlowForge customers will only get support for issues relating to the FlowForge
-application or their account & billing. Any questions around Node-RED
-itself or their flows should be redirected to the
-[FlowForge Community forum][support-forum].
-
-3rd party nodes are not supported at this time. It is reasonable to point a
-customer direct to a repo for a 3rd party node question.
-
-### SLA
-
-Support will be available between during business hours (Berlin time zones)
-Monday to Friday, with anything outside of those hours on a 'best effort' basis
-unless the customer and FlowForge agreed otherwise.
-
-### Escalation
-
-Where the issue relates to a bug in the FlowForge application then the person
-dealing with the ticket should aim to reproduce that bug and then raise an
-appropriate issue in GitHub, The issue should reference the support ticket but
-not mention the customer by name. Once raised the issue URL should be added to
-the ticket and shared with the customer for visibility. The ticket should not be
-closed until the bug is resolved.
-
-## Community Forum
-
-As the Node-RED forums are intended to be vendor neutral, FlowForge has a
-[community forum][support-forum] too.
-
-### Scope of Support
-
-FlowForge customers will only get support for issues relating to the FlowForge
-application or their account & billing. Any questions around Node-RED
-itself or their flows should be redirected to the
-[FlowForge Community forum][support-forum].
-
-3rd party nodes are not supported at this time. It is reasonable to point a
-customer direct to a repo for a 3rd party node question.
-
-[support-tickets]: ../../support/
-[support-forum]: https://community.flowforge.com
\ No newline at end of file
diff --git a/src/handbook/operations/vendors.md b/src/handbook/operations/vendors.md
index d500344f43..63419ec15f 100644
--- a/src/handbook/operations/vendors.md
+++ b/src/handbook/operations/vendors.md
@@ -4,10 +4,16 @@ navTitle: Vendors
# Vendors
+In accordance with our [Third-Party Risk Management policy](../company/security/third-party-risk-management.md)
+all vendors should be reviewed to ensure their suitability for handling FlowFuse
+data.
+
+A list of approved vendors is available interally [here](https://docs.google.com/spreadsheets/d/1ro77wy0cRK6gpzVv_iq4vpdmbdMq61X5-tTwI_F3hXM/edit?usp=sharing){rel="nofollow"}.
+
### Process
To start to process of approval and paying of invoices a PDF of the invoice should
-be mailed to billing@flowforge.com. FlowForge pays invoices 30 days after filing
+be mailed to billing@flowfuse.com. FlowFuse pays invoices 30 days after filing
unless specifically agreed otherwise prior to filing the invoice.
The invoice should include:
diff --git a/src/handbook/peopleops/code-of-conduct.md b/src/handbook/peopleops/code-of-conduct.md
new file mode 100644
index 0000000000..b361286356
--- /dev/null
+++ b/src/handbook/peopleops/code-of-conduct.md
@@ -0,0 +1,118 @@
+---
+navTitle: Code of Conduct
+---
+
+## Code of Conduct
+
+The primary goal of our Code of Conduct is to foster inclusive, collaborative
+and safe working conditions for all FlowFuse staff and community members who
+participate in our open core projects.
+
+As such, FlowFuse is committed to providing a friendly, safe and welcoming
+environment regardless of gender, sexual orientation, ability, ethnicity,
+socioeconomic status, or religion (or lack thereof).
+
+This code of conduct outlines our expectations for the FlowFuse community, as
+well as the consequences for unacceptable behavior.
+
+### Scope
+
+The Code of Conduct applies to all FlowFuse staff. This includes full-time,
+part-time and contractor staff employed at every seniority level. It also applies
+to contributors who engage with our open core projects.
+
+The Code of Conduct is to be upheld during all professional functions and events,
+including but not limited to:
+
+ - Working remotely and communicating on FlowFuse resources with other team members.
+ - At FlowFuse-related extracurricular activities and events.
+ - While attending conferences and other professional events on behalf of FlowFuse.
+
+We expect all FlowFuse staff to abide by this Code of Conduct in all business
+matters -- online and in-person -- as well as in all one-on-one communications
+with customers and staff pertaining to FlowFuse business.
+
+This Code of Conduct also applies to unacceptable behavior occurring outside the
+scope of business activities when such behavior has the potential to adversely
+affect the safety and well-being of FlowFuse staff and clients.
+
+### Culture and Belonging
+
+A supplemental goal of this Code of Conduct is to increase open community by
+encouraging participants to recognize the relationships between our actions and
+their effects within FlowFuse culture.
+
+At the core are our [company values](../company/values.md). This Code of Conduct
+makes explict how we should behave whilst uphold our values.
+
+ - [**Be inclusive**](../company/values.md#š„-collaborative-community). We strive
+ to be a company that welcomes and supports people of all backgrounds and identities.
+ - [**Be considerate**](../company/values.md#š¤-customer-empathy). Your work at
+ FlowFuse will be used by other people, and you in turn will depend on the
+ work of others. Any decision you take will affect users and colleagues, and
+ you should take those consequences into account when making decisions.
+ - **Be respectful**. Not all of us will agree all the time, but disagreement is
+ no excuse for poor behavior and poor manners. We expect everyone to remain polite
+ and to keep conversations healthy and constructive. We do not allow our frustrations
+ to turn in [personal attacks](https://en.wikipedia.org/wiki/Ad_hominem).
+
+### Acceptable and Expected Behavior
+
+The following behaviors are expected and requested of all FlowFuse staff:
+
+ - Participate in an authentic and active way. In doing so, you contribute to the
+ health and longevity of FlowFuse.
+ - Exercise consideration and respect in your speech and actions at all times.
+ - Attempt collaboration before conflict.
+ - Refrain from demeaning, discriminatory, or harassing behavior and speech.
+ - Be mindful of your surroundings and of your fellow participants. Alert FlowFuse
+ leaders if you notice a dangerous situation, someone in distress, or violations
+ of this Code of Conduct, even if they seem inconsequential.
+
+### Unacceptable Behavior
+
+The following behaviors are considered harassment and are unacceptable within our community:
+
+ - Violence, threats of violence, or violent language directed against another person.
+ - Sexist, racist, homophobic, transphobic, [ableist](https://en.wikipedia.org/wiki/Ableism) or otherwise discriminatory jokes and language.
+ - Posting or displaying sexually explicit or violent material.
+ - Posting or threatening to post other peopleās personally identifying information ("doxing").
+ - Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
+ - Inappropriate photography or recording.
+ - Inappropriate physical contact. You should have someoneās consent before touching them in any manner.
+ - Unwelcome sexual attention. This includes sexualized comments or jokes; inappropriate touching, groping, and unwelcome sexual advances.
+ - Deliberate intimidation, stalking or following (online or in person).
+ - Advocating for, or encouraging, any of the above behavior.
+ - Repeated harassment of others. In general, if someone asks you to stop, then stop.
+ - Other conduct which could reasonably be considered inappropriate in a professional setting.
+
+### Consequences of Unacceptable Behavior
+
+Unacceptable behavior from any FlowFuse staff, including those with
+decision-making authority, will not be tolerated.
+
+Anyone asked to stop unacceptable behavior is expected to comply immediately.
+
+If a staff member engages in unacceptable behavior, FlowFuse leadership may take
+any action deemed appropriate, up to and including suspension or termination.
+
+### Reporting Violations
+
+If you are subject to or witness unacceptable behavior, or have any other concerns,
+please notify an appropriate member of FlowFuse leadership (Peopleops manager, CTO, and/or CEO) as soon as possible.
+
+It is a violation of this policy to retaliate against any person making a
+complaint of Unacceptable Behavior or against any person participating in the
+investigation of (including testifying as a witness to) any such allegation. Any
+retaliation or intimidation may be subject to punitive action up to and including
+termination.
+
+### Disciplinary Action
+
+Employees who violate this policy may face disciplinary consequences in proportion
+to their violation. FlowFuse management will determine how serious an employee's
+offense is and take the appropriate action.
+
+### Responsibility
+
+Everyone has a responsibility to ensure this policy is followed.
diff --git a/src/handbook/peopleops/compensation.md b/src/handbook/peopleops/compensation.md
index fd02939610..a1d725dcd7 100644
--- a/src/handbook/peopleops/compensation.md
+++ b/src/handbook/peopleops/compensation.md
@@ -4,49 +4,53 @@ navTitle: Compensation
# Compensation
-Total compensation consists of 3 elements, salary, equity, and benefits.
-FlowForge aims to provide a total compensation package on par with similar
-companies in terms of: stage of the company, market, role, and level in the role.
-The data to validate our compensation is obtained through OptionImpact/Pave.com.
+FlowFuse provides a comprehensive compensation package with salary, equity,
+and benefits, aiming to be competitive with similar companies. Factors like
+company stage, market conditions, role, and level influence salary
+determination during the hiring process. FlowFuse typically pays in the local
+currency, unless there are explicit discussions stating otherwise, taking
+into account location and company context.
-## Salary
+## Compensation Increase Cycle
-Salary for each role is determined initially during the hiring process based
-on compensation expectation of the candidate as well as the market rates. Salary
-is based on your location you live in and the company context. FlowForge pays in
-your local currency unless explicitly discussed otherwise.
+FlowFuse follows a single-point increase cycle for salary adjustments. These
+adjustments take place once a year, aligning with the company's budgeting
+and planning process. When determining compensation changes, FlowFuse considers
+three factors: performance, inflation, and market standards. These factors are
+taken into account together to make decisions about adjusting employee compensation.
+
+# Performance Review
+
+Performance reviews will be carried out annually, in September. Any employee or
+contractor who has completed more than six months of service at FlowFuse is eligible
+to participate in the performance review process.
### Adjustment
-FlowForge can choose to increase compensation based on varying situations:
-- Past year performance, as documented in the September performance review
-- To stay between the 50-75th percentile for companies our stage
+FlowFuse can choose to increase compensation based on varying situations:
+- Past year performance, as evaluated during the September performance review.
+- Market positioning, aiming to align compensation within the 50-75th percentile range for companies at the same stage.
## Equity
-FlowForge intents to offers equity for most roles. The level of stock compensation
+FlowFuse intents to offers equity for most roles. The level of stock compensation
can vary based on when an employee joined, their performance, and the variables
that decide salary. Equity is offered as stock options, which upon
execution will be transformed in the underlying stock. Stock compensation are
awarded on a 4 year vesting schedule with a 1 year cliff.
Employees might be taxed personally when accepting or executing stock options.
-FlowForge does not provide any advice on financial decisions for employees. For
-FlowForge employees the Fair Market Value of the underlying stock can be found
+FlowFuse does not provide any advice on financial decisions for employees. For
+FlowFuse employees the Fair Market Value of the underlying stock can be found
in [this internal document](https://docs.google.com/document/d/1_DmqzQ5rmjYHlBvF5owJpj3JVR_BlJUg_S-pwfRtA5g).
Equity is subject to board approval.
## Benefits
-Last component of the total compensation are the benefits offered. The intent is
-to keep these as location independent as possible and practical. However, as a
-company we strive to offer everyone a decent standard of living. As such we might
-offer location dependant benefits to ensure standards are met.
+The final component of our total compensation is the benefits package. While our intention is to keep these benefits as location independent as possible and practical, we also strive to provide all employees with a decent standard of living. Therefore, in certain cases, we may offer location-dependent benefits to ensure that appropriate standards are met.
-Benefits might change during your employment based on changing legislation,
-changing costs to offer said benefits, or costs outweighing the benefits for team
-members, or other reasons.
+Please note that the benefits offered may be subject to change during your employment. These changes may occur due to evolving legislation, fluctuations in the costs associated with providing the benefits, situations where the costs outweigh the benefits for team members, or other relevant reasons. We aim to ensure that any adjustments made to the benefits package are made with careful consideration and the best interests of our employees in mind.
### For everyone
@@ -65,14 +69,14 @@ A lunch is organized to celebrate every release, and team members participating
#### Dinner Bonus
-The company's [KPI tracking FlowForge ARR](../company/achieving-success.md#kpi)
+The company's [KPI tracking FlowFuse ARR](../company/achieving-success.md#kpi)
sets an aggressive goal for growth. When the growth target is met a $100 bonus is
awarded to be expensed for a dinner out. The bonus is awarded per release.
### Health Care
-FlowForge offers a health care package for all employees in the United States, Canada, and India.
+FlowFuse offers a health care package for all employees in the United States, Canada, and India.
-For employees located in the United States, FlowForge offer basic health insurance coverage which includes dental and vision benefits through Deel.
-However, employees who choose not to participate in the health insurance provided by FlowForge have the option to opt out. This can be done by registering with Zenefits and declining coverage during the enrollment process on the platform. It is important to note that if an employee decides to opt out, they must have alternative qualified coverage to ensure compliance with the ACA (Affordable Care Act).
+For employees located in the United States, FlowFuse offer basic health insurance coverage which includes dental and vision benefits through Deel.
+However, employees who choose not to participate in the health insurance provided by FlowFuse have the option to opt out. This can be done by registering with Zenefits and declining coverage during the enrollment process on the platform. It is important to note that if an employee decides to opt out, they must have alternative qualified coverage to ensure compliance with the ACA (Affordable Care Act).
diff --git a/src/handbook/peopleops/expenses.md b/src/handbook/peopleops/expenses.md
index c6bea69b9f..33fdc43d4f 100644
--- a/src/handbook/peopleops/expenses.md
+++ b/src/handbook/peopleops/expenses.md
@@ -56,14 +56,14 @@ it can be recorded.
### Education & Conferences
-Continual professional development is very important, and FlowForge will support
+Continual professional development is very important, and FlowFuse will support
you in any activities you wish to undertake. Speak to your manager if you have
particular material you would like to study, or an event you would like to
-attend. FlowForge will help cover reasonable costs associated with the activity - such as travel and ticket fees.
+attend. FlowFuse will help cover reasonable costs associated with the activity - such as travel and ticket fees.
### Software Licenses
-Licenses and software assets can be purchased for third-party software will be useful for particular tasks, efforts and processes at FlowForge.
+Licenses and software assets can be purchased for third-party software will be useful for particular tasks, efforts and processes at FlowFuse.
If you are seeking a license of software that we do not currently use, put together a short summary as to the costs associated with the licenses and describe the value that the software would provide. If it would modify the way in which the company operates, then the best place to present this is as a PR to the Handbook. With approval from the CEO and CTO you can proceed with the acquisition of the licenses.
@@ -71,7 +71,7 @@ When seeking an additional license for existing software we pay for, file an iss
#### Zoom
-When your role at FlowForge requires you to have calls with external parties, a
+When your role at FlowFuse requires you to have calls with external parties, a
Zoom pro license can be requested by opening an issue to provision you one
in the [flowforge/admin][gh-admin]{rel="nofollow"} GitHub project. Assign this issue to the CTO
or CEO, who will provision it for you.
diff --git a/src/handbook/peopleops/hiring.md b/src/handbook/peopleops/hiring.md
index ad6c7b0127..6414bc6b66 100644
--- a/src/handbook/peopleops/hiring.md
+++ b/src/handbook/peopleops/hiring.md
@@ -19,6 +19,10 @@ the job advert on Greenhouse. This was introduced [here](https://github.com/flow
1. Update the redirect URL in the `njk` file to match that added in Step 1.
1. Open an [Art Request](/handbook/design/art-requests/) to have a new Social Tile designed & attach it to the relevant page
+### Referrals
+
+To participate in FlowFuse's employee referral program, kindly send all referral resumes to the People Ops Manager. If your recommended candidate gets hired and successfully completes 3 months, you will receive a $100 reward. Alternatively, you can choose a charitable foundation of your liking, and we will double the referral amount donated to that organization.
+
### Sharing an Existing Role
The URLs for the existing roles we have on the website are any files found in [here](https://github.com/flowforge/website/tree/main/src/jobs).
@@ -26,21 +30,14 @@ The URL will be structured accordingly: `https://flowforge.com/jobs/Self-Service
Fast first response time from support, fast turn around times on issues. Direct communications
āJust needs to workā out of the box
- Hands on when first using FlowForge/Node-RED
+ Hands on when first using FlowFuse/Node-RED
The core principles guiding and driving the whole company
+| [Vision](/handbook/company/vision.md)Where we're going with FlowFuse
| +| [Operations](/handbook/operations/)The day to day operations, tactical bizzops
+| [PeopleOps](/handbook/peopleops/)Humans aren't resources, so people ops
| +| [Communication](/handbook/company/communication.md)Increase signal, decrease noise.
+| | -### Sales and Marketing +### How we build the product + +| | | +|:----|:----| +| [Product](/handbook/product/)Planning, scheduling, and where the product will be a year from now
+| [Development](/handbook/development/)How features are delivered with velocity and quality
| +| [Design](/handbook/design/)How information is presented through UX/UI to users, prospects, and internally.
+| [Security](/handbook/company/security.md)Keeping what's private private, and what needs protecting protected.
| + - - [Sales](./sales/) - - [Marketing & Communication](./marketing) +### Bringing the built product to market -### Internal Operations +| | | +|:----|:----| +| [Marketing](/handbook/marketing/)Keeping what's private private, and what needs protecting protected.
+| [Sales](/handbook/sales/)Meeting customer demand.
| +| [Customer Success](/handbook/operations/customer-success.md)Happy customers is what makes FlowFuse a sustainable business.
+| | - - [Communication](./company/communication.md) - - [PeopleOps](./peopleops) - - [Security](./company/security.md) ### About the Handbook -The FlowForge handbook is inspired by the [GitLab handbook](https://about.gitlab.com/handbook/about/). +The FlowFuse handbook is inspired by the [GitLab handbook](https://about.gitlab.com/handbook/about/). As an all-remote company, we share [their rationale](https://about.gitlab.com/handbook/about/#advantages) for having a handbook. The aim is to avoid institutional knowledge building up inside our heads without @@ -46,20 +59,14 @@ also being written down for others to share. We could do that all on the interna Google Drive, but by publishing in the handbook it allows for an open and honest conversation about what we do. - #### Contributing The handbook is maintained on [GitHub](https://github.com/flowforge/website/tree/main/src/handbook) and contributions can be made through pull-requests. All changes merged to the `main` branch will be automatically deployed to the handbook on the -[FlowForge website](https://flowforge.com/handbook). - -#### Private information - -Whilst instinctively we want to be open in all we do, there will inevitably by content that is not appropriate -to make public. That content should be shared on the FlowForge Google Drive. +[FlowFuse website](https://flowforge.com/handbook). -## Building the site locally +##### Building the site locally To run the handbook locally, follow the instructions on the [website repository](https://github.com/flowforge/website). diff --git a/src/handbook/legal/index.md b/src/handbook/legal/index.md index 1a1d512eec..3412aaf169 100644 --- a/src/handbook/legal/index.md +++ b/src/handbook/legal/index.md @@ -5,17 +5,17 @@ navGroup: Internal Operations ## Subscription agreement -For self-managed licenses FlowForge has a standard [subscription agreement template](https://docs.google.com/document/d/1szqCRC7w-f82I4HL-cOTTCiSMKDhVWju84Md4M07RGk). +For self-managed licenses FlowFuse has a standard [subscription agreement template](https://docs.google.com/document/d/1szqCRC7w-f82I4HL-cOTTCiSMKDhVWju84Md4M07RGk). ## Cloud Partnership agreement -For partners that will refer FlowForge customer to FlowForge, FlowForge Cloud or otherwise, a +For partners that will refer FlowFuse customer to FlowFuse, FlowFuse Cloud or otherwise, a [standard referral agreement](https://docs.google.com/document/d/1BVls7LEC1CBQ6wlrb8GeWSYr2vj9fMqgdsWiWLoQZOY) is used. The terms of the contract are set by the CEO prior to sending the first draft to each partner. ## Non-disclosure agreement (NDA) -FlowForge has templates for standard NDA's: +FlowFuse has templates for standard NDA's: - [One way NDA](https://docs.google.com/document/d/1r6a3qgYrfKwNnNwQwx2Wp63QiC_sHGHYca8f9IR_fCI){rel="nofollow"} - When the other parties cannot share to any third parties - [Mutual NDA](https://docs.google.com/document/d/1YiOQPbcEwbqpLcnrYjaui9ur1iLO_8Y3Ty4TOVJNiTk){rel="nofollow} - Neither party can discuss details outside of the listed parties diff --git a/src/handbook/marketing/blog.md b/src/handbook/marketing/blog.md index 76715fdf72..55bcc0d7a9 100644 --- a/src/handbook/marketing/blog.md +++ b/src/handbook/marketing/blog.md @@ -10,9 +10,9 @@ meta: Content creation and blogging are an effective way to communicate with our community. The process for publishing a blog is as follows: 1. Raise an issue for the content in our private [Github repository](https://github.com/flowforge/content). -2. If the content is date specific create an 'all day' event on the Google Calendar [FlowForge Publishing Schedule](https://calendar.google.com/calendar/u/0?cid=Y18yMGFjMmM5MmMwYmE0YTYwNDg4NDE1MjBmMGU2YWE0MGFhZGUxNTlkNThjZGY0ZGMwMjA0NTI4ZjFjMTcxZmQ0QGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20), include a link to the issue in the event description. If you don't have the permission to create events please ask our Google Workspace admin to give you access. +2. If the content is date specific create an 'all day' event on the Google Calendar [FlowFuse Publishing Schedule](https://calendar.google.com/calendar/u/0?cid=Y18yMGFjMmM5MmMwYmE0YTYwNDg4NDE1MjBmMGU2YWE0MGFhZGUxNTlkNThjZGY0ZGMwMjA0NTI4ZjFjMTcxZmQ0QGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20), include a link to the issue in the event description. If you don't have the permission to create events please ask our Google Workspace admin to give you access. 3. If you want to work on the content immediately please triage the issue into our [development board](https://github.com/orgs/flowforge/projects/1/views/33). -4. Create the draft blog post in a Google Doc. The document should be stored in the [Marketing -> Content](https://drive.google.com/drive/folders/1sdyVfD29dFE74i7zfmL0Cp9tPmPyK0-8?usp=share_link){rel="nofollow"} folder. Everyone at FlowForge should be given access to comment on the document. Add a link to the document in the GitHub issue. +4. Create the draft blog post in a Google Doc. The document should be stored in the [Marketing -> Content](https://drive.google.com/drive/folders/1sdyVfD29dFE74i7zfmL0Cp9tPmPyK0-8?usp=share_link){rel="nofollow"} folder. Everyone at FlowFuse should be given access to comment on the document. Add a link to the document in the GitHub issue. 5. Ask people to review the document draft by sharing it directly with them using the Share button in the document. This will send your reviewers an email notification. 6. As a document reviewer, you should leave red-line edits in the document or add comments to the document. 7. Once the document is finished, create a new branch of the website repository and then follow our standard [development processes](https://flowforge.com/handbook/development/#development-board). Google Docs has an [extension to convert the document to markdown](https://workspace.google.com/marketplace/app/docs_to_markdown/700168918607?hl=en&pann=docs_addon_widget). diff --git a/src/handbook/marketing/boilerplate.md b/src/handbook/marketing/boilerplate.md index 3def117aab..c2485e82db 100644 --- a/src/handbook/marketing/boilerplate.md +++ b/src/handbook/marketing/boilerplate.md @@ -8,20 +8,20 @@ DevOps for Node-RED ### One sentence description -FlowForge allows organizations to reliably deliver Node-RED applications in a continuous, collaborative, and secure manner. +FlowFuse allows organizations to reliably deliver Node-RED applications in a continuous, collaborative, and secure manner. -### About FlowForge - 50 Words +### About FlowFuse - 50 Words -FlowForge helps Node-RED developers delivery applications in a more reliable, collaborative, and secure manner. Node-REDās intuitive, low-code development environment is great for connecting together hardware devices, APIs, and online services. FlowForge adds to Node-RED; collaborative development, management of remote deployments, support for DevOps deliver pipelines, and the ability to host Node-RED applications on FlowForge Cloud. FlowForge is the DevOps platform for Node-RED application development and delivery. +FlowFuse helps Node-RED developers delivery applications in a more reliable, collaborative, and secure manner. Node-REDās intuitive, low-code development environment is great for connecting together hardware devices, APIs, and online services. FlowFuse adds to Node-RED; collaborative development, management of remote deployments, support for DevOps deliver pipelines, and the ability to host Node-RED applications on FlowFuse Cloud. FlowFuse is the DevOps platform for Node-RED application development and delivery. -### About FlowForge - 150 Words +### About FlowFuse - 150 Words -FlowForge is an open-core company investing in Node-RED. Nick OāLeary, co-creator of Node-RED is FlowForge co-founder and CTO. +FlowFuse is an open-core company investing in Node-RED. Nick OāLeary, co-creator of Node-RED is FlowFuse co-founder and CTO. Node-RED is an open-source low-code programming tool, allowing developers to quickly and easily connect IoT devices, APIs, and online services by creating flow-based applications. It uses a drag-and-drop interface to wire together nodes, which can represent devices, APIs, or functions, to process data, and create powerful automations. Node-RED is very popular in the manufacturing industry for collecting factory data at the edge and transmitting it to a database or the cloud. Its visual programming environment makes it easy for non-traditional software developers to create data applications that accelerate innovation on the factory floor. -FlowForge adds to Node-RED collaborative development, management of remote deployments, support for DevOps delivery pipelines and the ability to host Node-RED applications on FlowForge Cloud. FlowForge is the devops platform for Node-RED application development and delivery. +FlowFuse adds to Node-RED collaborative development, management of remote deployments, support for DevOps delivery pipelines and the ability to host Node-RED applications on FlowFuse Cloud. FlowFuse is the devops platform for Node-RED application development and delivery. diff --git a/src/handbook/marketing/channels.md b/src/handbook/marketing/channels.md index 5383ca1431..d41cfcb82b 100644 --- a/src/handbook/marketing/channels.md +++ b/src/handbook/marketing/channels.md @@ -8,7 +8,7 @@ Each content type has channels which are appropriate, this table sets out which |Content |Blog |Mailing List |Twitter |Youtube |LinkedIn |Reddit |Node-RED Slack|Node-RED Discourse | |--- |--- |--- |--- |--- |--- |--- |--- |--- | -|Release |* | |* |* |* |* |* |* | +|Release |* | |* | |* |* |* |* | |Patch |* | |* | | |* |* | | |Planned Downtime |* | |* | |* |* |* | | |Outage | | | | | | | | | @@ -42,13 +42,13 @@ Videos should: #### LinkedIn -Posts should be framed in the context of FlowForge as an organisation and a team, don't get too technical. A relevant photo or image should be included in every post. Where the post is primarily of a video it should be embedded from Youtube. Where possible include the content in the post rather than linking out to external content. +Posts should be framed in the context of FlowFuse as an organisation and a team, don't get too technical. A relevant photo or image should be included in every post. Where the post is primarily of a video it should be embedded from Youtube. Where possible include the content in the post rather than linking out to external content. #### Reddit Keep it short, Reddit posts should be factual, informal and have a call to action (a link) where a user can read more. If the content is a video we should post that directly on Reddit as that should result in greater interaction. -#### Node-RED Slack (FlowForge section) +#### Node-RED Slack (FlowFuse section) Keep it short, Slack messages should be factual, informal and have a call to action (a link) where a user can read more. diff --git a/src/handbook/marketing/hubspot.md b/src/handbook/marketing/hubspot.md index bb3195509a..74b0b67099 100644 --- a/src/handbook/marketing/hubspot.md +++ b/src/handbook/marketing/hubspot.md @@ -9,25 +9,25 @@ It enables the creation of customer contacts, and then logging of emails/notes a ### Creating Contacts -Given that we have multiple client-facing roles within FlowForge, it's important to document those that +Given that we have multiple client-facing roles within FlowFuse, it's important to document those that we talk to to ensure no crossover in sales and conversations. #### Lifecycle Stage -All contacts in HubSpot need to have a defined lifecycle. It is required that all contacts pass through each lifecycle stage at the appropriate time based on their interaction with FlowForge marketing and sales. Contacts should not skip a stage. It is up to the contact owner to ensure their contacts have the appropriate lifecycle stage set. +All contacts in HubSpot need to have a defined lifecycle. It is required that all contacts pass through each lifecycle stage at the appropriate time based on their interaction with FlowFuse marketing and sales. Contacts should not skip a stage. It is up to the contact owner to ensure their contacts have the appropriate lifecycle stage set. The folowing is a description of each stage. | Lifecycle Stage|Description | - | - | -| Subscriber | Contact has signed up to hear more information, when it is available, about FlowForge, e.g. newsletter subscriber | +| Subscriber | Contact has signed up to hear more information, when it is available, about FlowFuse, e.g. newsletter subscriber | | Lead | Contact that has converted on our website, or through some other interaction, with our organisation beyond a subscription sign up. For example, registered for a webinar, signed up for a free trial, etc.| -| Marketing Qualified Lead | The contact has requested to talk to someone directly at FlowForge about the product/services of FlowForge, either through book a demo, contact us, or direct outreach to a FlowForge employee. Support requests are not considered MQL. | +| Marketing Qualified Lead | The contact has requested to talk to someone directly at FlowFuse about the product/services of FlowFuse, either through book a demo, contact us, or direct outreach to a FlowFuse employee. Support requests are not considered MQL. | | Sales Qualified Lead | After the initial discussion with an MQL, the sales team will qualify if the contact is a potential customer by changing the lifecycle stage to SQL. This status of this stage is then further qualified in the [Lead Status](#lead-status) property. | -| Opportunity | A contact becomes an Opportunity once a Deal has been opened. A deal is opened once the sales qualification questions have been answered. | -| Customer | An active, paying, user of FlowForge. | -| Evangelist | FlowForge will not actively use Evangelist lifecycle stage. | -| Other | Does not fit into any of the other descriptions, likely someone we are talking to about FlowForge, but will never be a paying customer, .e.g. Partners | +| Opportunity | A contact becomes an Opportunity once a Deal has been opened. The [3 W's need to be answered before opening a deal](../sales/#from-sql-to-opportunity) | +| Customer | An active, paying, user of FlowFuse. | +| Evangelist | FlowFuse will not actively use Evangelist lifecycle stage. | +| Other | Does not fit into any of the other descriptions, likely someone we are talking to about FlowFuse, but will never be a paying customer, .e.g. Partners | #### Lead Status @@ -37,17 +37,17 @@ details your options here, and when to use the respective value: | Lead Status | Description | | - | - | | None | - | -| Attempted to Contact | A member of FlowForge has reached out to this contact, but is yet to receive a response. | +| Attempted to Contact | A member of FlowFuse has reached out to this contact, but is yet to receive a response. | | Connected | Two-way conversation has undertaken, but not yet qualified as a Lead. A lead with this status may still be waiting on a booked meeting with a decision-maker on their team or may still be working to establish a budget. | -| Open Deal | Contact has expressed interest in buying FlowForge, and negotiations are actively open. | -| Unqualified | Contact is no longer interested in FlowForge. | +| Open Deal | Contact has expressed interest in buying FlowFuse, and negotiations are actively open. | +| Unqualified | Contact is no longer interested in FlowFuse. | ### Importing Contacts Into HubSpot -If you import contacts into HubSpot, it is important that the First Name and Last Name are populated correctly. Currently the FlowForge Cloud database stores first and last name in a single field called Name. If you import this field into HubSpot the default is set to populate the Last Name field. The First Name field will not be populated so any email personalization with First Name will not be effective. +If you import contacts into HubSpot, it is important that the First Name and Last Name are populated correctly. Currently the FlowFuse Cloud database stores first and last name in a single field called Name. If you import this field into HubSpot the default is set to populate the Last Name field. The First Name field will not be populated so any email personalization with First Name will not be effective. -The ideal process for importing FlowForge Cloud contacts is that you first split the Name field into a First Name and Last Name. Google Sheets has the ability to split a column of text into two columns based on the delimiter of a space. Once that is completed then you can import the list into HubSpot. +The ideal process for importing FlowFuse Cloud contacts is that you first split the Name field into a First Name and Last Name. Google Sheets has the ability to split a column of text into two columns based on the delimiter of a space. Once that is completed then you can import the list into HubSpot. ### Recommended Apps diff --git a/src/handbook/marketing/index.md b/src/handbook/marketing/index.md index 7221335d31..8b9d837ece 100644 --- a/src/handbook/marketing/index.md +++ b/src/handbook/marketing/index.md @@ -4,8 +4,8 @@ navGroup: Sales & Marketing --- ## Content -Find details on here on how we communicate at FlowForge, what type of content we produce and where we post it. -If you're looking to contribute content to FlowForge, this is the best place to start. +Find details on here on how we communicate at FlowFuse, what type of content we produce and where we post it. +If you're looking to contribute content to FlowFuse, this is the best place to start. - [Blog](./blog.md) - [Channels](./channels.md) diff --git a/src/handbook/marketing/types.md b/src/handbook/marketing/types.md index ea89c58ee9..79ce926ffd 100644 --- a/src/handbook/marketing/types.md +++ b/src/handbook/marketing/types.md @@ -8,7 +8,7 @@ Content should be published to the appropriate channels, the types of published #### Release -Major releases of FlowForge, the timing of these releases are governed by our [development cadence](../development/releases/planning#cadence). +Major releases of FlowFuse, the timing of these releases are governed by our [development cadence](../development/releases/planning#cadence). #### Patch diff --git a/src/handbook/marketing/videos.md b/src/handbook/marketing/videos.md index 7a43b75643..5ebbd0c31c 100644 --- a/src/handbook/marketing/videos.md +++ b/src/handbook/marketing/videos.md @@ -3,41 +3,41 @@ navTitle: Video navGroup: Sales & Marketing --- -## FlowForge Videos +## FlowFuse Videos -This section of our handbook is dedicated to guidance on how to create video/media assets for FlowForge. Here you can find information on what types of videos we produce at FlowForge and the templating and formatting we recommend for each. +This section of our handbook is dedicated to guidance on how to create video/media assets for FlowFuse. Here you can find information on what types of videos we produce at FlowFuse and the templating and formatting we recommend for each. Videos should be produced at 1920 x 1080 resolution. -Any text included in the videos will use the ["DIN Alternate Bold"](https://fontsgeek.com/fonts/DIN-Alternate-Bold) font. The FlowForge logo is made with ["Baloo Da 2"](https://fonts.google.com/specimen/Baloo+Da+2). +Any text included in the videos will use the ["DIN Alternate Bold"](https://fontsgeek.com/fonts/DIN-Alternate-Bold) font. The FlowFuse logo is made with ["Baloo Da 2"](https://fonts.google.com/specimen/Baloo+Da+2). We have a collection of [assets](#assets) that will make video editing and creation a lot simpler, particularly in Adobe Premiere Pro. ## Assets -If you have an Adobe Creative Cloud account, and are a member of the FlowForge team, then you will have access to the "FlowForge Templates" library in Premiere Pro. This contains a collection of [Essential Graphics templates](https://helpx.adobe.com/uk/premiere-pro/using/essential-graphics-panel.html), videos and audio files that can be used across any FlowForge videos. +If you have an Adobe Creative Cloud account, and are a member of the FlowFuse team, then you will have access to the "FlowFuse Templates" library in Premiere Pro. This contains a collection of [Essential Graphics templates](https://helpx.adobe.com/uk/premiere-pro/using/essential-graphics-panel.html), videos and audio files that can be used across any FlowFuse videos. #### Essential Graphics Templates -These can be created in Adobe After Effects and provide an easy-to-use editable template for composition in Premiere Pro. We have a growing collection of FlowForge templates that can be dropped and modified accordingly in your own FlowForge videos. +These can be created in Adobe After Effects and provide an easy-to-use editable template for composition in Premiere Pro. We have a growing collection of FlowFuse templates that can be dropped and modified accordingly in your own FlowFuse videos.Using Essential Graphics in Premiere Pro
#### Videos
-Re-usable `.mp4` files that may be used across FlowForge videos. These are also available in "FlowForge Templates" Premiere Pro Library. For example, our introduction and outro title sequences:
+Re-usable `.mp4` files that may be used across FlowFuse videos. These are also available in "FlowFuse Templates" Premiere Pro Library. For example, our introduction and outro title sequences:
-FlowForge - Intro
+FlowFuse - Intro
-FlowForge - Outro
+FlowFuse - Outro
## Tools
@@ -50,7 +50,7 @@ If you require a license to one of the following tools (where applicable), then
- **After Effects** enables the generation of videos and provides control of individual animated elements within a composition. Use this if you're looking to generate bespoke animations to use in your videos.
-- **Premiere Pro** - Use this when piecing together multiple bits of footage and existing FlowForge templates. Premiere Pro is better for stitching existing compositions, for example, the opening/closing FlowForge title sequences, either side of some demo footage.
+- **Premiere Pro** - Use this when piecing together multiple bits of footage and existing FlowFuse templates. Premiere Pro is better for stitching existing compositions, for example, the opening/closing FlowFuse title sequences, either side of some demo footage.
#### Image Editing
@@ -67,15 +67,15 @@ If you require a license to one of the following tools (where applicable), then
Our Release Videos follow a very fixed structure [with templates listed]:
-1. FlowForge Intro _[Template: /Bookends/Intro]_
+1. FlowFuse Intro _[Template: /Bookends/Intro]_
2. Call out 3-4 Major Features introduced in this particular release (with screen recorded demos) _[Template: /UI Previews]_
3. "and much more..." to include additional important features & bug fixes _[Templates: Overlays/Corner Stamps/Release & Date, /Feature Bullet]_
-4. FlowForge Outro Ident _[Template: /Bookends/Outro]_
+4. FlowFuse Outro Ident _[Template: /Bookends/Outro]_
##### Recording Demos for Release Videos
Screen recordings used within the Release Videos should be recorded at 1800 x 1080 in order to fit within the reusable template. The border size can be easily adjusted though if required.
-In our "FlowForge Templates" Adobe Premiere Pro library we have three "UI Preview" templates available at different lengths (10, 13 and 15 seconds). It is recommended to edit the recordings in a piece of software of your choice down to your chosen timing, as this will make use of the templates a lot easier.
+In our "FlowFuse Templates" Adobe Premiere Pro library we have three "UI Preview" templates available at different lengths (10, 13 and 15 seconds). It is recommended to edit the recordings in a piece of software of your choice down to your chosen timing, as this will make use of the templates a lot easier.
#### Marketing Videos
diff --git a/src/handbook/marketing/webinars.md b/src/handbook/marketing/webinars.md
index 21ab2f5930..d5e9acd714 100644
--- a/src/handbook/marketing/webinars.md
+++ b/src/handbook/marketing/webinars.md
@@ -1,72 +1,72 @@
----
-navTitle: Webinars
-navGroup: Sales & Marketing
----
-
-## FlowForge Webinars
-
-FlowForge will organize two types of webinars: 1) Ask Me Anything session that is an ope mic for community members to ask questions of Node-RED and FlowForge experts, and 2) Educational webinars that will educational topics. The current plan is to do an AMA session the second week of each month and an educational webinar the last week of the month.
-
-### Hosting Webinars
-FlowForge will use the Zoom Webinar platform to host each webinar. This platform provides the automated recording, email reminders, calendar entries, Q&A and accommodate up to 500 attendees.
-
-Hubspot will be used to collect attendee registrations.
-
-### Steps to Schedule a Webinar
-
-1. Select a topic and speaker
- * Create a title and abstract for the webinar and speaker bio
-2. Schedule webinar in Zoom
- * Zoom will automatically send a confirmation email and a two reminder emails to all registrants.
-3. Create a webinar page for the website
- * Follow the templates from previous months - more details can be found [below](#creating-a-webinar-page).
-4. Create a graphic to promote the webinar
- * Follow the templates from previous months.
-5. Setup Hubspot for Webinar
- * Create a static list to track the registrations
- * Change the webinar workflow to point to the new static list
- * Change the webinar workflow to point to the new Zoom Webinar ID. The ID can be found in the Zoom webinar page. NOTE: you need to use hyphens to replace the spaces in the ID number.
-
-### Promoting Webinars
-
-Each webinar should be available for promotion 2-4 weeks before the live date. Channels for promotion include:
-* Flowforge newsletter
-* Social media
-* Slack channels
-* Node-RED forums
-* FlowForge website
-
-### Creating a Webinar Page
-
-Webinar pages follow a fixed structure, you can see plenty of examples [here](https://github.com/flowforge/website/tree/main/src/webinars) in our website repository. Importantly, they must define the following properties at the top of the `.md` file:
-
-#### Properties
-
-| Property | Description
-|-|-|
-| `title` | The title of the webinar, this will also be what shows as the "title" when shared on socials
-| `subtitle` | More context on what the webinar will involve
-| `video` | Once you have an available video recording of the session, you can include the videos' YouTube id here to include the recording in the webinar's page
-| `image` | Absolute file path to the image to show for the Webinar's tile
-| `date` | The date that the webinar will take place
-| `time` | The time that the webinar will take place, in both GMT & ET
-| `duration` | How long, in minutes with the webinar last for
-| `hosts` | A list of the webinar hosts, the names need to be formatted inline with the file names found [here](https://github.com/flowforge/website/tree/main/src/_data/team)
-| `hubspot.formId` | The formId from HubSpot to handle the event registration
-
-#### Example
-
-```yml
----
-title: "DevOps for Node-RED: An Introduction to FlowForge"
-subtitle: Join FlowForge's CTO Nick O'Leary for an introduction to FlowForge and how it provides DevOps for Node-RED.
-video: 47EvfmJji-k
-image: /images/webinars/webinar-nr-5mins.jpg
-date: YYYY-MM-DD
-time: HH:MM GMT (HH:MM ET)
-duration: MM
-hosts: ["rob-marcer"]
-hubspot:
- formId:
diff --git a/src/handbook/product/plan.md b/src/handbook/product/plan.md
index e73d5a8e46..f1e23cdae1 100644
--- a/src/handbook/product/plan.md
+++ b/src/handbook/product/plan.md
@@ -3,9 +3,7 @@ navTitle: Plan
---
# Product Plan
-## Background
-
-Our [Product Strategy](./strategy.md) sets out 4 pillars that our product work is focussed around.
+Our [Product Strategy](/handbook/product/strategy.md) sets out 5 pillars that our product work is focussed around.
## Planning
@@ -17,58 +15,53 @@ We use three project boards to plan and track our work.
The detailed planning process can be found [here](../development/releases/planning.md)
-## Principles
+## High-Level Strategy Implementation for Q3/Q4 2023
+
+Our high-level strategy implementation plan serves as a broad outline of the key focus areas for each strategy pillar we will be tackling over the course of the next six months. The points mentioned here are just an overview, and for more granular details on each initiative, we recommend referring to our roadmap.
+
+The progress bars presented adjacent to each category are rough estimates, offering an initial glance at the projected level of completion for each category's planned feature set. These are not precise calculations, nor do they represent the current status of each strategy pillar. It's important to note that at the start of every new product plan cycle, these progress bars reset to a lower level, reflecting the onset of new development and implementation stages. For detailed updates on the actual status, please keep an eye on our [release blog posts](/blog/releases/).
+
+### Advancing Enterprise-Readiness
+
+
+- [High availability & Scalability](https://github.com/flowforge/flowforge/issues/1678)
+
+- Improve DevOps Pipelines
+
+- [VPN support for Instances](https://github.com/flowforge/flowforge/issues/1570)
+
+- [Introduce Value Layer Model](https://github.com/flowforge/flowforge/issues/2167)
+
+- [Implement "Organization" as an additional hierarchy level](https://github.com/flowforge/flowforge/issues/2338)
+
+
+### Node-RED Deployments at the Edge (Device Management)
+
-#### Convention over configuration
+- [Device can be managed independently of Instances on Application level](https://github.com/flowforge/flowforge/issues/2334)
-We want the default configuration of FlowForge to be the best user experience for
-the majority of users.
+- [Grouped Device Deployments](https://github.com/flowforge/flowforge/issues/1509)
-Every new option we add to the platform, whether for an administrator or end-user,
-represents another choice they have to deal with. This increases the cognitive burden
-of using the platform and can have a negative impact on user experience. It also
-increases the engineering cost to develop and test features where there are many
-possible combinations to consider.
+### Enhanced Integration Capabilities
+
-For every feature we add that has some scope for configuration, our starting point
-in the design is to **identify the right configuration and hard-code it in**.
+- [Official Support for selected Node-RED nodes](https://github.com/flowforge/flowforge/issues/1901)
-This removes the choice from users' hands and minds. It does not prevent us from
-choosing to make it more configurable in the future if user-feedback/business-needs
-requires it.
+- [Support for custom NPM Module registry](https://github.com/flowforge/flowforge/issues/217)
-Where there is a strong case to expose an option to the end user, it should still
-be provided with a sensible default value where possible that removes the need
-for the user to set it themselves. This gives users the ability to customise
-the option if/when they are ready to. But the default value should be the right
-answer for most users.
+- [Visibility of different palette catalogues in Node-RED](https://github.com/node-red/node-red/issues/4057)
-Some configuration options cannot be defaulted - the user has to do make a choice.
-For example, setting up email on the platform. The UX around these options must
-be carefully considered to help the user get to the right choice with a minimum
-of effort.
-Node-RED provides a lot of configuration options. We should not assume they are all
-candidates to be exposed to FlowForge users. For example, options to customise the
-editor appearance should be reserved options that we determine the right values for
-to ensure a consistent user experience across FlowForge instances.
+### Data Visualization & Analytics
+
-Options that have an impact on the behaviour of flows will need to be considered
-on a case-by-case basis. But the starting point should always be to pick the right
-default and only expose to the user if absolutely necessary.
+- Version 1.0 of the Node-RED Dashboard successor, with a comparable feature set like [Node-RED Dashboard](https://github.com/node-red/node-red-dashboard).
+- FlowFuse Dashboard extension (Version 1.0) allowing [user specific dashboards](https://github.com/flowforge/flowforge-nr-dashboard/issues/1) and RBAC.
-See also: [Convention over Configuration on Wikipedia](https://en.wikipedia.org/wiki/Convention_over_configuration).
+### User-Friendly Low-Code Approach
+
-##Ā Open Source & Enterprise
+- [Immersive Node-RED experience](https://github.com/flowforge/flowforge/issues/2246)
-We offer a number of ways that users can run the FlowForge product, we will
-always offer an open source version that has the core features. Features that
-offer higher business value or permit users to share across larger groups will
-be offered as part of our paid enterprise proposition. Our managed FlowForge
-offering is public and will generally include all features that are available
-but may not offer certain features such as SSO where integration is required
-between the platform and an enterprise. We will offer customers the ability to
-have a dedicated managed instance if thats is a deployment model they require.
-A more detailed breakdown of the pricing and split between our Open Source and
-Enterprise Editions is on the [pricing principles](pricing.md) page.
+- First out of the box IIoT Solutions template (e.g. ANDON for Node-RED)
\ No newline at end of file
diff --git a/src/handbook/product/pricing.md b/src/handbook/product/pricing.md
index d24b9ba745..3ff8ebcccd 100644
--- a/src/handbook/product/pricing.md
+++ b/src/handbook/product/pricing.md
@@ -4,10 +4,20 @@ navTitle: Pricing Principles
# Pricing Principles
-This page sets out the concepts that we license and what units are measured across both FlowForge Cloud and Self-managed. Commercial decisions outside the scope of this document.
+This page sets out the concepts that we license and what units are measured across both FlowFuse Cloud and Self-managed. Commercial decisions outside the scope of this document.
We have three primary tiers: Starter (Open-Source when self-managed), Premium, and Enterprise. The value and features provided within each tier correspond to the specific [persona](./personas/), acknowledging that a higher placement in the organisational chart typically implies different requirements.
+## Buyer-Based Open Core (BBOC) Principle
+
+The [Buyer-Based Open Core (BBOC)](https://opencoreventures.com/blog/2023-01-open-core-standard-pricing-model/) principle is a fundamental guideline in our product
+development and monetization strategy. It's a framework we employ to discern which features should be open source and which should be proprietary.
+BBOC aligns features into tiers based on their target users or 'buyers' ā individual contributors, management, or executives.
+
+Features that are most beneficial to individual contributors, such as PLC engineers and line workers, fall within our Starter (Open-Source) tier. On the other hand, features that have broader organizational relevance, like Edge Device Management or high availability, are offered in our Premium tier or Enterprise tier, targeted towards IIoT managers and plant managers who need to manage multiple Node-RED instances.
+
+This buyer-based approach helps us focus our efforts on the value to the end-user, rather than technical specifications or development effort. It aligns our pricing strategy with the value each tier provides, ensuring that the cost is justified by the capabilities offered and the user persona it serves.
+
## Value Layers
| Tier | Objective | Problem it Solves | Persona |
@@ -18,12 +28,12 @@ We have three primary tiers: Starter (Open-Source when self-managed), Premium, a
## Teams
-Teams are the basic unit within FlowForge Cloud and the entity to which bills are charged.
+Teams are the basic unit within FlowFuse Cloud and the entity to which bills are charged.
A teams can create zero or more applications, and one or more user can be members.
Subject to access controls, some users can add cloud instances and remote devices (agents)
to applications, and invite other members.
-The number of teams for the open source offering of FlowForge is limited to 50.
+The number of teams for the open source offering of FlowFuse is limited to 50.
## Applications
@@ -32,14 +42,14 @@ based on the number of Node-RED instances consuming resources inside application
## Cloud instances
-On the FlowForge Cloud, different levels of pricing is offered based on the
+On the FlowFuse Cloud, different levels of pricing is offered based on the
resources that the instance has available (CPU/Mem). The price point is defined
by the instance type which allows for an abstraction of stacks and billing. Additional
features may also be defined by the instance type, for example: Custom Domains support.
-Self-managed FlowForge installs are licensed based on the number of Node-RED instances, regardless of
+Self-managed FlowFuse installs are licensed based on the number of Node-RED instances, regardless of
available resources for each. Open source installs are limited to 50 instances per
-FlowForge installation, and some features for instances aren't available, for example Persistent Context.
+FlowFuse installation, and some features for instances aren't available, for example Persistent Context.
## Devices
@@ -51,7 +61,7 @@ Devices are part of the licensed instances. The limit in the open source edition
## Licenses
-From the perspective of licensing the there's an unlicensed edition: open-source. This version is always self-managed. There's also a licensed version of FlowForge, this can be self-managed or FlowForge Managed. For FlowForge managed properties there's 3 tiers; Starter, Premium, and Enterprise.
+From the perspective of licensing the there's an unlicensed edition: open-source. This version is always self-managed. There's also a licensed version of FlowFuse, this can be self-managed or FlowFuse Managed. For FlowFuse managed properties there's 3 tiers; Starter, Premium, and Enterprise.
The open source edition doesn't require a license key to be uploaded. Without a valid license a basic set of features and
quantity of instances(50), users(150), teams(50), and devices(50) are available.
When a license is purchased it provides all of the functionality of the higher
diff --git a/src/handbook/product/strategy.md b/src/handbook/product/strategy.md
index c417e4d823..03c9fd6828 100644
--- a/src/handbook/product/strategy.md
+++ b/src/handbook/product/strategy.md
@@ -4,61 +4,47 @@ navTitle: Strategy
# Product Strategy
-Our strategy is an indication and statement of intent for the next 2 years, and reflects FlowForgeās vision. Itās a draft, as everything in the handbook is a draft, so we will revisit regularly and iterate when there is a reason to do so. FlowForge is a 100 percent agile company, so our product is; timing is everything. Have a look at our roadmap for what we're pursuing in the upcoming releases.
+Our strategy is an indication and statement of intent for the next 2 years, and reflects FlowFuseās vision, to become the leading "Low-Code IIoT Application Platform".
+FlowFuse will allow everyone to build custom applications to achieve their business goals and depend less on off-the-shelf software.
+Itās a draft, as everything in the handbook is a draft, so we will revisit regularly and iterate when there is a reason to do so. FlowFuse is a 100 percent agile company, so our product is; timing is everything.
+Have a look at our [roadmap](/product/roadmap/) for what we're pursuing in the upcoming releases.
-### FlowForge for enterprise
+### Advancing Enterprise-Readiness
-The cornerstone of FlowForge is to make Node-RED more accessible to enterprises. Therefore, we are constantly implementing requirements that support the easy use of Node-RED in production environments. We will focus on:
+FlowFuse is committed to augmenting the enterprise-readiness of Node-RED. Our strategy emphasises enhancing audit and compliance capabilities, instituting stringent preventive and corrective controls, and bolstering security. By integrating these vital aspects, we aim to create a reliable, secure, and scalable environment. This initiative underlines our dedication to surpassing enterprise expectations and strengthening Node-RED's position in the industry.
-1. [High availability & Scalability](https://github.com/flowforge/flowforge/issues/1678)
-
-2. State-of-the-art built-in security e.g. VPN support
-
-3. DevOps
-
- 1. Change control
-
- 2. Collaborative Development
-
- 3. Pipelines (e.g. staging)
-
-### Node-RED at edge
+### Node-RED Deployments at the Edge (Device Management)
Many organizations position Node-RED instances on remote servers, edge or industrial devices, to meet network, infrastructure, or use case requirements. Therefore, management of remote instances is crucial for the overall success of closing the gap between IT and OT.
-FlowForge already supports this process by creating snapshots on Node-RED instances that can be deployed to multiple remote targets. We will continue to expand the functionalities to allow users to manage existing Node-RED instances, improve their development practices to accelerate development and ensure a reliable and repeatable process, providing more flexible remote deployment options and offering the best support for devices in closed and segmented networks as we are facing it in production environments.
-
-### Certified nodes marketplace
+FlowFuse already supports this process by creating snapshots on Node-RED instances that can be deployed to multiple remote targets. We will continue to expand the functionalities to allow users to manage existing Node-RED instances, improve their development practices to accelerate development and ensure a reliable and repeatable process, providing more flexible remote deployment options and offering the best support for devices in closed and segmented networks as we are facing it in production environments.
-The "Node-RED Library" offers a unique added value to many Node-RED and FlowForge users. It is already possible today to easily create technical implementations out of the box for several OT and IT protocols, thanks to the community and Node-RED library.
+### Enhanced Integration Capabilities
-The logical consequence of FlowForgeās journey is to also include ācustom nodesā as one element of the product. Therefore, FlowForge will offer official support for certain popular nodes and in addition enable the community to offer commercial ānodesā via FlowForge. Nevertheless, an open-source core is always required and wanted. However, premium extensions and commercial support allow the community to participate in the success of FlowForge.
+The "Node-RED Library" offers a unique added value to many Node-RED and FlowFuse users. It is already possible today to easily create technical implementations out of the box for several OT and IT protocols, thanks to the community and Node-RED library.
-### IIoT Solutions
+As a part of our evolution, FlowFuse plans to incorporate "custom nodes" into our product line. In this endeavour, we'll offer official support for selected popular nodes while also enabling the community to provide commercial nodes via FlowFuse. While maintaining an open-source core remains a priority, we believe that offering premium extensions and commercial support can encourage community participation in FlowFuse's success.
-Today, a whole range of use cases can be implemented with Node-RED. From KPI calculations to intralogistics solutions, incredible use cases are already being realized in Node-RED.
+This integration strategy includes communication protocols, APIs, and application adapters. These elements will not only meet the data and process integration needs but also address enterprise application and IIoT ecosystem integration requirements across cloud and on-premises implementations, providing a comprehensive solution.
-To make it easy for FlowForge users in particular to get started and address their specific need, a use case library is to be created (based on the "Node-RED Library"), which offers standard templates for specific IT and OT related use cases. This way, we as FlowForge address direct added values in production, for example:
+### Data Visualization & Analytics
-1. Condition Monitoring
+FlowFuse's commitment to a low-programming approach via Node-RED, complemented by Node-RED Dashboard, allows for advanced data management and analytical functions. The Node-RED Dashboard provides a crucial interactive graphical user interface for Node-RED applications, allowing users to see data in a more visually engaging and understandable format. By processing and visualization of data, we will deliver insights into asset state, track patterns, and optimize asset use.
-2. Overall Equipment Effectiveness (OEE) calculation and visualization
+### User-Friendly Low-Code Approach
-3. ANDON for Node-RED
+FlowFuse is built upon the strength of Node-RED's user-friendly, low-code approach, positioning us well within the IIoT market. We believe Node-RED provides the best foundation, but we're committed to not only utilizing its existing capabilities but also contributing to its upstream improvement. By refining Node-RED and adding enhancements, we aim to create an even more intuitive, powerful, and accessible platform. This will enable end-users to swiftly and intuitively build applications and reducing the dependency on expert programmers.
-4. Process monitoring for e.g. tightening equipment
+----
-5. Predictive maintenance analysis
-
-6. Reliable feedback loops between IT and OT
-
-.......
## Principles
-#### Convention over configuration
+Embedded within our strategy are the principles that guide our decision-making and product evolution, representing our commitment to providing a user-centered platform that seamlessly merges the virtues of open-source development with enterprise-grade functionality.
+
+### Convention over configuration
-We want the default configuration of FlowForge to be the best user experience for
+We want the default configuration of FlowFuse to be the best user experience for
the majority of users.
Every new option we add to the platform, whether for an administrator or end-user,
@@ -86,9 +72,9 @@ be carefully considered to help the user get to the right choice with a minimum
of effort.
Node-RED provides a lot of configuration options. We should not assume they are all
-candidates to be exposed to FlowForge users. For example, options to customise the
+candidates to be exposed to FlowFuse users. For example, options to customise the
editor appearance should be reserved options that we determine the right values for
-to ensure a consistent user experience across FlowForge instances.
+to ensure a consistent user experience across FlowFuse instances.
Options that have an impact on the behaviour of flows will need to be considered
on a case-by-case basis. But the starting point should always be to pick the right
@@ -96,12 +82,12 @@ default and only expose to the user if absolutely necessary.
See also: [Convention over Configuration on Wikipedia](https://en.wikipedia.org/wiki/Convention_over_configuration).
-## Open Source & Enterprise
+### Open Source & Enterprise
-We offer a number of ways that users can run the FlowForge product, we will
+We offer a number of ways that users can run the FlowFuse product, we will
always offer an open source version that has the core features. Features that
offer higher business value or permit users to share across larger groups will
-be offered as part of our paid propositions. FlowForge Cloud is public and will
+be offered as part of our paid propositions. FlowFuse Cloud is public and will
generally include all open-source features that are available but may not offer
certain features such as SSO where integration is required between the platform
and an enterprise. We offer customers the ability to have a dedicated managed
diff --git a/src/handbook/product/versioning.md b/src/handbook/product/versioning.md
index dc99693777..bc0b3e57ca 100644
--- a/src/handbook/product/versioning.md
+++ b/src/handbook/product/versioning.md
@@ -6,7 +6,7 @@ navTitle: Versioning
## Preview Features
-As part of our [continuous improvement](../company/values/#š-iterative-improvement) process at FlowForge, we may designate certain functionalities as Preview Features. During this phase, all of our customers are given the unique opportunity to trial and test these features. While we ensure the provision of support services, it's important to understand that standard service-level agreements do not apply to these Preview Features. We highly value [customer feedback](./feedback.md) during this period; it not only contributes to our feature refinement process, but also shapes the future development of our offerings.
+As part of our [continuous improvement](../company/values/#š-iterative-improvement) process at FlowFuse, we may designate certain functionalities as Preview Features. During this phase, all of our customers are given the unique opportunity to trial and test these features. While we ensure the provision of support services, it's important to understand that standard service-level agreements do not apply to these Preview Features. We highly value [customer feedback](./feedback.md) during this period; it not only contributes to our feature refinement process, but also shapes the future development of our offerings.
There are no extra charges associated with the utilization of Preview Features. Nevertheless, we want to clarify that as these features transition from their preview status to being generally available, they may become subject to changes in pricing in subsequent releases.
@@ -14,7 +14,7 @@ Preview Features exemplify our commitment to expedited innovation and iterative
## 1.0
-The 1.0 Release of FlowForge represents a significant milestone, we are making a statement to our customers about the product.
+The 1.0 Release of FlowFuse represents a significant milestone, we are making a statement to our customers about the product.
Therefore the following are considerations & requirements in order to be able to stand behind that statement.
diff --git a/src/handbook/product/verticals.md b/src/handbook/product/verticals.md
index 3cb9c5069f..f5926be22f 100644
--- a/src/handbook/product/verticals.md
+++ b/src/handbook/product/verticals.md
@@ -8,7 +8,7 @@ Product categories refer to specific, identifiable segments within an industry o
## Industrial IoT Platforms
-An IIoT platform is a comprehensive solution that securely collects, integrates, and manages vast volumes of data from IoT endpoints. It supports various manufacturer and industry protocols, normalizing and analyzing data at the edge and in the cloud. By bridging IT and OT endpoints, it enhances asset management and promotes application development. It can supplement traditional OT functions and pivot asset-intensive industries like manufacturing or energy towards digitalization. The IIoT platform should fulfill key requirements like security, automation, and sustainability. It enables interoperability with various business applications. Key capabilities include device management, integration, data management, analytics, application enablement, and security (see also [IIoT platform definition](https://www.gartner.com/doc/reprints?id=1-2C757S9J&ct=230105&st=sb)). With its prowess in connecting and processing data from IIoT devices, Node-RED finds a fitting place in the sphere of IIoT platforms, becoming an integral tool in industries like manufacturing where the utility of such data is paramount for fostering operational efficacy and stimulating innovation. Further augmenting Node-RED's proficiency, FlowForge introduces enterprise-grade features that streamline the management of remote deployments and delivery pipelines, thus amplifying Node-RED's and FlowForge's potential as IIoT platform.
+An IIoT platform is a comprehensive solution that securely collects, integrates, and manages vast volumes of data from IoT endpoints. It supports various manufacturer and industry protocols, normalizing and analyzing data at the edge and in the cloud. By bridging IT and OT endpoints, it enhances asset management and promotes application development. It can supplement traditional OT functions and pivot asset-intensive industries like manufacturing or energy towards digitalization. The IIoT platform should fulfill key requirements like security, automation, and sustainability. It enables interoperability with various business applications. Key capabilities include device management, integration, data management, analytics, application enablement, and security (see also [IIoT platform definition](https://www.gartner.com/doc/reprints?id=1-2C757S9J&ct=230105&st=sb)). With its prowess in connecting and processing data from IIoT devices, Node-RED finds a fitting place in the sphere of IIoT platforms, becoming an integral tool in industries like manufacturing where the utility of such data is paramount for fostering operational efficacy and stimulating innovation. Further augmenting Node-RED's proficiency, FlowFuse introduces enterprise-grade features that streamline the management of remote deployments and delivery pipelines, thus amplifying Node-RED's and FlowFuse's potential as IIoT platform.
However, a potential downside is that it may currently be perceived as too general-purpose and not specialized enough for specific IIoT tasks compared to other, more narrowly focused IIoT platforms.
@@ -34,11 +34,11 @@ The primary customer base in the IIoT sector includes manufacturing, energy, tra
### Positioning
-FlowForge needs to leverage its enterprise features and also focus on providing an end-to-end IIoT solution. By promoting its capacity for device management and remote deployments, it can appeal to organizations seeking greater operational control and efficiency. Furthermore, forging partnerships with key industrial equipment manufacturers can help integrate FlowForge as part of a comprehensive IIoT solution.
+FlowFuse needs to leverage its enterprise features and also focus on providing an end-to-end IIoT solution. By promoting its capacity for device management and remote deployments, it can appeal to organizations seeking greater operational control and efficiency. Furthermore, forging partnerships with key industrial equipment manufacturers can help integrate FlowFuse as part of a comprehensive IIoT solution.
## Low-Code Tools
-Low-code platforms enable rapid application development with minimal hand-coding, which aligns well with Node-RED's offering of a visual, drag-and-drop interface for creating flow-based applications. Node-RED allows users with limited programming knowledge to create complex IoT applications, which fits well with FlowForge's focus on collaborative development and management of Node-RED applications.
+Low-code platforms enable rapid application development with minimal hand-coding, which aligns well with Node-RED's offering of a visual, drag-and-drop interface for creating flow-based applications. Node-RED allows users with limited programming knowledge to create complex IoT applications, which fits well with FlowFuse's focus on collaborative development and management of Node-RED applications.
However, the potential disadvantage is that low-code tools can sometimes be viewed as less powerful or flexible than high-code platforms, and the target customers are challenging to define.
@@ -59,13 +59,13 @@ Businesses looking to accelerate digital transformation are the primary customer
### Positioning
-FlowForge should position itself as a comprehensive low-code platform, ideal for both novices and experienced developers. This includes emphasizing its drag-and-drop interface for application building and the ability to scale and manage applications easily. A strong focus on community-building and providing an extensive library of pre-built components can help attract a wider user base.
+FlowFuse should position itself as a comprehensive low-code platform, ideal for both novices and experienced developers. This includes emphasizing its drag-and-drop interface for application building and the ability to scale and manage applications easily. A strong focus on community-building and providing an extensive library of pre-built components can help attract a wider user base.
## Data Integration Tools
Also known as IPaaS (Integration Platform as a Service), this market serves business users looking to integrate workflows across multiple different systems. Typically, these are cloud-hosted SaaS types of systems, usually with some sort of public API. There is also the scenario of integrating between cloud systems and internal company systems or data stores.
-While this is an essential function of Node-RED, it doesn't encompass all the capabilities and the broader aim of FlowForge.
+While this is an essential function of Node-RED, it doesn't encompass all the capabilities and the broader aim of FlowFuse.
### [Market Size](https://www.vynzresearch.com/ict-media/global-ipaas-market)
@@ -94,4 +94,4 @@ Some of the companies that are in this market include:
### Positioning
-FlowForge should highlight its capabilities as an advanced data integration platform, emphasizing its ability to simplify data collection and transmission. Showcasing partnerships with major database providers and cloud systems could enhance its appeal as a capable and versatile data integration tool.
\ No newline at end of file
+FlowFuse should highlight its capabilities as an advanced data integration platform, emphasizing its ability to simplify data collection and transmission. Showcasing partnerships with major database providers and cloud systems could enhance its appeal as a capable and versatile data integration tool.
\ No newline at end of file
diff --git a/src/handbook/sales/demo.md b/src/handbook/sales/demo.md
index 1158469132..d62a03c883 100644
--- a/src/handbook/sales/demo.md
+++ b/src/handbook/sales/demo.md
@@ -1,32 +1,48 @@
## Demo
-This document explains the process of delivering a sales demo of the features of FlowForge. It is not intended to cover all features but to give potential customers a good understanding of FlowForge's value.
+This document explains the process of delivering a sales demo of the features of FlowFuse. It is not intended to cover all features but to give potential customers a good understanding of FlowFuse's value.
-### Setup (complete before the demo)
+### Setup - Before the demo
Before we begin a sales demo we need to set up an environment. Make sure you are
-already logged into your flowforge account (@flowforge.com email) on production, not as an administrator.
+already logged into your flowforge account (@flowfuse.com email) on production, not as an administrator.
Create a new team for this demo, you need to do this before the demo so that
you donāt have to show your credit card details on screen. After creating the
team, apply [this coupon](https://dashboard.stripe.com/coupons/zkNy9DxL) to your
newly created team. On the stripe team page, click "Actions" > "Apply Coupon".
+Please also make this team your 'default team' under your user settings.
+
Create one instance called ācentral-ā, leave the rest to be created in the demo.
Make sure you have an example device ready, [install the latest device agent](https://flowforge.com/docs/user/devices/).
-Make sure the device agent is running before you start the demo and connected to the team you've just created.
+Create a new device in your team, download the `.yml`. Do not yet install the
+agent, that's done during the demo using the web ui.
+
+```
+cd /tmp
+```
+```
+mkdir demo-
+```
+```
+cd demo-
+```
+```
+flowforge-device-agent -d . --ui --ui-user foo --ui-pass bar
+```
The script should not be followed word for word, it's more a suggestion of what to say which fits with what will be displayed. Be natural, use your own words.
### Script
-FlowForge makes it easy for teams of developers to collaborate on creating, maintaining, and improving applications built in Node-RED.
+FlowFuse makes it easy for teams of developers to collaborate on creating, maintaining, and improving applications built in Node-RED.
-It can manage instances of Node-RED running on FlowForge Cloud, a version of FlowForge hosted by yourselves, and on your own hardware, for example devices running sensors on your shop floor.
+It can manage instances of Node-RED running on FlowFuse Cloud, a version of FlowFuse hosted by yourselves, and on your own hardware, for example devices running sensors on your shop floor.
-In this demo we're going to focus on the key features of FlowForge, there is a lot that we're not going to cover to keep this suitably brief but we will have some time after the demo for any questions.
+In this demo we're going to focus on the key features of FlowFuse, there is a lot that we're not going to cover to keep this suitably brief but we will have some time after the demo for any questions.
#### Key Concepts
@@ -39,7 +55,7 @@ To start, letās cover some [key concepts](/docs/user/concepts/) which are:
#### Live Demo
-Now weāve covered off some of the key concepts, let's run through some common tasks on how FlowForge makes them easier.
+Now weāve covered off some of the key concepts, let's run through some common tasks on how FlowFuse makes them easier.
Firstly, weāll create a new application with 3 instances.
@@ -49,9 +65,9 @@ The second is going to be deployed to PLCs in a factory. Each device has access
The third instance will provide a HMI which would be accessed via installed devices on the shop floor (mounted tablets) as well as via mobile devices carried by managers and engineers.
-So, Iāve now spun up three instances with descriptive names. At this time all the instances are running on FlowForge, weāll look at how to deploy the instance to the PLC once we have a system up and running.
+So, Iāve now spun up three instances with descriptive names. At this time all the instances are running on FlowFuse, weāll look at how to deploy the instance to the PLC once we have a system up and running.
-FlowForge has a fantastic feature build in which is called Project Link Nodes. These nodes leverage the MQTT protocol to pass data securely from each of the instances within an application. We are going to be using the project link nodes to pass data from the on-site devices to the central processing system. The HMI will also use this same communication method to pull down the data needed to populate its interface.
+FlowFuse has a fantastic feature build in which is called Project Link Nodes. These nodes leverage the MQTT protocol to pass data securely from each of the instances within an application. We are going to be using the project link nodes to pass data from the on-site devices to the central processing system. The HMI will also use this same communication method to pull down the data needed to populate its interface.
Iām going to install [node-red-contrib-os](https://flows.nodered.org/node/node-red-contrib-os), itās a great node which can pull data from the hardware Node-RED is running on. Iām using that to simulate data coming from the shop floor device. In a real world example weād usually be collecting data via USB or GPIO sensors but the data from the device is a good proxy.
@@ -65,9 +81,9 @@ Letās now move the device instance to the actual device itās going to run on
To do that Iām going to take a snapshot of the instance, associate the device with it then set the snapshot as a target.
-OK, we can now see the flow being deployed to the device and the data is now coming in from two places, from the instance on FlowForge as well as the device.
+OK, we can now see the flow being deployed to the device and the data is now coming in from two places, from the instance on FlowFuse as well as the device.
-To save on resources Iām going to pause the instance on FlowForge, you can leave an instance paused on FlowForge, you are only charged for the time it is running.
+To save on resources Iām going to pause the instance on FlowFuse, you can leave an instance paused on FlowFuse, you are only charged for the time it is running.
We can now see we are only getting one payload per second.
@@ -75,9 +91,9 @@ Maybe once a second is a little too often, letās make that change directly on
Iām going to put the device into development mode then open up the design interface directly on that device. Whatās great about this is, that device can be anywhere in the world, as long as it can connect out to the internet we can access it, view debug and as we are going to do now make changes to the flow.
-Iāve changed the inject to only run every 5 seconds. I can deploy that change but I also want to store the correct snapshot back in FlowForge. This is really useful where you are running multiple devices with the same instance on them all.
+Iāve changed the inject to only run every 5 seconds. I can deploy that change but I also want to store the correct snapshot back in FlowFuse. This is really useful where you are running multiple devices with the same instance on them all.
-Back in FlowForge Iāve taken a snapshot, set it as the target snapshot and set the device to no longer be in development mode.
+Back in FlowFuse Iāve taken a snapshot, set it as the target snapshot and set the device to no longer be in development mode.
We can now link up the central device to store the data, potentially in SQL or a time series database such as InfluxDB. There are easy to use custom nodes for both. Iām not going to set that up now to save us a little time but itās something thatās easy to get working.
@@ -89,13 +105,15 @@ Letās build a simple dashboard to show the data. Weāll use [node-red-dashboa
Iām going to output the current RAM usage onto a graph which shows data for the last hour. This graph will auto update. This system will request new data every 10 seconds. Letās also output the current value in a gauge.
+
+
You can access the HMI yourself now if you want, the URL isā¦
### End of Demo
-Hopefully this demo has given you some good examples of how FlowForge offers significant value beyond a standard Node-RED installation.
+Hopefully this demo has given you some good examples of how FlowFuse offers significant value beyond a standard Node-RED installation.
-There is a lot Iāve not covered today so we can have a good amount of time for questions. If there are features of FlowForge Iāve not mentioned that are of interest or if youād like to ask more about what I have covered today Iād be happy to hear your questions.
+There is a lot Iāve not covered today so we can have a good amount of time for questions. If there are features of FlowFuse Iāve not mentioned that are of interest or if youād like to ask more about what I have covered today Iād be happy to hear your questions.
### Housekeeping
diff --git a/src/handbook/sales/index.md b/src/handbook/sales/index.md
index f69da5f716..2ef5bde1ab 100644
--- a/src/handbook/sales/index.md
+++ b/src/handbook/sales/index.md
@@ -2,11 +2,52 @@
navGroup: Sales & Marketing
---
-This section details how to engage with customers at FlowForge and particularly how you should communicate with customers about FlowForge, including a recommended demo script for showing how FlowForge works.
+This section details how to engage with customers at FlowFuse and particularly how you should communicate with customers about FlowFuse, including a recommended demo script for showing how FlowFuse works.
# Sales
- [Demo](./demo.md)
- - [Sales Pitch](./pitch.md)
- [Engagements & Pricing](./pricing.md)
- [Sales playbook (internal)](https://docs.google.com/document/d/1Jrt5sNg46wngQ5UAii8sbN94PTlIAscOWrFcOhSVNPE/edit){rel="nofollow"}
+
+## Lead status
+
+For leads who are [MQLs or SQLs](/handbook/marketing/hubspot.md) the `Lead status`
+field is used to mark what the status is. Even though they're beyond being a lead.
+This field is maintained by the primary contact owner, likely the account executive.
+
+At this stage we're using the default set of status's in HubSpot:
+
+| Lead status | When to use |
+| :---------: | :---------- |
+| New | The contact in question has had only _marketing_ contact (E-mails, etc). |
+| Open | In the stage where a contact is assigned to a Account exec, but no official connection has be made. Usually contacts are only in this stage for a short while.|
+| Attempted to contact | From the moment the AE reached out, until there's a reply from them. |
+| Connected | MQLs and SQL that have replied and engaged with FlowFuse. |
+| In Progress | After contact has been made, this status captures the nurturing process toward an opportunity. |
+| Open Deal | When a deal is on the board, and the opportunity is real, this is the status! |
+| Unqualified | Either this contact specifically cannot lead the sales process, or the account itself has been found unqualified. |
+| Unresponsive | We have not received a reply in 2 weeks, they are ghosting us. |
+| Bad timing | FlowFuse was, for whatever reason, not a great fit right now. However, it's potentially a good fit later. |
+
+## From MQL to SQL - Qualifying questions
+
+1. Have you adopted Node-RED? If so, what have you built with Node-RED?
+1. How many Node Red instances do you have, and how many people are developing on Node-RED?
+1. Is Node-RED used in production?
+1. What are you looking to build in the next year with Node-RED?
+
+## From SQL to Opportunity
+
+For each sales opportunity a clear answer for the customers needs and wants should be known. It boils down to the following questions:
+
+| Question | |
+| :------- | :------ |
+| Why change? | What's the trigger to invest in FlowFuse and Node-RED? |
+| Why now? | Timeline is everything! |
+| Why FlowFuse? | What value does FlowFuse offer, what features are of most interest? |
+
+If, and only if, the answers are known and added as notes to HubSpot, an
+opportunity is added to the HubSpot deals board.
+
+See also the [stages each contact in HubSpot must go through](/handbook/marketing/hubspot.md#lifecycle-stage).
diff --git a/src/handbook/sales/pitch.md b/src/handbook/sales/pitch.md
deleted file mode 100644
index fed537f3f2..0000000000
--- a/src/handbook/sales/pitch.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-navTitle: Sales Pitch
----
-
-## Pitch
-
-Through the rapid growth of connected devices in IoT and new SaaS offerings
-being launched each day, the cost to integrate them is growing more than
-exponentially. Not integrating services isnāt an option, competitors will
-achieve higher operational efficiencies and outcompete you.
-
-Node-RED is the most deployed open source integration platform to connect
-IT (internet technology) and OT (operational technology).
-
-Bringing Node-RED to production creates toil, and the effectiveness of Node-RED
-drops due to open questions around security, deployment, and collaboration.
-FlowForge has taken all those worries and ensures peace of mind around
-everything Node-RED. Focus on integrating all your systems with each other,
-operational technology to your IT systems and back again, while FlowForge brings
-your flows to production.
diff --git a/src/handbook/sales/pricing.md b/src/handbook/sales/pricing.md
index 5ecb336072..92a85beb65 100644
--- a/src/handbook/sales/pricing.md
+++ b/src/handbook/sales/pricing.md
@@ -4,7 +4,7 @@ navTitle: Engagements & Pricing
## Pricing
-FlowForge has two commercial offerings; self-managed and FlowForge Cloud. How we
+FlowFuse has two commercial offerings; self-managed and FlowFuse Cloud. How we
engage with customers will differentiate based on the install method and size of
the opportunity.
diff --git a/src/handbook/videos/ff-intro.mp4 b/src/handbook/videos/ff-intro.mp4
deleted file mode 100755
index 40854c91ae..0000000000
Binary files a/src/handbook/videos/ff-intro.mp4 and /dev/null differ
diff --git a/src/handbook/videos/ff-outro.mp4 b/src/handbook/videos/ff-outro.mp4
deleted file mode 100755
index 7b202e793c..0000000000
Binary files a/src/handbook/videos/ff-outro.mp4 and /dev/null differ
diff --git a/src/handbook/videos/ui-services-demo.mp4 b/src/handbook/videos/ui-services-demo.mp4
deleted file mode 100755
index f2bcc3d239..0000000000
Binary files a/src/handbook/videos/ui-services-demo.mp4 and /dev/null differ
diff --git a/src/handbook/videos/using-essential-graphics-in-pp.mp4 b/src/handbook/videos/using-essential-graphics-in-pp.mp4
deleted file mode 100644
index 1c56b50f1c..0000000000
Binary files a/src/handbook/videos/using-essential-graphics-in-pp.mp4 and /dev/null differ
diff --git a/src/images/about/about.png b/src/images/about/about.png
new file mode 100644
index 0000000000..d0d8b5f0d8
Binary files /dev/null and b/src/images/about/about.png differ
diff --git a/src/images/about/investors/cota-capital.png b/src/images/about/investors/cota-capital.png
new file mode 100644
index 0000000000..474d29582c
Binary files /dev/null and b/src/images/about/investors/cota-capital.png differ
diff --git a/src/images/about/investors/opencore.png b/src/images/about/investors/opencore.png
new file mode 100644
index 0000000000..293d303ca7
Binary files /dev/null and b/src/images/about/investors/opencore.png differ
diff --git a/src/images/about/investors/uncorrelated.png b/src/images/about/investors/uncorrelated.png
new file mode 100644
index 0000000000..260f2fdd70
Binary files /dev/null and b/src/images/about/investors/uncorrelated.png differ
diff --git a/src/images/about/investors/westwave.png b/src/images/about/investors/westwave.png
new file mode 100644
index 0000000000..43fb202686
Binary files /dev/null and b/src/images/about/investors/westwave.png differ
diff --git a/src/images/blog/community-news.jpeg b/src/images/blog/community-news.jpeg
index 294d886d9c..a4a50bd2cb 100644
Binary files a/src/images/blog/community-news.jpeg and b/src/images/blog/community-news.jpeg differ
diff --git a/src/images/careers/hiring.jpeg b/src/images/careers/hiring.jpeg
index f8581763b0..0ecfa3be61 100644
Binary files a/src/images/careers/hiring.jpeg and b/src/images/careers/hiring.jpeg differ
diff --git a/src/images/careers/opening-front-end.jpg b/src/images/careers/opening-front-end.jpg
new file mode 100644
index 0000000000..373d67c12c
Binary files /dev/null and b/src/images/careers/opening-front-end.jpg differ
diff --git a/src/images/careers/opening-man-advocate.jpeg b/src/images/careers/opening-man-advocate.jpeg
index 032e571d9b..5a4b7caa4a 100644
Binary files a/src/images/careers/opening-man-advocate.jpeg and b/src/images/careers/opening-man-advocate.jpeg differ
diff --git a/src/images/careers/opening-sales-rep.jpeg b/src/images/careers/opening-sales-rep.jpeg
index 8f6b270edf..d2ca405d3e 100644
Binary files a/src/images/careers/opening-sales-rep.jpeg and b/src/images/careers/opening-sales-rep.jpeg differ
diff --git a/src/images/features.png b/src/images/features.png
deleted file mode 100644
index ef88968cf8..0000000000
Binary files a/src/images/features.png and /dev/null differ
diff --git a/src/images/features/feature-low-code-nr.png b/src/images/features/feature-low-code-nr.png
new file mode 100644
index 0000000000..c8654ea8ca
Binary files /dev/null and b/src/images/features/feature-low-code-nr.png differ
diff --git a/src/images/features/feature-scalable.png b/src/images/features/feature-scalable.png
new file mode 100644
index 0000000000..ef174faacc
Binary files /dev/null and b/src/images/features/feature-scalable.png differ
diff --git a/src/images/features/features-bg.png b/src/images/features/features-bg.png
new file mode 100644
index 0000000000..f7200e3644
Binary files /dev/null and b/src/images/features/features-bg.png differ
diff --git a/src/images/features/features-pipelines.png b/src/images/features/features-pipelines.png
new file mode 100644
index 0000000000..c90fa32507
Binary files /dev/null and b/src/images/features/features-pipelines.png differ
diff --git a/src/images/features/features-video-bg.png b/src/images/features/features-video-bg.png
new file mode 100644
index 0000000000..0296e94d4e
Binary files /dev/null and b/src/images/features/features-video-bg.png differ
diff --git a/src/images/ff-bg-flows.svg b/src/images/ff-bg-flows.svg
new file mode 100644
index 0000000000..9a77ce3292
--- /dev/null
+++ b/src/images/ff-bg-flows.svg
@@ -0,0 +1,287 @@
+
diff --git a/src/images/ff-cloud.svg b/src/images/ff-cloud.svg
deleted file mode 100644
index 510bab65da..0000000000
--- a/src/images/ff-cloud.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/src/images/ff-cloud_50.svg b/src/images/ff-cloud_50.svg
deleted file mode 100644
index 8522a2a5bb..0000000000
--- a/src/images/ff-cloud_50.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/src/images/ff-cloud_75.svg b/src/images/ff-cloud_75.svg
deleted file mode 100644
index a2a807026a..0000000000
--- a/src/images/ff-cloud_75.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/src/images/flowforge-logo-compact-wordmark.png b/src/images/flowforge-logo-compact-wordmark.png
deleted file mode 100644
index 592212d692..0000000000
Binary files a/src/images/flowforge-logo-compact-wordmark.png and /dev/null differ
diff --git a/src/images/flowforge-logo-compact-wordmark.svg b/src/images/flowforge-logo-compact-wordmark.svg
deleted file mode 100644
index 93a251d611..0000000000
--- a/src/images/flowforge-logo-compact-wordmark.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/src/images/flowforge-logo-wordmark-white.svg b/src/images/flowforge-logo-wordmark-white.svg
deleted file mode 100644
index 8fca1f9180..0000000000
--- a/src/images/flowforge-logo-wordmark-white.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/src/images/flowforge-logo-wordmark.svg b/src/images/flowforge-logo-wordmark.svg
deleted file mode 100644
index df6dc46234..0000000000
--- a/src/images/flowforge-logo-wordmark.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/src/images/flowforge-logo.png b/src/images/flowforge-logo.png
deleted file mode 100644
index 054a07de85..0000000000
Binary files a/src/images/flowforge-logo.png and /dev/null differ
diff --git a/src/images/flowforge-logo.svg b/src/images/flowforge-logo.svg
deleted file mode 100644
index 15c7588c4e..0000000000
--- a/src/images/flowforge-logo.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/src/images/flowforge.svg b/src/images/flowforge.svg
deleted file mode 100644
index de9eb138a9..0000000000
--- a/src/images/flowforge.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/src/images/flowfuse-logo-wordmark-white.svg b/src/images/flowfuse-logo-wordmark-white.svg
new file mode 100644
index 0000000000..395ccea680
--- /dev/null
+++ b/src/images/flowfuse-logo-wordmark-white.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/images/home-logos/airship-logo.png b/src/images/home-logos/airship-logo.png
new file mode 100644
index 0000000000..8ddc35942f
Binary files /dev/null and b/src/images/home-logos/airship-logo.png differ
diff --git a/src/images/home-logos/bosch-logo.png b/src/images/home-logos/bosch-logo.png
new file mode 100644
index 0000000000..88477b84cc
Binary files /dev/null and b/src/images/home-logos/bosch-logo.png differ
diff --git a/src/images/home-logos/enexis-logo.png b/src/images/home-logos/enexis-logo.png
new file mode 100644
index 0000000000..3dcc695c2a
Binary files /dev/null and b/src/images/home-logos/enexis-logo.png differ
diff --git a/src/images/home-logos/heatweb-logo.png b/src/images/home-logos/heatweb-logo.png
new file mode 100644
index 0000000000..fd7eb6ca3c
Binary files /dev/null and b/src/images/home-logos/heatweb-logo.png differ
diff --git a/src/images/home-logos/iniationware-logo.png b/src/images/home-logos/iniationware-logo.png
new file mode 100644
index 0000000000..4bcede27cb
Binary files /dev/null and b/src/images/home-logos/iniationware-logo.png differ
diff --git a/src/images/node-box.png b/src/images/node-box.png
deleted file mode 100644
index 80ecc11841..0000000000
Binary files a/src/images/node-box.png and /dev/null differ
diff --git a/src/images/node-box.svg b/src/images/node-box.svg
deleted file mode 100644
index b50f88efa5..0000000000
--- a/src/images/node-box.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/src/images/og-book-demo.jpeg b/src/images/og-book-demo.jpeg
index 7639389b6e..01f89aae46 100644
Binary files a/src/images/og-book-demo.jpeg and b/src/images/og-book-demo.jpeg differ
diff --git a/src/images/og-social-tile.jpg b/src/images/og-social-tile.jpg
index e2ebcd0896..675b5a1626 100644
Binary files a/src/images/og-social-tile.jpg and b/src/images/og-social-tile.jpg differ
diff --git a/src/images/pictograms/book-a-demo.png b/src/images/pictograms/book-a-demo.png
new file mode 100644
index 0000000000..532021cc8b
Binary files /dev/null and b/src/images/pictograms/book-a-demo.png differ
diff --git a/src/images/pictograms/briefcase_red.png b/src/images/pictograms/briefcase_red.png
new file mode 100644
index 0000000000..e808a26cb4
Binary files /dev/null and b/src/images/pictograms/briefcase_red.png differ
diff --git a/src/images/pictograms/feature-data-sharing.png b/src/images/pictograms/feature-data-sharing.png
new file mode 100644
index 0000000000..ca3d99933f
Binary files /dev/null and b/src/images/pictograms/feature-data-sharing.png differ
diff --git a/src/images/pictograms/iteration.png b/src/images/pictograms/iteration.png
new file mode 100644
index 0000000000..595952075d
Binary files /dev/null and b/src/images/pictograms/iteration.png differ
diff --git a/src/images/pictograms/no_credit_card.png b/src/images/pictograms/no_credit_card.png
new file mode 100644
index 0000000000..f46154232b
Binary files /dev/null and b/src/images/pictograms/no_credit_card.png differ
diff --git a/src/images/pictograms/speech_red.png b/src/images/pictograms/speech_red.png
new file mode 100644
index 0000000000..ac5b7cbccf
Binary files /dev/null and b/src/images/pictograms/speech_red.png differ
diff --git a/src/images/product/og-product-roadmap.jpg b/src/images/product/og-product-roadmap.jpg
deleted file mode 100644
index 047a23e69c..0000000000
Binary files a/src/images/product/og-product-roadmap.jpg and /dev/null differ
diff --git a/src/images/product/og-product-roadmap.png b/src/images/product/og-product-roadmap.png
new file mode 100644
index 0000000000..80ed9a98bf
Binary files /dev/null and b/src/images/product/og-product-roadmap.png differ
diff --git a/src/images/screen-pseudo-audit--dark.png b/src/images/screen-pseudo-audit--dark.png
deleted file mode 100644
index 1d32cafa3f..0000000000
Binary files a/src/images/screen-pseudo-audit--dark.png and /dev/null differ
diff --git a/src/images/screen-pseudo-audit.png b/src/images/screen-pseudo-audit.png
index 1d86e9f96c..9e684b4f83 100644
Binary files a/src/images/screen-pseudo-audit.png and b/src/images/screen-pseudo-audit.png differ
diff --git a/src/images/screen-pseudo-devices--dark.png b/src/images/screen-pseudo-devices--dark.png
deleted file mode 100644
index 8be0846eca..0000000000
Binary files a/src/images/screen-pseudo-devices--dark.png and /dev/null differ
diff --git a/src/images/screen-pseudo-devices.png b/src/images/screen-pseudo-devices.png
index 9e9499fa11..d50f80ecea 100644
Binary files a/src/images/screen-pseudo-devices.png and b/src/images/screen-pseudo-devices.png differ
diff --git a/src/images/screen-pseudo-overview--dark.png b/src/images/screen-pseudo-overview--dark.png
deleted file mode 100644
index b0322348d4..0000000000
Binary files a/src/images/screen-pseudo-overview--dark.png and /dev/null differ
diff --git a/src/images/screen-pseudo-overview.png b/src/images/screen-pseudo-overview.png
index 00570cb9a0..d9fe8683ab 100644
Binary files a/src/images/screen-pseudo-overview.png and b/src/images/screen-pseudo-overview.png differ
diff --git a/src/images/solutions/device-management-reflection.png b/src/images/solutions/device-management-reflection.png
deleted file mode 100644
index 000cb640ad..0000000000
Binary files a/src/images/solutions/device-management-reflection.png and /dev/null differ
diff --git a/src/images/solutions/og-solutions-data-integration.jpg b/src/images/solutions/og-solutions-data-integration.jpg
index 881b7de12d..b175bc8f77 100644
Binary files a/src/images/solutions/og-solutions-data-integration.jpg and b/src/images/solutions/og-solutions-data-integration.jpg differ
diff --git a/src/images/solutions/og-solutions-device-management.jpg b/src/images/solutions/og-solutions-device-management.jpg
index b2655e3534..3d4a13177a 100644
Binary files a/src/images/solutions/og-solutions-device-management.jpg and b/src/images/solutions/og-solutions-device-management.jpg differ
diff --git a/src/images/solutions/og-solutions-manufacturing.jpg b/src/images/solutions/og-solutions-manufacturing.jpg
index 49190e583e..788ba72aec 100644
Binary files a/src/images/solutions/og-solutions-manufacturing.jpg and b/src/images/solutions/og-solutions-manufacturing.jpg differ
diff --git a/src/images/solutions/webinar-july-2023_video_tile.jpg b/src/images/solutions/webinar-july-2023_video_tile.jpg
new file mode 100644
index 0000000000..c4ba920746
Binary files /dev/null and b/src/images/solutions/webinar-july-2023_video_tile.jpg differ
diff --git a/src/images/team/headshot-piotr.png b/src/images/team/headshot-piotr.png
new file mode 100644
index 0000000000..0bb9f75844
Binary files /dev/null and b/src/images/team/headshot-piotr.png differ
diff --git a/src/images/team/headshot-richard.png b/src/images/team/headshot-richard.png
deleted file mode 100644
index 4e2ecfb5c2..0000000000
Binary files a/src/images/team/headshot-richard.png and /dev/null differ
diff --git a/src/images/team/headshot-zack.png b/src/images/team/headshot-zack.png
new file mode 100644
index 0000000000..3db6e7f9c2
Binary files /dev/null and b/src/images/team/headshot-zack.png differ
diff --git a/src/images/thumbnail-nick-flowfuse.png b/src/images/thumbnail-nick-flowfuse.png
new file mode 100644
index 0000000000..c115b68ddc
Binary files /dev/null and b/src/images/thumbnail-nick-flowfuse.png differ
diff --git a/src/images/webinars/webinar-august.jpg b/src/images/webinars/webinar-august.jpg
new file mode 100644
index 0000000000..356acdc067
Binary files /dev/null and b/src/images/webinars/webinar-august.jpg differ
diff --git a/src/images/webinars/webinar-july.jpg b/src/images/webinars/webinar-july.jpg
new file mode 100644
index 0000000000..c1deb9e5bc
Binary files /dev/null and b/src/images/webinars/webinar-july.jpg differ
diff --git a/src/index.njk b/src/index.njk
index 623e371402..f9d9e91787 100644
--- a/src/index.njk
+++ b/src/index.njk
@@ -3,23 +3,23 @@ layout: default
sitemapPriority: 1.0
---
-
+
@@ -27,24 +27,33 @@ sitemapPriority: 1.0
{% include "components/divider-flow--default.njk" %}
DevOps for Node-RED
- FlowForge allows organizations to reliably deliver Node-RED applications in a continuous, collaborative, and secure manner. + FlowFuse allows organizations to reliably deliver Node-RED applications in a continuous, collaborative, and secure manner.
-
-
+
+
+
Trusted by:
+-
+
- {% image "./images/home-logos/heatweb-logo.png", "Heatweb logo", [60] %} +
- {% image "./images/home-logos/airship-logo.png", "Airship logo", [80] %} +
- {% image "./images/home-logos/enexis-logo.png", "Enexis logo", [90] %} +
- {% image "./images/home-logos/iniationware-logo.png", "Iniationware logo", [140] %} +
Collaborative Development
-FlowForge adds team collaboration to Node-RED, allowing multiple developers to work together on a single instance. With FlowForge, developers +
FlowFuse adds team collaboration to Node-RED, allowing multiple developers to work together on a single instance. With FlowFuse, developers can easily share projects, collaborate in real-time and streamline workflow for faster development and deployment.
- {% image "./images/screen-pseudo-overview.png", "A pseudo-screenshot of FlowForge's UI that lets users manage their multiple Node-RED instances.", [384] %}
+ {% image "./images/screen-pseudo-overview.png", "A pseudo-screenshot of FlowFuse's UI that lets users manage their multiple Node-RED instances.", [384] %}
@@ -53,11 +62,11 @@ sitemapPriority: 1.0
Manage Remote Deployments
-Many organizations deploy Node-RED instances to remote servers or edge devices. FlowForge automates this process by creating snapshots on Node-RED instances that can be +
Many organizations deploy Node-RED instances to remote servers or edge devices. FlowFuse automates this process by creating snapshots on Node-RED instances that can be deployed to multiple remote targets. It also allows for rollback in cases where something might not have gone correctly.
- {% image "./images/screen-pseudo-devices.png", "A pseudo-screenshot of FlowForge's UI that lets users manage their fleet of devices and remote Node-RED deployments.", [384] %}
+ {% image "./images/screen-pseudo-devices.png", "A pseudo-screenshot of FlowFuse's UI that lets users manage their fleet of devices and remote Node-RED deployments.", [384] %}
@@ -66,10 +75,10 @@ sitemapPriority: 1.0
Streamline Application Delivery
-FlowForge simplifies the software development lifecycle of Node-RED applications. You can now set up DevOps delivery pipelines to support development, test and production environments for Node-RED application delivery.
+FlowFuse simplifies the software development lifecycle of Node-RED applications. You can now set up DevOps delivery pipelines to support development, test and production environments for Node-RED application delivery.
- {% image "./images/screen-pseudo-audit.png", "A pseudo-screenshot of FlowForge's UI that shows how users can view an audit of all activity in their team and Node-RED projects.", [384] %}
+ {% image "./images/screen-pseudo-audit.png", "A pseudo-screenshot of FlowFuse's UI that shows how users can view an audit of all activity in their team and Node-RED projects.", [384] %}
@@ -77,11 +86,11 @@ sitemapPriority: 1.0
-
Flexible FlowForge Deployment
-We want to make it easy for you to use FlowForge, so we offer FlowForge Cloud, a managed cloud service, or a self-hosted solution. You have the freedom to choose the deployment method that works best for your organization.
+Flexible FlowFuse Deployment
+We want to make it easy for you to use FlowFuse, so we offer FlowFuse Cloud, a managed cloud service, or a self-hosted solution. You have the freedom to choose the deployment method that works best for your organization.
- {% image "./images/screen-pseudo-devices.png", "A pseudo-screenshot of FlowForge's UI that lets users manage their fleet of devices and remote Node-RED deployments.", [384] %}
+ {% image "./images/screen-pseudo-devices.png", "A pseudo-screenshot of FlowFuse's UI that lets users manage their fleet of devices and remote Node-RED deployments.", [384] %}
@@ -90,12 +99,12 @@ sitemapPriority: 1.0
@@ -104,28 +113,30 @@ sitemapPriority: 1.0
{% include "components/divider-flow--top-red--dark.njk" %}
-Professional Support for Node-RED deployments
-FlowForge is the trusted partner for providing professional support for business critical applications, built on Node-RED. Our experts can help +
FlowFuse is the trusted partner for providing professional support for business critical applications, built on Node-RED. Our experts can help with any challenge, ensuring that your Node-RED applications are running smoothly and securely. We keep your systems up-to-date with the latest versions of Node-RED and security updates, ensuring the continuity of your operations.
- {% image "./images/screen-pseudo-audit.png", "A pseudo-screenshot of FlowForge's UI that shows how users can view an audit of all activity in their team and Node-RED projects.", [384] %}
+ {% image "./images/screen-pseudo-audit.png", "A pseudo-screenshot of FlowFuse's UI that shows how users can view an audit of all activity in their team and Node-RED projects.", [384] %}
+
-
diff --git a/src/partners.njk b/src/partners.njk
index 35e13b7952..44c44807b8 100644
--- a/src/partners.njk
+++ b/src/partners.njk
@@ -1,8 +1,8 @@
---
layout: layouts/page.njk
-title: Introducing the FlowForge Referral Program
-description: "
diff --git a/src/pricing.njk b/src/pricing.njk
index 3286f97caf..f888f7b1fe 100644
--- a/src/pricing.njk
+++ b/src/pricing.njk
@@ -1,15 +1,15 @@
---
-title: Pricing
align: center
layout: layouts/page.njk
sitemapPriority: 0.90
meta:
-description: Find out how much it costs to use FlowForge.
+ description: Find out how much it costs to use FlowFuse.
---
-
-
-
Start using FlowForge
+Start using FlowFuse
For a full feature comparison, please visit our Pricing page.
- {% image "./images/pictograms/opensource.png", "Graphics depicting the Open-Source logo.", [160] %}
+ {% image "./images/pictograms/book-a-demo.png", "Icon representing a booked demo.", [160] %}
- Open Source
- - Install +Book a Demo
+ + Book a Demo
-
diff --git a/src/jobs/frontend-dashboard.njk b/src/jobs/frontend-dashboard.njk
new file mode 100644
index 0000000000..28f802f2fa
--- /dev/null
+++ b/src/jobs/frontend-dashboard.njk
@@ -0,0 +1,13 @@
+---
+layout: "nohero"
+title: Job Opening - Front-End Developer
+description: We are searching for a highly skilled Contract Front-End Developer to help develop the successor to the Node-RED Dashboard
+skipIndex: true
+image: /images/careers/opening-front-end.jpg
+---
+
+You will be re-directed to the job posting
+
+
diff --git a/src/jobs/manufacturing-advocate.njk b/src/jobs/manufacturing-advocate.njk
index c0a1f430a9..117206bd35 100644
--- a/src/jobs/manufacturing-advocate.njk
+++ b/src/jobs/manufacturing-advocate.njk
@@ -1,7 +1,7 @@
---
layout: "nohero"
title: Job Opening - Developer Advocate - Manufacturing & Industrial Automation
-description: FlowForge is looking to expand our community outreach team to support the users of Node-RED and FlowForge in the Manufacturing and Industrial Automation industries.
+description: FlowFuse is looking to expand our community outreach team to support the users of Node-RED and FlowFuse in the Manufacturing and Industrial Automation industries.
skipIndex: true
image: /images/careers/opening-man-advocate.jpeg
---
diff --git a/src/node-red/core-nodes/common.njk b/src/node-red/core-nodes/common.njk
new file mode 100644
index 0000000000..78ce79f0fb
--- /dev/null
+++ b/src/node-red/core-nodes/common.njk
@@ -0,0 +1,16 @@
+---
+pagination:
+ data: coreNodes.common
+ size: 1
+ alias: node
+ addAllPagesToCollections: true
+coreNodeCategory: "common"
+permalink: "node-red/core-nodes/{{ node | coreNodeName }}/"
+eleventyComputed:
+ meta:
+ title: "{{ node | coreNodeName }}"
+ navTitle: "{{ node | coreNodeName }}"
+ navGroup: "{{ coreNodeCategory }}"
+---
+
+{% include "core-node-docs.njk" %}
\ No newline at end of file
diff --git a/src/node-red/core-nodes/core-nodes.json b/src/node-red/core-nodes/core-nodes.json
new file mode 100644
index 0000000000..2f471e530f
--- /dev/null
+++ b/src/node-red/core-nodes/core-nodes.json
@@ -0,0 +1,7 @@
+{
+ "layout": "layouts/node-docs.njk",
+ "nav": "core-nodes",
+ "tags": [
+ "core-nodes"
+ ]
+}
diff --git a/src/node-red/core-nodes/function.njk b/src/node-red/core-nodes/function.njk
new file mode 100644
index 0000000000..60697391ab
--- /dev/null
+++ b/src/node-red/core-nodes/function.njk
@@ -0,0 +1,16 @@
+---
+pagination:
+ data: coreNodes.function
+ size: 1
+ alias: node
+ addAllPagesToCollections: true
+coreNodeCategory: "function"
+permalink: "node-red/core-nodes/{{ node | coreNodeName }}/"
+eleventyComputed:
+ meta:
+ title: "{{ node | coreNodeName }}"
+ navTitle: "{{ node | coreNodeName }}"
+ navGroup: "{{ coreNodeCategory }}"
+---
+
+{% include "core-node-docs.njk" %}
diff --git a/src/node-red/core-nodes/images/change-data-transform.png b/src/node-red/core-nodes/images/change-data-transform.png
new file mode 100644
index 0000000000..92ce592757
Binary files /dev/null and b/src/node-red/core-nodes/images/change-data-transform.png differ
diff --git a/src/node-red/core-nodes/images/change-default.png b/src/node-red/core-nodes/images/change-default.png
new file mode 100644
index 0000000000..56f68c5835
Binary files /dev/null and b/src/node-red/core-nodes/images/change-default.png differ
diff --git a/src/node-red/core-nodes/images/change-message-enrich.png b/src/node-red/core-nodes/images/change-message-enrich.png
new file mode 100644
index 0000000000..42860a0d71
Binary files /dev/null and b/src/node-red/core-nodes/images/change-message-enrich.png differ
diff --git a/src/node-red/core-nodes/images/change-message-filter.png b/src/node-red/core-nodes/images/change-message-filter.png
new file mode 100644
index 0000000000..0e1699fe48
Binary files /dev/null and b/src/node-red/core-nodes/images/change-message-filter.png differ
diff --git a/src/node-red/core-nodes/images/change-message-format.png b/src/node-red/core-nodes/images/change-message-format.png
new file mode 100644
index 0000000000..fe69614ab9
Binary files /dev/null and b/src/node-red/core-nodes/images/change-message-format.png differ
diff --git a/src/node-red/core-nodes/images/change-rename-property.png b/src/node-red/core-nodes/images/change-rename-property.png
new file mode 100644
index 0000000000..2ba33b94a6
Binary files /dev/null and b/src/node-red/core-nodes/images/change-rename-property.png differ
diff --git a/src/node-red/core-nodes/images/comment-node-full-text.png b/src/node-red/core-nodes/images/comment-node-full-text.png
new file mode 100644
index 0000000000..c01bb88aa0
Binary files /dev/null and b/src/node-red/core-nodes/images/comment-node-full-text.png differ
diff --git a/src/node-red/core-nodes/images/comment-node.png b/src/node-red/core-nodes/images/comment-node.png
new file mode 100644
index 0000000000..c687ee0fe8
Binary files /dev/null and b/src/node-red/core-nodes/images/comment-node.png differ
diff --git a/src/node-red/core-nodes/images/delay-node-2.png b/src/node-red/core-nodes/images/delay-node-2.png
new file mode 100644
index 0000000000..5bd8d4fe34
Binary files /dev/null and b/src/node-red/core-nodes/images/delay-node-2.png differ
diff --git a/src/node-red/core-nodes/images/delay-node.png b/src/node-red/core-nodes/images/delay-node.png
new file mode 100644
index 0000000000..ecda5e7194
Binary files /dev/null and b/src/node-red/core-nodes/images/delay-node.png differ
diff --git a/src/node-red/core-nodes/images/example-debug-flows.png b/src/node-red/core-nodes/images/example-debug-flows.png
new file mode 100644
index 0000000000..d011559b9b
Binary files /dev/null and b/src/node-red/core-nodes/images/example-debug-flows.png differ
diff --git a/src/node-red/core-nodes/images/example-debug-output.png b/src/node-red/core-nodes/images/example-debug-output.png
new file mode 100644
index 0000000000..9ae3b11e2e
Binary files /dev/null and b/src/node-red/core-nodes/images/example-debug-output.png differ
diff --git a/src/blog/2023/06/images/filter-only-report-changes.png b/src/node-red/core-nodes/images/filter-only-report-changes.png
similarity index 100%
rename from src/blog/2023/06/images/filter-only-report-changes.png
rename to src/node-red/core-nodes/images/filter-only-report-changes.png
diff --git a/src/blog/2023/06/images/filter-report-changes-ignore-init.png b/src/node-red/core-nodes/images/filter-report-changes-ignore-init.png
similarity index 100%
rename from src/blog/2023/06/images/filter-report-changes-ignore-init.png
rename to src/node-red/core-nodes/images/filter-report-changes-ignore-init.png
diff --git a/src/blog/2023/06/images/filter-report-changes-over.png b/src/node-red/core-nodes/images/filter-report-changes-over.png
similarity index 100%
rename from src/blog/2023/06/images/filter-report-changes-over.png
rename to src/node-red/core-nodes/images/filter-report-changes-over.png
diff --git a/src/blog/2023/06/images/filter-send-one-value.png b/src/node-red/core-nodes/images/filter-send-one-value.png
similarity index 100%
rename from src/blog/2023/06/images/filter-send-one-value.png
rename to src/node-red/core-nodes/images/filter-send-one-value.png
diff --git a/src/node-red/core-nodes/images/inject-node-nightly.png b/src/node-red/core-nodes/images/inject-node-nightly.png
new file mode 100644
index 0000000000..15d8a68b8d
Binary files /dev/null and b/src/node-red/core-nodes/images/inject-node-nightly.png differ
diff --git a/src/node-red/core-nodes/images/inject-node-once.png b/src/node-red/core-nodes/images/inject-node-once.png
new file mode 100644
index 0000000000..bc90cfab52
Binary files /dev/null and b/src/node-red/core-nodes/images/inject-node-once.png differ
diff --git a/src/node-red/core-nodes/images/link-node.png b/src/node-red/core-nodes/images/link-node.png
new file mode 100644
index 0000000000..276a942e82
Binary files /dev/null and b/src/node-red/core-nodes/images/link-node.png differ
diff --git a/src/node-red/core-nodes/images/range-node.png b/src/node-red/core-nodes/images/range-node.png
new file mode 100644
index 0000000000..dc4fafe055
Binary files /dev/null and b/src/node-red/core-nodes/images/range-node.png differ
diff --git a/src/node-red/core-nodes/images/range-node2.png b/src/node-red/core-nodes/images/range-node2.png
new file mode 100644
index 0000000000..f0ea192bfc
Binary files /dev/null and b/src/node-red/core-nodes/images/range-node2.png differ
diff --git a/src/node-red/core-nodes/images/split-node-array.png b/src/node-red/core-nodes/images/split-node-array.png
new file mode 100644
index 0000000000..2b9a5b68bf
Binary files /dev/null and b/src/node-red/core-nodes/images/split-node-array.png differ
diff --git a/src/node-red/core-nodes/images/split-node-by-line.png b/src/node-red/core-nodes/images/split-node-by-line.png
new file mode 100644
index 0000000000..870e1d3d1c
Binary files /dev/null and b/src/node-red/core-nodes/images/split-node-by-line.png differ
diff --git a/src/node-red/core-nodes/images/split-node-by-word.png b/src/node-red/core-nodes/images/split-node-by-word.png
new file mode 100644
index 0000000000..c1c2969cb6
Binary files /dev/null and b/src/node-red/core-nodes/images/split-node-by-word.png differ
diff --git a/src/node-red/core-nodes/images/split-node-hash.png b/src/node-red/core-nodes/images/split-node-hash.png
new file mode 100644
index 0000000000..893540a260
Binary files /dev/null and b/src/node-red/core-nodes/images/split-node-hash.png differ
diff --git a/src/node-red/core-nodes/images/split-node-regroup.png b/src/node-red/core-nodes/images/split-node-regroup.png
new file mode 100644
index 0000000000..f5c191c560
Binary files /dev/null and b/src/node-red/core-nodes/images/split-node-regroup.png differ
diff --git a/src/node-red/core-nodes/images/status-node-output.png b/src/node-red/core-nodes/images/status-node-output.png
new file mode 100644
index 0000000000..0814c90e03
Binary files /dev/null and b/src/node-red/core-nodes/images/status-node-output.png differ
diff --git a/src/node-red/core-nodes/images/status-node.png b/src/node-red/core-nodes/images/status-node.png
new file mode 100644
index 0000000000..73127d5e43
Binary files /dev/null and b/src/node-red/core-nodes/images/status-node.png differ
diff --git a/src/node-red/core-nodes/images/yaml-node-error.png b/src/node-red/core-nodes/images/yaml-node-error.png
new file mode 100644
index 0000000000..b57a6d3406
Binary files /dev/null and b/src/node-red/core-nodes/images/yaml-node-error.png differ
diff --git a/src/node-red/core-nodes/images/yaml-node-from-json.png b/src/node-red/core-nodes/images/yaml-node-from-json.png
new file mode 100644
index 0000000000..37b9a9bc76
Binary files /dev/null and b/src/node-red/core-nodes/images/yaml-node-from-json.png differ
diff --git a/src/node-red/core-nodes/images/yaml-node-to-json.png b/src/node-red/core-nodes/images/yaml-node-to-json.png
new file mode 100644
index 0000000000..46693c7707
Binary files /dev/null and b/src/node-red/core-nodes/images/yaml-node-to-json.png differ
diff --git a/src/node-red/core-nodes/index.njk b/src/node-red/core-nodes/index.njk
new file mode 100644
index 0000000000..067686b08f
--- /dev/null
+++ b/src/node-red/core-nodes/index.njk
@@ -0,0 +1,23 @@
+---
+navTitle: "Node-RED Core Nodes"
+---
+Node-RED Core Nodes
+ +In Node-RED, the core nodes are the set of nodes that are included with the +Node-RED runtime by default without the node install procedure. These nodes are +maintained and supported by the Node-RED development team and are intended to +provide the basic building blocks for creating Node-RED flows.
+ +Core nodes include nodes for basic functionality like input/output, processing, +and control flow. They are the foundation upon which more complex workflows can +be built, and they are essential to the operation of Node-RED.
+ +The nodes are grouped in a few sections in the nodes sidebar: +
-
+
- common - miscellaneous nodes +
- function - Control flow, blocking or sending additional messages. +
- network - Receive and send messages over the network on different protocols. +
- sequence - Working with collections of messages, or creating them. +
- parser - transforming data from one format to another. +
- storage - for reading or writing files. +
Many companies are realizing the benefits of using FlowForge for -their Node-RED development. We want to encourage them to recommend FlowForge to +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.
" heroimg: "./images/pictograms/anvil1.png" @@ -30,7 +30,7 @@ meta:
-
Benefits of FlowForge
+Benefits of FlowFuse
@@ -54,7 +54,7 @@ meta:
Node-RED, Managed
Node-RED, Managed
For You
- {% image "./images/pictograms/browser.png", "Graphic of a globe, depicting FlowForge being full browser-based.", [128] %}
+ {% image "./images/pictograms/browser.png", "Graphic of a globe, depicting FlowFuse being full browser-based.", [128] %}
Full Browser-Based
-
\ No newline at end of file
diff --git a/src/product/index.njk b/src/product/index.njk
index bef9560806..c4aadeacc6 100644
--- a/src/product/index.njk
+++ b/src/product/index.njk
@@ -1,7 +1,7 @@
---
title: Team-Based Low-Code Development
layout: layouts/page.njk
-subtitle: Get started with FlowForge today. Run it for yourself, or sign-up to our managed service.
+subtitle: Get started with FlowFuse today. Run it for yourself, or sign-up to our managed service.
description:
-
+
+
+
+
+
-
+
@@ -48,7 +48,7 @@ description: Find out how much it costs to use FlowForge.
Pricing
+Plans for every project. Whether you're an individual contributor, an IIoT manager, or an IT department, you'll find a suitable option to take your Node-RED applications to the next level.
Premium
- +
Contact us for annual billing discounts
@@ -62,7 +62,7 @@ description: Find out how much it costs to use FlowForge.
per Node-REDinstance/month
Install FlowForge yourself or we will manage it for you.
+Install FlowFuse yourself or we will manage it for you.
TRY FOR FREE
@@ -122,8 +122,12 @@ description: Find out how much it costs to use FlowForge.
}
+
+{% include "components/divider-flow--top-red--light.njk" %}
+
-{% include "components/divider-flow--top-red--light.njk" %}
{% set featuresHtml %}
@@ -142,7 +146,7 @@ description: Find out how much it costs to use FlowForge.
{{ featuresHtml | safe }}
- At FlowForge we understand that the security practises of our product + At FlowFuse we understand that the security practises of our product are important to your company. We've prepared a security statement for you to understand the choices we've made.
diff --git a/src/privacy-policy.md b/src/privacy-policy.md index f985c14de6..d62da2a080 100644 --- a/src/privacy-policy.md +++ b/src/privacy-policy.md @@ -9,7 +9,7 @@ meta: # Privacy Policy -This Privacy Policy describes the privacy practices of FlowForge Inc (**āFlowForgeā**, **āweā**, **āusā** or **āourā**) and how we handle personal information that we collect through our digital properties that link to this Privacy Policy, including our website, (the **āServiceā**), as well as through social media, our marketing activities, our events and other activities described in this policy. +This Privacy Policy describes the privacy practices of FlowFuse Inc (**āFlowFuseā**, **āweā**, **āusā** or **āourā**) and how we handle personal information that we collect through our digital properties that link to this Privacy Policy, including our website, (the **āServiceā**), as well as through social media, our marketing activities, our events and other activities described in this policy. At the time we collect personal information, we may provide additional or supplemental privacy notices to individuals for specific services and personal information processing activities. @@ -135,6 +135,6 @@ We reserve the right to modify this Privacy Policy at any time. If we make mater ## How to contact us - - **Email:** `contact@flowforge.com` + - **Email:** `contact@flowfuse.com` - **Mail:** `PO Box 7775 #29439, San Francisco, CA 94120-7775`
Join our managed service
@@ -55,7 +55,7 @@ heroLg: true
{% image "../images/pictograms/time_red.png", "A red clock icon", [150] %}
@@ -100,7 +100,7 @@ heroLg: true
{% image "../images/pictograms/browser_red.png", "Icon representing a browser", [150] %}
@@ -125,7 +125,7 @@ heroLg: true
- At FlowForge we understand that the security practises of our product
+ At FlowFuse we understand that the security practises of our product
are important to your company. We've prepared a security statement
for you to understand the choices we've made.
diff --git a/src/product/roadmap.njk b/src/product/roadmap.njk
index f847bac9eb..51e89d95da 100644
--- a/src/product/roadmap.njk
+++ b/src/product/roadmap.njk
@@ -1,55 +1,80 @@
---
-layout: layouts/solution.njk
+layout: layouts/page.njk
title: Roadmap
-image: /images/product/og-product-roadmap.jpg
-subtitle: Stay up-to-date with our progress
-heroImg: "./images/pictograms/anvil1.png"
-description:
-
Fast setup
-With FlowForge, deploying a new Node-RED project takes moments. No configuration of proxies and setting up DNS, get going in less time than it takes to make a cup of tea.
+With FlowFuse, deploying a new Node-RED project takes moments. No configuration of proxies and setting up DNS, get going in less time than it takes to make a cup of tea.
Fully Browser Based
-No need to install any software, everything can be managed from a web browser. Simple drag and drop editing of your workflows. Manage your project settings and config from within the FlowForge application.
+No need to install any software, everything can be managed from a web browser. Simple drag and drop editing of your workflows. Manage your project settings and config from within the FlowFuse application.
Stay up-to-date with our progress and plans on the FlowForge Roadmap. This is your go-to resource for staying informed about the latest developments and future direction of our platform.
-Here you can find information about upcoming features, enhancements, and other changes we're actively working on to make FlowForge an even more powerful and versatile tool for your business needs.
---- - - -
-
-
- 
- See our entire Roadmap on GitHub
+subtitle:
- See our entire Roadmap on GitHub
+subtitle: Stay up-to-date with our progress
+description:
+ Here you can find information about upcoming features, enhancements, and other changes we're actively working on to make FlowFuse an even more powerful and versatile tool for your business needs.
+ +image: /images/product/og-product-roadmap.png +--- +
+ {% include "components/divider-flow--top-red--light.njk" %}
+
-
-
-
+
+
+
+
-
-
š Consideration
-We would appreciate your feedback on the potential new features that we are considering for development.
- +
+
-
+
+
+ Under consideration
++
We would appreciate your feedback on the potential new features that we are considering for development.
++ {% include "components/icons/github.svg" %}Vote on Github{% include "components/icons/arrow-small-down.svg" %} +
+
-
-{% include "components/divider-flow--top-red--dark.njk" %}
+
+š In Progress
-We are currently working on the following topics and would appreciate any feedback you may have.
- +
+
-
+
+
+ In Progress
++
We are currently working on the following topics and would appreciate any feedback you may have.
++ {% include "components/icons/github.svg" %}See status on Github{% include "components/icons/arrow-small-down.svg" %} +
+
-
š Newly released
-- Check out product updates on - - our blog - - to see the latest features and improvements. -
+
+
+
+
+
+
+ Newly released
++
+ Check out product updates on + + our blog + + to see the latest features and improvements. +
++ Latest posts{% include "components/icons/arrow-small-down.svg" %} +
+
+
+ -
+ {%- for releases in collections.releases | reverse | limit(2) -%}
+
- {{ releases.data.title }} + {%- endfor -%} +
+ Sign up +
- +
+
+
+
+
+
+
+
+ Under consideration
++
We would appreciate your feedback on the potential new features that we are considering for development.
+
+
+
+
+
+
+ In Progress
++
We are currently working on the following topics and would appreciate any feedback you may have.
+
+
+
+
+
+
+ Newly released
++
Check out product updates on + + our blog + + to see the latest features and improvements. +
+
+
+
+ + {% include "components/icons/github.svg" %}Vote on Github{% include "components/icons/arrow-small-down.svg" %} +
+ +
+
+
+ + {% include "components/icons/github.svg" %}See status on Github{% include "components/icons/arrow-small-down.svg" %} +
+ +
+
+ Latest posts{% include "components/icons/arrow-small-down.svg" %} +
+
+
+ -
+ {%- for releases in collections.releases | reverse | limit(2) -%}
+
- {{ releases.data.title }} + {%- endfor -%} +
+ Sign up +
+ +{% include "components/dividers/light-grey-curve-inverted.svg" %}
+
-
-
-
-
Suggest a new feature
-If you haven't found the feature you're looking for, we encourage you to provide your valuable feedback and suggestions. Your input will help us shape the future of FlowForge, ensuring it meets your needs and expectations. Please consider sharing your thoughts and ideas with us by suggesting a new feature. To do so, simply click the button below to open a new feature request on our GitHub repository.
- Suggest a new feature +
+
-{% include "components/divider-flow--top-grey.njk" %}
+
\ No newline at end of file
diff --git a/src/product/security.md b/src/product/security.md
index b6723cdb14..8d1a4f4ffe 100644
--- a/src/product/security.md
+++ b/src/product/security.md
@@ -1,13 +1,13 @@
---
layout: nohero
-title: Security Statement - FlowForge
+title: Security Statement - FlowFuse
---
-
+
+
+
Suggest a new feature
+Provide your valuable feedback and suggestions. Your input will help us shape the future of FlowFuse, ensuring it meets your needs and expectations. To do so, simply click the button below to open a new feature request on our GitHub repository.
+ SUGGEST NEW FEATURE +
+
-Security aspects of FlowForge are divided up into two sections, configuration
+Security aspects of FlowFuse are divided up into two sections, configuration
and application level. Application level security aspects apply to both self
-managed and FlowForge managed instances.
+managed and FlowFuse managed instances.
## Application
@@ -20,10 +20,10 @@ User provisioning is on a per user basis.
## Configuration
-Configuration of the FlowForge application influences security aspects of the
-system at large. For each section the implementation of FlowForge Cloud is
+Configuration of the FlowFuse application influences security aspects of the
+system at large. For each section the implementation of FlowFuse Cloud is
mentioned too. For self managed installs we advise to follow the choices made
-by FlowForge Cloud.
+by FlowFuse Cloud.
### Data storage
@@ -32,7 +32,7 @@ by FlowForge Cloud.
All user data is stored in a relational database, which are encrypted by default
for all install methods except local.
-_FlowForge Cloud_: Data is stored in a PostgreSQL database. All data is encrypted
+_FlowFuse Cloud_: Data is stored in a PostgreSQL database. All data is encrypted
[since October 2022](/blog/2022/10/db-migration-01/).
#### Data residency
@@ -40,16 +40,16 @@ _FlowForge Cloud_: Data is stored in a PostgreSQL database. All data is encrypte
Long term data storage is depended on the location of the relational database
storage.
-_FlowForge Cloud_: Data is stored in the European Union, specificially
+_FlowFuse Cloud_: Data is stored in the European Union, specificially
Ireland, on AWS eu-west-1.
### Data in Transit
-Traffic from external sources to the FlowForge application can be encrypted.
+Traffic from external sources to the FlowFuse application can be encrypted.
When a load balancer is used, the encryption is terminated on the edge. Internal
traffic is not encrypted.
-_FlowForge Cloud_: Data in transit to and from external sources is protected
+_FlowFuse Cloud_: Data in transit to and from external sources is protected
with SSL/TLS. Encryption is terminated at the edge, both for HTTP and MQTT
traffic.
@@ -60,17 +60,17 @@ Adding internal SSL/TLS is [being investigated](https://github.com/flowforge/flo
Communication between a teams projects is MQTT based. Traffic can be encrypted
based on the broker configuration.
-_FlowForge Cloud_: Inbound and outbound traffic is send encrypted to
-FlowForge. The encryption is terminated at the load balancer. Internal traffic
+_FlowFuse Cloud_: Inbound and outbound traffic is send encrypted to
+FlowFuse. The encryption is terminated at the load balancer. Internal traffic
is not encrypted.
### Service endpoints
-It's recommended to run the FlowForge application and the flow runtimes on
+It's recommended to run the FlowFuse application and the flow runtimes on
different domains. This will create separation of concerns and enhances security
for, among others, cookies.
-_FlowForge Cloud_: Our SaaS offering has multiple service domains. The
+_FlowFuse Cloud_: Our SaaS offering has multiple service domains. The
corporate website is hosted at [flowforge.com](https://flowforge.com). The
application is served at [app.flowforge.com](https://app.flowforge.com), while
the Node-RED instances are served from \*.flowforge.cloud.
diff --git a/src/public/.well-known/security.txt b/src/public/.well-known/security.txt
index e8e78bdd61..38529827ba 100644
--- a/src/public/.well-known/security.txt
+++ b/src/public/.well-known/security.txt
@@ -1,4 +1,4 @@
-Contact: mailto:security@flowforge.com
+Contact: mailto:security@flowfuse.com
Expires: 2023-08-11T23:00:00.000Z
Preferred-Languages: en
Canonical: https://flowforge.com/.well-known/security.txt
diff --git a/src/redirect.md b/src/redirect.md
index fd0c2c8524..e0cdf85b90 100644
--- a/src/redirect.md
+++ b/src/redirect.md
@@ -9,22 +9,9 @@ pagination:
alias: redirect
# Add your redirection tuples to this list!
redirects:
+ # This line serves as an example, but can safely be removed if it's no longer
+ # needed
- { "from": "/blog/first-deploy/", "to": "/blog/2021/04/first-deploy/"}
- - { "from": "/blog/welcome-ben/", "to": "/blog/2021/05/welcome-ben/" }
- - { "from": "/blog/welcome-sam/", "to": "/blog/2021/05/welcome-sam/" }
- - { "from": "/blog/welcome-zj/", "to": "/blog/2022/01/welcome-zj/" }
- - { "from": "/blog/welcome-steve/", "to": "/blog/2022/01/welcome-steve/" }
- - { "from": "/blog/flowforge-01-released/", "to": "/blog/2022/01/flowforge-01-released/" }
- - { "from": "/blog/community-news-01/", "to": "/blog/2022/01/community-news-01/" }
- - { "from": "/blog/welcome-joe/", "to": "/blog/2022/02/welcome-joe/" }
- - { "from": "/blog/use-case-solar-afloat/", "to": "/blog/2022/02/use-case-solar-afloat/" }
- - { "from": "/blog/flowforge-02-released/", "to": "/blog/2022/02/flowforge-02-released/" }
- - { "from": "/blog/announcing-flowforge-cloud/", "to": "/blog/2022/02/announcing-flowforge-cloud/" }
- - { "from": "/blog/community-news-02/", "to": "/blog/2022/03/community-news-02/" }
- - { "from": "/blog/flowforge-03-released/", "to": "/blog/2022/03/flowforge-03-released/" }
- - { "from": "/blog/2023/03/comparinig-dashboards/", "to": "/blog/2023/03/comparing-node-red-dashboards" }
- - { "from": "/roadmap/", "to": "/product/roadmap/" }
- - { "from": "/handbook/development/release/", "to": "/handbook/development/releases/" }
# The "permalink" attribute determines where the output page will be located.
permalink: "{{ redirect.from }}"
# The "redirect" layout just has a small html header with the meta tags that do redirection.
diff --git a/src/sign-up.md b/src/sign-up.md
new file mode 100644
index 0000000000..4e981691a6
--- /dev/null
+++ b/src/sign-up.md
@@ -0,0 +1,20 @@
+---
+# Inspired by https://github.com/11ty/eleventy/issues/510#issuecomment-824104799
+#
+# This file generates redirects for pages that have moved.
+#
+pagination:
+ data: redirects
+ size: 1
+ alias: redirect
+# Add your redirection tuples to this list!
+redirects:
+ - { "from": "/sign-up/", "to": "https://app.flowforge.com/account/create"}
+# The "permalink" attribute determines where the output page will be located.
+permalink: "{{ redirect.from }}"
+# The "redirect" layout just has a small html header with the meta tags that do redirection.
+layout: redirect
+title: "Create an account for FlowFuse"
+sitemapPriority: 0.9
+---
+(the content can be left blank; it's entirely the frontmatter doing the work here.)
diff --git a/src/solutions/data-integration.njk b/src/solutions/data-integration.njk
index bf582ba824..1db915ebdd 100644
--- a/src/solutions/data-integration.njk
+++ b/src/solutions/data-integration.njk
@@ -69,7 +69,7 @@ description:
Support for Different Protocols
- FlowForge makes it possible for teams to collaborate on the same Node-RED flows. Team members can now share the same Node-RED instances to make for quicker and more efficient development of your Node-RED application. + FlowFuse makes it possible for teams to collaborate on the same Node-RED flows. Team members can now share the same Node-RED instances to make for quicker and more efficient development of your Node-RED application.
@@ -93,7 +93,7 @@ description:
- FlowForge Adds DevOps
+ FlowFuse Adds DevOps
FlowForge Adds DevOps
to Node-RED for Data Integration
+ FlowFuse Adds DevOps
to Node-RED for Data Integration
@@ -104,7 +104,7 @@ description:
Collaborative
@@ -130,7 +130,7 @@ description:
Software Delivery
+
-Collaborative
Development
- FlowForge makes it possible for teams to collaborate on the same Node-RED flows. + FlowFuse makes it possible for teams to collaborate on the same Node-RED flows.
Team members can now share the same Node-RED instances to make for quicker and more efficient development of your Node-RED application. @@ -118,7 +118,7 @@ description:
Managed Node-RED Service
- FlowForge offers a managed service for running Node-RED instances so you donāt need to worry about the production reliability of your Node-RED application. + FlowFuse offers a managed service for running Node-RED instances so you donāt need to worry about the production reliability of your Node-RED application.
Software Delivery
Pipelines
- FlowForge allows you to create snapshots of Node-RED instances so you can create software delivery pipelines for development > test > production. + FlowFuse allows you to create snapshots of Node-RED instances so you can create software delivery pipelines for development > test > production.
It is also possible to revert to a previous version of a snapshot to rollback any changes. @@ -141,7 +141,7 @@ description:
- Contact us to discover how FlowForge can help you use Node-RED for your Data Integration requirements. + Contact us to discover how FlowFuse can help you use Node-RED for your Data Integration requirements.
GET IN TOUCH
diff --git a/src/solutions/device-management.njk b/src/solutions/device-management.njk
index f85c6ddcd1..4122d2fe97 100644
--- a/src/solutions/device-management.njk
+++ b/src/solutions/device-management.njk
@@ -6,7 +6,7 @@ subtitle:
heroImg: ./images/pictograms/edge.png
description:
@@ -32,8 +32,8 @@ description:
@@ -42,7 +42,7 @@ description:
@@ -61,7 +61,7 @@ description:
@@ -70,25 +70,29 @@ description:
Companies often deploy Node-RED to edge devices (equipment, gateways, PLCs, etc.) to monitor and collect data from these devices. How to manage deployments - to a large number of devices can be a challenge. Luckily, FlowForge makes it possible to manage Node-RED deployments out to fleets of devices + to a large number of devices can be a challenge. Luckily, FlowFuse makes it possible to manage Node-RED deployments out to fleets of devices in a secure and reliable manner.
--- @@ -23,7 +23,7 @@ description:Manage Hundreds of Devices
- FlowForge allows you to manage hundreds of devices that all run the same Node-RED instance. The FlowForge device agent is deployed + FlowFuse allows you to manage hundreds of devices that all run the same Node-RED instance. The FlowFuse device agent is deployed to each device to handle the synchronization of the future updates to the Node-RED instances. From a central console, you can now see the status of your devices and manage Node-RED deployments in a reliable and repeatable process.
Effortless Data Streaming
- Streaming device data to the cloud can be a complicated due to network configuration setup. FlowForge Project Nodes hide this complexity within custom nodes that transparently - establish an MQTT connection between the device and the FlowForge platform. Data streaming from a device can now be setup with a simple Node-RED flow. No configuration of + Streaming device data to the cloud can be a complicated due to network configuration setup. FlowFuse Project Nodes hide this complexity within custom nodes that transparently + establish an MQTT connection between the device and the FlowFuse platform. Data streaming from a device can now be setup with a simple Node-RED flow. No configuration of IP address, domain name, certificates or firewalls is required for the device.
Consistent Deployment of Instances
- FlowForge allows you to create Snapshots of your Node-RED flows that can then be deployed out to all your registered devices. From a central console, a single snapshot + FlowFuse allows you to create Snapshots of your Node-RED flows that can then be deployed out to all your registered devices. From a central console, a single snapshot can be deployed out to a group of devices. This gives you the peace of mind that all your devices are running the same version of your Node-RED flows.
@@ -52,7 +52,7 @@ description:Quick to Deploy Security Updates
- The quick deployment of security updates and new versions for Node-RED is important for the overall security of your system. FlowForge's + The quick deployment of security updates and new versions for Node-RED is important for the overall security of your system. FlowFuse's device management capability makes it easy to re-host your Node-RED flows on a new version of Node-RED and then deploy it out to your devices.
Remote Troubleshooting
- If a production error occurs on a device, FlowForge allows you to remotely debug the running Node-RED instance on the devices. This makes + If a production error occurs on a device, FlowFuse allows you to remotely debug the running Node-RED instance on the devices. This makes it much easier to identify and resolve production issues that might occur.
Easy Onboarding
- New devices can be onboarded to FlowForge through a adminstrative interface or an automated process. The automated process allows for groups of - devices to connect with FlowForge without operator involvement. + New devices can be onboarded to FlowFuse through a adminstrative interface or an automated process. The automated process allows for groups of + devices to connect with FlowFuse without operator involvement.
+
+
+
+
+
- {% image "./images/solutions/device-management-reflection.png", "Screen shot of FlowForge device management capabilities.", [1024] %}
-
{% include "components/divider-flow--top-red--dark.njk" %}
-
+
@@ -178,7 +178,7 @@ description:
- Contact us to discover how FlowForge can help manage your Node-RED device deployments.
+ Contact us to discover how FlowFuse can help manage your Node-RED device deployments. diff --git a/src/solutions/manufacturing.njk b/src/solutions/manufacturing.njk index 5639248621..fda87deccc 100644 --- a/src/solutions/manufacturing.njk +++ b/src/solutions/manufacturing.njk @@ -92,9 +92,9 @@ description:
- FlowForge Adds DevOps
+ FlowFuse Adds DevOps
@@ -113,7 +113,7 @@ description:
factory or fleets of devices in remote locations.
FlowForge Adds DevOps
to Node-RED for Manufacturing
+ FlowFuse Adds DevOps
to Node-RED for Manufacturing
- FlowForge helps companies to reliably deliver Node-RED applications in a continuous, + FlowFuse helps companies to reliably deliver Node-RED applications in a continuous, collaborative and secure manner. We integrate Node-RED with numerous devops concepts that are widely recognized and comprehended within IT organizations.
- FlowForge automates the process + FlowFuse automates the process of remote deployment of a Node-RED instance. It can automatically deploy a new version of a Node-RED flow or even roll-back to a previous snapshot.
@@ -130,7 +130,7 @@ description:Collaborative Node-RED Development
- FlowForge makes it possible for teams to collaborate on the same Node-RED flows. + FlowFuse makes it possible for teams to collaborate on the same Node-RED flows. Team members can now share the same Node-RED instances to make for quicker and more efficient development of your Node-RED application.
@@ -147,7 +147,7 @@ description:Streamlined Application Delivery
- With FlowForge, you can not set up devops delivery pipelines to support + With FlowFuse, you can not set up devops delivery pipelines to support development, test and production environments. A key to ensuring your Node-RED application delivery is reliable, secure and high quality.
@@ -164,11 +164,11 @@ description:Professional Support for Node-RED
- FlowForge offers professional support for Node-RED deployments. Our experts are - available to support your Node-RED and FlowForge deployments. + FlowFuse offers professional support for Node-RED deployments. Our experts are + available to support your Node-RED and FlowFuse deployments.
- The FlowForge platform keeps your systems up-to-date with the latest versions of + The FlowFuse platform keeps your systems up-to-date with the latest versions of Node-RED and security updates, ensuring the continuity of your operations.
- Contact us to discover how FlowForge can help
Connect, Integrate, Visualize & Automate your industrial data
+ Contact us to discover how FlowFuse can help
Connect, Integrate, Visualize & Automate your industrial data
GET IN TOUCH
diff --git a/src/support.njk b/src/support.njk
index 280cd2702e..acab8def03 100644
--- a/src/support.njk
+++ b/src/support.njk
@@ -1,27 +1,115 @@
---
-layout: layouts/nohero.njk
-title: Request Support
+align: center
+layout: layouts/page.njk
+title: Help Center
+description:
Search through our extensive range of resources, knowledge base, or reach out to our dedicated support team by submitting a ticket.
sitemapPriority: 0.8 --- - -
-
-
-
- {% image "./images/pictograms/browser_red.png", "Graphic of a globe, depicting 'Connectivity'.", [288] %}
-
-
-
-
+
+For community support, please visit the community forum.
-
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/src/team.njk b/src/team.njk
index 9315fdcc2d..9a75d79d51 100644
--- a/src/team.njk
+++ b/src/team.njk
@@ -2,7 +2,7 @@
title: Meet the Team
layout: layouts/nohero.njk
---
-
+
-
+
+ Find answers instantly
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ {% image "./images/pictograms/community_red.png", "Graphics depicting low-code programming.", [64] %}
+
+
+ Ask the community
+
+
+ + Explore our forum to find answers and solutions. Others may have already shared similar issues, providing + valuable insights that could address your concerns. +
+
+
+
+
+
+
+
+
+ {% image "./images/pictograms/speech_red.png", "Graphics depicting low-code programming.", [64] %}
+
+
+ Reach out via our chat
+
+
+ + Get real-time assistance and quick answers. Chat with us for prompt support and solutions to your queries. +
+
+
+
+
+
+ {% include "components/dividers/light-grey-curve-inverted.svg" %}
+
+
+
+ Submit a ticket
+If you need assistance with the FlowFuse application, account, or billing, please submit a ticket by filling + out the form below.
+
+
+
+
+
+
+
+
{%- for member in team | dictsortBy(false, 'order') -%}
@@ -70,7 +70,7 @@ layout: layouts/nohero.njk
{% include "values.njk" %}
-
diff --git a/src/terms.md b/src/terms.md
index 4da06785a3..830c12bd6e 100644
--- a/src/terms.md
+++ b/src/terms.md
@@ -10,7 +10,7 @@ meta:
THESE TERMS AND CONDITIONS (āTERMSā) GOVERN YOUR ACCESS TO AND USE OF OUR SAAS SERVICES INCLUDING ANY CONTENT THEREIN (THE āSAAS SERVICESā). BY ACCEPTING THESE TERMS, EITHER BY CLICKING A BOX INDICATING YOUR ACCEPTANCE OR BY EXECUTING AN ORDER FORM THAT REFERENCES THESE TERMS, YOU AGREE TO THESE TERMS. THE TERM āAGREEMENTā AS USED HEREIN SHALL MEAN THESE TERMS, TOGETHER WITH THE ORDER FORM AND ANY DPA ENTERED INTO BY THE PARTIES. IN THE EVENT OF A CONFLICT BETWEEN THESE TERMS AND ANY ENTERPRISE SERVICES AGREEMENT, IF ANY, EXECUTED BETWEEN FLOWFORGE INC. AND THE ORGANIZATION WHICH YOU REPRESENT, THAT ENTERPRISE SERVICES AGREEMENT WILL CONTROL. IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY AND ITS AFFILIATES TO THESE TERMS, IN WHICH CASE āYOUā OR āYOURā OR āCUSTOMERā SHALL REFER TO SUCH ENTITY AND ITS AFFILIATES. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT AGREE WITH THESE TERMS, YOU MUST NOT ACCEPT THIS AGREEMENT AND MAY NOT USE THE SAAS SERVICES.
-This Agreement is effective as of the date of your acceptance of this Agreement. Reference to āweā, āourā and āusā in its related variations and āCompanyā shall mean FlowForge Inc. or its aļ¬liates, as applicable, from whom you receive the SaaS Services.
+This Agreement is effective as of the date of your acceptance of this Agreement. Reference to āweā, āourā and āusā in its related variations and āCompanyā shall mean FlowFuse Inc. or its aļ¬liates, as applicable, from whom you receive the SaaS Services.
# 1. AUTHORIZED USE.
By accepting these Terms, you agree to these Terms on behalf of yourself, your organization and any entity that you represent or on behalf of which you use the SaaS Services. You further agree that you have the authority to bind that organization to these Terms and that you are authorized to be an Administrative User (as defined below) on behalf such organization. The SaaS Services may only be used for your internal business purposes (the āAuthorized Useā). You are responsible for Authorized Usersā (as defined below) compliance with this Agreement, and any act or omission of any Authorized User shall be treated as if undertaken by You.
@@ -144,7 +144,7 @@ Any delay in the performance of any duties or obligations of either party (excep
## 13.8 Independent Contractors.
Customerās relationship to Company is that of an independent contractor, and neither party is an agent or partner of the other. Customer will not have, and will not represent to any third party that it has, any authority to act on behalf of Company.
## 13.9 Notices.
-All notices required or permitted under this agreement must be delivered in writing, if to Company, by emailing support@flowforge.com and if to Customer by emailing the Customer Point of Contact email address listed on the Cover Page, provided, however, that with respect to any notices relating to breaches of this agreement or termination, a copy of such notice will also be sent in writing to the other party at the address listed on the Cover Page by courier, by certified or registered mail (postage prepaid and return receipt requested), or by a nationally-recognized express mail service. Each party may change its email address and/or address for receipt of notice by giving notice of such change to the other party.
+All notices required or permitted under this agreement must be delivered in writing, if to Company, by emailing support@flowfuse.com and if to Customer by emailing the Customer Point of Contact email address listed on the Cover Page, provided, however, that with respect to any notices relating to breaches of this agreement or termination, a copy of such notice will also be sent in writing to the other party at the address listed on the Cover Page by courier, by certified or registered mail (postage prepaid and return receipt requested), or by a nationally-recognized express mail service. Each party may change its email address and/or address for receipt of notice by giving notice of such change to the other party.
## 13.10 Counterparts.
This Agreement may be executed in one or more counterparts, each of which will be deemed an original and all of which will be taken together and deemed to be one instrument.
## 13.11 Entire Agreement.
diff --git a/src/webinars.njk b/src/webinars.njk
index 22ccc1d26b..bb9d569bf1 100644
--- a/src/webinars.njk
+++ b/src/webinars.njk
@@ -4,7 +4,7 @@ sitemapPriority: 0.9
meta:
title: Webinars
---
-
-
{% include "benefits.njk" %}
@@ -87,6 +87,6 @@ layout: layouts/nohero.njk
Working at FlowForge
+Working at FlowFuse
Here are just some of the benefits enjoyed by our employees. We are always looking to improve and expand these too. You can read more about them in our Handbook.
We are full open about our company values, you can read more about them in our Handbook.
Interested in joining FlowForge? Check out our Jobs page for our current openings.
+Interested in joining FlowFuse? Check out our Jobs page for our current openings.
+
Webinars
diff --git a/src/webinars/2023/building-scalable-ha-node-red.md b/src/webinars/2023/building-scalable-ha-node-red.md
index 235713a403..0259366930 100644
--- a/src/webinars/2023/building-scalable-ha-node-red.md
+++ b/src/webinars/2023/building-scalable-ha-node-red.md
@@ -1,8 +1,8 @@
---
title: "Building Node-RED Applications for Scalability and High Availability"
-subtitle: Join Marian Demme, FlowForge Product Manger, to learn how to build Node-RED applications that can scale and be highly available.
+subtitle: Join Marian Demme, FlowFuse Product Manger, to learn how to build Node-RED applications that can scale and be highly available.
image: /images/webinars/webinar-june.jpg
-video:
+video: yOLvdAbopUg
date: 2023-06-22
time: 17:00 CEST (11:00 ET)
duration: 60
@@ -15,10 +15,10 @@ hubspot:
-In this webinar, we will dive deep into the world of building Node-RED applications that can effortlessly scale and maintain high availability. Marian Demme, FlowForge Product Manager, will lead this session and share practical insights and best practices to show how FlowForge can unlock the true potential of Node-RED in large-scale deployments.
+In this webinar, we will dive deep into the world of building Node-RED applications that can effortlessly scale and maintain high availability. Marian Demme, FlowFuse Product Manager, will lead this session and share practical insights and best practices to show how FlowFuse can unlock the true potential of Node-RED in large-scale deployments.
Key topics to be covered:
* Understanding scalability and high availability requirements in Node-RED applications.
* Designing scalable architectures using Node-RED flows and modules.
-* Leveraging FlowForge for scaling and load balancing Node-RED applications.
+* Leveraging FlowFuse for scaling and load balancing Node-RED applications.
-Whether you are a seasoned Node-RED developer or just beginning your journey, this webinar is designed to equip you with the essential understanding of principles related to scalability and high availability in applications using Node-RED. Join us to discover how FlowForge helps you to unlock the full potential of Node-RED in your next project and ensure your applications can handle the demands of today's connected world.
\ No newline at end of file
+Whether you are a seasoned Node-RED developer or just beginning your journey, this webinar is designed to equip you with the essential understanding of principles related to scalability and high availability in applications using Node-RED. Join us to discover how FlowFuse helps you to unlock the full potential of Node-RED in your next project and ensure your applications can handle the demands of today's connected world.
\ No newline at end of file
diff --git a/src/webinars/2023/flowforge-device-management.md b/src/webinars/2023/flowforge-device-management.md
new file mode 100644
index 0000000000..c2268be7f1
--- /dev/null
+++ b/src/webinars/2023/flowforge-device-management.md
@@ -0,0 +1,18 @@
+---
+title: "How to deploy Node-RED to hundreds of PLCs and IoT edge devices"
+subtitle: Discover how to deploy and managed hundreds of devices running Node-RED on PLCs and IoT edge computers.
+image: /images/webinars/webinar-july.jpg
+video: dvTgCBXCa5A
+date: 2023-07-27
+time: 17:00 CEST (11:00 ET)
+duration: 60
+hosts: ["rob-marcer"]
+hubspot:
+ formId: b4ec9aa1-8648-47b3-b908-ec8597e8735d
+---
+
+**Many organizations are using Node-RED as an integration platform for industrial PLCs and IoT edge computing devices. Node-REDās low code visual programming environment makes it simple to collect, analyze and take action on data at the edge. As organizations deploy Node-RED out to multiple devices or even hundreds of devices, the tools and processes can become manual and cumbersome.**
+
+
+
+FlowFuse device management features allow you to deploy Node-RED out to hundreds of PLCs and IoT edge devices. In the webinar, Rob Marcer will do a deep dive into the challenges of managing hundreds of devices running Node-RED, how to securely on-board these devices, how to deploy new versions of Node-RED in an automated manner and how to remotely troubleshoot a device. Attendees will gain a better understanding on how to Node-RED device management for large scale fleets of devices.
diff --git a/src/webinars/2023/getting-started-nodered-dashboard.md b/src/webinars/2023/getting-started-nodered-dashboard.md
index edb5713af7..d8cedf8dd4 100644
--- a/src/webinars/2023/getting-started-nodered-dashboard.md
+++ b/src/webinars/2023/getting-started-nodered-dashboard.md
@@ -1,6 +1,6 @@
---
title: "Getting Started with Node-RED Dashboard"
-subtitle: Join Rob Marcer, Developer Educator at FlowForge, for a webinar on how to use the Node-RED Dashboard nodes
+subtitle: Join Rob Marcer, Developer Educator at FlowFuse, for a webinar on how to use the Node-RED Dashboard nodes
image: /images/webinars/webinar-may.jpg
video: o6Hpvm9T6_I
date: 2023-05-25
diff --git a/src/webinars/2023/getting-started-nodered.md b/src/webinars/2023/getting-started-nodered.md
index f028f12b80..5f3b92d6bd 100644
--- a/src/webinars/2023/getting-started-nodered.md
+++ b/src/webinars/2023/getting-started-nodered.md
@@ -1,6 +1,6 @@
---
title: "Introduction to Node-RED: 5 minutes to your first program"
-subtitle: Join Rob Marcer, Developer Educator at FlowForge, for a webinar on getting started with Node-RED
+subtitle: Join Rob Marcer, Developer Educator at FlowFuse, for a webinar on getting started with Node-RED
video: 47EvfmJji-k
image: /images/webinars/webinar-nr-5mins.jpg
date: 2023-02-23
@@ -17,6 +17,6 @@ hubspot:
This webinar will introduce you to Node-RED, the key concepts and use cases that have attracted hundreds of thousands of people to adopt Node-RED as their development environment. We will show you how to create real world examples of useful projects in Node-RED in under 5 minutes each.
-Join Rob Marcer, FlowForge Developer Educator as he introduces the power of Node-RED and showcases how easy it is to get started.
+Join Rob Marcer, FlowFuse Developer Educator as he introduces the power of Node-RED and showcases how easy it is to get started.
To attend the webinar please register in advance.
diff --git a/src/webinars/2023/getting-started-opcua-node-red.md b/src/webinars/2023/getting-started-opcua-node-red.md
new file mode 100644
index 0000000000..f6300f2e20
--- /dev/null
+++ b/src/webinars/2023/getting-started-opcua-node-red.md
@@ -0,0 +1,28 @@
+---
+title: "Getting Started with OPC-UA and Node-RED"
+subtitle: Discover how easy it is to build an OPC-UA client using Node-RED
+image: /images/webinars/webinar-august.jpg
+date: 2023-08-30
+time: 17:00 CEST (11:00 ET)
+duration: 60
+hosts: ["ian-skerrett"]
+hubspot:
+ formId: b4ec9aa1-8648-47b3-b908-ec8597e8735d
+---
+
+**OPC-UA is a popular communication protocol used to communicate industrial data between different types of hardware and software. Many of the popular industrial automation PLCs vendors support an OPC server running on their hardware. Node-RED is a great low-code platform for creating an OPC client to consume the data from these PLCs.**
+
+
+
+In this webinar, we will introduce the OPC-UA nodes for creating an OPC client in Node-RED and take you through the steps to read data from an OPC server and visualize the data in Node-RED. Leading our webinar this month will be Mika Karaila, Research Director at Valmet Automation and creator of the Node-RED OPC-UA nodes. Mika will demonstrate how to get started with the OPC-UA nodes and discuss the different options for interacting between an OPC client and server.
+
+Attendees of the webinar will learn the following:
+- Understand the high level architecture and components of OPC-UA.
+- Learn how to connect with an OPC server.
+- Discover the steps for creating an OPC client inside Node-RED.
+
+
+**About Mika Karaila**
+
+Mika Karaila has over 37 years of industrial automation experience. He is currently the Research Director at Valmet Automation, a leading developer and supplier of process and automation technologies for the pulp, paper and energy industries. Mika is the creator of the Node-RED OPC-UA nodes and is a long-time member of the OPC Foundation.
+
diff --git a/src/webinars/2023/industrial-data-node-red.md b/src/webinars/2023/industrial-data-node-red.md
index ff754ac6f4..3436599779 100644
--- a/src/webinars/2023/industrial-data-node-red.md
+++ b/src/webinars/2023/industrial-data-node-red.md
@@ -1,6 +1,6 @@
---
title: "Connect, Integrate & Visualize Industrial Production Metrics with Node-RED"
-subtitle: Join FlowForge's Steve McLaughlin as he showcases how easy it is to use Node-RED to visualize popular production metrics using Node-RED.
+subtitle: Join FlowFuse's Steve McLaughlin as he showcases how easy it is to use Node-RED to visualize popular production metrics using Node-RED.
image: /images/webinars/webinar-april.jpg
video: yx_YduKR5Fs
date: 2023-04-27
@@ -27,4 +27,4 @@ This webinar will include a live demonstration of how to set up Node-RED to acco
To attend the webinar please register in advance.
**About Steve:**
-Steve McLaughlin, Node-RED OSS Developer at FlowForge, will be leading this webinar. Steve has over 25 years as an engineer in the automotive sector primarily interfacing field technologies and IS/IT. During his work in the automotive industry, he discovered the power of using Node-RED to connect, integrate and visualize industrial data. Steve is also a long time member of the Node-RED community.
\ No newline at end of file
+Steve McLaughlin, Node-RED OSS Developer at FlowFuse, will be leading this webinar. Steve has over 25 years as an engineer in the automotive sector primarily interfacing field technologies and IS/IT. During his work in the automotive industry, he discovered the power of using Node-RED to connect, integrate and visualize industrial data. Steve is also a long time member of the Node-RED community.
\ No newline at end of file
diff --git a/src/webinars/2023/introduction-to-flowforge.md b/src/webinars/2023/introduction-to-flowforge.md
index 8cee289105..690f0f8448 100644
--- a/src/webinars/2023/introduction-to-flowforge.md
+++ b/src/webinars/2023/introduction-to-flowforge.md
@@ -1,6 +1,6 @@
---
-title: "DevOps for Node-RED: An Introduction to FlowForge"
-subtitle: Join FlowForge's CTO Nick O'Leary for an introduction to FlowForge and how it provides DevOps for Node-RED.
+title: "DevOps for Node-RED: An Introduction to FlowFuse"
+subtitle: Join FlowFuse's CTO Nick O'Leary for an introduction to FlowFuse and how it provides DevOps for Node-RED.
image: /images/webinars/webinar-intro-ff.jpg
video: G6Ve84yrV2Q
date: 2023-03-30
@@ -11,10 +11,10 @@ hubspot:
formId: b4ec9aa1-8648-47b3-b908-ec8597e8735d
---
-**Join Nick O'Leary, CTO of FlowForge and co-creator of Node-RED, as he presents an in-depth webinar showcasing how FlowForge delivers reliable and secure Node-RED applications in a continuous, collaborative manner.**
+**Join Nick O'Leary, CTO of FlowFuse and co-creator of Node-RED, as he presents an in-depth webinar showcasing how FlowFuse delivers reliable and secure Node-RED applications in a continuous, collaborative manner.**
-Nick will introduce the vision of FlowForge providing the DevOps tools for Node-RED development and demo the hosted Node-RED platform, which enables delivery pipelines, team collaboration, management of remote instances, and much more. Attendees will learn how FlowForge can help scale up Node-RED development in their organization.
+Nick will introduce the vision of FlowFuse providing the DevOps tools for Node-RED development and demo the hosted Node-RED platform, which enables delivery pipelines, team collaboration, management of remote instances, and much more. Attendees will learn how FlowFuse can help scale up Node-RED development in their organization.
To attend the webinar please register in advance.
diff --git a/test/title.spec.js b/test/title.spec.js
index 5850875613..e889bd3ae2 100644
--- a/test/title.spec.js
+++ b/test/title.spec.js
@@ -18,6 +18,6 @@ describe("Page titles", async function() {
var nodes = xpath.select("//title", doc)
- assert.equal(nodes[0].firstChild.data, "FlowForge ā¢ DevOps for Node-RED")
+ assert.equal(nodes[0].firstChild.data, "FlowFuse ā¢ DevOps for Node-RED")
})
})