rename: data-management to data-handling

* Remove id and slug from pages where it was not necessary Signed-off-by: Mike Szczys <mike@golioth.io>
golioth · Nov 28, 2023 · 1bc914e · 1bc914e
1 parent 7deb245
commit 1bc914e
Show file tree

Hide file tree

Showing 76 changed files with 25 additions and 47 deletions.
diff --git a/...-data/1-lightdb-state/2-structure-data.md → ...-data/1-lightdb-state/2-structure-data.md b/...-data/1-lightdb-state/2-structure-data.md → ...-data/1-lightdb-state/2-structure-data.md
diff --git a/...data/1-lightdb-state/3-read-write-data.md → ...data/1-lightdb-state/3-read-write-data.md b/...data/1-lightdb-state/3-read-write-data.md → ...data/1-lightdb-state/3-read-write-data.md
diff --git a/...a/1-lightdb-state/4-simulating-devices.md → ...a/1-lightdb-state/4-simulating-devices.md b/...a/1-lightdb-state/4-simulating-devices.md → ...a/1-lightdb-state/4-simulating-devices.md
diff --git a/...t/1-stored-data/1-lightdb-state/README.md → ...g/1-stored-data/1-lightdb-state/README.md b/...t/1-stored-data/1-lightdb-state/README.md → ...g/1-stored-data/1-lightdb-state/README.md
@@ -1,7 +1,5 @@
 ---
-id: overview
 title: LightDB State Overview
-slug: /data-management/stored-data/lightdb-state
 ---
 
 ## What is LightDB?

diff --git a/...tored-data/1-lightdb-state/_category_.yml → ...tored-data/1-lightdb-state/_category_.yml b/...tored-data/1-lightdb-state/_category_.yml → ...tored-data/1-lightdb-state/_category_.yml
diff --git a/...d-data/4-lightdb-stream/2-sending-data.md → ...d-data/4-lightdb-stream/2-sending-data.md b/...d-data/4-lightdb-stream/2-sending-data.md → ...d-data/4-lightdb-stream/2-sending-data.md
diff --git a/...-data/4-lightdb-stream/3-querying-data.md → ...-data/4-lightdb-stream/3-querying-data.md b/...-data/4-lightdb-stream/3-querying-data.md → ...-data/4-lightdb-stream/3-querying-data.md
diff --git a/.../1-stored-data/4-lightdb-stream/README.md → .../1-stored-data/4-lightdb-stream/README.md b/.../1-stored-data/4-lightdb-stream/README.md → .../1-stored-data/4-lightdb-stream/README.md
@@ -1,7 +1,5 @@
 ---
-id: overview
 title: LightDB Stream Overview
-slug: /data-management/stored-data/lightdb-stream
 ---
 
 ## What is LightDB Stream?

diff --git a/...ored-data/4-lightdb-stream/_category_.yml → ...ored-data/4-lightdb-stream/_category_.yml b/...ored-data/4-lightdb-stream/_category_.yml → ...ored-data/4-lightdb-stream/_category_.yml
diff --git a/docs/data-management/1-stored-data/README.md → docs/data-handling/1-stored-data/README.md b/docs/data-management/1-stored-data/README.md → docs/data-handling/1-stored-data/README.md
@@ -1,7 +1,5 @@
 ---
-id: overview
 title: Data Storage on Golioth
-slug: /data-management/stored-data
 ---
 
 This is page describes two types of device data stored on Golioth:

diff --git a/...a-management/1-stored-data/_category_.yml → ...ata-handling/1-stored-data/_category_.yml b/...a-management/1-stored-data/_category_.yml → ...ata-handling/1-stored-data/_category_.yml
diff --git a/...gement/2-output-streams/1-mongo/README.md → ...ndling/2-output-streams/1-mongo/README.md b/...gement/2-output-streams/1-mongo/README.md → ...ndling/2-output-streams/1-mongo/README.md
diff --git a/...t/2-output-streams/1-mongo/_category_.yml → ...g/2-output-streams/1-mongo/_category_.yml b/...t/2-output-streams/1-mongo/_category_.yml → ...g/2-output-streams/1-mongo/_category_.yml
diff --git a/...streams/1-mongo/assets/add-ip-address.png → ...streams/1-mongo/assets/add-ip-address.png b/...streams/1-mongo/assets/add-ip-address.png → ...streams/1-mongo/assets/add-ip-address.png
diff --git a/...s/1-mongo/assets/atlas-connect-button.png → ...s/1-mongo/assets/atlas-connect-button.png b/...s/1-mongo/assets/atlas-connect-button.png → ...s/1-mongo/assets/atlas-connect-button.png
diff --git a/...-mongo/assets/atlas-connection-string.png → ...-mongo/assets/atlas-connection-string.png b/...-mongo/assets/atlas-connection-string.png → ...-mongo/assets/atlas-connection-string.png
diff --git a/...s/1-mongo/assets/atlas-network-access.png → ...s/1-mongo/assets/atlas-network-access.png b/...s/1-mongo/assets/atlas-network-access.png → ...s/1-mongo/assets/atlas-network-access.png
diff --git a/.../choosing-timeseries-additional-prefs.png → .../choosing-timeseries-additional-prefs.png b/.../choosing-timeseries-additional-prefs.png → .../choosing-timeseries-additional-prefs.png
diff --git a/...mongo/assets/create-collection-button.png → ...mongo/assets/create-collection-button.png b/...mongo/assets/create-collection-button.png → ...mongo/assets/create-collection-button.png
diff --git a/...1-mongo/assets/create-collection-form.png → ...1-mongo/assets/create-collection-form.png b/...1-mongo/assets/create-collection-form.png → ...1-mongo/assets/create-collection-form.png
diff --git a/...mongo/assets/create-outputstream-form.png → ...mongo/assets/create-outputstream-form.png b/...mongo/assets/create-outputstream-form.png → ...mongo/assets/create-outputstream-form.png
diff --git a/...s/1-mongo/assets/ip-access-list-entry.png → ...s/1-mongo/assets/ip-access-list-entry.png b/...s/1-mongo/assets/ip-access-list-entry.png → ...s/1-mongo/assets/ip-access-list-entry.png
diff --git a/...ms/1-mongo/assets/select-outputstream.png → ...ms/1-mongo/assets/select-outputstream.png b/...ms/1-mongo/assets/select-outputstream.png → ...ms/1-mongo/assets/select-outputstream.png
diff --git a/...mongo/assets/timefield-metafield-form.png → ...mongo/assets/timefield-metafield-form.png b/...mongo/assets/timefield-metafield-form.png → ...mongo/assets/timefield-metafield-form.png
diff --git a/...ment/2-output-streams/2-webhook/README.md → ...ling/2-output-streams/2-webhook/README.md b/...ment/2-output-streams/2-webhook/README.md → ...ling/2-output-streams/2-webhook/README.md
@@ -1,7 +1,5 @@
 ---
-id: overview
 title: Webhooks Overview
-slug: /data-management/output-streams/webhook
 ---
 
 Webhooks are a simple and flexible way to receive events from the Golioth platform using HTTP. It is really easy to build a web server to receive these events and you can write you own logic to process them.
@@ -17,9 +15,9 @@ For each Output Stream type, there is a set of specify attributes. Here are the
 
 ### Example
 
-As mentioned on [Output Streams Overview](/data-management/output-streams), events are sent using the [Cloud Events](https://cloudevents.io) format. For Webhooks specifically, some metadata of the event are sent as HTTP headers.
+As mentioned on [Output Streams Overview](/data-handling/output-streams), events are sent using the [Cloud Events](https://cloudevents.io) format. For Webhooks specifically, some metadata of the event are sent as HTTP headers.
 
-Here is an example of an event arriving on a webhook. Headers prefixed with `Ce-` are related to Cloud Events and the message body is the event payload (see event payloads on [Output Streams Event Types](/data-management/output-streams/event-types/events)).
+Here is an example of an event arriving on a webhook. Headers prefixed with `Ce-` are related to Cloud Events and the message body is the event payload (see event payloads on [Output Streams Event Types](/data-handling/output-streams/event-types/events)).
 
 ```
 POST {your-uri-path} HTTP/1.1

diff --git a/...2-output-streams/2-webhook/_category_.yml → ...2-output-streams/2-webhook/_category_.yml b/...2-output-streams/2-webhook/_category_.yml → ...2-output-streams/2-webhook/_category_.yml
diff --git a/...utput-streams/3-azure-event-hub/README.md → ...utput-streams/3-azure-event-hub/README.md b/...utput-streams/3-azure-event-hub/README.md → ...utput-streams/3-azure-event-hub/README.md
@@ -1,7 +1,5 @@
 ---
-id: overview
 title: Azure Event Hub Overview
-slug: /data-management/output-streams/azure-event-hub
 ---
 
 Azure Event Hub is a fully managed, real-time data ingestion service that can be used to consume Golioth events in a simple, trusted, and scalable way. You can ingest data in multiple ways inside Azure with support for popular protocols, including AMQP, HTTPS, and Apache Kafka. You can also consume Azure Event Hub in a serverless manner using Azure Functions.
@@ -33,9 +31,9 @@ To use this integration, you need to create an Event Hub on Azure and get the co
 
 ### Example
 
-As mentioned on [Output Streams Overview](/data-management/output-streams), events are sent using [Cloud Events](https://cloudevents.io) format. For Azure Event Hub, some metadata of the event are sent together with the message body.
+As mentioned on [Output Streams Overview](/data-handling/output-streams), events are sent using [Cloud Events](https://cloudevents.io) format. For Azure Event Hub, some metadata of the event are sent together with the message body.
 
-Here is an example of an event arriving on Event Hub. The payload will be inside a `data` attribute (see event payloads on [Output Streams Event Types](/data-management/output-streams/event-types/events)). The other attributes are metadata related to Cloud Events.
+Here is an example of an event arriving on Event Hub. The payload will be inside a `data` attribute (see event payloads on [Output Streams Event Types](/data-handling/output-streams/event-types/events)). The other attributes are metadata related to Cloud Events.
 
 ```json
 {

diff --git a/...-streams/3-azure-event-hub/_category_.yml → ...-streams/3-azure-event-hub/_category_.yml b/...-streams/3-azure-event-hub/_category_.yml → ...-streams/3-azure-event-hub/_category_.yml
diff --git a/...ment/2-output-streams/4-aws-sqs/README.md → ...ling/2-output-streams/4-aws-sqs/README.md b/...ment/2-output-streams/4-aws-sqs/README.md → ...ling/2-output-streams/4-aws-sqs/README.md
@@ -1,7 +1,5 @@
 ---
-id: overview
 title: AWS SQS Overview
-slug: /data-management/output-streams/aws-sqs
 ---
 
 Amazon Simple Queue Service (SQS) is a fully managed message queuing service that enables you receive events generated on the Golioth platform that can be processed in a decoupled and scalable way. SQS eliminates the complexity and overhead associated with managing and operating message-oriented middleware systems. Data can be ingested using multiple solutions inside of AWS, including Serverless offerings like AWS Lambda.
@@ -55,9 +53,9 @@ To use this integration, you need to create an SQS Queue and and a user with per
 
 ### Example
 
-As mentioned on the [Output Streams Overview](/data-management/output-streams), events are sent using the [Cloud Events](https://cloudevents.io) format. For AWS SQS, some metadata of the event are sent together with the message body.
+As mentioned on the [Output Streams Overview](/data-handling/output-streams), events are sent using the [Cloud Events](https://cloudevents.io) format. For AWS SQS, some metadata of the event are sent together with the message body.
 
-Here is an example of an event arriving on SQS. The payload is going to be inside of a `data` attribute (see event payloads on [Output Streams Event Types](/data-management/output-streams/event-types/events)). The other attributes are metadata related to Cloud Events.
+Here is an example of an event arriving on SQS. The payload is going to be inside of a `data` attribute (see event payloads on [Output Streams Event Types](/data-handling/output-streams/event-types/events)). The other attributes are metadata related to Cloud Events.
 
 ```json
 {

diff --git a/...2-output-streams/4-aws-sqs/_category_.yml → ...2-output-streams/4-aws-sqs/_category_.yml b/...2-output-streams/4-aws-sqs/_category_.yml → ...2-output-streams/4-aws-sqs/_category_.yml
diff --git a/...put-streams/4-aws-sqs/assets/msg-body.png → ...put-streams/4-aws-sqs/assets/msg-body.png b/...put-streams/4-aws-sqs/assets/msg-body.png → ...put-streams/4-aws-sqs/assets/msg-body.png
diff --git a/...t-streams/4-aws-sqs/assets/msg-header.png → ...t-streams/4-aws-sqs/assets/msg-header.png b/...t-streams/4-aws-sqs/assets/msg-header.png → ...t-streams/4-aws-sqs/assets/msg-header.png
diff --git a/...t/2-output-streams/5-gcp-pubsub/README.md → ...g/2-output-streams/5-gcp-pubsub/README.md b/...t/2-output-streams/5-gcp-pubsub/README.md → ...g/2-output-streams/5-gcp-pubsub/README.md
@@ -1,7 +1,5 @@
 ---
-id: overview
 title:  Google Cloud Platform (GCP) PubSub Overview
-slug: /data-management/output-streams/gcp-pubsub
 ---
 
 [Google Cloud PubSub](https://cloud.google.com/pubsub/) works as a messaging middleware for traditional service integration or a simple communication medium for modern microservices. Events can be ingested with serverless environments like Cloud Functions, Cloud Run or custom environments on Google Kubernetes Engine or Compute Engine.
@@ -108,7 +106,7 @@ Go the [Golioth Platform](https://console.golioth.io), log in and select your Pr
 
 Golioth Output Streams use the [Cloud Events](https://cloudevents.io) format. For GCP PubSub, this means some metadata of the event are sent together with the message body.
 
-Here is an example of an event arriving on PubSub. The payload will be inside a `data` attribute (see event payloads on [Output Streams Event Types](/data-management/output-streams/event-types/events)). The other attributes are metadata related to Cloud Events.
+Here is an example of an event arriving on PubSub. The payload will be inside a `data` attribute (see event payloads on [Output Streams Event Types](/data-handling/output-streams/event-types/events)). The other attributes are metadata related to Cloud Events.
 
 ```json
 {

diff --git a/...utput-streams/5-gcp-pubsub/_category_.yml → ...utput-streams/5-gcp-pubsub/_category_.yml b/...utput-streams/5-gcp-pubsub/_category_.yml → ...utput-streams/5-gcp-pubsub/_category_.yml
diff --git a/...pubsub/assets/gcp-created-service-acc.png → ...pubsub/assets/gcp-created-service-acc.png b/...pubsub/assets/gcp-created-service-acc.png → ...pubsub/assets/gcp-created-service-acc.png
diff --git a/...bsub/assets/gcp-detailing-service-acc.png → ...bsub/assets/gcp-detailing-service-acc.png b/...bsub/assets/gcp-detailing-service-acc.png → ...bsub/assets/gcp-detailing-service-acc.png
diff --git a/...sub/assets/gcp-iam-create-service-acc.png → ...sub/assets/gcp-iam-create-service-acc.png b/...sub/assets/gcp-iam-create-service-acc.png → ...sub/assets/gcp-iam-create-service-acc.png
diff --git a/...p-pubsub/assets/gcp-pubsub-topic-name.png → ...p-pubsub/assets/gcp-pubsub-topic-name.png b/...p-pubsub/assets/gcp-pubsub-topic-name.png → ...p-pubsub/assets/gcp-pubsub-topic-name.png
diff --git a/...5-gcp-pubsub/assets/gcp-pubsub-topics.png → ...5-gcp-pubsub/assets/gcp-pubsub-topics.png b/...5-gcp-pubsub/assets/gcp-pubsub-topics.png → ...5-gcp-pubsub/assets/gcp-pubsub-topics.png
diff --git a/...golioth-creating-pubsub-output-stream.png → ...golioth-creating-pubsub-output-stream.png b/...golioth-creating-pubsub-output-stream.png → ...golioth-creating-pubsub-output-stream.png
diff --git a/...bsub/assets/golioth-gcp-output-stream.png → ...bsub/assets/golioth-gcp-output-stream.png b/...bsub/assets/golioth-gcp-output-stream.png → ...bsub/assets/golioth-gcp-output-stream.png
diff --git a/...ent/2-output-streams/6-datacake/README.md → ...ing/2-output-streams/6-datacake/README.md b/...ent/2-output-streams/6-datacake/README.md → ...ing/2-output-streams/6-datacake/README.md
@@ -1,7 +1,5 @@
 ---
-id: overview
 title: Datacake Overview
-slug: /data-management/output-streams/datacake
 ---
 
 [Datacake](https://datacake.co/) is a multi-purpose, low-code IoT platform that requires no programming skills and minimal time to create custom IoT applications that can be brought into a white label IoT solution at the push of a button.
@@ -40,7 +38,7 @@ In this tutorial you will see how to:
 
 Golioth Output Streams use the [Cloud Events](https://cloudevents.io) format. For Datacake, this means some metadata of the event are sent as HTTP headers.
 
-Here is an example of an event arriving on Datcake. Headers prefixed with `Ce-` are related to Cloud Events and the message body is the event payload (see event payloads on [Output Streams Event Types](/data-management/output-streams/event-types/events)).
+Here is an example of an event arriving on Datcake. Headers prefixed with `Ce-` are related to Cloud Events and the message body is the event payload (see event payloads on [Output Streams Event Types](/data-handling/output-streams/event-types/events)).
 
 
 ```

diff --git a/...-output-streams/6-datacake/_category_.yml → ...-output-streams/6-datacake/_category_.yml b/...-output-streams/6-datacake/_category_.yml → ...-output-streams/6-datacake/_category_.yml
diff --git a/...ment/2-output-streams/7-ubidots/README.md → ...ling/2-output-streams/7-ubidots/README.md b/...ment/2-output-streams/7-ubidots/README.md → ...ling/2-output-streams/7-ubidots/README.md
@@ -1,7 +1,5 @@
 ---
-id: overview
 title: Ubidots Overview
-slug: /data-management/output-streams/ubidots
 ---
 
 [Ubidots](https://ubidots.com/) makes it easy to white-label visualizations to produce a
@@ -46,7 +44,7 @@ In this tutorial you will see how to:
 
 Golioth Output Streams use the [Cloud Events](https://cloudevents.io) format. For Ubidots, this means some metadata of the event are sent as HTTP headers.
 
-Here is an example of an event arriving on Ubidots. Headers prefixed with `Ce-` are related to Cloud Events and the message body is the event payload (see event payloads on [Output Streams Event Types](/data-management/output-streams/event-types/events)).
+Here is an example of an event arriving on Ubidots. Headers prefixed with `Ce-` are related to Cloud Events and the message body is the event payload (see event payloads on [Output Streams Event Types](/data-handling/output-streams/event-types/events)).
 
 ```
 POST {your-uri-path} HTTP/1.1

diff --git a/...2-output-streams/7-ubidots/_category_.yml → ...2-output-streams/7-ubidots/_category_.yml b/...2-output-streams/7-ubidots/_category_.yml → ...2-output-streams/7-ubidots/_category_.yml
diff --git a/...ement/2-output-streams/8-influx/README.md → ...dling/2-output-streams/8-influx/README.md b/...ement/2-output-streams/8-influx/README.md → ...dling/2-output-streams/8-influx/README.md
@@ -1,7 +1,5 @@
 ---
-id: overview
 title: InfluxDB Overview
-slug: /data-management/output-streams/influxdb
 ---
 
 [InfluxDB Cloud](https://www.influxdata.com/products/influxdb-cloud/) is a

diff --git a/.../2-output-streams/8-influx/_category_.yml → .../2-output-streams/8-influx/_category_.yml b/.../2-output-streams/8-influx/_category_.yml → .../2-output-streams/8-influx/_category_.yml
diff --git a/...eams/8-influx/assets/2023-07-20_15-37.png → ...eams/8-influx/assets/2023-07-20_15-37.png b/...eams/8-influx/assets/2023-07-20_15-37.png → ...eams/8-influx/assets/2023-07-20_15-37.png
diff --git a/...utput-streams/8-influx/assets/buckets.png → ...utput-streams/8-influx/assets/buckets.png b/...utput-streams/8-influx/assets/buckets.png → ...utput-streams/8-influx/assets/buckets.png
diff --git a/...t-streams/8-influx/assets/cluster-url.png → ...t-streams/8-influx/assets/cluster-url.png b/...t-streams/8-influx/assets/cluster-url.png → ...t-streams/8-influx/assets/cluster-url.png
diff --git a/...nflux/assets/create-outputstream-form.png → ...nflux/assets/create-outputstream-form.png b/...nflux/assets/create-outputstream-form.png → ...nflux/assets/create-outputstream-form.png
diff --git a/...8-influx/assets/generate-token-button.png → ...8-influx/assets/generate-token-button.png b/...8-influx/assets/generate-token-button.png → ...8-influx/assets/generate-token-button.png
diff --git a/...treams/8-influx/assets/generate-token.png → ...treams/8-influx/assets/generate-token.png b/...treams/8-influx/assets/generate-token.png → ...treams/8-influx/assets/generate-token.png
diff --git a/...treams/8-influx/assets/load-data-menu.png → ...treams/8-influx/assets/load-data-menu.png b/...treams/8-influx/assets/load-data-menu.png → ...treams/8-influx/assets/load-data-menu.png
diff --git a/...ams/8-influx/assets/org-settings-menu.png → ...ams/8-influx/assets/org-settings-menu.png b/...ams/8-influx/assets/org-settings-menu.png → ...ams/8-influx/assets/org-settings-menu.png
diff --git a/...s/8-influx/assets/select-outputstream.png → ...s/8-influx/assets/select-outputstream.png b/...s/8-influx/assets/select-outputstream.png → ...s/8-influx/assets/select-outputstream.png
diff --git a/...ams/8-influx/assets/token-create-form.png → ...ams/8-influx/assets/token-create-form.png b/...ams/8-influx/assets/token-create-form.png → ...ams/8-influx/assets/token-create-form.png
diff --git a/...output-streams/9-event-types/2-events.mdx → ...output-streams/9-event-types/2-events.mdx b/...output-streams/9-event-types/2-events.mdx → ...output-streams/9-event-types/2-events.mdx
diff --git a/.../2-output-streams/9-event-types/README.md → .../2-output-streams/9-event-types/README.md b/.../2-output-streams/9-event-types/README.md → .../2-output-streams/9-event-types/README.md
@@ -1,7 +1,7 @@
 ---
 id: overview
 title: Event Types Overview
-slug: /data-management/output-streams/event-types
+slug: event-types
 ---
 
 The Golioth platform uses Cloud Events to communicate between services internally. With the Output Stream feature, we are making some of those events available for users to consume for use in their own applications.

diff --git a/...tput-streams/9-event-types/_category_.yml → ...tput-streams/9-event-types/_category_.yml b/...tput-streams/9-event-types/_category_.yml → ...tput-streams/9-event-types/_category_.yml
diff --git a/...ata-management/2-output-streams/README.md → .../data-handling/2-output-streams/README.md b/...ata-management/2-output-streams/README.md → .../data-handling/2-output-streams/README.md
@@ -1,7 +1,5 @@
 ---
-id: overview
 title: Output Streams Overview
-slug: /data-management/output-streams
 ---
 
 Output Streams are a feature of the Golioth platform that allows users to integrate their data seamlessly with a number of external services.
diff --git a/...anagement/2-output-streams/_category_.yml → ...-handling/2-output-streams/_category_.yml b/...anagement/2-output-streams/_category_.yml → ...-handling/2-output-streams/_category_.yml
diff --git a/...management/2-output-streams/messages.json → ...a-handling/2-output-streams/messages.json b/...management/2-output-streams/messages.json → ...a-handling/2-output-streams/messages.json
diff --git a/docs/data-management/README.md → docs/data-handling/README.md b/docs/data-management/README.md → docs/data-handling/README.md
@@ -1,6 +1,6 @@
 ---
-title: Golioth Data Management
-slug: /data-management
+title: Golioth Data Handling
+slug: /data-handling
 sidebar_position: 0
 ---
 

diff --git a/...utput-streams_azure-event-hub-connect.png → ...utput-streams_azure-event-hub-connect.png b/...utput-streams_azure-event-hub-connect.png → ...utput-streams_azure-event-hub-connect.png
diff --git a/...t-streams_azure-event-hub-send-policy.png → ...t-streams_azure-event-hub-send-policy.png b/...t-streams_azure-event-hub-send-policy.png → ...t-streams_azure-event-hub-send-policy.png
diff --git a/...streams_azure-event-hub-shared-access.png → ...streams_azure-event-hub-shared-access.png b/...streams_azure-event-hub-shared-access.png → ...streams_azure-event-hub-shared-access.png
diff --git a/...ware/hardware/5-virtual-device/2-zephyr-quickstart/3-simulating-devices-coap.md b/...ware/hardware/5-virtual-device/2-zephyr-quickstart/3-simulating-devices-coap.md
@@ -119,4 +119,4 @@ testing. We recommend using `coap` when first working on LightDB data storage
 and retrieval. The interactive nature makes it easy to test your schema before
 moving to embedded devices.
 
-Examples of using `coap` with LightDB are [found in the Cloud documentation](/data-management/stored-data/lightdb-state/read-write-data).
+Examples of using `coap` with LightDB are [found in the Cloud documentation](/data-handling/stored-data/lightdb-state/read-write-data).
diff --git a/docs/firmware/zephyr-device-sdk/light-db-stream/README.md b/docs/firmware/zephyr-device-sdk/light-db-stream/README.md
@@ -7,4 +7,4 @@ LightDB Stream is a persistent database service hosted by Golioth. The LightDB S
 
 ![Console](../assets/lightDB-stream-svg-a4.svg)
 
-Checkout the [LightDB Stream](https://docs.golioth.io/data-management/lightdb-stream/) guide for a walkthrough of the sample demonstrating the firmware calls used to interact with the Golioth LightDB Stream service.
+Checkout the [LightDB Stream](https://docs.golioth.io/data-handling/lightdb-stream/) guide for a walkthrough of the sample demonstrating the firmware calls used to interact with the Golioth LightDB Stream service.
diff --git a/docs/reference/2-protocols/1-coap/3-lightdb.md b/docs/reference/2-protocols/1-coap/3-lightdb.md
@@ -3,11 +3,11 @@ id: lightdb
 title: LightDB
 ---
 
-[LightDB Device Service](/data-management/stored-data/lightdb-state) definitions over CoAP.
+[LightDB Device Service](/data-handling/stored-data/lightdb-state) definitions over CoAP.
 
 How to use guides:
 
-- [Read Write Data](/data-management/stored-data/lightdb-state/read-write-data)
+- [Read Write Data](/data-handling/stored-data/lightdb-state/read-write-data)
 
 ### Interface
 

diff --git a/docs/reference/2-protocols/1-coap/4-lightdb-stream.md b/docs/reference/2-protocols/1-coap/4-lightdb-stream.md
@@ -3,11 +3,11 @@ id: lightdb-stream
 title: LightDB Stream
 ---
 
-[LightDB Stream Device Service](/data-management/stored-data/lightdb-stream) definitions over CoAP.
+[LightDB Stream Device Service](/data-handling/stored-data/lightdb-stream) definitions over CoAP.
 
 How to use guides:
 
-- [Sending Data](/data-management/stored-data/lightdb-stream/sending-data)
+- [Sending Data](/data-handling/stored-data/lightdb-stream/sending-data)
 
 ### Interface
 

diff --git a/docs/reference/2-protocols/1-coap/7-limits.md b/docs/reference/2-protocols/1-coap/7-limits.md
@@ -11,7 +11,7 @@ Golioth servers enforce the following limit on CoAP requests:
 
 When passing frequent readings from a single device to Golioth (greater than 1
 Hz) we recommend sending in batches. As noted for the [LightDB Stream
-service](/data-management/stored-data/lightdb-stream/sending-data), your device
+service](/data-handling/stored-data/lightdb-stream/sending-data), your device
 can add timestamps to data packets by using `t`, `ts`, or `time` as the key. The
 Golioth LightDB Stream service will use the timestamp for the database entry
 instead of the time received.

diff --git a/docs/reference/4-websocket/3-Endpoints/1-lightdb.md b/docs/reference/4-websocket/3-Endpoints/1-lightdb.md
@@ -3,7 +3,7 @@ id: lightdb
 title: LightDB
 ---
 
-[LightDB Device Service](/data-management/stored-data/lightdb-state) definitions.
+[LightDB Device Service](/data-handling/stored-data/lightdb-state) definitions.
 
 Real-time endpoint to listen to any changes in a device state path.
 

diff --git a/docs/reference/4-websocket/3-Endpoints/2-lightdb-stream.md b/docs/reference/4-websocket/3-Endpoints/2-lightdb-stream.md
@@ -3,7 +3,7 @@ id: lightdb-stream
 title: LightDB Stream
 ---
 
-[LightDB Stream Device Service](/data-management/stored-data/lightdb-stream) definitions.
+[LightDB Stream Device Service](/data-handling/stored-data/lightdb-stream) definitions.
 
 Real-time endpoint to listen to a device's data stream as it arrives at the Golioth Cloud.
 

diff --git a/docusaurus.config.js b/docusaurus.config.js
@@ -40,9 +40,9 @@ module.exports = {
           position: "left",
         },
         {
-          to: "data-management",
-          activeBasePath: "data-management",
-          label: "Data Management",
+          to: "data-handling",
+          activeBasePath: "data-handling",
+          label: "Data Handling",
           position: "left",
         },
         {

diff --git a/sidebars.js b/sidebars.js
@@ -40,7 +40,7 @@ const devicemanagement = [
 const datamanagement = [
   {
     type: 'autogenerated',
-    dirName: 'data-management',
+    dirName: 'data-handling',
   },
 ]
Original file line number	Diff line number	Diff line change
Expand Up		@@ -7,4 +7,4 @@ LightDB Stream is a persistent database service hosted by Golioth. The LightDB S

		![Console](../assets/lightDB-stream-svg-a4.svg)

		Checkout the [LightDB Stream](https://docs.golioth.io/data-management/lightdb-stream/) guide for a walkthrough of the sample demonstrating the firmware calls used to interact with the Golioth LightDB Stream service.
		Checkout the [LightDB Stream](https://docs.golioth.io/data-handling/lightdb-stream/) guide for a walkthrough of the sample demonstrating the firmware calls used to interact with the Golioth LightDB Stream service.