dzwillia
commented
7 years ago A checklist of use cases that have been written or still need to be written can be found in issue #279.
Closed natetrek closed 5 years ago
dzwillia
commented
7 years ago A checklist of use cases that have been written or still need to be written can be found in issue #279.
dzwillia
commented
5 years ago Moved to #279 (in checklist form).
Currently, there's a significant "use case" gap in our website content. On one end of the spectrum, the content makes general promises we make ("let cloud-based pipes do your dirty work") and on the other, we offer specific examples/templates for a given pipe, but don't fully explain the use case and how to implement these examples in the context of the developer's own code.
To address this gap, we need to add a series of "use case" pages under a new "Use Cases" section.
In each case, the individual use case page acts as a "sales rep" for our product -- it makes a specific pitch or offering, and if some one wants this offering, the page provides a set of steps on how to get set up with the solution. In this way, each "use case" page can function as an input to our web-driven sales funnel.
Here's what's needed to make this happen:
1. Create a set of use case pages
Each page should have a set of content that makes a "pitch" for the use case:
If we include a feedback request, if the user clicks "no", we can pop open a form asking them what info was missing or why the use case didn't meet their needs.
2. Create overview page for the use cases
This is a portal page for the use cases. It lists a set of categories for the use cases, along with links to 4-5 use cases for each category. Here are some options for the page heading:
For a nice comp see: https://www.twilio.com/use-cases
3. Update the navigation and the home page
Generally, we should simplify the home page and reduce the verbiage. In addition, it should focus more on the use case examples and specific tasks what Flex.io can do.
The overall message/promise we can convey to developers here is that we're giving them a range of pre-built data processing tools and building blocks that they can plug into their code immediately, saving them the time and hassle of writing code to create these building blocks themselves.
Here are the changes needed to the home pages and site navigation:
New site organization and navigation
The new use cases section does not replace the existing example templates, but supplements and makes use of these. Multiple use case pages might link to a single example/template. Alternately, a single use case page might link to or reference multiple examples/templates, if there are different pipe variations that are all relevant to a single use case.
Here's a diagram that shows how the new site organization and navigation works:
Ultimately, the focus of these changes is to incorporate a large number of use case pages into the website. Everything revolves around these use cases and their content.
Here's a set of use case categories and individual use cases that could be listed under them:
CHARTS AND GRAPHS
DATA VISUALIZATION
SAAS UTILITIES
SAAS CONNECTORS
DATA-DRIVEN COMPONENTS
DATA FEEDS
DATA CLEANING
DATA VALIDATION
IMAGE PROCESSING
WEB SCRAPING
API INTEGRATION