FMI simulations moved. Manual installation in process: composition explained.

Author: juliarobles

docs/docs/guides/definition/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "DT definition",
+    "position": 1,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+  

docs/docs/guides/dt-schema-creation.mdx renamed to docs/docs/guides/definition/dt-schema-creation.mdx

@@ -1,99 +1,99 @@
----
-sidebar_position: 1
----
-
-# Create a type
-
-The way to interact with [Eclipse Ditto](https://eclipse.dev/ditto/index.html) and therefore create not only digital twins, but connections, etc. is through http requests and methods. 
-Although the graphical interface of OpenTwins makes it unnecessary to go so low level, the option to communicate directly with Eclipse Ditto is still available.
-
-
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
-```mdx-code-block
-<Tabs className="unique-tabs"
-    defaultValue="ui"
-    values={[
-        {label: 'Using Grafana interface', value: 'ui'},
-        {label: 'Using http methods', value: 'http'},
-    ]}>
-<TabItem value="ui">
-```
-As explained in TWINS WIP, OpenTwins has two types of DT schemas. One for creating a single DT and other for creating a type to create multiple instances of a DT.
-
-
-To create a new DT type using OpenTwins plugin in Grafana, just select "Create new type in" button in "Types" tab.
-![CreateType](./img/createTypeButton.png)
-
-A new window with a form that will define the DT and a viewer of the produced JSON schema will have appeared.
-
-The first required information is the identification of the twin. There are two required field.
-- Namespace: Is the name of the context to which the type belongs.
-- ID: This must be unique within the scope of the type. The name of the type will precede it automatically.
-
-![Identification](./img/typeidentification.png)
-
-Next is type information. This basic static information about the type for description. There are several fields, but just one is required:
-- Policy* : We must select a policy.
-- Name.
-- Description.
-- Image: You can paste a image url to show in the type information.
-
-![Information](./img/typeinformation.png)
-
-In addition to the above information, new custom attributes can be defined, normally used as static information. By simply filling in the attribute name and its value, click on the "add" button to add a new attribute.
-
-![Attributes](./img/attributes.png)
-
-Finally, the features section is used to create the variables to be collected by the DT. Simply type the name and click on the "add" button. This will add a new variable to the twin schema.
-
-![Features](./img/typefeatures.png)
-
-An example of a schema of a DT of an abstract vehicle can be seen in the following JSON:
-
-```JSON
-{
-    "thingId": "benchmark:vehicle",
-    "policyId": "default:basic_policy",
-    "attributes": {
-        "name": "Vehicle",
-        "description": "Vehicle type for generating new vehicles.",
-        "image": "ImageLink",
-        "Brand": "EMPTY",
-        "Subtype": "EMPTY"
-    },
-    "features": {
-        "wheels": {
-            "properties": {
-                "value": null
-            }
-        },
-        "power": {
-            "properties": {
-                "value": null
-            }
-        },
-        "capacity": {
-            "properties": {
-                "value": null
-            }
-        }
-    }
-}
-
-```
-
-
-```mdx-code-block
-</TabItem>
-
-<TabItem value="http">
-```
-# Creation using HTTP requests
-
-```mdx-code-block
-</TabItem>
-</Tabs>
-
+---
+sidebar_position: 1
+---
+
+# Create a type
+
+The way to interact with [Eclipse Ditto](https://eclipse.dev/ditto/index.html) and therefore create not only digital twins, but connections, etc. is through http requests and methods. 
+Although the graphical interface of OpenTwins makes it unnecessary to go so low level, the option to communicate directly with Eclipse Ditto is still available.
+
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+```mdx-code-block
+<Tabs className="unique-tabs"
+    defaultValue="ui"
+    values={[
+        {label: 'Using Grafana interface', value: 'ui'},
+        {label: 'Using http methods', value: 'http'},
+    ]}>
+<TabItem value="ui">
+```
+As explained in TWINS WIP, OpenTwins has two types of DT schemas. One for creating a single DT and other for creating a type to create multiple instances of a DT.
+
+
+To create a new DT type using OpenTwins plugin in Grafana, just select "Create new type in" button in "Types" tab.
+![CreateType](./img/createTypeButton.png)
+
+A new window with a form that will define the DT and a viewer of the produced JSON schema will have appeared.
+
+The first required information is the identification of the twin. There are two required field.
+- Namespace: Is the name of the context to which the type belongs.
+- ID: This must be unique within the scope of the type. The name of the type will precede it automatically.
+
+![Identification](./img/typeidentification.png)
+
+Next is type information. This basic static information about the type for description. There are several fields, but just one is required:
+- Policy* : We must select a policy.
+- Name.
+- Description.
+- Image: You can paste a image url to show in the type information.
+
+![Information](./img/typeinformation.png)
+
+In addition to the above information, new custom attributes can be defined, normally used as static information. By simply filling in the attribute name and its value, click on the "add" button to add a new attribute.
+
+![Attributes](./img/attributes.png)
+
+Finally, the features section is used to create the variables to be collected by the DT. Simply type the name and click on the "add" button. This will add a new variable to the twin schema.
+
+![Features](./img/typefeatures.png)
+
+An example of a schema of a DT of an abstract vehicle can be seen in the following JSON:
+
+```JSON
+{
+    "thingId": "benchmark:vehicle",
+    "policyId": "default:basic_policy",
+    "attributes": {
+        "name": "Vehicle",
+        "description": "Vehicle type for generating new vehicles.",
+        "image": "ImageLink",
+        "Brand": "EMPTY",
+        "Subtype": "EMPTY"
+    },
+    "features": {
+        "wheels": {
+            "properties": {
+                "value": null
+            }
+        },
+        "power": {
+            "properties": {
+                "value": null
+            }
+        },
+        "capacity": {
+            "properties": {
+                "value": null
+            }
+        }
+    }
+}
+
+```
+
+
+```mdx-code-block
+</TabItem>
+
+<TabItem value="http">
+```
+# Creation using HTTP requests
+
+```mdx-code-block
+</TabItem>
+</Tabs>
+
 ```

docs/docs/guides/img/attributes.png renamed to docs/docs/guides/definition/img/attributes.png

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 3
+sidebar_position: 2
 ---
 
 # API Documentation

docs/docs/guides/img/createTwinButton.png renamed to docs/docs/guides/definition/img/createTwinButton.png

@@ -1,6 +1,6 @@
 {
   "label": "FMI Simulation",
-  "position": 5,
+  "position": 4,
   "link": {
     "type": "generated-index",
     "description": "OpenTwins supports the Functional Mock-up Interface (FMI) standard for simulation."

docs/docs/guides/img/createTypeButton.png renamed to docs/docs/guides/definition/img/createTypeButton.png

@@ -1,5 +1,6 @@
 ---
-sidebar_position: 2
+sidebar_position: 1
+sidebar_label: Concepts
 ---
 
 import useBaseUrl from '@docusaurus/useBaseUrl';

docs/docs/guides/img/typefeatures.png renamed to docs/docs/guides/definition/img/typefeatures.png

@@ -0,0 +1,15 @@
+---
+sidebar_position: 4
+---
+
+import DocCardList from '@theme/DocCardList';
+
+# Guides
+
+:::warning
+
+The guides is being written right now. Sorry for the inconvenience.
+
+:::
+
+<DocCardList className="DocCardList--no-description"/>

docs/docs/guides/img/typeidentification.png renamed to docs/docs/guides/definition/img/typeidentification.png

@@ -0,0 +1,8 @@
+{
+    "label": "Machine Learning",
+    "position": 3,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+  

docs/docs/guides/img/typeinformation.png renamed to docs/docs/guides/definition/img/typeinformation.png

@@ -1,6 +1,6 @@
 {
-    "label": "Guides",
-    "position": 4,
+    "label": "Monitoring",
+    "position": 2,
     "link": {
       "type": "generated-index"
     }