Linked youtube videos to relevant documentation sections

website/src/docs/hotchocolate/defining-a-schema/extending-types.md

@@ -10,6 +10,10 @@ Because of these capabilities, they also allow for better organization of our ty
 
 Type extensions are especially useful if we want to modify third-party types, such as types that live in a separate assembly and are therefore not directly modifiable by us.
 
+<iframe width="560" height="315"
+src="https://www.youtube.com/embed/EHTr4Fq6GlA"frameborder="0"
+allowfullscreen></iframe>
+
 > ⚠️ Note: Type extensions do not produce the [extend type syntax that GraphQL offers](http://spec.graphql.org/draft/#sec-Object-Extensions), since it would unnecessarily complicate the resulting schema. Instead, Hot Chocolate's type extensions are directly merged with the original type definition to create a single type at runtime.
 
 # Object Types

website/src/docs/hotchocolate/defining-a-schema/index.md

@@ -79,3 +79,11 @@ As our data graph and number of developers/clients grows, we need to ensure that
 [Relay](https://relay.dev) proposes some schema design principles for GraphQL servers in order to more efficiently fetch, refetch and cache entities on the client. Since these principles make for a better schema, we encourage all users, not only those of Relay, to consider these principles.
 
 [Learn more about Relay-compatible schema design](/docs/hotchocolate/defining-a-schema/relay)
+
+# Automatic type registration
+
+Starting with Hot Chocolate 12.7 we introduced a new source generator that automatically registers types and DataLoader with your GraphQL configuration builder. Watch on YouTube how you can simplify your Hot Chocolate configuration code.
+
+<iframe width="560" height="315"
+src="https://www.youtube.com/embed/QPelWd9L9ck"frameborder="0"
+allowfullscreen></iframe>

website/src/docs/hotchocolate/execution-engine/index.md

@@ -2,7 +2,15 @@
 title: Overview
 ---
 
-In this section we will learn about the features of the Hot Chocolate execution engine.
+In this section we will learn about the Hot Chocolate execution engine.
+
+<iframe width="560" height="315"
+src="https://www.youtube.com/embed/Ut33sSTYmgw"frameborder="0"
+allowfullscreen></iframe>
+
+# Request Middleware
+
+The GraphQL execution is abstraction into a request pipeline that is composed of many request middleware. Each request middleware represents one part of executing a GraphQL request like the parsing of the GraphQL request document or the semantical validation of the GraphQL document.
 
 # Field middleware
 

website/src/docs/hotchocolate/fetching-data/fetching-from-rest.md

@@ -6,7 +6,14 @@ import { ExampleTabs, Annotation, Code, Schema } from "../../../components/mdx/e
 
 In this section, we will cover how you can easily integrate a REST API into your GraphQL API.
 
+If you want to have an outlook into the upcoming native REST integration with Hot Chocolate 13 you can head over to YouTube and have a look.
+
+<iframe width="560" height="315"
+src="https://www.youtube.com/embed/l2QsFlKYqhk"frameborder="0"
+allowfullscreen></iframe>
+
 GraphQL has a strongly-typed type system and therefore also has to know the dotnet runtime types of the data it returns in advance.
+
 The easiest way to integrate a REST API is, to define an OpenAPI specification for it.
 OpenAPI describes what data a REST endpoint returns.
 You can automatically generate a dotnet client for this API and integrate it into your schema.

website/src/docs/hotchocolate/index.md

@@ -19,3 +19,5 @@ You can use Hot Chocolate Server as:
 Hot Chocolate is very easy to set up and takes the clutter away from writing GraphQL schemas. We update Hot Chocolate continuously and implement new spec features as they hit draft status. This lets you pick up new GraphQL features incrementally to open up new development opportunities for your ideas.
 
 Let's [get started](/docs/hotchocolate/get-started) with Hot Chocolate!
+
+Join us on [YouTube](https://youtube.chillicream.com) for Hot Chocolate deep dives.