Document subscriptions (#3525)

Author: tobias-tengler

website/src/docs/hotchocolate/api-reference/extending-filtering.md

@@ -72,7 +72,7 @@ This convention is also configurable with a fluent interface, so in most cases y
 ## Descriptor
 
 Most of the capabilities of the descriptor are already documented under `Fetching Data -> Filtering`.
-If you have not done this already, it is now the right time to head over to [Filtering](https://chillicream.com/docs/hotchocolate/fetching-data/filtering) and read the parts about the `FilterConventions`
+If you have not done this already, it is now the right time to head over to [Filtering](/docs/hotchocolate/fetching-data/filtering) and read the parts about the `FilterConventions`
 
 There are two things on this descriptor that are not documented in `Fetching Data`:
 
@@ -284,8 +284,7 @@ A little simplified this is what happens during visitation:
 ```graphql
 {
   users(
-    where: # instance[0] = x # Create SCOPE 1 with parameter x of type User
-    # level[0] = []
+    where: # level[0] = [] # instance[0] = x # Create SCOPE 1 with parameter x of type User
     {
       # Push property User.Company onto the scope
       # instance[1] =  x.Company

website/src/docs/hotchocolate/api-reference/filtering.md

@@ -1462,7 +1462,7 @@ private static bool TryCreateStringFilter(
     IFilterConvention filterConventions,
     [NotNullWhen(true)] out FilterFieldDefintion? definition)
 {
-    if (type == typeof())
+    if (type == typeof(string))
     {
         var field = new StringFilterFieldDescriptor(context, property, filterConventions);
         definition = field.CreateDefinition();
@@ -1646,14 +1646,14 @@ public static class DateTimeFilterConventionExtensions
 `DateTime` is a new filter. Hot Chocolate is only aware of its existence because of the delegate passed to `AddImplicitFilter`
 
 ```csharp
-private static bool TryCreateDateTimeFiler(
+private static bool TryCreateDateTimeFilter(
     IDescriptorContext context,
     Type type,
     PropertyInfo property,
     IFilterConvention filterConventions,
     [NotNullWhen(true)] out FilterFieldDefintion? definition)
 {
-    if (type == typeof())
+    if (type == typeof(DateTime))
     {
         var field = new DateTimeFilterFieldDescriptor(
           context, property, filterConventions);

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

@@ -4,13 +4,13 @@ title: "Get started with Hot Chocolate"
 
 > We are still working on the documentation for Hot Chocolate 11.1 so help us by finding typos, missing things or write some additional docs with us.
 
-In this tutorial, we will walk you through the basics of creating a GraphQL server with Hot Chocolate. If you want to dig deeper into Hot Chocolate, we have our GraphQL workshop, which touches on topics like schema design, DataLoader, and many more things.
+In this tutorial, we will walk you through the basics of creating a GraphQL server with Hot Chocolate. If you want to dig deeper into Hot Chocolate, we have our [GraphQL workshop](https://github.com/ChilliCream/graphql-workshop), which touches on topics like schema design, DataLoader, and many more things.
 
-In this tutorial, we will teach you:
+In this tutorial, we will teach you how to:
 
-- To set up a GraphQL Server.
-- To define a GraphQL schema.
-- To query your GraphQL server.
+- Set up a GraphQL server.
+- Define a GraphQL schema.
+- Query your GraphQL server.
 
 # Step 1: Create a GraphQL server project
 
@@ -20,14 +20,12 @@ Open your preferred terminal and select a directory where you want to add the co
 
 ```bash
 dotnet new web -n Demo
-dotnet new sln -n Demo
-dotnet sln add ./Demo
 ```
 
 2. Add the `HotChocolate.AspNetCore` package.
 
 ```bash
-dotnet add ./Demo package HotChocolate.AspNetCore --version 11.1.0
+dotnet add ./Demo package HotChocolate.AspNetCore
 ```
 
 # Step 2: Create a GraphQL schema
@@ -60,7 +58,7 @@ namespace Demo
 }
 ```
 
-We have a nice and simple model with these two classes that we can use to build our GraphQL schema. We now need to define a query root type. The query root type exposes all the possible queries that a user can drill into. A query root type can be defined as our models just with C#.
+With these two classes we have a nice and simple model that we can use to build our GraphQL schema. We now need to define a query root type. The query root type exposes all the possible queries that a user can drill into. A query root type can be defined in the same way we defined our models.
 
 3. Add a new class `Query`.
 
@@ -109,6 +107,8 @@ public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
 }
 ```
 
+> Note: We also have a template, which includes the configurations we have just made. Just install the template using `dotnet new -i HotChocolate.Templates.Server` and now you can use `dotnet new graphql` to bootstrap your future GraphQL servers!
+
 # Step 3: Execute a GraphQL query
 
 Now that your server is finished let us try it out by executing a simple GraphQL query.
@@ -119,11 +119,11 @@ Now that your server is finished let us try it out by executing a simple GraphQL
 dotnet run --project ./Demo
 ```
 
-2. Open Chrome, Edge or Firefox and head over to `http://localhost:5000/graphql` to open the built-in GraphQL IDE Banana Cake Pop.
+2. Open your browser and head over to `http://localhost:5000/graphql` to open our built-in GraphQL IDE [Banana Cake Pop](/docs/bananacakepop/).
 
 ![GraphQL IDE](../../images/get-started-bcp.png)
 
-3. Next, click on the `Book` icon on the left-hand navigation bar to explore the server GraphQL schema. If this is the first time you are running the demo, you will need to enter `http://localhost:5000/graphql` as the schema endpoint URI. In the schema explorer, we can see that we have one query root field exposed. By clicking on the field, we can drill into the schema structure.
+3. Next, click on the `Book` icon in the left-hand navigation bar to explore the server's GraphQL schema. If this is the first time you are running the demo, you will need to enter `http://localhost:5000/graphql` as the schema endpoint URI. In the schema explorer, we can see that we have one query root field exposed. By clicking on the field, we can drill into the schema structure.
 
 ![GraphQL IDE Schema Explorer](../../images/get-started-bcp-schema-explorer.png)
 

website/src/docs/hotchocolate/get-started.md

@@ -172,7 +172,7 @@ const IndexPage: FunctionComponent = () => {
               our startup guide and see how simple it is to create your first
               API.
             </p>
-            <Link to="/docs/hotchocolate/v10/">Learn more</Link>
+            <Link to="/docs/hotchocolate">Learn more</Link>
           </ContentContainer>
         </SectionRow>
       </Section>

website/src/pages/index.tsx

@@ -39,11 +39,11 @@ const PlatformPage: FunctionComponent = () => {
           <ContentContainer>
             <SectionTitle>Hot Chocolate</SectionTitle>
             <p>
-              Hot Chocolate is the GraphQL server and provides core libraries
+              Hot Chocolate is our GraphQL server and provides core libraries
               for Strawberry Shake, our GraphQL client, and our GraphQL tools.
               No wonder why Hot Chocolate is the ChilliCream's platform core.
             </p>
-            <Link to="/docs/hotchocolate/v10/">Learn more</Link>
+            <Link to="/docs/hotchocolate">Learn more</Link>
           </ContentContainer>
         </SectionRow>
       </Section>
@@ -88,7 +88,8 @@ const PlatformPage: FunctionComponent = () => {
             <p>
               Keep track of all clients that depend on your GraphQL endpoints.
             </p>
-            <Link to="/docs/marshmallowpie">Learn more</Link>
+            {/* comment in again, once there is documentation */}
+            {/* <Link to="/docs/marshmallowpie">Learn more</Link> */}
           </ContentContainer>
         </SectionRow>
       </Section>