Mutation Documentation Refinements (ChilliCream#4558)

website/src/blog/2021-12-14-hot-chocolate-12-4/2021-09-27-hot-chocolate-12-4.md

@@ -257,6 +257,8 @@ services
         })
 ```
 
+> Note: You can also partially opt-out of the convention by for instance crafting your own input type but letting the convention produce the payload.
+
 ## Errors
 
 The second part of this new mutation convention involves user errors. We did a lot of work investigating how we should enable errors or even what pattern we should follow. 

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

@@ -223,7 +223,7 @@ type UpdateUserNamePayload {
 
 Following this pattern helps to keep the schema evolvable but requires a lot of boilerplate code to realize.
 
-## Introduction
+## Input and Payload
 
 HotChocolate has built-in conventions for mutations to minimize boilerplate code.
 
@@ -349,7 +349,7 @@ type Mutation {
 </ExampleTabs.Schema>
 </ExampleTabs>
 
-## Defining Errors
+## Errors
 
 The mutation conventions also allow you to create mutations that follow the error
 [stage 6a Pattern Marc-Andre Giroux layed out](https://xuorig.medium.com/a-guide-to-graphql-errors-bb9ba9f15f85) with minimal effort.
@@ -958,6 +958,15 @@ public UpdateUserNamePayload UpdateUserNameAsync(UpdateUserNameInput input)
 }
 ```
 
+You can also partially opt-out:
+
+```csharp
+public User UpdateUserNameAsync(UpdateUserNameInput input)
+{
+    //...
+}
+```
+
 ### Custom error interface
 
 Lastly, we can customize the error interface we want to use with our mutation convention. The error interface is shared across all error types that the schema defines and provides the minimum shape that all errors have to fulfill.