Support multiple news feeds

[ryankeairns]

As a user, I would like to view news items that are relevant to my job.

As a solution provider, I would like to communicate relevant news to my target audience.

Kibana currently provides a "What's New" feature, via the header, that presents a broadly scoped set of news items. There is now a desire to expand this feature to accommodate multiple, specialized news feeds.

cc:/ @alexfrancoeur

Figma prototype

https://www.figma.com/proto/EG8LewmUTK2la66aXfkOKE/Kibana-Header-Search?node-id=736%3A3307&viewport=804%2C417%2C1&scaling=min-zoom

Screenshot from Figma link

[elasticmachine]

Pinging @elastic/kibana-core-ui (Team:Core UI)

[ryankeairns]

@MichaelMarcialis assigning you just as a reminder that we need to provide Alex a mockup. Not urgent, but let me know when you have time and we can chat further. It seems fairly straightforward.

[alexfrancoeur]

Heya @ryankeairns, taking the underlying implementation out of it (separate feeds vs. one massive feed that's filterable / tagged), this is what I was thinking. Hope it helps!

• One global feed for all content coming in. News, training, promotion, release blogs, press releases, security vulnerabilities, etc.
• A feed per landing page within Kibana (SIEM, Observability, etc.)
• The global feed should be filterable and a subset of the content should be what's shown in the feeds for each landing page. These filters should be persisted on a per user basis.
• The feeds that come to mind are Enterprise Search, Observability, Security, Elastic Stack, Kibana, Elastic Cloud
• All feeds enabled by default with option to disable from within the global feed
• For the global feed, I would expect that the items are sorted by time, not content, possibly visually differencing them each item by tag

The prototype looks good, but some sort of indicator of category might be nice to have in the feed itself

[ryankeairns]

@alexfrancoeur thanks, that helps. Do you envision users being allowed to disable only by solution? In other words, you can disable each of Enterprise Search, Observability, Security, Elastic Stack, Kibana, Elastic Cloud, but you'd still have some news coming in (that which is not tied to a solution)?

What I'm ultimately trying to avoid (possibly) is an empty news feed situation.

[alexfrancoeur]

Great point and I agree. I'm watching a presentation around how Cloud will be approaching this at the moment. To align with what @osmanis is thinking for Cloud, it might make sense to use the categories Elastic Stack, Elastic Cloud, Elastic News, Enterprise Search, Observability and Security.

To answer your question, I see a two options.

• Don't allow for disabling of "Elastic News" (depending on the expected content, but I imagine it's things like release blogs)
• Always show one feed and disable the ability to filter out the last feed. Seems like an odd experience though.

@osmanis has been putting some thought into this from the Cloud side and we probably want the same experiences, any thoughts?

[osmanis]

What I'm ultimately trying to avoid (possibly) is an empty news feed situation.

One approach to consider is to always show all categories in the newsfeed. Users don't get the ability to filter out content on the feed. Instead, users get the ability to select what they get notified on (the categories we make available).

Benefits with this approach:

• Users can fully select what they want to be notified on. They can disable everything if they want. They won't see the notification light on content they don't care about.
• Users still have the ability to see a list of all new items if they choose to click on the icon. This helps to give us views and eliminates edge cases where there would be no content to show (if we were to allow filtering by content).