academy: create tutorials group

Author: mstephen19

content/academy/concepts.md

@@ -7,7 +7,7 @@ paths:
     - concepts
 ---
 
-# [](#concepts) Concepts
+# [](#concepts) Concepts 🤔
 
 There are some terms and concepts you'll see frequently repeated throughout various courses in the academy. Many of these concepts are common, and even fundamental in the scraping world, which makes it necessary to explain them to our course-takers; however it would be inconvenient for our readers to explain these terms each time they appear in a lesson.
 

content/academy/expert_scraping_with_apify.md

@@ -33,19 +33,21 @@ Throughout the next lessons, we will sometimes use certain technologies and term
 - [HTTP protocol](https://developer.mozilla.org/en-US/docs/Web/HTTP)
 - [DevTools]({{@link web_scraping_for_beginners/data_collection/browser_devtools.md}})
 
-### [](#crawlee-apify-sdk-and-cli) Crawlee, Apify SDK, and the Apify CLI
-
-If you're feeling ambitious, you don't need to have any prior experience with Crawlee to get started with this course; however, at least 5-10 minutes of exposure is recommended. If you haven't yet tried out Crawlee, you can refer to [this lesson]({{@link web_scraping_for_beginners/crawling/pro_scraping.md}}) in the **Web scraping for beginners** course (and ideally follow along). To familiarize with the Apify SDK,you can refer to the [Apify Platform]({{@link apify_platform.md}}) course.
+### [](#jquery-or-cheerio) jQuery or Cheerio
 
-The Apify CLI will play a core role in the running and testing of the actor you will build, so if you haven't gotten it installed already, please refer to [this short lesson]({{@link tools/apify_cli.md}}).
+We'll be using the [`cheerio`](https://www.npmjs.com/package/cheerio) package a whole lot to parse data from HTML. This package provides a simple API using jQuery syntax to help traverse downloaded HTML within Node.js.
 
 ### [](#puppeteer-playwright) Puppeteer/Playwright
 
 [Puppeteer](https://pptr.dev/) is a library for running and controlling a [headless browser]({{@link web_scraping_for_beginners/crawling/headless_browser.md}}) in Node.js, and was developed at Google. The team working on it was hired by Microsoft to work on the [Playwright](https://playwright.dev/) project; therefore, many parallels can be seen between both the `puppeteer` and `playwright` packages. Proficiency in at least one of these will be good enough.
 
-### [](#jquery-or-cheerio) jQuery or Cheerio
+### [](#crawlee-apify-sdk-and-cli) Crawlee, Apify SDK, and the Apify CLI
 
-We'll be using the [`cheerio`](https://www.npmjs.com/package/cheerio) package a whole lot to parse data from HTML. This package provides a simple API using jQuery syntax to help traverse downloaded HTML within Node.js.
+If you're feeling ambitious, you don't need to have any prior experience with Crawlee to get started with this course; however, at least 5-10 minutes of exposure is recommended. If you haven't yet tried out Crawlee, you can refer to [this lesson]({{@link web_scraping_for_beginners/crawling/pro_scraping.md}}) in the **Web scraping for beginners** course (and ideally follow along). To familiarize with the Apify SDK,you can refer to the [Apify Platform]({{@link apify_platform.md}}) course.
+
+The Apify CLI will play a core role in the running and testing of the actor you will build, so if you haven't gotten it installed already, please refer to [this short lesson]({{@link tools/apify_cli.md}}).
+
+<!-- todo: remove all requirements up to this point -->
 
 ### [](#git) Git
 
@@ -57,7 +59,7 @@ Docker is a massive topic on its own, but don't be worried! We only expect you t
 
 ### [](#actor-basics) The basics of actors
 
-Part of this course will be learning more in-depth about actors; however, some basic knowledge is already assumed. If you haven't yet read the [actors]({{@link apify_platform/getting_started/actors.md}}) lesson of the **Apify platform** course, it's highly recommended to give it a glance before moving forward.
+Part of this course will be learning more in-depth about actors; however, some basic knowledge is already assumed. If you haven't yet gone through the [actors]({{@link apify_platform/getting_started/actors.md}}) lesson of the **Apify platform** course, it's highly recommended to at least give it a glance before moving forward.
 
 ## [](#next) Next up
 

content/academy/tools.md

@@ -7,7 +7,7 @@ paths:
     - tools
 ---
 
-# [](#tools) Tools
+# [](#tools) Tools 🔧
 
 Here at Apify, we've found many tools, some quite popular and well-known and some niche, which can aid any developer in their scraper development process. We've compiled some of our favorite developer tools into to this short section. Each tool featured here serves a specific purpose, if not multiple purposes, which are directly relevant to web-scraping and web-automation.
 

content/academy/tutorials.md

@@ -0,0 +1,12 @@
+---
+title: Tutorials
+description: Learn 
+menuWeight: 11
+category: glossary
+paths:
+    - tutorials
+---
+
+# Tutorials 📚
+
+<!-- blah blah this section has tutorials -->

content/academy/web_scraping_for_beginners/crawling/dealing_with_dynamic_pages.md renamed to content/academy/tutorials/dealing_with_dynamic_pages.md

@@ -1,24 +1,24 @@
 ---
 title: Dealing with dynamic pages
 description: Learn about dynamic pages and dynamic content. How can we find out if a page is dynamic? How do we programmatically scrape dynamic content?
-menuWeight: 10
+menuWeight: 1
 paths:
-- web-scraping-for-beginners/crawling/dealing-with-dynamic-pages
+- tutorials/dealing-with-dynamic-pages
 ---
 
 # [](#dealing-with-dynamic-pages) Dealing with dynamic pages
 
-In the last few lessons, we learned about Crawlee, which is a powerful library for writing reliable and efficient scrapers. We recommend reading up on those last two lessons in order to install the `crawlee` package and familiarize yourself with it before moving forward with this lesson.
+<!-- In the last few lessons, we learned about Crawlee, which is a powerful library for writing reliable and efficient scrapers. We recommend reading up on those last two lessons in order to install the `crawlee` package and familiarize yourself with it before moving forward with this lesson. -->
 
 In this lesson, we'll be discussing dynamic content and how to scrape it while utilizing Crawlee.
 
 ## [](#quick-experiment) A quick experiment
 
 From our adored and beloved [Fakestore](https://demo-webstore.apify.org/), we have been tasked to scrape each product's title, price, and image from the [new arrivals](https://demo-webstore.apify.org/search/new-arrivals) page. Easy enough! We did something very similar in the previous modules.
 
-![New arrival products in Fakestore]({{@asset web_scraping_for_beginners/crawling/images/new-arrivals.webp}})
+![New arrival products in Fakestore]({{@asset tutorials/images/new-arrivals.webp}})
 
-In your project from the previous lessons, or in a new project, create a file called **dynamic.js** and copy-paste the following boiler plate code into it:
+First, create a file called **dynamic.js** and copy-paste the following boiler plate code into it:
 
 ```JavaScript
 import { CheerioCrawler } from 'crawlee';
@@ -71,16 +71,14 @@ const crawler = new CheerioCrawler({
     },
 });
 
-await crawler.addRequests([{ url: 'https://demo-webstore.apify.org/search/new-arrivals' }]);
-
-await crawler.run();
+await crawler.run([{ url: 'https://demo-webstore.apify.org/search/new-arrivals' }]);
 ```
 
 > Here, we are using the [`Array.prototype.map()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/map) function to loop through all of the product elements and save them into an array we call `results` all at the same time.
 
 After running it, you might say, "Great! It works!" **But wait...** What are those results being logged to console?
 
-![Bad results in console]({{@asset web_scraping_for_beginners/crawling/images/bad-results.webp}})
+![Bad results in console]({{@asset tutorials/images/bad-results.webp}})
 
 Every single image seems to have the same exact "URL," but they are most definitely not the image URLs we are looking for. This is strange, because in the browser, we were getting URLs that looked like this:
 
@@ -130,14 +128,12 @@ const crawler = new PuppeteerCrawler({
     },
 });
 
-await crawler.addRequests([{ url: 'https://demo-webstore.apify.org/search/new-arrivals' }])
-
-await crawler.run();
+await crawler.run([{ url: 'https://demo-webstore.apify.org/search/new-arrivals' }]);
 ```
 
 After running this one, we can see that our results look different from before. We're getting the image links!
 
-![Not perfect results]({{@asset web_scraping_for_beginners/crawling/images/almost-there.webp}})
+![Not perfect results]({{@asset tutorials/images/almost-there.webp}})
 
 Well... Not quite. It seems that the only images which we got the full links to were the ones that were being displayed within the view of the browser. This means that the images are lazy-loaded. **Lazy-loading** is a common technique used across the web to improve performance. Lazy-loaded items allow the user to load content incrementally, as they perform some action. In most cases, including our current one, this action is scrolling.
 
@@ -177,9 +173,7 @@ const crawler = new PuppeteerCrawler({
     },
 });
 
-await crawler.addRequests([{ url: 'https://demo-webstore.apify.org/search/new-arrivals' }])
-
-await crawler.run();
+await crawler.run([{ url: 'https://demo-webstore.apify.org/search/new-arrivals' }]);
 ```
 
 Let's run this and check our dataset results...
@@ -197,7 +191,3 @@ Each product looks like this, and each image is a valid link that can be visited
 ## [](#small-recap) Small Recap
 
 Making static HTTP requests only downloads the HTML content from the `DOMContentLoaded` event. We must use a browser to allow dynamic code to load, or find different means altogether of scraping the data (see [API Scraping]({{@link api_scraping.md}}))
-
-## [](#wrap-up) Wrap up 💥
-
-And this is it for the [Basics of crawling section]({{@link web_scraping_for_beginners/crawling.md}}) of the [Web scraping for beginners]({{@link web_scraping_for_beginners.md}}) course. For now, this is also the last section of the **Web scraping for beginners** course. If you want to learn more about web scraping, we recommend checking venturing out and following the other lessons in the Academy. We will keep updating the Academy with more content regularly, until we cover all the advanced and expert topics we promised at the beginning.