From e090f787c67c558159b3da29819f1a64d560b142 Mon Sep 17 00:00:00 2001 From: Court Ewing Date: Fri, 21 Jul 2017 21:46:27 -0400 Subject: [PATCH] Remove translations from management section We need to revisit how we embed translations into templates, so until we do we might as well go back to embedding text directly in the page. The translation implementation now makes it difficult to navigate throughout complicated HTML. It also suffers from an inability to flag on unused translation keys, which creates a good deal of technical debt. Close to half of all translation keys in the translation file in this initial pilot were already unused since it was introduced a couple of months ago. --- .../create_index_pattern.html | 49 +++++++++---------- .../create_index_pattern.js | 8 +-- .../pick_create_button_text.js | 10 ++-- .../edit_index_pattern.html | 2 +- .../management/sections/indices/index.html | 8 +-- src/core_plugins/kibana/translations/en.json | 44 +---------------- 6 files changed, 37 insertions(+), 84 deletions(-) diff --git a/src/core_plugins/kibana/public/management/sections/indices/create_index_pattern/create_index_pattern.html b/src/core_plugins/kibana/public/management/sections/indices/create_index_pattern/create_index_pattern.html index ad497a5f4dee8..b3a65d8db7992 100644 --- a/src/core_plugins/kibana/public/management/sections/indices/create_index_pattern/create_index_pattern.html +++ b/src/core_plugins/kibana/public/management/sections/indices/create_index_pattern/create_index_pattern.html @@ -5,15 +5,15 @@ data-test-subj="createIndexPatternContainer" class="kuiViewContent" > -

+

+ Configure an index pattern +

-

+

+ In order to use Kibana you must configure at least one index pattern. + Index patterns are used to identify the Elasticsearch index to run + search and analytics against. They are also used to configure fields. +

@@ -27,14 +27,15 @@
@@ -67,18 +68,16 @@
-

+

+ Patterns allow you to define dynamic index names using * as a wildcard. Example: logstash-* +

-