Rename core article sections and update toc

Author: glopesdev

articles/firmware-updates.md articles/firmware.mdarticles/firmware-updates.md renamed to articles/firmware.md

@@ -1,4 +1,6 @@
-# Firmware update
+# Firmware
+
+## Updating device firmware
 
 As `Harp Devices` are updated, new features are added and bugs are fixed. To ensure that your device is running the latest firmware, you can use the `Device Setup` tool available in Bonsai. This tool will be available with the `Bonsai.Harp.Design` package. To launch it, simply add a generic `Device` node to your workflow, and open its default editor (by double-clicking on the node). If an `Harp Device` is detected on the currently selected `COM port`, the following dialog will appear:
 

articles/getting-started.md

@@ -0,0 +1,15 @@
+# Getting started with Bonsai.Harp
+
+The process of setting up your system to be able to use the `Bonsai.Harp` package is simple, and documented in the next few steps:
+
+1. Install Bonsai (if not already installed) by following the instructions available [here](https://bonsai-rx.org/docs/articles/installation.html).
+
+2. Install the FTDI drivers necessary for the USB communication between Harp device and the host PC. For Windows, these can be found [here](https://www.ftdichip.com/old2020/Drivers/CDM/CDM%20v2.12.26%20WHQL%20Certified.zip).
+
+3. Download the latest release of the `Bonsai.Harp` package through the Bonsai Package Manager. [Detailed instructions can be found here.](https://bonsai-rx.org/docs/articles/packages.html) We also advise you to download the `Bonsai.Harp.Design` package that adds useful functionality to the package such has additional dialogs and visualizers.
+
+4. Install the device specific package for the Harp device you are using. First, change `package source` to `nuget.org` then, in the search bar, look for your device by typing: `harp.<device>`. For instance, for the Harp Behavior board, you would get:
+
+![HarpDevicePackage](~/images/behaviorpackage.png)
+
+5. The device nodes should now be available in the Bonsai Toolbox. You can now start using them in your workflows.

articles/intro.md

@@ -1,4 +1,30 @@
-# Manipulating timestamped streams
+# Manipulating `HarpMessage` objects
+
+## Modifying `HarpMessage` Fields
+
+So far, we have covered how to generate `HarpMessages` using a constructor operator (*i.e.* [`CreateMessage`](xref:Bonsai.Harp.CreateMessage)) or by using [`Format`](xref:Bonsai.Harp.Format) with compatible data types. However, in specific cases, we might want to take a given `HarpMessage` and simply change the value of one or more of it fields, for example its `Address`. While one could, in theory, [`Parse`](xref:Bonsai.Harp.Parse) the incoming message into its components and "reassemble" everything with the aforementioned operators, this tends to be too cumbersome. As an alternative, one can use a different overload of [`Format`](xref:Bonsai.Harp.Format) that takes an `HarpMessage` and replaces the value of one or more of its fields by non-null values defined in the properties of the operator. This overload is only available when the `Register` property of the [`Parse`](xref:Bonsai.Harp.Format) operator is set to [`FormatMessagePayload`](xref:Bonsai.Harp.FormatMessagePayload). For instance, if one would like to change the `Address` of an `HarpMessage`:
+
+:::workflow
+![ModifyHarpMessageAddress](~/workflows/modify-message-address.bonsai)
+:::
+
+It should be noted that multiple fields can be changed simultaneously by settings the corresponding property to a non-null value.
+
+## Injecting timestamps in `HarpMessage` `Payload`
+
+Finally, we can inject a timestamp into a `HarpMessage` by also using the [`Format`](xref:Bonsai.Harp.Format) operator. This is done by providing an input in the form of a `Timestamped<T>`, where `T` must be a compatible type. For instance, if one would want to set the timestamp of a given message to `0`:
+
+:::workflow
+![ModifyHarpMessageTimestampFromDouble](~/workflows/modify-message-double-timestamp.bonsai)
+:::
+
+Alternatively, one can also construct the [`Timestamped<T>`](xref:Bonsai.Harp.Timestamped) from another using another timestamped `HarpMessage`:
+
+:::workflow
+![ModifyHarpMessageTimestamp](~/workflows/modify-message-timestamp.bonsai)
+:::
+
+## Manipulating timestamped streams
 
 While the `Timestamped` portion of an Harp Message is optional, it is often useful to have access to it. After all, it provides temporal information on `Events` and `Commands`, and can be used to perform time-based operations on the data. The `Bonsai.Harp` library provides a set of operators that can be used to manipulate the `Timestamped` portion of a [`HarpMessage`](xref:Bonsai.Harp.HarpMessage).
 

articles/logging-harp-messages.md articles/logging.mdarticles/logging-harp-messages.md renamed to articles/logging.md

@@ -1,6 +1,6 @@
-# Bonsai.Harp
+# Operators
 
-All [Harp Devices](https://harp-tech.org/Devices/device_list.html) implement the [Harp Protocol](https://harp-tech.org/About/How-HARP-works/index.html) via which they can communicate with an host PC. The `Bonsai.Harp` library provides an implementation of the Harp protocol that can be used to interface with any Harp device.
+All [Harp Devices](https://harp-tech.org/Devices/device_list.html) implement the [Harp Protocol](https://harp-tech.org/About/How-HARP-works/index.html) to communicate with an host PC. The `Bonsai.Harp` library provides an implementation of the Harp protocol that can be used to interface with any Harp device.
 
 The `Bonsai.Harp` library provides the following operators:
 
@@ -13,7 +13,7 @@ It is crucial to understand the function of each of these operators as they are
 The [`Device`](xref:Bonsai.Harp.Device) operator is the first node you will probably add to your workflow when using any Harp Device. This source is responsible for establishing a serial connection link with the device and providing an interface that can be used to send and receive messages, represented by [`HarpMessage`](xref:Bonsai.Harp.HarpMessage) objects. Messages sent from the host application into the node represent commands to be sent to the device, whereas message objects emitted by the device node represent command replies or events sent by the device to the host.
 
 > [!Note]
-> The `Device` node also provides a default editor that allows you to configure core device settings and upload new firmware to the board in the form of `.hex` files. To open this dialog you can simply double-click the node while bonsai is not running.
+> The `Device` node also provides a default editor that allows you to configure core device settings and upload new firmware to the board in the form of `.hex` files. To open this dialog you can simply double-click the node while the workflow is not running.
 
 The current specification of the `Harp Protocol` defines three [`HarpMessage types`](xref:Bonsai.Harp.MessageType):
 

articles/manipulating-messages.md

@@ -1,9 +1,10 @@
 - name: Getting Started
-  href: harp-core.md
   items:
+    - name: Quickstart
+      href: intro.md
     - name: Operators
-      href: harp-core.md
+      href: operators.md
     - name: Firmware Updates
-      href: firmware-updates.md
+      href: firmware.md
     - name: Logging
-      href: logging-harp-messages.md
+      href: logging.md