Callout Valuable Integrations

joepavitt commented 2 years ago

Description

As part of the landing page, we should be calling out recognisable integrations we offer (e.g. twitter, mqtt) that customers will relate to. Currently, our homepage is very vague.

Design to come, but my thinking at the moment is that we show 4+ high level groups of integrations we offer (e.g. socials, hardware), then beneath the icons/pictogram for each group, we list a few of the most recognisable ones.

This will replace the existing 0.1 intro video, and later, the Landing Video will also be included on the homepage.

Currently, in our draft landing video, we have the following integrations advertised:

Socials: Facebook, Twitter, Telegram, Slack, WhatsApp, Discord
Cloud Services: AWS, Azure, S3
AI & Smart Home: Alexa, Azure Cognitive Services, Google Home, IBM Watson, TensorFlow
Storage: MongoDB, MySQL, Redis, DB2, MSSQL, CouchDB, DashDB, CloudantDB
Media: Storage Tools, OpenCV, SVG, FFMPEG
File Support: CSV, Json, XML, YML, ONVIF
Hardware: Arduino, Raspberry Pi
???: Websockets, HTTP, MQTT, RSS, E-Mail, FTP, SNMP

Note sure where these group:

OPCUA, S7, MC Protocol, FINS Protocol, OpenProtocol, ZWave, Zigbee, Twilio, Viseo, AMQP, SSH

joepavitt commented 2 years ago

@Steve-Mcl can you run through these and group them into something sensible please that would appeal to our customers/stakeholders?

Steve-Mcl commented 2 years ago

Social: Twitter, Twillo, Telegram, Slack, WhatsApp, Discord, Facebook
Cloud: AWS, Azure, S3
Smart: Alexa, Azure Cognitive Services, Alexa, Google Home, IBM Watson, TensorFlow, ZWave, Zigbee
Storage: MongoDB, MySQL, PostgreSQL, SQL Server, Redis, DB2, CouchDB, DashDB, CloudantDB
Media: OpenCV, SVG, FFMPEG, Image Processing
~~File Support: CSV, Json, XML, YML, ONVIF~~ move to storage?
Hardware: Arduino, Raspberry Pi, Zigbee
Industrial Protocols: OPCUA, ModBus, Siemens S7, Mitsubishi MC Protocol, OMRON FINS Protocol, OpenProtocol
Communication: WebSocket, HTTP, MQTT, AMQP, SNMP, RSS, E-Mail, FTP

Other potential categories to consider...

Digital transformation - this could encompass a lot of the social/protocol/communication stuff
Field - could encompass industrial protocols and hardware

NOTE: I have added and removed a hand full of items under several headers (and slight juggling too)

Hope that helps - let me know if you need something different.

joepavitt commented 2 years ago

Draft pass on how these will be laid out:

Steve-Mcl commented 2 years ago

What will be in the boxes Joe?

Where / how do you see the text displayed - as it is now in a CSV list?

joepavitt commented 2 years ago

Smart: Alexa, Azure Cognitive Services, Alexa, Google Home, IBM Watson, TensorFlow, ZWave, Zigbee

Can we think of an alternative term, instead of "Smart". I see what you're doing in grouping AI/Smart Home & Home IoT stuff together, but "Smart Home" and "AI" may not warrant their own groups? Arguably "Smart Home" could warrant it's own group actually...

joepavitt commented 2 years ago

What will be in the boxes Joe?

Placeholders for pictograms/icons that will match the style of the rest of the website. Just left them blank for now as to not get bogged down in iconography discussion/opinions

joepavitt commented 2 years ago

Where / how do you see the text displayed - as it is now in a CSV list?

yeah, I'd envisioned it being just a sample selection in comma-separated list, with an ", etc" at the end, although open to alternative suggestions.

ZJvandeWeg commented 2 years ago

I like the iteration on the homepage. I wonder though if we should invest in a onboarding guide? To answer "how" you integrate them.

joepavitt commented 2 years ago

I like the iteration on the homepage. I wonder though if we should invest in a onboarding guide? To answer "how" you integrate them.

Would that not partly be responsibility of (to be hired) developer advocate/educator/content creator

Steve-Mcl commented 2 years ago

BMS (Building Management Services) and Smart Home are quite similar (workplace vs home place)

Can we think of an alternative term, instead of "Smart". I see what you're doing in grouping AI/Smart Home & Home IoT stuff together, but "Smart Home" and "AI" may not warrant their own groups? Arguably "Smart Home" could warrant it's own group actually...

Ok, I understand. Then AI can be separate.

Initial breakdown...

Socials

Twitter, Twillo, Telegram, Slack, WhatsApp, Discord, Facebook

Hardware

Server, NUC, Raspberry Pi, Arduino, ESP

Hardware Integrations (alternative to above)

Server, PLCs, Network Switches, Network Routers, Edge devices, NUCs, Raspberry Pi, Arduino, ESP, etc

Messaging

WebSocket, HTTP, MQTT, AMQP, SNMP, RSS, E-Mail, FTP, OPCUA, ModBus, Siemens S7, Mitsubishi MC Protocol, OMRON FINS Protocol, OpenProtocol, Zigbee, Z-Wave

Cloud

AWS, Azure, S3

AI

TensorFlow, IBM Watson, Azure Cognitive Services

Storage

MongoDB, MySQL, PostgreSQL, SQL Server, Redis, DB2, CouchDB, DashDB, CloudantDB, CSV, JSON, YAML, XML

Whats left...

Smart: Alexa, , Alexa, Google Home, , ZWave, Zigbee Media: ONVIF, OpenCV, SVG, FFMPEG, Image Processing

Steve-Mcl commented 2 years ago

TBH, Twitter & Telegram can also be part of messaging too (as can Slack, WhatsApp, Twillo). Not 100% certain categories are best fit.

An endless (mixed) list underneath the set of icons may be a better fit? Perhaps the text could be coded e.g. Database stuff in a different colour/format to AI etc?

ZJvandeWeg commented 2 years ago

Would that not partly be responsibility to (to be hired) developer advocate/educator/content creator

@joepavitt yes, but now it's everybody's responsibility. So we should start iterating

joepavitt commented 2 years ago

@Steve-Mcl any way we could split "Messaging"?

joepavitt commented 2 years ago

First pass (with icons):

sammachin commented 2 years ago

Personally the word Messaging doesn't make me think of those things which are protocols,

I would also change Socials to Communications

joepavitt commented 2 years ago

@sammachin any better?

joepavitt commented 2 years ago

Closed by #132

FlowFuse / website