Elastic Branding Updates

[alexfrancoeur]

@elastic/kibana-core-ui While we wait on the navigation changes, we'd like to introduce some branding changes to Kibana in 7.7. The full list can be found below and the changes should be made for all builds.

• Login screen text and icon updates Login screen text and icon updates #59170
• Loading screen text and icon updates Loading screen text and icon updates #59167
• Change "Add Data to Kibana" references to "Add Data" Change "Add Data to Kibana" references to "Add Data" #59160
• Update newsfeed header Update newsfeed header #59165
• Update web app / tab title Update web app / tab title #59174

[chandlergibb]

Hi @alexfrancoeur — apologies for parachuting in, but I noticed that several of these requests involve changing "Kibana" to "Elastic Kibana." I wondered what the background here was. Is this part of a move to reinforce the Elastic brand over the Kibana brand?

In case it's helpful, @beckyq and I recently drafted these guidelines to document our approach for naming products vs solutions vs features etc. Here, we say that core products (Elasticsearch, Kibana) aren't preceded by "Elastic," since that's reserved for solutions. These guidelines aren't set in stone, but I'd like to make sure that wide-ranging changes like this account for any downstream implications.

Adding "Elastic" before Kibana gives Kibana different treatment than Elasticsearch, Logstash, and Beats, for example, which is something we might want to consider. There's also the matter of where Kibana appears in copy on the website or in emails, such as "Hosted Elasticsearch and Kibana." Just want to make sure we account for all angles here :)

Would it be worthwhile to connect briefly on this (with @gchaps as well) to make sure that we're all on the same page?

[VijayDoshi]

@chandlergibb these changes are coming with the approval/visibility of Shay and Steve Kearns. It seems like we may want to re-look at the treatment of Kibana in the guideline referenced above. There is a decision document here that captures the considerations and decisions.

[snide]

We'll be fixing this in #58160