moving content around

Author: erikhatcher

docs/20_Intro_to_Atlas_Search/1_system.md

@@ -17,13 +17,3 @@ The Atlas Search process can be deployed either coupled alongside the database n
 
 ## Dedicated search nodes
 ![dedicated search nodes](/img/search_nodes.png)
-
-## Aggregation pipeline search stages
-
-### $search
-
-where the magic happens
-
-### $searchMeta
-
-The `$searchMeta` stage performs the same search that `$search` does, but only returns the results metadata, not actual matching documents. Results metadata includes the count of matching results and facets. This same metadata is available when using `$search` too, accessible in the $$SEARCH_META context variable.

docs/20_Intro_to_Atlas_Search/2_aggregation_stages.mdx

@@ -1,4 +1,4 @@
-# Aggregation pipeline search stages
+# 👐 Aggregation pipeline search stages
 
 ## $search
 

docs/30_Index_configuration/2_index_config.md

@@ -8,10 +8,6 @@ Documents are mapped to an index through a flexible configuration.
 
 ## Dynamic mapping
 
-## String-focused workshop
-
-Most data types are queried straightforwardly, and match as one would expect.  We'll survey non-string types in the next section, however we primarily focus on `string` fields, as that's where the power of Atlas Search shines.
-
 ## Configuring a real Atlas Search index
 
 * Atlas Search Visual Index Builder or JSON Editor

docs/30_Index_configuration/3_field_mapping.mdx

@@ -1,4 +1,4 @@
-# 👐 Field types
+# 👐 Basic field types
 
 Document fields are mapped to a search index based on their BSON data type.
 
@@ -9,30 +9,22 @@ mapped type.
 
 **TODO**: Turn each of these playgrounds into a challenge
 
-## Basic field types
-
-### boolean
+## boolean
   * `equals`: https://search-playground.mongodb.com/tools/code-playground/snapshots/669e6ab1d49ef6fad98118b4
   * `in`: ...
 
-### date
+## date
   * `equals`: ...
   * `in`: ...
   * `near`: ...
   * `range`: https://search-playground.mongodb.com/tools/code-playground/snapshots/669e6b18d49ef6fad98118b6
 
-### number
+## number
   * `equals`: 
   * `in`: ...
   * `near`: ...
   * `range`: https://search-playground.mongodb.com/tools/code-playground/snapshots/669e6b4ad49ef6fad98118b8
 
-### ObjectId
+## ObjectId
   * `equals`: https://search-playground.mongodb.com/tools/code-sandbox/snapshots/678506c2b6487c1cfd0bb540
   * `in`: 
-
-## Other field types
-
-* Geo-spatial
-* Nested documents
-* Strings

docs/30_Index_configuration/4_geo.mdx

@@ -1,4 +1,9 @@
-# 📘 Geo-spatial
+# 📘 Geo-spatial fields
+
+GeoJSON and Points
+
+* https://www.mongodb.com/docs/atlas/atlas-search/geoWithin/
+* https://www.mongodb.com/docs/atlas/atlas-search/geoShape/
 
 ### geo
 Dynamic mapping does not support geo-spatial fields, and require a manual/static mapping configuration.

docs/30_Index_configuration/5_nested_docs.mdx

@@ -0,0 +1,15 @@
+# 📘 Nested documents
+
+A document can contain a nested document, or an array of them.
+
+There are two distinct ways to map and index the contents of nested documents.
+
+## `document`
+
+Default dynamic mapping behavior, flattens nested documents into “arrays” of values on main document
+
+## `embeddedDocuments`
+
+Attribute pattern `elemMatch`-like matching, more nuanced and expensive than document type flattening
+
+WARNING: Each nested document mapped as as `embeddedDocuments` counts as an additional "index object".

docs/30_Index_configuration/6_string.mdx

@@ -1,5 +1,11 @@
 # 📘 String fields
 
+## String-focused workshop
+
+Most data types are queried straightforwardly, and match as one would expect.
+We'll survey non-string types in the next section, however we primarily focus on `string` fields,
+as that's where the power of Atlas Search shines.
+
 ### autocomplete
 blah, don’t do it! ;)
 See also: Relevant As-You-Type Suggestions Search Solution

docs/90_Summary.mdx

@@ -10,4 +10,4 @@ Do a demonstration of this tool, discussing it's sweet spot
 
 * Faceting
 * Highlighting
-* 
+* Pagination

docs/99_TODO.md

@@ -5,6 +5,8 @@
 * rename .md's to .mdx's
 * rename Playground section to something else - it's the workshop practicals
 * should completed/solved playgrounds be saved and linked in here as well?
+* Add coverage of "index objects" counting
+* Add transition verbiage at the end of each page/section to lead into the next one
 
 Cool Tricks
 Which clause matches?