diff --git a/.eslintignore b/.eslintignore
index 4dae1a36513ee..ceff2d9d22291 100644
--- a/.eslintignore
+++ b/.eslintignore
@@ -28,3 +28,4 @@ bower_components
/x-pack/plugins/**/__tests__/fixtures/**
**/*.js.snap
!/.eslintrc.js
+
diff --git a/package.json b/package.json
index 61b20ac8abe66..d3a9982c7b9d4 100644
--- a/package.json
+++ b/package.json
@@ -216,6 +216,7 @@
"whatwg-fetch": "^2.0.3",
"wreck": "12.4.0",
"x-pack": "link:x-pack",
+ "yarn": "^1.6.0",
"yauzl": "2.7.0"
},
"devDependencies": {
@@ -313,6 +314,7 @@
"pixelmatch": "4.0.2",
"prettier": "^1.12.1",
"proxyquire": "1.7.11",
+ "react-intl": "^2.4.0",
"simple-git": "1.37.0",
"sinon": "^5.0.7",
"source-map": "0.5.6",
diff --git a/packages/kbn-i18n/guideline.md b/packages/kbn-i18n/guideline.md
new file mode 100644
index 0000000000000..685afd5b7fd96
--- /dev/null
+++ b/packages/kbn-i18n/guideline.md
@@ -0,0 +1,233 @@
+# I18n Guideline
+
+## For Vendors
+
+#### Message types
+
+Each message id ends with a descriptive type.
+
+The following types are supported:
+- header
+- label
+- button
+- dropDown
+- placeholder
+- tooltip
+- aria
+- errorMessage
+- toggleSwitch
+
+There is one more complex case, when we have to divide a single expression into different labels. For example the message before translation likes like:
+
+ ```js
+
+ The following deprecated languages are in use: {deprecatedLangsInUse.join(', ')}. Support for these languages will be removed in the next major version of Kibana and Elasticsearch. Convert you scripted fields to
-
-
- You can use a
-
- *
-
- as a wildcard in your index pattern.
+
- You can't use spaces or the characters
-
- %
-
- .
+
- You can use a
-
- *
-
- as a wildcard in your index pattern.
+
- You can't use spaces or the characters
-
- %
-
- .
+
You can use a * as a wildcard in your index pattern.
-You can't use spaces or the characters {characterList}.
+
+
+
There's already an index pattern called `{query}`
+- The Time Filter will use this field to filter your data by time. -
-
- You can choose not to have a time field, but you will not be able to narrow down your data by a time range.
+
- The Time Filter will use this field to filter your data by time. -
-
- You can choose not to have a time field, but you will not be able to narrow down your data by a time range.
+
- The Time Filter will use this field to filter your data by time. -
-
- You can choose not to have a time field, but you will not be able to narrow down your data by a time range.
+
- The indices which match this index pattern don't contain any time fields.
+
The Time Filter will use this field to filter your data by time.
-You can choose not to have a time field, but you will not be able to narrow down your data by a time range.
+
+
The indices which match this index pattern don't contain any time fields.
+
+
- This page lists every field in the {{::indexPattern.title}} index and the field's associated core type as recorded by Elasticsearch. To change a field type, use the Elasticsearch + - Mapping API +
@@ -37,16 +42,16 @@ >