I note that there is a lack of breadcrumbs displayed in the search results displayed by KB Site 2.0, and only the parent category name is displayed. This means that there is an absence of full navigational context for each article in the search results. For content in my company's information architecture, all parts of the breadcrumb are important and provide valuable information about the context of the search result. In our case, the first navigation level is product name, second level is product version, third level and lower are documentation structure. Without all this context displayed in the search results (directly displayed, rather than hidden in a tooltip), our users will be unable to understand at a glance what each search result is about.

An additional factor is that multiple articles in different parts of the knowledgebase might each have a parent category that has the same name as another category in the knowledgebase. For example, there will be an Installation Guide category in the Product A part of the navigation, and also an Installation Guide category in the Product B part of the navigation, so that the user has a consistent experience when navigating the knowledgebase. In the current KB Site 2.0 search results implementation, the user would be unable to see which product’s installation guide a particular article in the search result was part of.

Please could you consider how to offer customers like us an alternative search result context layout, this perhaps could be an option in Settings because I understand that the current layout in KB Site 2.0 search results will suit some customers fine. As a suggestion, perhaps in an alternative search result layout, 1.) the current category name could instead be the full breadcrumbs and occupy the whole width of the search results window, 2.) the site and language indicators could move to a new line underneath the breadcrumbs, 3.) the site and language indicators could be hidable (because, for example, in my company's case this information is not useful to the reader), 4.) the breadcrumbs line could be configured to wrap if necessary rather than truncate (although, because the current category name text is small, maybe this wouldn’t be necessary), and 5.) the breadcrumb text colour could be configurable.