handbook: Merge product and dev into engineering #4492

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open

ZJvandeWeg wants to merge 1 commit into main from zj-merge-product-development-handbook

src/blog/2023/06/flowforge-1-8-released.md

-Original file line number
+Diff line change
@@ Expand Up @@
     Additionally, we're pleased to offer a 30-day premium trial license for self-managed installs on Kubernetes. To avail of this offer, book a demo at [flowforge.com/book-demo](/book-demo).
-    High Availability is our first [preview feature](/handbook/product/versioning/#preview-features), and your feedback is crucial. We encourage you to try out HA in your Node-RED instances and share your experiences with us. Your feedback will help us refine this feature and make it even better.
+    High Availability is our first [preview feature](/handbook/engineering/product/versioning/#preview-features), and your feedback is crucial. We encourage you to try out HA in your Node-RED instances and share your experiences with us. Your feedback will help us refine this feature and make it even better.
     <iframe width="560" height="315" src="https://www.youtube.com/embed/mbDkjKhVwIw" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
@@ Expand Down @@

src/blog/2024/05/product-strategy-updates.md

-Original file line number
+Diff line change
@@ Expand Up @@
     If you're interested in learning more about our company and product strategies, you can read more detail in our Handbook:
     - [Company Strategy](/handbook/company/strategy)
-    - [Product Mission Statement](/handbook/product/strategy)
+    - [Product Mission Statement](/handbook/engineering/product/strategy)

src/blog/2024/07/flowfuse-2-6-release.md

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -17,7 +17,7 @@ tags:
  
       - Node-RED

    ---

    FlowFuse 2.6 is packed with great new features, and in this release we've had a heavy focus on improving the development experience of Node-RED, lowering the barrier to entry for new users and aligning to our [Simplified Hosting](https://flowfuse.com/handbook/product/strategy/#simplified-hosting) and [Low-Code](https://flowfuse.com/handbook/product/strategy/#low-code) plans from our [Product Strategy](https://flowfuse.com/handbook/product/strategy/).

    FlowFuse 2.6 is packed with great new features, and in this release we've had a heavy focus on improving the development experience of Node-RED, lowering the barrier to entry for new users and aligning to our [Simplified Hosting](https://flowfuse.com/handbook/engineering/product/strategy/#simplified-hosting) and [Low-Code](https://flowfuse.com/handbook/engineering/product/strategy/#low-code) plans from our [Product Strategy](https://flowfuse.com/handbook/engineering/product/strategy/).

    <!--more-->

src/blog/2025/08/getting-started-with-flowfuse-tables.md

-Original file line number
+Diff line change
@@ Expand Up / @@ -10,7 +10,7 @@ tags: @@
        - flowfuse
     ---
-    FlowFuse recently introduced a [beta release](/handbook/development/releases/#beta-release) built-in database service to their platform, making it easier than ever to store Industrial IoT data. In a typical setup, you would need to provision a database, manage connection strings and credentials, configure nodes, and handle security settings. The goal of this new feature is to simplify or even eliminate those steps entirely. In this article, you will learn how it works and how to get started.
+    FlowFuse recently introduced a [beta release](/handbook/engineering/releases/#beta-release) built-in database service to their platform, making it easier than ever to store Industrial IoT data. In a typical setup, you would need to provision a database, manage connection strings and credentials, configure nodes, and handle security settings. The goal of this new feature is to simplify or even eliminate those steps entirely. In this article, you will learn how it works and how to get started.
     <!--more-->
@@ Expand Down @@

src/changelog/2024/01/security-updates.md

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -8,7 +8,7 @@ tags:
  
    ---

    As part of our dedication to providing a secure platform for our customers, we

    operate a [Bug Bounty programme](https://flowfuse.com/handbook/development/security/)

    operate a [Bug Bounty programme](https://flowfuse.com/handbook/engineering/security/)

    to encourage responsible disclosure of potential issues.

    With all disclosures we evaluate their severity in terms of their direct impact,

    @@ -34,7 +34,7 @@ the relevant API responses.
  
    We value the effort people put into making responsible disclosures to us and look

    to reward the work where it meets our criteria.

    Find out more about our [Bug Bounty programme](https://flowfuse.com/handbook/development/security/).

    Find out more about our [Bug Bounty programme](https://flowfuse.com/handbook/engineering/security/).

src/changelog/2025/07/flowfuse-tables.md

Original file line number	Diff line number	Diff line change
Expand Up		@@ -28,4 +28,4 @@ The database is a Postgres instance and you will be able to connect 3rd party cl

		This feature will be available to FlowFuse Cloud Enterprise Tier customers and to Enterprise Licensed Self Hosted customers on Kubernetes to start with, we hope to make it available to Docker Compose users in a future release.

		It is currently marked as a [Beta Feature](https://flowfuse.com/handbook/development/releases/#beta-release) while we continue to iterate on adding new features and observe how it is used.
		It is currently marked as a [Beta Feature](https://flowfuse.com/handbook/engineering/releases/#beta-release) while we continue to iterate on adding new features and observe how it is used.

src/handbook/company/security/incident-response.md

-Original file line number
+Diff line change
@@ Expand Up @@
     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).
+    components from outside the company, please refer to our [Vulnerability Reporting policy](/handbook/engineering/security).
     ## Incident and Event Definitions
@@ Expand Down @@

src/handbook/company/security/information-security.md

-Original file line number
+Diff line change
@@ Expand Up @@
     details.
     Any security issue related to vulnerabilities in the product should be reported
-    via our [disclosure policy](../../development/security.md).
+    via our [disclosure policy](../../engineering/security.md).
     ## Device Policy
@@ Expand Down @@

src/handbook/company/security/secure-development.md

-Original file line number
+Diff line change
@@ Expand Up / @@ -37,7 +37,7 @@ FlowFuse policy requires that: @@
         - manual product testing and verification prior to release to production
        Code reviews should also cover documentation and tests to ensure our
-       [definition of done](../../development/project-management.md#defining-done) is
+       [definition of done](../../engineering/project-management.md#defining-done) is
        achieved.
 . Risk assessment activities (i.e. threat modeling) must be performed for a
@@ Expand Down @@

src/handbook/company/strategy.md

-Original file line number
+Diff line change
@@ Expand Up / @@ -129,7 +129,7 @@ assess product-market fit. @@
     We review KPIs every Tuesday as part of our recurring strategy meeting.
     At this time, we review the following KPIs:
     * Product & Engineering
-       * [Engineering Throughput](../development/project-management.md#engineering-throughput)
+       * [Engineering Throughput](../engineering/project-management.md#engineering-throughput)
        * Active Node-RED Instances
     * Marketing
        * Pipeline Generated
@@ Expand Down @@

src/handbook/design/design-thinking.md

-Original file line number
+Diff line change
@@ Expand Up @@
     ## User 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/).
+    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](../engineering/product/personas/).
     <div class="grid grid-cols-2 gap-4">
         <div class="rounded-md bg-gray-900 text-white p-4 border-2 border-black">
@@ Expand Down @@

src/handbook/design/process.md

-Original file line number
+Diff line change
@@ Expand Up @@
     ### Product design
-    The Design process is bound by the [Development Cadence](../development/project-management#cadence).
+    The Design process is bound by the [Development Cadence](../engineering/project-management#cadence).
     Work begins on formal design (mid and high-fidelity UX and visual design assets)
     two weeks prior to a release cycle beginning.
@@ Expand Down @@

0 ...velopment/contributing/certified-nodes.md → ...gineering/contributing/certified-nodes.md

File renamed without changes.

0 ...ook/development/contributing/ff-tables.md → ...ook/engineering/contributing/ff-tables.md

File renamed without changes.

0 ...andbook/development/contributing/index.md → ...andbook/engineering/contributing/index.md

File renamed without changes.

0 ...lopment/contributing/team-npm-registry.md → ...neering/contributing/team-npm-registry.md

File renamed without changes.

0 ...k/development/frontend/data-attributes.md → ...k/engineering/frontend/data-attributes.md

File renamed without changes.

0 src/handbook/development/frontend/index.md → src/handbook/engineering/frontend/index.md

File renamed without changes.

0 src/handbook/development/frontend/layouts.md → src/handbook/engineering/frontend/layouts.md

File renamed without changes.

0 ...handbook/development/frontend/services.md → ...handbook/engineering/frontend/services.md

File renamed without changes.

0 src/handbook/development/frontend/testing.md → src/handbook/engineering/frontend/testing.md

File renamed without changes.

0 ...lopment/images/npm-registry-team-type.png → ...neering/images/npm-registry-team-type.png

File renamed without changes

0 ...dbook/development/images/pm-burn-rate.png → ...dbook/engineering/images/pm-burn-rate.png

File renamed without changes

src/handbook/development/index.md → src/handbook/engineering/index.md

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -5,17 +5,27 @@ navGroup: Engineering & Design Practices
  
    # Engineering

    The Engineering team is responsible for writing and maintaining the code for

    FlowFuse's product and infrastructure.

    The Engineering department combines product management and software development

    to build and maintain FlowFuse's product and infrastructure.

    This includes, but is not limited to:

     - Developing new product features in accordance to the Product plan

     - Providing technical input into the Product planning process - assisting with

       scoping of items, technical prioritization and sizing.

     - Defining and prioritizing product requirements based on user and customer needs

     - Developing new product features in accordance with the product strategy

     - Providing technical input into the planning process - assisting with

       scoping of items, technical prioritization and sizing

     - Providing technical support to our customers and community members

     - Ensuring the ongoing operations of FlowFuse Cloud

    ## Product

    The product function defines what we build and why.

    - [Product Overview](./product/) - how product management works

    - [Strategy](./product/strategy.md) - where the product is headed

    - [Feedback](./product/feedback.md) - how we collect and process feedback

    - [Pricing Principles](./product/pricing.md) - how we decide feature tiers

    ## General

    - [Security Policy](./security.md)

0 src/handbook/development/ops/dedicated.md → src/handbook/engineering/ops/dedicated.md

File renamed without changes.

0 src/handbook/development/ops/deployment.md → src/handbook/engineering/ops/deployment.md

File renamed without changes.

0 ...book/development/ops/incident-response.md → ...book/engineering/ops/incident-response.md

File renamed without changes.

src/handbook/development/ops/index.md → src/handbook/engineering/ops/index.md

-Original file line number
+Diff line change
@@ Expand Up @@
     You can read more about our various environments here:
-    - [Pre Staging](https://flowfuse.com/handbook/development/contributing/#test-changes-in-staging) - used for each individual pull request as part of the code review process.
+    - [Pre Staging](https://flowfuse.com/handbook/engineering/contributing/#test-changes-in-staging) - used for each individual pull request as part of the code review process.
     - [Staging](./staging.md) - triggered by merge to `main` branch, used for testing the full application, without fear of damaging the production environment.
     - [Production](./production.md) - the live environment that our customers use.

0 ...handbook/development/ops/observability.md → ...handbook/engineering/ops/observability.md

File renamed without changes.

0 ...evelopment/ops/production-stack-update.md → ...ngineering/ops/production-stack-update.md

File renamed without changes.

0 src/handbook/development/ops/production.md → src/handbook/engineering/ops/production.md

File renamed without changes.

0 .../development/ops/self-hosted-assistant.md → .../engineering/ops/self-hosted-assistant.md

File renamed without changes.

0 src/handbook/development/ops/staging.md → src/handbook/engineering/ops/staging.md

File renamed without changes.

0 src/handbook/development/packaging.md → src/handbook/engineering/packaging.md

File renamed without changes.

0 src/handbook/product/blueprints.md → ...andbook/engineering/product/blueprints.md

File renamed without changes.

0 src/handbook/product/dashboard.md → ...handbook/engineering/product/dashboard.md

File renamed without changes.

0 src/handbook/product/feedback.md → src/handbook/engineering/product/feedback.md

File renamed without changes.

0 src/handbook/product/glossary.md → src/handbook/engineering/product/glossary.md

File renamed without changes.

src/handbook/product/index.md → src/handbook/engineering/product/index.md

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -1,14 +1,13 @@
  
    ---

    navTitle: Product

    navGroup: Company

    ---

    # Product

    The product department, and Product Managers (PM) by extend are responsible for:

    The product function, and Product Managers (PM) by extension, are responsible for:

    1. Understanding and communicating the problem of our users and customers.

    2. Defining requirements for a solution that is loved by our users, customers and the community.

    3. Continuously aligning the product strategy with FlowFuse's core [strategic objectives](../company/strategy.md), ensuring not only that the product meets current market demands but also anticipates future trends.

    3. Continuously aligning the product strategy with FlowFuse's core [strategic objectives](../../company/strategy.md), ensuring not only that the product meets current market demands but also anticipates future trends.

    ## Core tasks and responsibilities

    @@ -22,14 +21,14 @@ The product department, and Product Managers (PM) by extend are responsible for:
  
    | Determine Pricing Tier for Features                            | While the CEO and Sales team handle pricing, the PM is responsible for determining which features belong to specific [tiers](./pricing.md).                                                                                                                       |

    | Product-Related Decisions                                      | The PM is responsible for making strategic decisions that shape the overall direction of the product.                                                                                                                                                                                                         |

    ## How the product department works

    ## How product works

    - [Glossary](./glossary.md)

    - [Feedback](./feedback.md)

    - [Product Categories](./verticals.md)

    - [Strategy](./strategy.md)

    - [Pricing Principles](./pricing.md)

    - [Feature Demos](/handbook/development/project-management#feature-demos)

    - [Feature Demos](/handbook/engineering/project-management#feature-demos)

    - [Versioning](./versioning.md)

    - [Metrics](./metrics.md)

    - [Node-RED Dashboard](./dashboard.md)

src/handbook/product/metrics.md → src/handbook/engineering/product/metrics.md

-Original file line number
+Diff line change
@@ Expand Up @@
     ## Principles
     #### Data-driven decision making
-    Aligned with our value of [Results](../company/values.md#📈-results), we are staunch advocates for data-driven decision-making. Instead of relying on assumptions or rushing decisions, we let data guide our actions to drive results. This doesn't mean we become paralyzed in the absence of data. Our Iterative Improvement and Bias for Action values remind us that it's crucial to keep moving forward, even when perfect data isn't available. We balance careful analysis with swift action, using the best information available to us at any given moment.
+    Aligned with our value of [Results](../../company/values.md#📈-results), we are staunch advocates for data-driven decision-making. Instead of relying on assumptions or rushing decisions, we let data guide our actions to drive results. This doesn't mean we become paralyzed in the absence of data. Our Iterative Improvement and Bias for Action values remind us that it's crucial to keep moving forward, even when perfect data isn't available. We balance careful analysis with swift action, using the best information available to us at any given moment.
     #### Continuous learning and improvement
-    Consistent with [Iterative Improvement](../company/values.md#🔁-iterative-improvement), we believe even the smallest changes can contribute to our growth. We're committed to consistently reassessing, learning, and evolving based on the insights our data provides.
+    Consistent with [Iterative Improvement](../../company/values.md#🔁-iterative-improvement), we believe even the smallest changes can contribute to our growth. We're committed to consistently reassessing, learning, and evolving based on the insights our data provides.
     ## Leading Product Metric
@@ Expand Down @@

src/handbook/product/personas/index.md → ...ook/engineering/product/personas/index.md

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -128,7 +128,7 @@ What problem does the persona want to solve, or which benefit does the character
  
    <div class="persona-card rounded-md bg-gray-900 text-white p-4 border-2 border-black flex flex-col">

        <div class="flex gap-6 border-b-2 border-red-400 pb-3 w-full">

            <div class="w-48 py-2 pr-6 text-center border-r-2 border-teal-400">

                <img class="w-full rounded-md border-2 border-white m-auto" src="../../images/personas/paul.jpg">

                <img class="w-full rounded-md border-2 border-white m-auto" src="../../../images/personas/paul.jpg">

                <label class="block mt-2 font-medium text-2xl">Paul</label>

                <label class="block">Plant Manager</label>

            </div>

    @@ -204,7 +204,7 @@ What problem does the persona want to solve, or which benefit does the character
  
    <div class="persona-card rounded-md bg-gray-900 text-white p-4 border-2 border-black flex flex-col">

        <div class="flex gap-6 border-b-2 border-red-400 pb-3 w-full">

            <div class="w-48 py-2 pr-6 text-center border-r-2 border-teal-400">

                <img class="w-full rounded-md border-2 border-white m-auto" src="../../images/personas/steve.jpg">

                <img class="w-full rounded-md border-2 border-white m-auto" src="../../../images/personas/steve.jpg">

                <label class="block mt-2 font-medium text-2xl">Steve</label>

                <label class="block">Plant Engineer</label>

            </div>

    @@ -280,7 +280,7 @@ What problem does the persona want to solve, or which benefit does the character
  
    <div class="persona-card rounded-md bg-gray-900 text-white p-4 border-2 border-black flex flex-col">

        <div class="flex gap-6 border-b-2 border-red-400 pb-3 w-full">

            <div class="w-48 py-2 pr-6 text-center border-r-2 border-teal-400">

                <img class="w-full rounded-md border-2 border-white m-auto" src="../../images/personas/sarah.jpg">

                <img class="w-full rounded-md border-2 border-white m-auto" src="../../../images/personas/sarah.jpg">

                <label class="block mt-2 font-medium text-2xl">Sarah</label>

                <label class="block">Process Engineer</label>

            </div>

    @@ -357,7 +357,7 @@ What problem does the persona want to solve, or which benefit does the character
  
    <div class="persona-card rounded-md bg-gray-900 text-white p-4 border-2 border-black flex flex-col">

        <div class="flex gap-6 border-b-2 border-red-400 pb-3 w-full">

            <div class="w-48 py-2 pr-6 text-center border-r-2 border-teal-400">

                <img class="w-full rounded-md border-2 border-white m-auto" src="../../images/personas/isabella.jpg">

                <img class="w-full rounded-md border-2 border-white m-auto" src="../../../images/personas/isabella.jpg">

                <label class="block mt-2 font-medium text-2xl">Isabella</label>

            <label class="block">IIoT Project Lead & Industrial IT Architect</label>

            </div>

    @@ -446,7 +446,7 @@ What problem does the persona want to solve, or which benefit does the character
  
    <div class="persona-card rounded-md bg-gray-900 text-white p-4 border-2 border-black flex flex-col">

        <div class="flex gap-6 border-b-2 border-red-400 pb-3 w-full">

            <div class="w-48 py-2 pr-6 text-center border-r-2 border-teal-400">

                <img class="w-full rounded-md border-2 border-white m-auto" src="../../images/personas/peter.jpg">

                <img class="w-full rounded-md border-2 border-white m-auto" src="../../../images/personas/peter.jpg">

                <label class="block mt-2 font-medium text-2xl">Peter</label>

                <label class="block">Automation and Controls Engineer</label>

            </div>

0 src/handbook/product/pricing.md → src/handbook/engineering/product/pricing.md

File renamed without changes.

0 src/handbook/product/principles.md → ...andbook/engineering/product/principles.md

File renamed without changes.

src/handbook/product/strategy.md → src/handbook/engineering/product/strategy.md

-Original file line number
+Diff line change
@@ Expand Up @@
     Any new feature requests, product improvements, or other changes to our product can be reflected back to these pillars to ensure they are in line with our product strategy.
-    We can break down our product pillars into smaller "Areas", which are more specific focus areas on how to optimize the product pillar. You can see how these Areas are used in our product planning [here](../development/project-management.md).
+    We can break down our product pillars into smaller "Areas", which are more specific focus areas on how to optimize the product pillar. You can see how these Areas are used in our product planning [here](../project-management.md).
     | Build | Manage | Deploy |
     |-------|--------|--------|
@@ Expand Down @@

0 src/handbook/product/telemetry.md → ...handbook/engineering/product/telemetry.md

File renamed without changes.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

handbook: Merge product and dev into engineering #4492

Uh oh!

Diff view

Diff view

There are no files selected for viewing

Uh oh!

Uh oh!

handbook: Merge product and dev into engineering #4492

Are you sure you want to change the base?

Uh oh!

handbook: Merge product and dev into engineering #4492

Uh oh!

Uh oh!

Diff view

Diff view

There are no files selected for viewing

Uh oh!

Uh oh!