1 files changed, 24 insertions, 1 deletions
diff --git a/src/quick/doc/src/concepts/layouts/qtquicklayouts-overview.qdoc b/src/quick/doc/src/concepts/layouts/qtquicklayouts-overview.qdoc
index 05e4465f2a..06ebe2d3d1 100644
--- a/src/quick/doc/src/concepts/layouts/qtquicklayouts-overview.qdoc
+++ b/src/quick/doc/src/concepts/layouts/qtquicklayouts-overview.qdoc
@@ -74,8 +74,31 @@
     \endlist
 
 
+    \section1 A Simple Layout
+
+    \snippet qml/layout-simple.qml 1
+
+    As the intention of using a layout is to rearrange its children whenever the layout changes
+    size, the application should make sure that the layout gets resized. In the above snippet the
+    RowLayout ensures that by specifying \c{anchors.fill: parent}. However, it can also be by other
+    means, such as directly specifying \l{Item::width}{width} and \l{Item::height}{height}
+    properties. In the same snippet, the \c azure Rectangle has a fixed size of \c{(100, 150)}
+    pixels, and the \c plum Rectangle will expand to occupy all the space it gets allocated.
+
+    \note A layout is responsible for its children's geometry. You should
+    therefore not specify \l{Item::width}{width}, \l{Item::height}{height}, \l{Item::x}{x},
+    \l{Item::y}{y} or any other properties that might influence those properties (such as
+    \l{Item::anchors}{anchors}) on those items. Otherwise there would be a conflict of interest,
+    and the result is undefined. This is also the case if the child item is a layout. Therefore,
+    only layouts with no parent layout can have \c{anchors.fill: parent}.
+
+    All items in the layout will have 6 pixels of spacing between them:
+
+    \snippet qml/layout-simple.qml spacing
+
+
+    \section2 Size Constraints
 
-    \section1 Size Constraints
     Since an item can be resized by its layout, the layout needs to know the
     \l{Layout::minimumWidth}{minimum}, \l{Layout::preferredWidth}{preferred},
     and \l{Layout::maximumWidth}{maximum} sizes of all items where \l{Layout::fillWidth}{Layout.fillWidth} or