Open gstout52 opened 2 months ago
After conversation with @joepavitt , for a first iteration we'll make a modification to the Blueprints webpage where users can submit flows and filter between blueprints and flows based on type (blueprint vs. flow) and other filters identified above.
The flow creation form will (probably) need to exist inside of FlowFuse, so some additional digging will be needed on this.
How does this overlap with your Certified nodes point in the strategy review @MichaelBDavis? Have these points of conversation come from the same origin?
We also need to consider prioritisation here vs. the other development items we have (and we have a lot of them, especially larger items right now), it's unlikely this will jump to the top ahead of MQTT Broker, Asset Service improvements, bill of materials, etc.
@joepavitt I understand. For my own planning, do you have an approximate timeframe in mind when you could pick this up?
1-2 months realistically. This is a large piece of work anyway, and we're already backlogged until then.
I've created two issues for tracking the details here, and how we'd expose this on our website:
"Certified Flows" as referred to in this issue, will be merged with our existing "Blueprints"
@joepavitt Can you clarify the intended hierarchy of the homepage, Integrations page, and Blueprints page?
Not sure what you mean in terms of the hierarchy?
Integrations page will be a wrapper for https://flows.nodered.org, and detail our "Certified Nodes", and we can tightly couple Blueprints to the relevant nodes here too, e.g. if you click on @flowfuse/node-red-dashboard
, we can advertise a Blueprint to get you started.
The Blueprints page is the collection of "official" flows to get you started in Industrial use cases
Description
This Epic is for creating a FlowFuse 'certified flows' function. The ultimate goal is for customers to create a flow, submit it for review to FlowFuse, and when approved, have it offered as 'certified by FlowFuse' in an internal creator marketplace, where our customers are the creators.
We can use Reforge.com as a model for this: (http://reforge.com/artifacts)
For a first iteration, we'll see how much appetite there is from customers to (1) share flows and (2) use flows created by others.
First iteration:
Flow export:
Flow import:
Subsequent iterations:
Which customers would this be available to
Team + Enterprise Tiers (EE)