Section safe subgraph generation tool

navigation/navigation.ts

@@ -181,6 +181,9 @@ export const navigation = (locale: AppLocale): NavItemDefinition[] => [
       {
         slug: 'grafting',
       },
+      {
+        slug: 'subgraph-uncrashable',
+      },
     ],
   },
   {

pages/en/cookbook/subgraph-uncrashable.md

@@ -0,0 +1,34 @@
+---
+title: Subgraph Uncrashable - a Safe Subgraph Code Generator
+---
+
+[Subgraph Uncrashable](https://float-capital.github.io/float-subgraph-uncrashable/) is a code generation tool that generates a set of helper functions from the graphql schema of a project. It ensures that all interactions with entities in your subgraph are completely safe and consistent.
+
+
+### Why integrate with Subgraph Uncrashable?
+
+  - **Continuous Uptime**. Mishandled entities may cause subgraphs to crash, which can be disruptive for projects that are dependent on The Graph. Set up helper functions to make your subgraphs “uncrashable” and ensure business continuity.
+
+  - **Completely Safe**. Common problems seen in subgraph development are issues of loading undefined entities, not setting or initializing all values of entities, and race conditions on loading and saving entities. Ensure all interactions with entities are completely atomic.
+
+  - **User Configurable** Set default values and configure the level of security checks that suits your individual project's needs. Warning logs are recorded indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
+
+<br>
+
+**Key Features**
+
+  - The code generation tool accommodates **all** subgraph types and is configurable for users to set sane defaults on values. The code generation will use this config to generate helper functions that are to the users specification.
+
+  - The framework also includes a way (via the config file) to create custom, but safe, setter functions for groups of entity variables. This way it is impossible for the user to load/use a stale graph entity and it is also impossible to forget to save or set a variable that is required by the function.
+
+  - Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy. These logs can be viewed in the The Graph's hosted service under the 'Logs' section.
+
+<br>
+
+Subgraph Uncrashable can be run as an optional flag using the Graph CLI codegen command.
+
+```sh
+graph codegen -u [options] [<subgraph-manifest>]
+```
+
+Visit the [subgraph uncrashable documentation](https://float-capital.github.io/float-subgraph-uncrashable/docs/) or watch this [video tutorial](https://float-capital.github.io/float-subgraph-uncrashable/docs/tutorial) to learn more and to get started with developing safer subgraphs. 

pages/en/developing/creating-a-subgraph.mdx

@@ -560,6 +560,7 @@ import { Gravatar } from '../generated/schema'
 
 Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to the Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.
 
+
 ## Data Source Templates
 
 A common pattern in Ethereum smart contracts is the use of registry or factory contracts, where one contract creates, manages, or references an arbitrary number of other contracts that each have their own state and events. The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.