Marketing Page: Device Agent

[joepavitt]

Epic

No response

Description

As a: FlowFuse Employee

I want to: have a marketing resource that I can share about our "Device Agent"

So that: we can better communicate what the customer value of the device agent is, without needing to link to technical/overwhelming documentation.

We are quite vague on our website about edge agents, etc. Having an explicit page I could link to when leads come up would be really useful.

Acceptance Criteria

• Emphasising how lightweight the agent is
• Remote management and deployment of Node-RED instances
• Easy deployment/updating of flows
• Centralised management of thousands of "devices"

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

[sumitshinde-84]

We do have newly created documentation available here that currently provides resources on setting up Node-RED on various hardware devices, using different databases, protocols, notification services, and integration technologies. This section will be expanded further, but I think you are referring to something more specific. Should that be added to this new documentation?

[joepavitt]

I don't think its documentation we need, more of a landing page for Device Agent to advertise it's value/feature. Similar to what we are doing for Dashboard with flowfuse.com/dashboard

[sumitshinde-84]

Thanks @joepavitt, now I understood !

[Hasmin-AC]

I will work on some draft content and share soon.

[joepavitt]

We should also update this link on the Manufacturing page to point to the new landing page:

[Hasmin-AC]

@joepavitt We have this page about Edge Device Management Is this pretty much the same content we would have for a page on Device Agent?

Should we just update this page rather than create a new one?

[joepavitt]

I think the existing page is more about the general use case for edge device management, which encompasses the story of FlowFuse, Device Agent, Project Nodes and even Dashboard.

For this new page, we want it focussed on the Device Agent offering, a little more technical than the other page, but not too much. Focus on what it enables, it's ease of use (maybe even a pseudo-demo animation - which I can storyboard)

[Hasmin-AC]

Got started on some draft content. I didn't have too much to go on so would be great if you can add more specific details to this doc - https://docs.google.com/document/d/1-brzrhsxGImHqNt6lUwiKq0UdTWQXqmQzL7QDeQkTC4/edit

[joepavitt]

I didn't have too much to go on

Exactly why we're needing this page, as nor do our customers! I've requested access to the file

[Hasmin-AC]

Done

[joepavitt]

Thanks @Hasmin-AC I've added comments and suggestions. The key here (which is a big confusion for customers too) we have:

• Device Agent
• Project Nodes

The agent is the piece that's installed onto devices/hardware and allows for remote management/deployment of Node-RED instances to that hardware, via FlowFuse.

The nodes are then what allow for easy collection of that remote data back to centralised instances on FF Cloud for example.

[joepavitt]

I've very quickly put a storyboard together for the video/animation too (fyi @Yndira-E)

Emphasis probably at the end here too on how this can then be deploy out to hundreds of devices, not just the one.

Storyboard is in https://www.figma.com/board/wOZC4A72Q48AAWcUe0uoF3/Storyboard---Device-Agent-Animation?node-id=0-1&t=A4LZjPcomIPeEowP-1

[joepavitt]

maybe even the terminal behind FlowFuse UI here, this is from the Mongo homepage:

Screen.Recording.2024-07-18.at.12.54.31.mov

[Yndira-E]

Here's the design:

For the video, we're adding this one until the new one is ready.

And we still need the FAQs, but those can be added in the PR.

[joepavitt]

The "Seamlessly" header/line I think could be a bit different, as it's not the true value of the device agent here. "Seamlessly manage your devices all in one place" is the value of the agent/flowfuse crossover

[Yndira-E]

Noted, Joe. Thanks for the suggestion.
The doc says: Url: flowfuse.com/device-agent.
But since "cloud" and "dashboard" are under /product/*, would it make sense to add this one to the same route?

[joepavitt]

But since "cloud" and "dashboard" are under /product/*, would it make sense to add this one to the same route?

Most certainly