chore: sync content to repo

roadmaps/graphql/content/authorization@G50ZMlmP7Ru5LcFne5Rhu.md

@@ -1,12 +1,6 @@
-# Authorization
+# GraphQL Over SSE Authorization
 
-Authorization in GraphQL controls access to data and operations based on user permissions and roles. It can be implemented at the schema level, field level, or within resolvers, ensuring users only access data they're permitted to see through various authentication and permission strategies.
-
-There are several ways to implement authorization in GraphQL:
-
-*   Using middleware
-*   Using schema directives
-*   Using a data source layer
+Authorization for GraphQL over Server-Sent Events (SSE) involves verifying a client's identity and permissions before establishing a persistent stream of data. Since standard HTTP headers are only sent during the initial handshake of an SSE connection, authentication tokens are typically passed via query parameters or specialized sub-protocols when the request is first initiated. Once the connection is established, the server enforces access control rules to ensure that the events pushed to the client match the data the user is authorized to receive.
 
 Visit the following resources to learn more:
 

roadmaps/graphql/content/authorization@GzwPvLybxTJM96fUhQUOi.md

@@ -1,12 +1,6 @@
-# Authorization
+# Authorization in GraphQL Over WebSockets
 
-Authorization in GraphQL refers to the process of controlling access to specific fields, types, or operations in a GraphQL schema based on user roles or permissions. It allows you to restrict access to certain data or functionality in your application based on the user's role or permissions.
-
-There are several ways to implement authorization in GraphQL:
-
-*   Using middleware
-*   Using schema directives
-*   Using a data source layer
+Authorization in GraphQL over WebSockets involves validating that a client has the necessary permissions to maintain a persistent connection and receive specific real-time updates. Since standard HTTP headers are typically only sent during the initial handshake, authorization is often handled during the connection initialization phase by passing authentication tokens through connection parameters. Once the connection is established, the server verifies these credentials against the requested operations to ensure that data access remains secure throughout the lifecycle of the subscription.
 
 Visit the following resources to learn more:
 

roadmaps/graphql/content/authorization@i-zcfN6RNXhA_sb7DcIon.md

@@ -1,12 +1,6 @@
-# Authorization
+# Authorization in GraphQL Over HTTP
 
-Authorization in GraphQL refers to the process of controlling access to specific fields, types, or operations in a GraphQL schema based on user roles or permissions. It allows you to restrict access to certain data or functionality in your application based on the user's role or permissions.
-
-There are several ways to implement authorization in GraphQL:
-
-*   Using middleware
-*   Using schema directives
-*   Using a data source layer
+Authorization in GraphQL over HTTP determines whether a client has the necessary permissions to access specific data or perform requested operations. This process typically occurs at the resolver level, where the server evaluates the user's identity and roles against the requested fields before returning any information. By implementing authorization checks directly within the business logic or through middleware, developers ensure that sensitive data remains protected regardless of the transport layer used for the request.
 
 Visit the following resources to learn more:
 

roadmaps/graphql/content/graphene@r3Yf5pxzgSGAckOPr3eSt.md

@@ -0,0 +1,8 @@
+# Graphene
+
+Graphene is a Python library that facilitates building GraphQL APIs. It allows developers to define GraphQL schemas using Python classes, mapping these classes to data sources and resolvers. Graphene simplifies the process of creating GraphQL endpoints in Python web applications, providing tools for defining types, fields, and queries.
+
+Visit the following resources to learn more:
+
+- [@official@Graphene](https://graphene-python.org/)
+- [@article@Graphene](https://github.com/graphql-python/graphene?tab=readme-ov-file)

roadmaps/graphql/content/multiple-fields-in-mutation@AySlY8AyI6jE-cy-qKKOU.md

@@ -4,4 +4,4 @@ GraphQL allows multiple mutations in a single query by including multiple mutati
 
 Visit the following resources to learn more:
 
-- [@official@Guide to Multiple fields in mutations](https://graphql.org/learn/mutations/#multiple-fields-in-mutations)
+- [@official@Guide to Multiple fields in mutations](https://graphql.org/learn/mutations/#multiple-fields-in-mutations)

roadmaps/graphql/content/root-fields@AlJlHZD3_SPoLNaqdM-pB.md

@@ -4,4 +4,4 @@ Root fields are the top-level fields available to clients in GraphQL queries and
 
 Visit the following resources to learn more:
 
-- [@official@Get Started with Root Fields](https://graphql.org/learn/execution/#root-fields-resolvers)
+- [@official@Get Started with Root Fields](https://graphql.org/learn/execution/#root-fields-resolvers)