#  Blueprints

Screenshot of the Blueprint selection UI in FlowFuse

As part of the FlowFuse platform, it is possible to define "Blueprints".

Blueprints are packaged flows that help users get up and running with a particular project or idea. They should be informative, easy to understand, and provide a clear path to value.

FlowFuse host a public version of our Blueprint Library here.

#  Tracking Blueprint Ideas

We have a GitHub Project Board used to track the state of each idea recorded in the private blueprint-library repository (link).

Screenshot of the Blueprint Project Board

#  Submitting a Blueprint

#  Public Submission

We encourage Blueprint submissions from our customers, partners, and the wider community. Anyone can submit their own Blueprint idea via our online portal here. Please check with the Minimum Requirements to ensure any submissions have provided the relevant details.

#  Internal Development

If a Blueprint is being developed internally, then the Blueprint can be added to the Blueprint repository directly, via a Pull Request. An issue should be raised first in the blueprint-library repository to track the progress of the Blueprint, and to be sure the Blueprint aligns with the product and company strategy.

#  Minimum Requirements

#  Flow

The bare minimum requirement for a Blueprint is the respective flow.json file which details the Node-RED flow associated to the Blueprint.

#  Dependencies

With the flow.json we also need to have details on any third-party nodes and dependencies that the flow.json will require in order to be functional.

#  Screenshots

Images help commuicate the value of a Blueprint, without the need to fully deploy it. Screenshots and images are used as part of marketing material in socials, as well as imagery on the Blueprint Library itself, e.g. the image background of the Blueprint's tile.

#  Appearance

Blueprints are designated to a category. On FlowFuse Cloud, these categories are currently:

• Getting Started
• Manufacturing
• Other

But others can, and should, be added as required.

Each Blueprint can also have a custom icon, which should be defined as an icon from Hero Icons v1. The color for the tile of each Blueprint is hardcoded then depending on the category. Any changes to color, or coloring of new categories currently require a code change within FlowFuse.`

#  Company Information

Submissions are encouraged to be from an organisation, rather than an individual. As such, any submission must has an associated:

• Company Name
• Company Logo

#  Publishing a Blueprint

Blueprints must be published in two locations:

• Website: This is our public Blueprint Library, where users can browse Blueprints and get access to a quick "Deploy" action.
• Platform: This is the internal Blueprint Library within FlowFuse. It is configured as part of the FlowFuse Admin Panel.

#  Website

To add a Blueprint to our public Blueprint Library, we need to add an .md file to the relevant category folder in the /src/blueprints directory of the website repository. The purpose of this page is to advertise the Blueprint, so entries should contain appealing visuals and a clear description of the Blueprint's purpose and value.

#  Platform

Screenshot of the Blueprint Admin Panel in FlowFuse

1. Make sure the Blueprint is published to the blueprint-library repository.
2. Login to FlowFuse Cloud as an Administrator
3. Navigate to the Admin Panel
4. Select the "Blueprints" tab
5. Click "Create Flow Blueprint"
6. Fill in the details of the Blueprint
7. Click "Create"