DOCSP-37133: Collections in Mixed data type

source/graphql/expose-data.txt

@@ -41,7 +41,7 @@ field, the field has a ``null`` value in the returned document.
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 GraphQL requires that all data conforms to a well-defined type, so you
-must :ref:`define a schema <enforce-a-schema>` for
+must :ref:`enforce-a-schema` for
 documents in the collection. App Services automatically generates
 :doc:`GraphQL types and resolvers
 </graphql/types-and-resolvers>` for documents in the collection

source/includes/note-collections-in-mixed-sync.rst

@@ -0,0 +1,24 @@
+.. note:: Collections in Mixed fields supported in Apps created after March XX, 2024
+
+    App Services Apps created *after* March XX, 2024 can store collections
+    (arrays and dictionaries) in mixed data properties. You can 
+    nest collections within other collections, which lets you store complex data
+    structures such as JSON or MongoDB documents without having to define a 
+    strict data model.
+
+    To use feature with Atlas Device SDK, you must use :ref:`Flutter SDK v2.0.0 or later <flutter-realm-value>`. Support for other SDKs will be added in future releases.
+
+    If your App was created before March XX, 2024, you can contact support to
+    learn more about enabling this feature.  
+
+.. TODO: Update this note with SDK versions once they release
+.. To use this feature with an Atlas Device SDK, you must use the following
+    SDK versions:
+.. - C++ SDK v1.0.0 or later
+.. - Flutter SDK v2.0.0 or later
+.. - Kotlin SDK v1.0.0 or later
+.. - .NET SDK v1.0.0 or later
+.. - Node.js SDK v1.0.0 or later
+.. - React Native SDK v1.0.0 or later
+.. - Swift SDK v1.0.0 or later
+.. - This feature is *not* supported in the Java SDK

source/schemas.txt

@@ -4,7 +4,12 @@
 Schemas
 =======
 
-.. default-domain:: mongodb
+.. meta:: 
+   :description: Learn about Atlas App Services Schemas.
+
+.. facet::
+  :name: genre
+  :values: reference
 
 .. contents:: On this page
    :local:
@@ -15,9 +20,9 @@ Schemas
 .. toctree::
    :titlesonly:
 
-   Enforce a Schema </schemas/enforce-a-schema>
+   Define & Enforce a Schema </schemas/enforce-a-schema>
    Remove a Schema </schemas/remove-a-schema>
-   Schema Types </schemas/types>
+   Schema Data Types </schemas/types>
 
 Overview
 --------

source/schemas/enforce-a-schema.txt

@@ -1,10 +1,21 @@
 .. _enforce-a-schema:
+.. _define-a-schema:
 
-================
-Enforce a Schema
-================
+=========================
+Define & Enforce a Schema
+=========================
 
-.. default-domain:: mongodb
+.. meta:: 
+   :keywords: code example
+   :description: Learn how to create and deploy an Atlas App Services Schema and define validation rules to enforce it.
+
+.. facet::
+  :name: genre
+  :values: reference
+
+.. facet::
+   :name: programming_language
+   :values: json
 
 .. contents:: On this page
    :local:
@@ -25,8 +36,16 @@ MongoDB Atlas collection.
 
 .. include:: /includes/adf-rules-note.rst
 
-Procedure
----------
+Define a Schema
+---------------
+
+You can define a schema for a collection in the App Services UI or with the
+App Services CLI. 
+
+When using the App Services UI, you can choose to: 
+
+- Generate a schema from existing data in the collection, and modify as needed.
+- Define a schema manually by adding field-level schema definitions.
 
 .. tabs-realm-admin-interfaces::
 
@@ -46,11 +65,11 @@ Procedure
             configuration screen.
 
 
-         .. step:: Generate a Schema
+         .. step:: Generate a Schema from Existing Data (Optional)
 
             If you already have data in your collection, App Services can
             sample a subset of the documents in the collection and generate a
-            schema for you based on the sample. This step is optional, so if you
+            schema for you based on the sample. If you
             already have a schema or prefer to define one manually, skip this
             step.
 
@@ -80,7 +99,9 @@ Procedure
                :alt: The Generate Schema sample size input in the App Services UI
 
 
-         .. step:: Add Field-Level Schema Definitions
+         .. step:: Define or Modify the Schema 
+
+            You can define a schema manually or modify an existing schema by adding field-level schema definitions. 
 
             You may define a single BSON schema for each collection. The root-level type
             of each collection schema is an ``object`` schema that represents a document
@@ -149,8 +170,7 @@ Procedure
                     }
                   }
 
-
-         .. step:: Add Change Validation Expressions
+         .. step:: Add Change Validation Expressions (Optional)
 
             In addition to configuring the content of each field, you can validate changes
             to documents by defining a validation :ref:`expression <expressions>` in the
@@ -308,7 +328,7 @@ Procedure
                }
 
 
-         .. step:: Define Change Validation
+         .. step:: Define Change Validation (Optional)
 
             You can validate changes to documents by defining a validation
             :ref:`expression <expressions>` in the ``validate`` field of a schema.