From ad68fc26b2ec0b05de3abf9a71622c3bd4a71819 Mon Sep 17 00:00:00 2001
From: Tina Luedtke <kickoke@users.noreply.github.com>
Date: Mon, 28 Mar 2022 23:12:10 +0100
Subject: Rename _concept-template.md to _concept-page-template.md

---
 .../.page-level/_concept-page-template.md          | 30 ++++++++++++++++++++++
 docs/.templates/.page-level/_concept-template.md   | 30 ----------------------
 2 files changed, 30 insertions(+), 30 deletions(-)
 create mode 100644 docs/.templates/.page-level/_concept-page-template.md
 delete mode 100644 docs/.templates/.page-level/_concept-template.md

diff --git a/docs/.templates/.page-level/_concept-page-template.md b/docs/.templates/.page-level/_concept-page-template.md
new file mode 100644
index 0000000000..685dd2ff36
--- /dev/null
+++ b/docs/.templates/.page-level/_concept-page-template.md
@@ -0,0 +1,30 @@
+<!--
+title: Noun that describes the concept
+description: Short summary (will be displayed in search engines)
+custom_edit_url: Edit URL of the source file
+keywords: [keywords, describing, the main topics]
+-->
+
+# Title
+
+Why should the reader care: “What’s in it for me?”
+
+## Subheading
+
+Ideally, try to explain one core idea per section. Questions that you could keep in mind while writing: 
+
+- How does it work?
+- What are the outcomes?
+- What are the positive and negative effects of it?
+- Are there alternatives that provide a similar result?
+
+## Subheading
+
+Add more subheadings and anything else that needs to be explained...
+Remember, if you start to describe about another concept, stop yourself.
+Each concept should be about one concept only.
+
+<!-- Optional -->
+### Related links
+<!-- Here, you could include links to task topic that describe how to implement the thing you discussed in this concept. -->
+- Visit the [related thing documentation](www.related-thing.com) to learn more about related thing. 
diff --git a/docs/.templates/.page-level/_concept-template.md b/docs/.templates/.page-level/_concept-template.md
deleted file mode 100644
index 0e38f0dad7..0000000000
--- a/docs/.templates/.page-level/_concept-template.md
+++ /dev/null
@@ -1,30 +0,0 @@
-<!--
-title: Noun that describes the concept
-description: Short summary (will be displayed in search engines)
-custom_edit_url: Edit URL of the source file
-keywords: [keywords, describing, the main topics]
--->
-
-# Title
-
-Why should the reader care: “What’s in it for me?”
-
-## Subheading
-
-Ideally, try to explain one core idea per section. Questions that you could keep in mind while writing: 
-
-- How does it work?
-- What are the outcomes?
-- What are the positive and negative effects of it?
-- Are there alternatives that provide a similar result?
-
-## Subheading
-
-Add more subheadings and anything else that needs to be explained...
-Remember, if you start to describe about another concept, stop yourself.
-Each concept should be about one concept only.
-
-<!-- Optional -->
-### Related links
-<!-- Here, you could include links to task topic that describe how to implement the thing you discussed in this concept. -->
-- Visit the [related thing documentation](www.related-thing.com) to learn more about related thing. 
\ No newline at end of file
-- 
cgit v1.2.3