-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create title and description based on guidelines for EMS, Sample Data and File Upload #114336
Comments
If we're not going to be able to integrate the install functionality of sample data directly within the Integrations page, then I suggest having a single The current functionality is that each Sample Data card goes to a single link/page where they then actually decide which set to install. |
Oh and can I recommend an adjustment to the "Upload file" text to include the types of files that they support. Mainly I'm thinking about search. If a user types "CSV" into the search input, nothing will come up, yet the file uploader supports this. So maybe something like:
|
I'd be fine with this. I think we leaned more into multiple cards for discoverability. It looks like @thomasneirynck already merged the PR (#113200), so maybe we treat this as a nice to have or something we can clean up post FF? Updated the text for these cards. @thomasneirynck @clintandrewhall do you think you'd be able to update the text for these three card types? I think the table below should suffice pending any changes we decide to make to sample data
|
@thomasneirynck here's a finalize list of descriptions. If we don't have time to consolidate sample data cards into one, let's go with this.
If we do, let's go with this.
|
In 7.16, we are planning to introduce the unified integrations view. The primary goal of this view is to improve the discoverability for all data ingest options at Elastic. As part of this initiative, we'd like to improve the titles and descriptions of each integration card and do so in a uniform way.
Guidelines
These are the general guidelines we plan to use for the integration cards
Examples
Here's an example for how we can leverage these guidelines, but please follow the guidelines as you see fit.
cc: @thomasneirynck @clintandrewhall
The text was updated successfully, but these errors were encountered: