From f0774b3b408c181f5e782f5c5b0717c95ad54ddf Mon Sep 17 00:00:00 2001
From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
Date: Mon, 14 Aug 2023 12:47:13 +0200
Subject: [PATCH] Blueprints: rephrase intro topic (#28407)
---
source/_docs/blueprint.markdown | 32 ++++++++++++++------------------
1 file changed, 14 insertions(+), 18 deletions(-)
diff --git a/source/_docs/blueprint.markdown b/source/_docs/blueprint.markdown
index a6444c141d9..e5609824622 100644
--- a/source/_docs/blueprint.markdown
+++ b/source/_docs/blueprint.markdown
@@ -1,28 +1,24 @@
---
-title: "Creating blueprints"
-description: "Documentation on how to get started creating blueprints."
+title: "About blueprints"
+description: "Introduction to blueprints."
---
-
+This section gives a high-level introduction to blueprints. To view a description of the YAML-schema used to create a valid blueprint, refer to the section [About the blueprint schema](/docs/blueprint/schema/).
-If you're looking on how to use blueprints, see the [automation documentation](/docs/automation/using_blueprints/).
+## What is a blueprint?
-
+A blueprint is a script or automation configuration with certain parts marked as configurable. This allows you to create different scripts or automations based on the same blueprint.
-
+Imagine you want to control lights based on motion. A blueprint provides the generic automation framework, while letting you select one specific motion sensor as a trigger, and the exact light to control. This blueprint makes it possible to create two automations. Each automation has their own configuration and act completely independently. Yet, they share some basic automation configuration so that you do not have to set this up every time.
-While the tutorial only shows how to create an automation blueprint, scripts also support blueprints in the same way.
+Blueprints are shared by the community in the [blueprint community forum][blueprint-forums].
-
+### Related information
-A blueprint is a script or automation configuration with certain parts marked as configurable. This allows users to create multiple scripts or automations based on the same blueprint, with each having its own configuration.
+- [About the blueprint schema](/docs/blueprint/schema/)
+- [About the blueprint selectors](/docs/blueprint/selectors/)
+- [Using blueprints in automations](/docs/automation/using_blueprints/)
+- [Tutorial: Create an automation blueprint](/docs/blueprint/tutorial/)
+- [Blueprint community forum][blueprint-forums]
-Imagine a blueprint that controls a light based on motion, that allows you to configure the motion sensor to trigger on, and the light to control. It is now possible to create two automations that each have their own configuration for this blueprint and that act completely independent, yet are based on the same automation configuration.
-
-
-
-This is an advanced feature and requires knowledge of writing [automations](/docs/automation/yaml/) and [scripts](/docs/scripts/) in YAML.
-
-
-
-### [Tutorial: Create an automation blueprint »](/docs/blueprint/tutorial/)
+[blueprint-forums]: /get-blueprints
\ No newline at end of file