docs: reworked the original documentation (#172)

* docs: reworked the original documentation
---------

Signed-off-by: Artem Shcherbatiuk <vertex451@gmail.com>
Co-authored-by: Valentin Zipf <valentin.zipf@sap.com>

Author: vertex451

CONTRIBUTING.md

@@ -8,253 +8,26 @@ The goal of this library is to provide a reusable and generic way of exposing k8
 This enables UIs that need to consume these objects to do so in a developer-friendly way, leveraging a rich ecosystem.
 
 ## Overview
-GQL Gateway expects a directory as input to watch for files containing OpenAPI specifications with resources.
 
-Each file in that directory will correspond to a KCP workspace (or API server).
+This repository contains two main components:
+- [Listener](./docs/listener.md): watches a cluster and stores its openAPI spec in a directory.
+- [Gateway](./docs/gateway.md): exposes the openAPI spec as a GraphQL endpoints.
 
-For each file it will create a separate URL like `/<workspace-name>/graphql` which will be used to query the resources of that workspace.
+## Quickstart
 
-It will be watching for changes in the directory and update the schema accordingly.
+If you want to get started quickly, you can follow the [quickstart guide](./docs/quickstart.md).
 
-## Usage
-
-### OpenAPI Spec
-
-You can run the gateway using the existing generic OpenAPI spec file which is located in the `./definitions` directory.
-
-(Optional) Or you can generate a new one from your own cluster by running the following command:
-```shell
-kubectl get --raw /openapi/v2 > filename
-```
-### Start the Service 
-```shell
-task start
-```
-OR
-```shell
-go run main.go start --watched-dir=./definitions
-# where ./definitions is the directory containing the OpenAPI spec files
-```
-
-After service start you can access the GraphQL playground. 
-All addresses correspond the content of the watched directory and can be found in the terminal output.
-
-For example, we have two KCP workspaces: `root` and `root:alpha`, for each of them we have a separate spec file in the `./definitions` directory.
-
-Then we will have two URLs:
-- `http://localhost:3000/root/graphql`
-- `http://localhost:3000/root:alpha/graphql`
-
-Open the URL in the browser and you will see the GraphQL playground. 
-
-### Authorization
-
-To send the request, you can attach the `Authorization` header with the token from kubeconfig `users.user.token`:
-```shell
-{
-  "Authorization": "5f89bc76-c5b8-4d6f-b575-9ca7a6240bca"
-}
-```
-
-**If you skip that header, service will try to use a runtime client with current context.(`kubectl config current-context`)**
-
-P.S. Skipping the header works with both API server and KCP workspace.
-
-#### Sending queries
-
-##### Create a Pod:
-
-```shell
-mutation {
-  core {
-    createPod(
-      namespace: "default",
-      object: {
-        metadata: {
-          name: "my-new-pod",
-          labels: {
-            app: "my-app"
-          }
-        }
-        spec: {
-          containers: [
-            {
-              name: "nginx-container"
-              image: "nginx:latest"
-              ports: [
-                {
-                  containerPort: 80
-                }
-              ]
-            }
-          ]
-          restartPolicy: "Always"
-        }
-      }
-    ) {
-      metadata {
-        name
-        namespace
-        labels
-      }
-      spec {
-        containers {
-          name
-          image
-          ports {
-            containerPort
-          }
-        }
-        restartPolicy
-      }
-      status {
-        phase
-      }
-    }
-  }
-}
-```
-
-##### Get the created Pod:
-```shell
-query {
-  core {
-    Pod(name:"my-new-pod", namespace:"default") {
-      metadata {
-        name
-      }
-      spec{
-        containers {
-          image
-          ports {
-            containerPort
-          }
-        }
-      }
-    }
-  }
-}
-```
-
-##### Delete the created Pod:
-```shell
-mutation {
-  core {
-    deletePod(
-      namespace: "default",
-      name: "my-new-pod"
-    )
-  }
-}
-```
-### Components Overview
-
-#### Workspace manager
-
-Holds the logic for watching a directory, triggering schema generation, and binding it to an HTTP handler.
-
-*P.S. We are going to have an Event Listener that will watch the KCP workspace and write the OpenAPI spec into that directory.*
-
-#### Gateway
-
-Is responsible for the conversion from OpenAPI spec into the GraphQL schema.
-
-#### Resolver
-
-Holds the logic of interaction with the cluster.
-
-### Testing
-
-```shell
-task test
-```
-
-If you want to run single test, you need to export a KUBEBUILDER_ASSETS environment variable:
-```shell
-KUBEBUILDER_ASSETS=$(pwd)/bin/k8s/$DIR_WITH_ASSETS
-# where $DIR_WITH_ASSETS is the directory that contains binaries for your OS.
-```
-P.S. You can also integrate it within your IDE run configuration.
-
-Then you can run the test:
-```
-
-
-You can also check the coverage:
-```shell
-task coverage
-```
-P.S. If you want to exclude some files from the coverage report, you can add them to the `.testcoverage.yml` file.
-
-
-
-### Linting
-
-```shell
-task lint
-```
-
-### Subscriptions
-
-To subscribe to events, you should use the SSE (Server-Sent Events) protocol.
-
-Since GraphQL playground doesn't support it, you should use curl.
-
-For instance, to subscribe to a change of a displayName field in a specific account in root workspace, you can run the following command:
-```shell
-curl \
-  -H "Accept: text/event-stream" \
-  -H "Content-Type: application/json" \
-  -H "Authorization: 7f41d4ea-6809-4714-b345-f9281981b2dd" \
-  -d '{"query": "subscription { core_openmfp_org_account(name: \"root-account\") { spec { displayName }}}"}' \
-  http://localhost:8080/root/graphql
-```
-Fields that will be listened are defined in the graphql query within the `{}` brackets.
-
-P.S. Don't forget to replace the `Authorization` header with the token from the kubeconfig.
-
-If you want to listen to all fields, you can set `subscribeToAll` to `true`:
-```shell
-curl \
-  -H "Accept: text/event-stream" \
-  -H "Content-Type: application/json" \
-  -H "Authorization: 7f41d4ea-6809-4714-b345-f9281981b2dd" \
-  -d '{"query": "subscription { core_openmfp_org_account(name: \"root-account\", subscribeToAll: true) { metadata { name } }}"}' \
-  http://localhost:8080/root/graphql
-```
-P.S. Note, that only fields specified in `{}` brackets will be returned.
-
-To subscribe to all accounts in the root workspace, you can run the following command:
-```shell
-curl \
-  -H "Accept: text/event-stream" \
-  -H "Content-Type: application/json" \
-  -H "Authorization: 7f41d4ea-6809-4714-b345-f9281981b2dd" \
-  -d '{"query": "subscription { core_openmfp_org_accounts { spec { displayName }}}"}' \
-  http://localhost:8080/root/graphql
-```
+## Contributing
+Please refer to the [contributing](./docs/contributing.md) section for instructions on how to contribute to OpenMFP.
 
 ## Releasing
 
-The release is performed automatically through a GitHub Actions Workflow. The resulting website will be available as github page under the following URL: https://openmfp.github.io/openmfp.org/
-
-## Requirements
-
-Please refer [README.md#usage](README.md#usage) for the requirements.
+The release is performed automatically through a GitHub Actions Workflow. The resulting website will be available as Github page under the following URL: https://openmfp.github.io/openmfp.org/
 
 ## Security / Disclosure
 
 If you find any bug that may be a security problem, please follow our instructions at [in our security policy](https://github.com/openmfp/openmfp.org/security/policy) on how to report it. Please do not create GitHub issues for security-related doubts or problems.
 
-## Contributing
-
-Please refer to the [CONTRIBUTING.md](CONTRIBUTING.md) file in this repository for instructions on how to contribute to OpenMFP.
-
-## Code of Conduct
-
-Please refer to the [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) file in this repository for information on the expected Code of Conduct for contributing to OpenMFP.
-
-
 ## Licensing
 
 Copyright 2025 SAP SE or an SAP affiliate company and OpenMFP contributors. Please see our [LICENSE](LICENSE) for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available [via the REUSE tool](https://api.reuse.software/info/github.com/openmfp/openmfp.org).

README.md

@@ -0,0 +1,87 @@
+# ConfigMap Queries
+
+This page shows you examples queries and mutations for GraphQL to perform operations on the `ConfigMap` resource. 
+For questions on how to execute them, please find our [Quick Start Guide](./quickstart.md).
+
+## Create a ConfigMap:
+```shell
+mutation {
+  core {
+    createConfigMap(
+      namespace: "default",
+      object: {
+        metadata: {
+          name: "example-config"
+        },
+        data: { key: "val" }
+      }
+    ) {
+      metadata {
+        name
+      }
+      data
+    }
+  }
+}
+```
+
+## List ConfigMaps:
+```shell
+{
+  core {
+    ConfigMaps {
+      metadata {
+        name
+      }
+      data
+    }
+  }
+}
+```
+
+## Get a ConfigMap:
+```shell
+{
+  core {
+    ConfigMap(name: "example-config", namespace: "default") {
+      metadata {
+        name
+      }
+      data
+    }
+  }
+}
+```
+
+## Update a ConfigMap:
+```shell
+mutation {
+  core {
+    updateConfigMap(
+      name:"example-config"
+      namespace: "default",
+      object: {
+        data: { key: "new-value" }
+      }
+    ) {
+      metadata {
+        name
+        namespace
+      }
+      data
+    }
+  }
+}
+```
+
+## Delete a ConfigMap:
+```shell
+mutation {
+  core {
+    deleteConfigMap(
+      name: "example-config", 
+      namespace: "default"
+    )
+  }
+}
+```