fixed links

docs/getting-started/download.md

@@ -16,4 +16,4 @@ To get started, head over to our [Downloads page](https://tagocore.com#download)
 - MacOS x64
 - Windows x64
 
-After you download TagoCore, follow the [Installation](/docs/installation) steps.
+After you download TagoCore, follow the [Installation](/installation) steps.

docs/plugins/create/getting-started.md

@@ -116,7 +116,7 @@ created your Plugin in TagoCore's default Plugin folder, all you have to do is r
 
 Once you do so, you should see something like this as soon as the application starts:
 
-<img className="big-image" src="/docs/img/plugin/getting-started-loaded.png" height="40px" />
+<img className="big-image" src="/img/plugin/getting-started-loaded.png" height="40px" />
 
 ### Give users options
 

docs/plugins/create/lifecycle.md

@@ -83,7 +83,7 @@ the plugin will still be loaded normally and its state will still be `started`.
 However, the Module will have its state as `stopped` and the error will appear in the `Plugin Configuration`
 page of your Plugin, under your Module's status:
 
-<img className="big-image" src="/docs/img/plugin/onload-error.png" height="150px" />
+<img className="big-image" src="/img/plugin/onload-error.png" height="150px" />
 
 This functionality is a great tool for you to indicate that something is not quite right in your Plugin, or that
 some unexpected error happened while trying to start/stop your Module.

docs/plugins/install/manually.md

@@ -11,7 +11,7 @@ plugin manually you have two choices:
 
 ## Install via the sidebar
 
-TagoCore's sidebar allows you to quickly install a bundled (.tcore) plugin file. Look for the &nbsp;<img src="/docs/img/icons/puzzle-piece.svg" width="15px"/>&nbsp; button in the sidebar and click on it.
+TagoCore's sidebar allows you to quickly install a bundled (.tcore) plugin file. Look for the &nbsp;<img src="/img/icons/puzzle-piece.svg" width="15px"/>&nbsp; button in the sidebar and click on it.
 
 :::info
 This option is designed to load bundled (.tcore) files. If you have a simple Node.js project, go to the next option.

docs/resources/action/overview.md

@@ -18,8 +18,8 @@ With Actions you can:
 
 ## Adding an Action
 
-To add a new Action, press the&nbsp; <img className="inline-image" src="/docs/img/action/add-action-button.png" height="25px" /> &nbsp;button on the **Actions** page. Once you press the button, the **Add Action** modal will appear for you to insert a new action:
+To add a new Action, press the&nbsp; <img className="inline-image" src="/img/action/add-action-button.png" height="25px" /> &nbsp;button on the **Actions** page. Once you press the button, the **Add Action** modal will appear for you to insert a new action:
 
-<img className="big-image" src="/docs/img/action/add-action-modal.png" height="300px" />
+<img className="big-image" src="/img/action/add-action-modal.png" height="300px" />
 
 In this modal, you must define a name, a [trigger](/action/trigger), and a [type](/action/type).

docs/resources/action/trigger.md

@@ -23,7 +23,7 @@ There are 2 (two) categories inside of this trigger type:
 ### Trigger Conditions
 After setting up the [Device](/device), you should set a condition for your Action to be executed.
 
-<img className="big-image" src="/docs/img/action/action-conditions.png" height="100px" />
+<img className="big-image" src="/img/action/action-conditions.png" height="100px" />
 
 1. **Select a variable** to be tested. This will be one of the variables that will be compared against the data from the device.
 2. **Define the type** of condition to test the variable. The available test conditions are:

docs/resources/analysis/console.md

@@ -27,14 +27,14 @@ If something goes wrong during this validation process, an error will be logged
 
 ## Clearing logs
 
-If you ever feel like there is too much information in your Console, feel free to click the &nbsp;<img src="/docs/img/icons/ban.svg" width="15px"/> &nbsp;button to hide all the logs and make room for new ones.
+If you ever feel like there is too much information in your Console, feel free to click the &nbsp;<img src="/img/icons/ban.svg" width="15px"/> &nbsp;button to hide all the logs and make room for new ones.
 
 Clearing logs is a temporary measure, all the logs will be back if you leave the Analysis' page and come back.
 
 
 ## Downloading logs
 
-TagoCore offers the possibility to download the logs of your Analysis by clicking the &nbsp;<img src="/docs/img/icons/download.svg" width="15px" /> &nbsp;button located in the Console header. The logs will be downloaded as a **.txt** file.
+TagoCore offers the possibility to download the logs of your Analysis by clicking the &nbsp;<img src="/img/icons/download.svg" width="15px" /> &nbsp;button located in the Console header. The logs will be downloaded as a **.txt** file.
 
 :::info
 Only the logs currently visible on the screen will be downloaded. If you clear the logs before downloading, the log file will be empty.

docs/resources/analysis/overview.md

@@ -11,9 +11,9 @@ Analysis is a powerful feature that experts and developers can use to implement
 
 ## Adding an Analysis
 
-To add a new Analysis, press the&nbsp; <img className="inline-image" src="/docs/img/analysis/add-analysis-button.png" height="25px" /> &nbsp;button on the **Analyses** page. Once you press the button, the **Add Analysis** modal will appear for you to insert a new Analysis:
+To add a new Analysis, press the&nbsp; <img className="inline-image" src="/img/analysis/add-analysis-button.png" height="25px" /> &nbsp;button on the **Analyses** page. Once you press the button, the **Add Analysis** modal will appear for you to insert a new Analysis:
 
-<img className="big-image" src="/docs/img/analysis/add-analysis-modal.png" height="200px" />
+<img className="big-image" src="/img/analysis/add-analysis-modal.png" height="200px" />
 
 In this modal, you must define a name for your Analysis in order to continue.
 
@@ -44,7 +44,7 @@ The File path field allows you to select a file that will be passed as a command
 
 Let's pretend you want to run code in Node.js. To achieve this, you could install [nvm](https://github.com/nvm-sh/nvm) in your local machine and then use the `node` executable provided by nvm in the **Binary executable path** field. After this, you may select a file in the **File path** field, like so:
 
-<img className="big-image" src="/docs/img/analysis/code-section.png" width="70%" />
+<img className="big-image" src="/img/analysis/code-section.png" width="70%" />
 
 Under the hood, TagoCore would use the following terminal command to run your analysis:
 

docs/resources/bucket/overview.md

@@ -14,8 +14,8 @@ When a [Device](/device) is created, TagoCore automatically creates a Bucket for
 
 ## Adding a Bucket
 
-To add a new Bucket, press the&nbsp; <img className="inline-image" src="/docs/img/bucket/add-bucket-button.png" height="25px" /> &nbsp;button on the **Buckets** page. Once you press the button, the **Add Bucket** modal will appear for you to insert a new bucket:
+To add a new Bucket, press the&nbsp; <img className="inline-image" src="/img/bucket/add-bucket-button.png" height="25px" /> &nbsp;button on the **Buckets** page. Once you press the button, the **Add Bucket** modal will appear for you to insert a new bucket:
 
-<img className="big-image" src="/docs/img/bucket/add-bucket-modal.png" height="400px" />
+<img className="big-image" src="/img/bucket/add-bucket-modal.png" height="400px" />
 
 In this modal, you must define a name and you can optionally define a [data retention](/bucket/data-retention) period for the [data](/bucket/data) in your Bucket.

docs/resources/device/live-inspector.md

@@ -10,7 +10,7 @@ Live Inspector is a useful tool for developers to debug [Payload Parser scripts]
 
 ## How to activate it
 
-To activate the Live Inspector of a Device, click the&nbsp; <img src="/docs/img/device/live-inspector-play-button.png" height="25px" /> &nbsp;button.
+To activate the Live Inspector of a Device, click the&nbsp; <img src="/img/device/live-inspector-play-button.png" height="25px" /> &nbsp;button.
 
 While the Live Inspector is active, all traffic related to the Device will be monitored in real time and each package sent will be recorded and displayed on the screen.
 
@@ -20,4 +20,4 @@ The Live Inspector will only stay activated while the Device page is open. It wi
 
 ## How to deactivate it
 
-To deactivate the Live Inspector of a Device, click the&nbsp; <img src="/docs/img/device/live-inspector-stop-button.png" height="25px" /> &nbsp;button.
+To deactivate the Live Inspector of a Device, click the&nbsp; <img src="/img/device/live-inspector-stop-button.png" height="25px" /> &nbsp;button.

docs/resources/device/overview.md

@@ -12,7 +12,7 @@ The default communication between external devices and TagoCore is done through
 
 ## Adding a Device
 
-To add a new device, press the&nbsp; <img className="inline-image" src="/docs/img/device/add-device-button.png" height="25px" /> &nbsp;button on the **Devices** page. Once you press the button, a new Device will automatically be created with the name **New Device**.
+To add a new device, press the&nbsp; <img className="inline-image" src="/img/device/add-device-button.png" height="25px" /> &nbsp;button on the **Devices** page. Once you press the button, a new Device will automatically be created with the name **New Device**.
 
 :::info
 When a Device is created, TagoCore automatically creates a [Bucket](/bucket) for it with the same name.

docs/resources/log.md

@@ -8,7 +8,7 @@ slug: /log
 
 Application Logs allow you to visualize the logs of the application and plugins.
 
-To access this page, click on the &nbsp;<img src="/docs/img/icons/scroll.svg" width="15px"/>&nbsp; button located on the upper right-hand corner of the screen.
+To access this page, click on the &nbsp;<img src="/img/icons/scroll.svg" width="15px"/>&nbsp; button located on the upper right-hand corner of the screen.
 
 
 ## Channel

docs/resources/settings.md

@@ -6,7 +6,7 @@ slug: /settings
 
 # Settings
 
-The settings page allows you to modify any configuration related to TagoCore. You can visit this page by clicking on the &nbsp;<img src="/docs/img/icons/cog.svg" width="15px"/>&nbsp; button on the sidebar.
+The settings page allows you to modify any configuration related to TagoCore. You can visit this page by clicking on the &nbsp;<img src="/img/icons/cog.svg" width="15px"/>&nbsp; button on the sidebar.
 
 Settings are saved to a `.yml` file located in the `tagocore` folder, which resides in your Operating System's `Home Directory`.