Document v0.4.0 (#6)

Author: bboure

docs/aws-credentials.md

@@ -0,0 +1,30 @@
+---
+slug: aws-credentials
+sidebar_position: 10
+---
+
+# 🔑 AWS credentials 
+
+GraphBolt only uses your local credentials in order to authenticate against your AWS accounts. Those credentials remain safe and secure. Everything happens on *your* machine. 
+
+We automatically detect the profiles that are configured in your credential files (e.g. `~/.aws/credentials` and/or `~/.aws/config`). 
+
+To start working from a specific account, pick a profile from the top bar.
+
+![Profile Picker](img/profiles.png)
+
+The following methods are supported:
+
+### Short or long-term credentials
+
+Those are the keys stored in the credentials file. i.e. `aws_access_key_id`, `aws_secret_access_key`, and optionally `aws_session_token`.
+
+:::tip
+At GraphBolt, we recommend that you use [Leapp](https://leapp.cloud) in order to manage your short-term credentials.
+:::
+
+### Single Sign-On
+
+GraphBolt supports AWS Single Sign-On. If you have [configured SSO profiles](https://docs.aws.amazon.com/cli/latest/userguide/sso-configure-profile-token.html) on your local machine, GraphBolt will detect them and prompt you to login if necessary.
+
+![SSO Login](img/sso.png)

docs/getting-started.md

@@ -12,9 +12,3 @@ description: GraphBolt is a desktop app for AWS AppSync. Build, manage, test and
 GraphBolt is the ultimate tool for AWS AppSync developers, providing a comprehensive solution for building, testing, and debugging GraphQL APIs.
 
 ![GraphBolt](./img/GraphBolt.png)
-
-## Setup
-
-The only thing you need to get started is to have your [AWS profiles](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html) configured on your machine. When you open GraphBolt, it will automatically detect them and discover all the AppSync APIs that you have in your accounts. You will find the available profiles in the top bar.
-
-![AWS profiles](img/aws-profiles.png)

docs/graphql-client/_category_.json

@@ -1,5 +1,5 @@
 {
-  "position": 2,
+  "position": 10,
   "collapsible": true,
   "collapsed": false
 }

docs/graphql-client/subscriptions.md

@@ -4,4 +4,4 @@ sidebar_position: 3
 
 # Subscriptions
 
-GraphBolt supports GraphQL subscriptions. For now, you will only see the last received payload in the response view. Keeping message history is on the [roadmap](https://github.com/orgs/graphboltdev/projects/1/views/1?filterQuery=subsc&pane=issue&itemId=11954314) for future improvements.
+GraphBolt supports GraphQL subscriptions. For now, you will only see the last received payload in the response view.

docs/img/GraphBolt.png

@@ -1,5 +1,5 @@
 {
-  "position": 4,
+  "position": 30,
   "collapsible": true,
   "collapsed": false
 }

docs/img/aws-profiles.png

@@ -6,11 +6,6 @@ sidebar_position: 1
 
 This tool allows you to quickly build and test your VTL mapping templates or AppSync JavaScript Resolvers. At the moment, this is nothing else than a friendly GUI for the [evaluate-mapping-template](https://docs.aws.amazon.com/cli/latest/reference/appsync/evaluate-mapping-template.html) and [evaluate-code](https://docs.aws.amazon.com/cli/latest/reference/appsync/evaluate-code.html) aws cli commands.
 
-:::info
-There are plans to allow executing the resulting JSON object against real data sources. See the [roadmap](https://github.com/orgs/graphboltdev/projects/1/views/1?filterQuery=mapping&pane=issue&itemId=11954302).
-:::
-
-
 ![Mapping template evaluation](./img/evaluation.png)
 
 ## 1. Context Object

docs/img/profiles.png

@@ -0,0 +1,13 @@
+---
+sidebar_position: 2
+---
+
+# Collections
+
+You can easily manage and categorize your resolvers by organizing them into collections. This feature enables you to perform the following actions:
+
+- Create, edit, and delete JS resolvers or VTL mapping templates.
+- Group them logically into folders.
+- Quickly find specific resolvers using the filter function.
+
+![Operation Collections](img/collections.png)

docs/img/sso.png

@@ -1,5 +1,5 @@
 {
-  "position": 3,
+  "position": 20,
   "collapsible": true,
   "collapsed": false
 }

docs/mapping-template-planner/_category_.json

@@ -34,7 +34,9 @@ This section gives you additional information about each field/resolver:
 | Resolver| The parent type and field name of the executed resolver. Next to it you'll see what kind of resolver it is (i.e. `Unit` or `Pipeline`), and icon (or icons) representing the underlying data source(s) that were used to resolve this field. |
 | Start offset| The difference in time between the beginning of this resolver invocation and the start of the request.|
 | Duration| How long this invocation of the resolver lasted.|
-| eye / 👁 | Click to see [resolver details](./resolver-details) |
+
+
+Click on a resolver to see [resolver details](./resolver-details)
 
 # X-Ray
 

docs/mapping-template-planner/code-evaluation.md

@@ -8,6 +8,6 @@ On this screen, you will find a list of the queries that were recently executed,
 
 You can filter the list by date-range, or by text (e.g. you can search for a specific operation name, or a request id).
 
-By clicking on the 👁, you can get more information about a specific request. See the [Query details](query-details) section for more details. 
+By clicking on a request, you can get more information about a specific request. See the [Query details](query-details) section for more details. 
 
 ![Recent Queries](img/recent-queries.png)

docs/mapping-template-planner/collections.md

@@ -116,11 +116,7 @@ const config = {
               {
                 label: 'Blog',
                 href: 'https://blog.graphbolt.dev',
-              },
-              {
-                label: 'Roadmap',
-                href: 'https://github.com/orgs/graphboltdev/projects/1',
-              },
+              }
             ],
           },
         ],