From 1a392772698ffccf5a4f1570af78028cca2e0688 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <srifenbark@gmail.com>
Date: Wed, 25 Apr 2018 08:06:27 -0700
Subject: overview-manual: Bolstered the "Layers" section in the concepts
 chapter.

This section was really sparse for being in the concepts chapter of
this manual.  I added some more text to it.

(From yocto-docs rev: 9369ba5292126957f89f8b96e06bc2492825c54b)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 .../overview-manual/overview-manual-concepts.xml   | 45 +++++++++++++++-------
 1 file changed, 31 insertions(+), 14 deletions(-)

(limited to 'documentation/overview-manual/overview-manual-concepts.xml')

diff --git a/documentation/overview-manual/overview-manual-concepts.xml b/documentation/overview-manual/overview-manual-concepts.xml
index 66457d8b5b..8f32dc62b1 100644
--- a/documentation/overview-manual/overview-manual-concepts.xml
+++ b/documentation/overview-manual/overview-manual-concepts.xml
@@ -198,27 +198,44 @@
         </section>
     </section>
 
-    <section id='cm-layers'>
+    <section id='overview-layers'>
         <title>Layers</title>
 
         <para>
-            Layers are repositories that contain related sets of instructions
-            that tell the OpenEmbedded build system what to do.
-            You use different layers to logically separate information in your
-            build.
-            You can collaborate, share, and reuse layers.
-            The Layer Model simultaneously supports collaboration and
-            customization.
+            Layers are repositories that contain related metadata (i.e.
+            sets of instructions) that tell the OpenEmbedded build system how
+            to build a target.
+            Yocto Project's
+            <link linkend='the-yocto-project-layer-model'>layer model</link>
+            facilitates collaboration, sharing, customization, and reuse
+            within the Yocto Project development environment.
+            Layers logically separate information for your project.
+            For example, you can use a layer to hold all the configurations
+            for a particular piece of hardware.
+            Isolating hardware-specific configurations allows you to share
+            other metadata by using a different layer where that metadata
+            might be common across several pieces of hardware.
         </para>
 
         <para>
-            For more introductory information on the Yocto Project's layer
-            model, see the
-            "<link linkend='the-yocto-project-layer-model'>The Yocto Project Layer Model</link>"
-            section.
-            For procedures on how to create layers, see the
+            Many layers exist that work in the Yocto Project development
+            environment.
+            The
+            <ulink url='https://caffelli-staging.yoctoproject.org/software-overview/layers/'>Yocto Project Curated Layer Index</ulink>
+            and
+            <ulink url='http://layers.openembedded.org/layerindex/branch/master/layers/'>OpenEmbedded Layer Index</ulink>
+            both contain layers from which you can use or leverage.
+        </para>
+
+        <para>
+            By convention, layers in the Yocto Project follow a specific form.
+            Conforming to a known structure allows BitBake to make assumptions
+            during builds on where to find types of metadata.
+            You can find procedures and learn about tools (i.e.
+            <filename>bitbake-layers</filename>) for creating layers suitable
+            for the Yocto Project in the
             "<ulink url='&YOCTO_DOCS_DEV_URL;#understanding-and-creating-layers'>Understanding and Creating Layers</ulink>"
-            section in the Yocto Project Development Tasks Manual.
+            section of the Yocto Project Development Tasks Manual.
         </para>
     </section>
 
-- 
cgit v1.2.3-54-g00ecf