ordering sections

Author: erikhatcher

docs/20_Intro_to_Atlas_Search/2_aggregation_stages.mdx

@@ -0,0 +1,11 @@
+# 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.
+
+**TODO**: Add exercise using $search and have developer switch to $searchMeta to see the results

docs/30_Index_configuration/2_index_config.md

@@ -14,6 +14,7 @@ Most data types are queried straightforwardly, and match as one would expect.  W
 
 ## Configuring a real Atlas Search index
 
-* Visual Index Builder
+* Atlas Search Visual Index Builder or JSON Editor
 * via Compass
 * Atlas CLI
+* Driver commands

docs/30_Index_configuration/3_field_mapping.mdx

@@ -31,50 +31,8 @@ mapped type.
   * `equals`: https://search-playground.mongodb.com/tools/code-sandbox/snapshots/678506c2b6487c1cfd0bb540
   * `in`: 
 
-### geo
-Dynamic mapping does not support geo-spatial fields, and require a manual/static mapping configuration.
-
-  * `geoWithin`: https://search-playground.mongodb.com/tools/code-playground/snapshots/669e6b762ce7658e786edbfa
-  * `geoShape`: 
-  * `near`: 
-
 ## Other field types
 
-### autocomplete
-blah, don’t do it! ;)
-See also: Relevant As-You-Type Suggestions Search Solution
-
-### document
-
-Default dynamic mapping behavior, flattens nested documents into “arrays” of values on main document
-
-### embeddedDocument
-Attribute pattern k/v matching, more nuanced than document type flattening
-See cool tricks for embedded documents
-
-## string
-Basic examples
-lucene.standard matching case-insensitive: https://search-playground.mongodb.com/tools/code-playground/snapshots/664738af4e0a3f240a5de9d9
-
-## Analysis matters
-“searches” query does not match “Search” with lucene.standard: https://search-playground.mongodb.com/tools/code-playground/snapshots/664739964e0a3f240a5de9db
-“searches” matches “Search” using lucene.english: https://search-playground.mongodb.com/tools/code-playground/snapshots/66473aa64e0a3f240a5de9dd
-
-## Custom analyzers
-Last 4 digit of phone number matching (regex extraction during indexing, keyword analysis at query time): https://search-playground.corp.mongodb.com/tools/code-playground/snapshots/669e6c98d49ef6fad98118ba
-Example of being able to do ‘startsWith’ and ‘endsWith’ using wildcard and ‘reverse’ token filter:
-https://search-playground.mongodb.com/tools/code-playground/snapshots/6683c8bc4a45448733549bbc
-
-Example of being able to do ‘startsWith’, ‘endsWith’ and ‘contains’ using nGrams: https://search-playground.mongodb.com/tools/code-playground/snapshots/6683c999934a05d9b585b6e7 
-Relevancy
-Example of an as-you-type suggest configuration; sophisticated use of multi and several weighted query clauses: https://search-playground.mongodb.com/tools/code-playground/snapshots/66473b744e0a3f240a5de9e1
-$project score?
-$project scoreDetails?
-
-# multi
-Why?
-Relevancy example: boost each multi uniquely
-Multiple language example: may not know the language of the content and each document could be different - multi across all possible languages, query across them as desired at query-time, let relevancy sort it out
-Example of being able to do ‘startsWith’ and ‘endsWith’ using wildcard and ‘reverse’ token filter:
-https://search-playground.mongodb.com/tools/code-playground/snapshots/6683c8bc4a45448733549bbc
-
+* Geo-spatial
+* Nested documents
+* Strings

docs/30_Index_configuration/4_geo.mdx

@@ -0,0 +1,8 @@
+# 📘 Geo-spatial
+
+### geo
+Dynamic mapping does not support geo-spatial fields, and require a manual/static mapping configuration.
+
+  * `geoWithin`: https://search-playground.mongodb.com/tools/code-playground/snapshots/669e6b762ce7658e786edbfa
+  * `geoShape`: 
+  * `near`: 

docs/30_Index_configuration/4_string.mdx

@@ -0,0 +1,32 @@
+# 📘 String fields
+
+### autocomplete
+blah, don’t do it! ;)
+See also: Relevant As-You-Type Suggestions Search Solution
+
+## string
+Basic examples
+lucene.standard matching case-insensitive: https://search-playground.mongodb.com/tools/code-playground/snapshots/664738af4e0a3f240a5de9d9
+
+## Analysis matters
+“searches” query does not match “Search” with lucene.standard: https://search-playground.mongodb.com/tools/code-playground/snapshots/664739964e0a3f240a5de9db
+“searches” matches “Search” using lucene.english: https://search-playground.mongodb.com/tools/code-playground/snapshots/66473aa64e0a3f240a5de9dd
+
+## Custom analyzers
+Last 4 digit of phone number matching (regex extraction during indexing, keyword analysis at query time): https://search-playground.corp.mongodb.com/tools/code-playground/snapshots/669e6c98d49ef6fad98118ba
+Example of being able to do ‘startsWith’ and ‘endsWith’ using wildcard and ‘reverse’ token filter:
+https://search-playground.mongodb.com/tools/code-playground/snapshots/6683c8bc4a45448733549bbc
+
+Example of being able to do ‘startsWith’, ‘endsWith’ and ‘contains’ using nGrams: https://search-playground.mongodb.com/tools/code-playground/snapshots/6683c999934a05d9b585b6e7 
+Relevancy
+Example of an as-you-type suggest configuration; sophisticated use of multi and several weighted query clauses: https://search-playground.mongodb.com/tools/code-playground/snapshots/66473b744e0a3f240a5de9e1
+$project score?
+$project scoreDetails?
+
+# multi
+Why?
+Relevancy example: boost each multi uniquely
+Multiple language example: may not know the language of the content and each document could be different - multi across all possible languages, query across them as desired at query-time, let relevancy sort it out
+Example of being able to do ‘startsWith’ and ‘endsWith’ using wildcard and ‘reverse’ token filter:
+https://search-playground.mongodb.com/tools/code-playground/snapshots/6683c8bc4a45448733549bbc
+