From 664e1bf86e9373bb2a8f45b245f935756bc6a7e1 Mon Sep 17 00:00:00 2001
From: Fabian Affolter <mail@fabian-affolter.ch>
Date: Thu, 5 Oct 2017 09:11:26 +0200
Subject: [PATCH] Add some new entries (#3521)

---
 source/_faq/configuration-file.markdown | 13 +++++++++++++
 source/_faq/documentation-tool.markdown | 14 ++++++++++++++
 source/_faq/python.markdown             | 14 ++++++++++++++
 3 files changed, 41 insertions(+)
 create mode 100644 source/_faq/configuration-file.markdown
 create mode 100644 source/_faq/documentation-tool.markdown
 create mode 100644 source/_faq/python.markdown

diff --git a/source/_faq/configuration-file.markdown b/source/_faq/configuration-file.markdown
new file mode 100644
index 00000000000..8f06e8247f4
--- /dev/null
+++ b/source/_faq/configuration-file.markdown
@@ -0,0 +1,13 @@
+---
+layout: page
+title: "Why are you using YAML for the configuration file?"
+description: "Why are you using YAML for the configuration file?"
+date: 2017-06-18 09:00
+comments: false
+sharing: true
+footer: true
+ha_category: Configuration
+---
+
+
+And not JSON or XML for the [configuration file](/docs/configuration/)? Because [YAML](/docs/configuration/yaml/) can be written by hand, you don't have to care about commas or tag and it's a superset of JSON.
diff --git a/source/_faq/documentation-tool.markdown b/source/_faq/documentation-tool.markdown
new file mode 100644
index 00000000000..2f700707a2e
--- /dev/null
+++ b/source/_faq/documentation-tool.markdown
@@ -0,0 +1,14 @@
+---
+layout: page
+title: "Documentation tools"
+description: "Tools for creating the documentation"
+date: 2017-06-18 09:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+ha_category: Documentation
+---
+
+
+Why are you not using tools X for the documentation? Because the current solution works for us and we see no additional value in using a seperate publishing platform.
diff --git a/source/_faq/python.markdown b/source/_faq/python.markdown
new file mode 100644
index 00000000000..97cdacb34c7
--- /dev/null
+++ b/source/_faq/python.markdown
@@ -0,0 +1,14 @@
+---
+layout: page
+title: "Python 2"
+description: "Support for Python 2"
+date: 2017-06-18 09:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+ha_category: Common
+---
+
+
+There will be no support for Python 2.x. Python 2 will be EOL in [2020](https://www.python.org/dev/peps/pep-0373/#id2) and it doesn't make any sense to support a release which was planned to be retired in 2015.