Added icons to pages

dfreniche · dfreniche · commit 7b39440f38f4 · 2024-01-30T18:04:41.000+01:00
diff --git a/docs/1-mongodb-atlas/setup-lab.mdx b/docs/1-mongodb-atlas/setup-lab.mdx
@@ -2,10 +2,10 @@
 description: Setting up your MongoDB Atlas account, importing Library data 
 ---
 
-# Set up Lab
+# 👐 Set up Lab
 
 To follow along you'll need:
 - a MongoDB Atlas account
 - test data. In this case, this is books, authors and reviews data for a library management system.
 
-💻 To get both, open the [Intro Lab](https://mongodb-developer.github.io/intro-lab/docs/intro) and follow it (only takes 10-15 mins) to get your database ready. Return here when finished!
+👐 To get both, open the [Intro Lab](https://mongodb-developer.github.io/intro-lab/docs/intro) and follow it (only takes 10-15 mins) to get your database ready. Return here when finished!
diff --git a/docs/20-what-is-aggregation/1-what-is-aggregation.mdx b/docs/20-what-is-aggregation/1-what-is-aggregation.mdx
@@ -2,7 +2,7 @@
 description: Learn what is an Aggregation Pipeline 
 ---
 
-# What is an Aggregation Pipeline
+# 📘 What is an Aggregation Pipeline
 
 ![](/img/20-what-is-aggregation/aggregation-pipeline.png)
 
diff --git a/docs/20-what-is-aggregation/2-sql-vs-aggregation.mdx b/docs/20-what-is-aggregation/2-sql-vs-aggregation.mdx
@@ -2,7 +2,7 @@
 description: Let's compare SQL with an Aggregation Pipeline 
 ---
 
-# SQL vs Aggregations
+# 📘 SQL vs Aggregations
 
 ## SQL
 
diff --git a/docs/20-what-is-aggregation/3-structure-aggregation.mdx b/docs/20-what-is-aggregation/3-structure-aggregation.mdx
@@ -2,7 +2,7 @@
 description: See the parts that compose an Aggregation Pipeline 
 ---
 
-# Structure of an aggregation pipeline
+# 📘 Structure of an aggregation pipeline
 
 To interact with a relational database we typically use SQL, a 4th Generation language to access our data. With MongoDB we instead get data and transform it in incremental steps.
 
diff --git a/docs/30-simple-queries/0-using-library-database.mdx b/docs/30-simple-queries/0-using-library-database.mdx
@@ -1,7 +1,7 @@
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-# Using the library database
+# 👐 Using the library database
 
 ## Select the library database
 
diff --git a/docs/30-simple-queries/1-empty-aggregation.mdx b/docs/30-simple-queries/1-empty-aggregation.mdx
@@ -1,7 +1,7 @@
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-# Empty aggregation pipeline
+# 👐 Empty aggregation pipeline
 
 ## An empty aggregation
 
@@ -31,7 +31,7 @@ db.authors.aggregate([])
 
 We can iterate over the returned cursor and get more documents typing `it`. 
 
-💻 Return all the documents in the `books` collection and iterate to get the next page of books.
+👐 Return all the documents in the `books` collection and iterate to get the next page of books.
 
 <details>
 <summary>Answer</summary>
@@ -56,7 +56,7 @@ A [cursor](https://www.mongodb.com/docs/manual/reference/method/js-cursor/) has
 cursor.itcount()
 ```
 
-💻 In our previous example with the empty aggregation, to check the size of the returned cursor, what should we type in?
+👐 In our previous example with the empty aggregation, to check the size of the returned cursor, what should we type in?
 
 <details>
 <summary>Answer</summary>
diff --git a/docs/30-simple-queries/2-match.mdx b/docs/30-simple-queries/2-match.mdx
@@ -1,7 +1,7 @@
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-# $match
+# 👐 $match
 
 The $match operator is used in conjunction with the aggregation framework to filter documents in a collection. It takes a document as input and returns a new document containing only the documents that match the specified criteria. The syntax for the $match operator is as follows:
 
@@ -52,7 +52,7 @@ The `<expression>` portion of the $match operator can be any valid MongoDB expre
 </Tabs>
 
 
-💻 Return all the `books` that have exactly 100 pages.
+👐 Return all the `books` that have exactly 100 pages.
 
 <details>
 <summary>Answer</summary>
@@ -119,7 +119,7 @@ IF pages == 100 AND totalInventory == 2 {
 }
 ```
 
-💻 Return all the `books` from 2015 that have exactly 100 pages.
+👐 Return all the `books` from 2015 that have exactly 100 pages.
 
 <details>
 <summary>Answer</summary>
@@ -150,7 +150,7 @@ db.books.aggregate([{$match: {$and: [{pages: 100}, {year: 2015}]}}])
 </div>
 </details>
 
-💻 How many are they?
+👐 How many are they?
 
 <details>
 <summary>Answer</summary>
@@ -205,7 +205,7 @@ db.books.aggregate([{$match: {pages: 100, totalInventory: 2}}])
 </Tabs>
 
 
-💻 Return all the `books` from 2015 that have exactly 100 pages, using the simple $and notation
+👐 Return all the `books` from 2015 that have exactly 100 pages, using the simple $and notation
 
 <details>
 <summary>Answer</summary>
diff --git a/docs/30-simple-queries/3-project.mdx b/docs/30-simple-queries/3-project.mdx
@@ -1,7 +1,7 @@
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-# $project
+# 👐 $project
 
 ## Including fields in a projection 
 
@@ -105,7 +105,7 @@ db.books.aggregate([{$project: {attributes: 0}}])
 </Tabs>
 
 
-💻 Show only `title` and `cover`.
+👐 Show only `title` and `cover`.
 
 <details>
 <summary>Answer</summary>
@@ -132,7 +132,7 @@ db.books.aggregate([{$project: {title: 1, cover: 1}}])
 
 ## Excluding fields
 
-💻 Exclude the `cover`, `attributes` and `_id` fields from the result.
+👐 Exclude the `cover`, `attributes` and `_id` fields from the result.
 
 <details>
 <summary>Answer</summary>
diff --git a/docs/30-simple-queries/4-limiting-results.mdx b/docs/30-simple-queries/4-limiting-results.mdx
@@ -1,7 +1,7 @@
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-# $limit
+# 👐 $limit
 
 If we return too many documents, but we're interested just in a few, we can limit the number of documents returned using `$limit`
 
@@ -22,7 +22,7 @@ db.books.aggregate([{$limit: 1}])
 
 This returns just one document.
 
-💻 Return just 7 `books`.
+👐 Return just 7 `books`.
 
 <details>
 <summary>Answer</summary>
diff --git a/docs/30-simple-queries/5-combining-them-all.mdx b/docs/30-simple-queries/5-combining-them-all.mdx
@@ -1,7 +1,7 @@
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-# Combining stages
+# 👐 Combining stages
 
 Up until now, we've just been using one stage in the pipeline. But the power of the aggregation pipeline is that we can use many stages, and the output of one will be the input of the next. Think of it as UNIX pipes or using functional programming with `map`, `filter`, `reduce`, `flatmap`, etc.
 
@@ -33,7 +33,7 @@ db.books.aggregate([
 </Tabs>
 
 
-💻 Get 15 books from 1985 with 150 pages. Show only the `title`, `year`, `totalInventory` and `available` books. If you don't remember which fields we have, you can refer to [the sample document](/docs/simple-queries/project).
+👐 Get 15 books from 1985 with 150 pages. Show only the `title`, `year`, `totalInventory` and `available` books. If you don't remember which fields we have, you can refer to [the sample document](/docs/simple-queries/project).
 
 <details>
 <summary>Answer</summary>
diff --git a/docs/30-simple-queries/6-writing-long-pipelines.mdx b/docs/30-simple-queries/6-writing-long-pipelines.mdx
@@ -1,4 +1,4 @@
-# Writing long pipelines
+# 👐 Writing long pipelines
 
 Aggregation pipelines can get very long, depending on how many stages we need to run. Writing a pipeline is writing code, as you will write it using one of the many MongoDB drivers in your own language. Here we're presenting the examples using JavaScript suitable for the MongoDB Shell [mongosh](https://www.mongodb.com/docs/mongodb-shell/), but if you are writing a microservice in Rust, you'll definitely write your pipelines in Rust.
 
@@ -32,7 +32,7 @@ db.books.aggregate([
 
 Easier to read, and reason about, right?
 
-💻 Try to run the above pipeline and compare your results: should be the same as before
+👐 Try to run the above pipeline and compare your results: should be the same as before
 
 :::tip
 
@@ -47,7 +47,7 @@ As this is code, we can even add comments (starting with `//`) to our pipelines
 :::
 
 
-💻 We can also use $gte to get the books with 150 pages or more. Check $gte syntax in the [docucumentation](https://www.mongodb.com/docs/manual/reference/operator/query/gte/) and write an aggregation pipeline to return 15 books from 1985 with more than 150 pages. Show only the `title`, `year`, `totalInventory` and `available` books. (Sample doc [here](/docs/simple-queries/project))
+👐 We can also use $gte to get the books with 150 pages or more. Check $gte syntax in the [docucumentation](https://www.mongodb.com/docs/manual/reference/operator/query/gte/) and write an aggregation pipeline to return 15 books from 1985 with more than 150 pages. Show only the `title`, `year`, `totalInventory` and `available` books. (Sample doc [here](/docs/simple-queries/project))
 
 _Hint:_ we'll need to use `$and` as maybe this is a bit more complex.
 
diff --git a/docs/40-using-arrays/1-simple-match-array.mdx b/docs/40-using-arrays/1-simple-match-array.mdx
@@ -1,4 +1,4 @@
-# Simple Array queries
+# 👐 Simple Array queries
 
 ## Find data in arrays
 
@@ -9,7 +9,7 @@ A JSON Array can contain scalar values or objects. In our data, `authors` have a
 db.authors.aggregate([{$limit: 1}])
 ```
 
-💻 Run this aggregation to get one author
+👐 Run this aggregation to get one author
 
 I got this one (can change depending on the data source you imported)
 
@@ -35,7 +35,7 @@ db.authors.aggregate([
 ])
 ```
 
-💻 Get book's author name for ISBN `0395623650`:
+👐 Get book's author name for ISBN `0395623650`:
 
 <details>
 <summary>Answer</summary>
@@ -63,7 +63,7 @@ db.authors.aggregate([
 ])
 ```
 
-💻 Who wrote the most books? (we can sort using `{ $sort: {"bookCount": -1}}`)
+👐 Who wrote the most books? (we can sort using `{ $sort: {"bookCount": -1}}`)
 
 <details>
 <summary>Answer</summary>
diff --git a/docs/40-using-arrays/2-search-inside-objects-in-arrays.mdx b/docs/40-using-arrays/2-search-inside-objects-in-arrays.mdx
@@ -1,4 +1,4 @@
-# Searching inside Objects in arrays
+# 👐 Searching inside Objects in arrays
 
 In our books we're using the [Attribute Pattern](https://www.mongodb.com/developer/products/mongodb/attribute-pattern/) to have different attributes in our documents. As we can see in the [sample doc](/docs/simple-queries/project) we have an `attributes` array, containing several objects, each with the same structure:
 
@@ -55,7 +55,7 @@ db.books.aggregate([
 
 Here we're getting a copy of each book for each object inside the `$attributes` array. This "flattens" the array and returns many copies of the same documents, one for each different attribute that we have which will be different for each of these generated docs.
 
-To better understand `$unwind`, run this aggregation
+👐 To better understand `$unwind`, run this aggregation
 
 ```js
 db.books.aggregate([
diff --git a/docs/50-counting-sorting/1-counting-documents.mdx b/docs/50-counting-sorting/1-counting-documents.mdx
@@ -1,4 +1,4 @@
-# $count
+# 👐 $count
 
 How can we be sure that this pipeline is returning exactly 2 books?
 
@@ -41,7 +41,7 @@ Here, `$count` will count the resulting docs and will return a document with jus
 ```
 
 
-💻 How many authors do we have in our `authors` collection?
+👐 How many authors do we have in our `authors` collection?
 
 <details>
 <summary>Answer</summary>
diff --git a/docs/50-counting-sorting/10-sorting.mdx b/docs/50-counting-sorting/10-sorting.mdx
@@ -1,8 +1,8 @@
-# Sorting
+# 👐 Sorting
 
 We can sort our results using the `$sort` stage. We need to sort on a field, being 1 ascending and -1 descending order.
 
-💻 Let's get all books from 1984, sorted by number of pages. We'll only show the title, pages and authors.
+👐 Let's get all books from 1984, sorted by number of pages. We'll only show the title, pages and authors.
 
 ```js
 let booksFrom1984 = {$match: {year: 1984}};
@@ -18,7 +18,7 @@ db.books.aggregate([
 
 As we can see, books with no `pages` info appear first. These documents don't have that information, hence `pages` is `null` and gets sorted as less than any number. 
 
-💻 We can sort the other way around:
+👐 We can sort the other way around:
 
 ```js
 let booksFrom1984 = {$match: {year: 1984}};
@@ -32,7 +32,7 @@ db.books.aggregate([
 ]);
 ```
 
-💻 How can we get the thickest book from 1984?
+👐 How can we get the thickest book from 1984?
 
 <details>
 <summary>Answer</summary>
diff --git a/docs/60-lookups/1-lookups.mdx b/docs/60-lookups/1-lookups.mdx
@@ -1,12 +1,12 @@
-# Lookupups AKA Left Outer Join
+# 👐 Lookupups AKA Left Outer Join
 
 Using Documents we usually model 1:1, 1:many relationships embedding documents inside other documents, even using arrays for that. For instance an Author can have many aliases, and they live inside an array in the `authors` collection.
 
 But other times we need to use references to those documents instead of embedding them. For instance an author has an array of the books she has written, but instead of moving the book documents inside an array inside author (which will be tricky for books with multiple authors) we embed the books `_id` instead.
 
 So how can we get the authors and all the books she has written, embedded in the array? Using `$lookup`, that will do a Left Outer Join and return author docs containing book docs inside. 
 
-💻 Run this aggregation and look at the results:
+👐 Run this aggregation and look at the results:
 
 ```js
 db.authors.aggregate([
diff --git a/docs/70-grouping/group.mdx b/docs/70-grouping/group.mdx
@@ -1,4 +1,4 @@
-# Group
+# 👐 Group
 
 We can sum all the pages for all books in each year:
 
@@ -13,7 +13,7 @@ db.books.aggregate([
 
 Here, we group by book's `year` (the _id of the grouping), and then we create a new field called `totalPages` that's the sum of all pages.
 
-💻 Can you get the results ordered ascending by year?
+👐 Can you get the results ordered ascending by year?
 
 <details>
 <summary>Answer</summary>
@@ -31,7 +31,7 @@ db.books.aggregate([
 </div>
 </details>
 
-💻 Can you get the average pages per year (hint: use `$avg`)?
+👐 Can you get the average pages per year (hint: use `$avg`)?
 
 <details>
 <summary>Answer</summary>
@@ -49,7 +49,7 @@ db.books.aggregate([
 </div>
 </details>
 
-💻 Which year had the most printed out pages?
+👐 Which year had the most printed out pages?
 
 <details>
 <summary>Answer</summary>
diff --git a/docs/80-modifying-results/adding-fields.mdx b/docs/80-modifying-results/adding-fields.mdx
@@ -1,4 +1,4 @@
-# Adding new fields to results
+# 👐 Adding new fields to results
 
 ## $addFields
 
@@ -15,7 +15,7 @@ db.books.aggregate([
 ])
 ```
 
-💻 Add a new field `notes` that contains the text `PLACEHOLDER` for all documents.
+👐 Add a new field `notes` that contains the text `PLACEHOLDER` for all documents.
 
 <details>
 <summary>Answer</summary>
diff --git a/docs/80-modifying-results/missing-data.mdx b/docs/80-modifying-results/missing-data.mdx
@@ -1,4 +1,4 @@
-# Missing Data
+# 🦸 Missing Data
 
 Sometimes we're missing a field we're looking for (it's not there, as documents in a collection can be polymorphic, so this field is `null`). For these cases we can check if something is there using `$ifNull` and add a default value in that case.
 
diff --git a/docs/90-exporting-data/saving-to-collection.mdx b/docs/90-exporting-data/saving-to-collection.mdx
@@ -1,4 +1,4 @@
-# Saving to a collection
+# 🦸 Saving to a collection
 
 You can export the result of an aggregation pipeline to a different DB / Collection. To do that just add a last aggregation stage to your pipeline:
 
@@ -12,7 +12,7 @@ You can omit the `db` attribute, in which case the new collection is created in
 { $out: "<output-collection>" }
 ```
 
-💻 Create a copy of the books with exactly 100 pages and output as a new collection named `OneHundredPagesBooks.
+👐 Create a copy of the books with exactly 100 pages and output as a new collection named `OneHundredPagesBooks.
 
 <details>
 <summary>Answer</summary>
diff --git a/docs/intro.mdx b/docs/intro.mdx
@@ -24,6 +24,6 @@ In the navigation bar and in some pages, you will notice some icons. Here is the
 |Icon|Meaning|
 |-|:-|
 |📘|Lecture material - If you're following along in an instructor lead session, they probably have covered this already.|
-|💻|Hands-on content - Get ready to get some work done. You should follow these steps.|
+|👐|Hands-on content - Get ready to get some work done. You should follow these steps.|
 |💬|Discussion - Item to discuss during the Lab|
 |🦸|Advanced content - This content isn't covered during the lab, but if you're interested in learning more, you can check it out.|
