[Getting Started] Update home page to promote Integrations more

[alexfrancoeur]

When all ways to add data are consolidated into a single view via linked cards (#93084), we'll also want to update the homepage to provide a single CTA for data ingestion. In addition to these changes, we'll also want to equally weigh the Analytics card with our other solutions.

As these cards exist with RBAC already supported, this is more of a slim down / restyling effort and should be fairly low touch. In the future, we can plan to make changes larger changes to the homepage

[elasticmachine]

Pinging @elastic/kibana-design (Team:Kibana-Design)

[MichaelMarcialis]

Hey, @alexfrancoeur! I'm planning on doing some design exploration on this task over the next week or two. Before diving in, I had a few questions for you:

• Would this be an appropriate time to reconsider changing the title of the "Kibana" solution/bucket to "Analytics" (both on the home and overview pages)? I believe that making such a change would 1) make it more obvious to new users as to what apps the bucket/solution contains, 2) be consistent with how the solution/bucket is identified in the main navigation (where it is titled "Analytics," and 3) avoid general confusion over the fact that the platform itself is also called Kibana.

• Am I correct in assuming this new, singular "add data" call-to-action is intended to navigate users to what is currently the integrations main page?

• In the area containing this new "add data" call-to-action, do we wish to also include shortcuts to supplemental data ingestion actions (in a subdued or secondary action style). For example, small links to sample data and uploading a file immediately come to mind as potentially valuable.

• In the area containing this new "add data" call-to-action, would there be any interest in also presenting the user with a handful of "recommended integrations," in addition to the primary "add data" call-to-action? In the short term, we could simply present our most popular integrations. In the long term, we could consider enhancing the section by making smart integration recommendations based on any data already ingested. Or alternatively, assuming we're considering asking users to identify their interests during the cloud deployment creation process, we can also use such a "recommended integrations" area to spotlight those selected integrations. Thoughts?

• What is the expected experience for users who don't have permission to access the integrations section of Kibana. Should the section containing the call-to-action(s) for "add data" be removed? Or should it be replaced with alternative actions/content?

Thanks for any answers. Let me know if you'd prefer to discuss over Zoom rather than GitHub, and I'll throw something on the calendar.

CCing @ryankeairns.

[alexfrancoeur]

Would this be an appropriate time to reconsider changing the title of the "Kibana" solution/bucket to "Analytics" (both on the home and overview pages)?

We discussed this when we adjusted the home page awhile back. I think it's probably time to revisit again, but we'll likely want to involve @VijayDoshi in the discussion as well.

Am I correct in assuming this new, singular "add data" call-to-action is intended to navigate users to what is currently the integrations main page?

That is the goal, though I'm not quite sure if we'll be able to execute on this in the near term. We are looking to prioritize as much as we can and I should have more details on how we might be able to in the next few days. When thinking through designs, I'm not sure if this is something we can safely assume at the moment. It might be worth thinking through two options. One with a single CTA, and another that relies on a primary and secondary approach to ingest - similar to the proposal here #107682. If this work is meant to be delivered in 7.15, we will not have a single unified view for ingestion.

In the area containing this new "add data" call-to-action, do we wish to also include shortcuts to supplemental data ingestion actions (in a subdued or secondary action style). For example, small links to sample data and uploading a file immediately come to mind as potentially valuable.

Similar to the comment above, to the extent we can (assuming 7.15 deliverable), we may wan to borrow the visual language from the overview pages here: #107682

In the area containing this new "add data" call-to-action, would there be any interest in also presenting the user with a handful of "recommended integrations," in addition to the primary "add data" call-to-action? In the short term, we could simply present our most popular integrations. In the long term, we could consider enhancing the section by making smart integration recommendations based on any data already ingested. Or alternatively, assuming we're considering asking users to identify their interests during the cloud deployment creation process, we can also use such a "recommended integrations" area to spotlight those selected integrations. Thoughts?

Yes, this is a goal long term, but we are nowhere near suggestions at the moment. We are tracking suggestions in the broad context in this meta issue: #83355. It's possible that we can hack it and not personalize, providing a list of "popular integrations" but this will likely require work and additional output from the Elastic Package Registry (EPR) team. If 7.15 is the goal for this design, I don't think we should rely on this functionality. At the moment, we also are not capturing intent or identification of interests during the deployment process. This is also further out.

What is the expected experience for users who don't have permission to access the integrations section of Kibana. Should the section containing the call-to-action(s) for "add data" be removed? Or should it be replaced with alternative actions/content?

I think this is up for debate. There is some interest in surfacing these integrations and modules for discoverability, but I imagine an administrator may also be interested in hiding this. Let's assume RBAC for now, and use the default homepage experience should we choose to promote discovery of integrations regardless of access

I hope this helps. If it's easier to touch base live and talk through some of this, let's find some time to connect in the next few days @MichaelMarcialis @ryankeairns