docs: update links

w4bremer · w4bremer · commit 2762a616b956 · 2024-10-01T20:40:43.000+02:00
diff --git a/docs/docs/features/features.md b/docs/docs/features/features.md
@@ -20,7 +20,7 @@ Basic c++ knowledge is necessary.
 
 ### Code generation
 
-Follow the documentation for the [code generation](/docs/guide/intro) in general and [CLI](/docs/cli/generate) or the [Studio](/docs/studio/intro) tools.
+Follow the documentation for the [code generation](/docs/guide/intro) in general and [CLI](/docs/tools/cli/generate) or the [Studio](/docs/tools/studio/intro) tools.
 Or try first the [quick start guide](../quickstart/index.md) which shows how to prepare api and generate code out of it.
 
 :::tip
@@ -50,11 +50,11 @@ Features generate a view model for the _API_ definition. This can be used to imp
 
 Features can be used in combination with _API_ and add more functionality on top, like simulation support (see [olink](olink.md#simulation))
 
-- [olink](olink.md) - provides a client and server adapters for each interface, that can be connected to any of the other technology templates with support for [ObjectLink](/docs/advanced/objectlink/intro). Use this feature to connect with ApiGear simulation tools.
+- [olink](olink.md) - provides a client and server adapters for each interface, that can be connected to any of the other technology templates with support for [ObjectLink](/docs/advanced/protocols/objectlink/intro). Use this feature to connect with ApiGear simulation tools.
 - examples_olink - examples of generated code for the olink feature. Contains:
 	- `olinkserver` shows use of your interfaces as an olink services.
 	- `olinkclient` shows use of your interfaces as an olink clients.
-- [monitor](monitor.md) - generates a middle-ware layer which logs all API events to the [CLI](/docs/cli/intro) or the [Studio](/docs/studio/intro)
+- [monitor](monitor.md) - generates a middle-ware layer which logs all API events to the [CLI](/docs/tools/cli/intro) or the [Studio](/docs/tools/studio/intro)
 - [MQTT](mqtt.md) _experimental_ - provides minimal working adapters for MQTT client and service side for each interfaces. Check also MQTT in other technology templates that supports it.
 - examples_mqtt - examples of generated code for the olink feature. Contains:
 	- `mqttserver` shows use of your interfaces with mqtt adapted for your services.
diff --git a/docs/docs/features/monitor.md b/docs/docs/features/monitor.md
@@ -7,7 +7,7 @@ import helloWorldModuleComponent from '!!raw-loader!./data/helloworld.module.yam
 
 # Monitor
 
-Use the monitor feature to examine the interface calls, state and signals during runtime. With this feature you obtain a monitor client and a monitored version of your interfaces. The monitoring server is embedded into the [ApiGear Studio](/docs/studio/intro) and [CLI version](/docs/cli/intro).
+Use the monitor feature to examine the interface calls, state and signals during runtime. With this feature you obtain a monitor client and a monitored version of your interfaces. The monitoring server is embedded into the [ApiGear Studio](/docs/tools/studio/intro) and [CLI version](/docs/tools/cli/intro).
 More details on [monitoring](/docs/advanced/monitor/intro)
 
 ## File overview for module
diff --git a/docs/docs/features/olink.md b/docs/docs/features/olink.md
@@ -13,7 +13,7 @@ import Figure from '../figure'
 
 # Olink
 
-This feature provides a _client_ and a _server_ adapter for your interfaces for the [ObjectLink](/docs/advanced/objectlink/intro) protocol. It allows you to connect different applications using the same or different technologies (check all of our [templates](/docs/sdk/intro)).
+This feature provides a _client_ and a _server_ adapter for your interfaces for the [ObjectLink](/docs/advanced/protocols/objectlink/intro) protocol. It allows you to connect different applications using the same or different technologies (check all of our [templates](/docs/sdk/intro)).
 
 Use an _OLink client_ instead of your interface implementation to connect to a remote service, or to a the [ApiGear simulation](olink#simulation). Use an _OLink server adapter_ to expose your interface implementation as a remote service.
 
@@ -26,7 +26,7 @@ If you want quickly start working with them go to use sections of [client](olink
 
 ### Apigear ObjectLink protocol and ObjectLink core library
 
-The [ObjectLink](/docs/advanced/objectlink/intro) protocol is a lightweight websocket based protocol for Objects described with an interface. It allows connecting a client object with a server object, and perform remote operations like: remote property change request (client) or notifications on property changed (server), inform about signal emission (server) and allows requesting a remote method call (client) and delivering a response to the caller (server).
+The [ObjectLink](/docs/advanced/protocols/objectlink/intro) protocol is a lightweight websocket based protocol for Objects described with an interface. It allows connecting a client object with a server object, and perform remote operations like: remote property change request (client) or notifications on property changed (server), inform about signal emission (server) and allows requesting a remote method call (client) and delivering a response to the caller (server).
 
 The Olink feature for your interface uses a library [ObjectLink core](https://github.com/apigear-io/objectlink-core-cpp), common for cpp based templates. The provided `CMakeLists` already contain all the dependencies, so you don't have to add it manually.
 
@@ -171,7 +171,7 @@ client.unlinkObjectSource(ioWorldHello->olinkObjectName());
 
 Files `📜helloservice.h` and `📜helloservice.h` contain the olink server adapter for the `Hello` interface - the `HelloService` class.
 
-It implements an `IObjectSource` interface (from [ObjectLink core](https://github.com/apigear-io/objectlink-core-cpp)), which wraps your `Hello` and exposes it for remote usage with the [ObjectLink](/docs/advanced/objectlink/intro) protocol. It handles all the network requests, and calls your local object.
+It implements an `IObjectSource` interface (from [ObjectLink core](https://github.com/apigear-io/objectlink-core-cpp)), which wraps your `Hello` and exposes it for remote usage with the [ObjectLink](/docs/advanced/protocols/objectlink/intro) protocol. It handles all the network requests, and calls your local object.
 
 When creating the `HelloService` you need to provide the local `IHello` service object, you want to expose to clients.
 
@@ -232,7 +232,7 @@ registry.removeSource(ioWorldOlinkHelloService->olinkObjectName());
 ## Simulation
 
 The simulation can be used to test, demonstrate or develop applications without the need to have the actual service available.
-The simulation server is integrated into the [ApiGear studio](/docs/studio/intro) and the [CLI](/docs/cli/simulate).
+The simulation server is integrated into the [ApiGear studio](/docs/tools/studio/intro) and the [CLI](/docs/tools/cli/simulate).
 
 For simulating you will use [simulation scenarios](/docs/advanced/simulation/scenario) They allow to define sequences of actions. The actions can change the property values of the service or emit signals. The scenarios can be written using a YAML schema.
 
diff --git a/docs/docs/intro.md b/docs/docs/intro.md
@@ -8,5 +8,5 @@ This is the documentation for the _cpp14_ template for the [ApiGear](/docs/guide
 
 It is split in several parts:
 
-- [Quick-Start](quickstart/index.md) is the easiest way to get started
+- [Quick-Start](quickstart/index.md?current-template=template-cpp14) is the easiest way to get started
 - [Features](features/features.md) explains the available code generator features and their usage and purpose.
