Update technical section

src/data.js

@@ -26,8 +26,18 @@ export const headerData = {
       href: '/community',
     },
     {
-      text: 'Protocol',
-      href: '/protocol',
+      text: 'Technical',
+      href: '/technical',
+      links: [
+        {
+          text: 'Technical',
+          href: '/technical'
+        },
+        {
+          text: "Logging",
+          href: "/technical/logging"
+        }
+      ]
     }
   ],
   actions: [

src/pages/protocol/discovery.md → src/pages/technical/discovery.md

@@ -3,16 +3,14 @@ title: "Discovery"
 layout: ~/layouts/MarkdownLayout.astro
 ---
 
-## Bluetooth (BLe Beacon)
-
-### Public Beacon
+## Public Beacon
 | Type | Name | Description |
 | - | - | - |
 | `uint8` | ScenarioType | Must be `1` |
 | `uint8` | DeviceType | enum |
 | `uint8` | VersionAndFlags | `value >> 5 == 1` |
-| `uint8` | _Reserved_ | ?? |
+| `uint8` | DeviceStatus | ignored |
 | `uint8[6]` | MacAddress | Rfcomm connection |
 | `string` | DeviceName | Display-Name for discovery |
 
-[See `CdpAdvertiseOptions`](https://github.com/ShortDevelopment/Nearby-Sharing-Windows/blob/c499d39cb121f49431ae43aa932957dc604bf6ea/ShortDev.Microsoft.ConnectedDevices/Transports/CdpAdvertiseOptions.cs)
+[See `BLeBeacon.cs`](https://github.com/nearby-sharing/android/blob/ba8c66bd6f0a0d2ad8852969f01b427e75e653a2/ShortDev.Microsoft.ConnectedDevices/Transports/BLeBeacon.cs)

src/pages/technical/index.md

@@ -0,0 +1,16 @@
+---
+title: "Technical"
+layout: ~/layouts/MarkdownLayout.astro
+---
+
+## Discovery
+The sender discovers capable devices via a bluetooth-low-enery (BLE) [beacon](/technical/discovery).
+
+## Connection
+The sender connects to the mac-address (specified in beacon) via `Rfcomm`. If a user entered the wrong address, the connection will fail but the receiving device can still be found as the beacon is visible anyway.
+
+In order to connect two devices via the `cdp`-protocol the [connect messages](/technical/msgorder) have to be exchanged.
+During a successful connection the [encryption](/technical/encryption) is established.
+
+## Transport-Upgrade
+After the connection is established the implementations exchange a list of possible alternative transports (e.g. `WiFi` or `WiFiDirect`) and try to upgrade to the faster transports (i.e. `WiFi`).

src/pages/protocol/logging.md → src/pages/technical/logging.md

@@ -3,11 +3,14 @@ title: "Enable logging"
 layout: ~/layouts/MarkdownLayout.astro
 ---
 
+## Windows
+Windows 10 / 11 has the Connected-Devices-Platform build-in:
+
 Service: `CDPSvc`   
 Settings directory: `%LOCALAPPDATA%\ConnectedDevicesPlatform\`    
 Settings directory: `C:\Windows\ServiceProfiles\LocalService\AppData\Local\ConnectedDevicesPlatform`    
 
-## Enable Logging
+### Enable Logging
  1. Create `.\CDPGlobalSettings.cdp.override` with this content:
 ```json
 {
@@ -21,7 +24,7 @@ Get-Service *cdp* | Restart-Service
 ```
  3. See output at `.\CDPTraces.log`   
 
-## Trace via pipe
+### Trace via pipe
 ```
 \\\\.\\pipe\\CDPInOut
 ```