fix broken links

Author: smrz2001

.github/workflows/build-deploy-docs.yml

@@ -35,7 +35,7 @@ jobs:
 
       - name: Deploy to GitHub Pages
         if: github.event_name == 'push' || github.event_name == 'workflow_dispatch'
-        uses: peaceiris/actions-gh-pages@v3
+        uses: peaceiris/actions-gh-pages@v4
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}
           publish_dir: ./build

docs/composedb/core-concepts.mdx

@@ -58,7 +58,7 @@ type Posts @createModel(accountRelation: LIST, description: "A simple Post") {
 
 #### Account to Model Relations
 
-Any document can always be queried by its author's account using the required `accountRelation` property. See [Account to Model Relations](./guides/data-modeling/relations.mdx#account-to-model-relations) for more.
+Any document can always be queried by its author's account using the required `accountRelation` property. See [Account to Model Relations](./guides/data-modeling/relations.mdx#account-to-model) for more.
 
 ##### Model
 
@@ -85,7 +85,7 @@ Let's query the `DisplayName` using the author's account:
 
 #### Model to Account Relations
 
-Enable a document to be queried by a referenced account using the `@accountReference` directive. See [Model to Account Relations](./guides/data-modeling/relations.mdx#model-to-account-relations) for more.
+Enable a document to be queried by a referenced account using the `@accountReference` directive. See [Model to Account Relations](./guides/data-modeling/relations.mdx#model-to-account) for more.
 
 ##### Model
 
@@ -113,7 +113,7 @@ Let's query messages based on recipient using `@accountReference`:
 
 #### Model to Model Relations
 
-Enable a document to be queried by its relationship to other documents using the `@documentReference` and `@relationFrom` directives. See [Model to Model Relations](./guides/data-modeling/relations.mdx#model-to-model-relations) for more.
+Enable a document to be queried by its relationship to other documents using the `@documentReference` and `@relationFrom` directives. See [Model to Model Relations](./guides/data-modeling/relations.mdx#model-to-model) for more.
 
 ##### Model
 

docs/composedb/guides/composedb-server/running-in-the-cloud.mdx

@@ -323,7 +323,7 @@ docker run -d \
 
 ### Editing the `daemon.config.json` file
 
-To have the settings persist in your Ceramic node, edit the `daemon.config.json` file to include the configurations. The default location is `~/.ceramic/daemon.config.json`. For a full file example, see the [Ceramic](../../../protocol/js-ceramic/guides/ceramic-nodes/running-cloud#example-daemonconfigjson) docs.
+To have the settings persist in your Ceramic node, edit the `daemon.config.json` file to include the configurations. The default location is `~/.ceramic/daemon.config.json`. For a full file example, see the [Ceramic](./server-configurations#default-configurations) docs.
 
 ```bash
 ...

docs/composedb/guides/composedb-server/server-configurations.mdx

@@ -192,16 +192,14 @@ Only Postgres is currently supported for production usage.
 | remote | IPFS running in separate compute process; recommended for production and everything besides early prototyping | ✅  |
 
 ### Persistent Storage
-To run a Ceramic node in production, it is critical to persist the [Ceramic state store](../../../protocol/js-ceramic/guides/ceramic-nodes/running-cloud#ceramic-state-store) and the [IPFS datastore](https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#datastorespec). The form of storage you choose should also be configured for disaster recovery with data redundancy, and some form of snapshotting and/or backups.
+To run a Ceramic node in production, it is critical to persist the [Ceramic state store](#ceramic-state-store) and the [IPFS datastore](https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#datastorespec). The form of storage you choose should also be configured for disaster recovery with data redundancy, and some form of snapshotting and/or backups.
 
 **Loss of this data can result in permanent loss of Ceramic streams and will cause your node to be in a corrupt state.**
 
 The Ceramic state store and IPFS datastore are stored on your machine's filesystem by default. The Ceramic state store defaults to `$HOME/.ceramic/statestore`. The IPFS datastore defaults to `ipfs/blocks` located wherever you run IPFS.
 
 The fastest way to ensure data persistence is by mounting a persistent volume to your instances and configuring the Ceramic and IPFS nodes to write to the mount location. The mounted volume should be configured such that the data persists if the instance shuts down.
 
-You can also use AWS S3 for data storage which is supported for both Ceramic and IPFS. Examples of the configuration are shared on the Ceramic docs [here](../../../protocol/js-ceramic/guides/ceramic-nodes/running-cloud#example-aws-s3-policies).
-
 ### IPFS Datastore
 
 The IPFS datastore stores the raw IPFS blocks that make up Ceramic streams. To prevent data corruption, use environment variables written to your profile file, or otherwise injected into your environment on start so that the datastore location does not change between reboots.

docs/composedb/set-up-your-environment.mdx

@@ -17,11 +17,11 @@ By the end of this guide you'll have a good understanding of how to get started
 
 There are a few ways to set up your environment. Choose the one that best fits your needs:
 
-- [Using `create-ceramic-app`](#installation-using-create-ceramic-app) - get up and running quickly with a basic ComposeDB application with one command. Good for the first quick experience with Ceramic and ComposeDB.
-- [Using the Wheel](#installation-using-wheel) - the recommended and the easiest way to configure your full working environment and install the necessary dependencies.
-- [Using JavaScript package managers](#installation-using-javascript-package-managers) - an alternative, more manual, way to configure your working environment which supports `npm`, `pnpm` and `yarn`.
+- [Using `create-ceramic-app`](#2a-installation-using-create-ceramic-app) - get up and running quickly with a basic ComposeDB application with one command. Good for the first quick experience with Ceramic and ComposeDB.
+- [Using the Wheel](#2b-installation-using-wheel) - the recommended and the easiest way to configure your full working environment and install the necessary dependencies.
+- [Using JavaScript package managers](#2c-installation-using-javascript-package-managers) - an alternative, more manual, way to configure your working environment which supports `npm`, `pnpm` and `yarn`.
 
-**Install and start the `ceramic-one` binary**
+##### Install and start the `ceramic-one` binary
 
 All of the configuration options listed above **require a `ceramic-one` binary up and running**, which provides a data network access. You can run `ceramic-one` on your
 local machine using two simple steps listed below.
@@ -145,7 +145,7 @@ The easiest and recommended way to configure your full local development environ
 
 In order to use Wheel, you’ll have to install a few dependencies:
 
-→ **Node.js**
+##### Node.js
 
 If you don’t already have them installed, you will need to install at least:
 
@@ -159,12 +159,12 @@ node -v
 npm -v
 ```
 
-→ **jq**
+##### jq
 
 `jq` is a lightweight and flexible command-line JSON processor. The installation method depends on your operating system. Install it using one of the methods defined in
 the [official tutorial here](https://stedolan.github.io/jq/download/).
 
-→ **PostgreSQL** (optional)
+##### PostgreSQL (optional)
 
 PostgreSQL is only required for a production configuration on the Mainnet. If you are new to ComposeDB on Ceramic and would like to quickly test it out, you can skip the PostgreSQL installation and come back to it once you are ready to scale your project. You will need Postgres installed on your machine to store indexed data.
 
@@ -311,7 +311,7 @@ Check out [this video tutorial](https://www.youtube.com/watch?v=r68FXBTCBZ4) for
 </table>
 
 Another way to install the dependencies and configure Ceramic is using JavaScript package managers. This option requires more manual steps. The guide below covers this
-process step-by-step. If you have followed the [Wheel installation](#installation-using-wheel) guide above, you can skip this section.
+process step-by-step. If you have followed the [Wheel installation](#2b-installation-using-wheel) guide above, you can skip this section.
 
 #### Install the dependencies
 
@@ -322,7 +322,7 @@ mkdir my-project #creates a new directory
 cd my-project #targets the created directory
 ```
 
-→ **Node.js**
+##### Node.js
 
 If you don’t already have them installed, you will need to install Node.js v20 and a package manager. We primarily use `pnpm`, but `npm` and `yarn` are supported as well.
 
@@ -336,11 +336,11 @@ node -v
 pnpm -v
 ```
 
-→ **ceramic-one**
+##### ceramic-one
 
 Make sure you have the `ceramic-one` binary up and running. To do that, follow the steps listed [here](#2-installation).
 
-→ **Ceramic**
+##### Ceramic
 
 ComposeDB runs on Ceramic, so you will need to run a Ceramic node. To get started, we recommend running a local Ceramic node. If you're interested in running the production node, you can follow one of the [guides here](./guides/composedb-server/).
 
@@ -383,7 +383,7 @@ yarn global add @ceramicnetwork/cli
   </TabItem>
 </Tabs>
 
-→ **ComposeDB**
+##### ComposeDB
 
 Next install the ComposeDB CLI, which enables you to interact with ComposeDB data from your terminal:
 
@@ -476,7 +476,7 @@ yarn add -D @composedb/devtools@^0.5.0 @composedb/devtools-node@^0.5.0
 
 All dependencies are installed. Now you can start setting up your project. The first step is to run a local Ceramic node.
 
-→ **Run a Ceramic node**
+##### Run a Ceramic node
 
 You can check that everything was installed correctly by spinning up a Ceramic node. Running the command below will start the Ceramic node in local mode and connect to Clay testnet.
 Indexing is a key component of ComposeDB, which syncs data across nodes. Enable indexing by toggling:
@@ -523,7 +523,7 @@ IMPORTANT: Ceramic API running on 0.0.0.0:7007
 Now, that you have installed everything successfully and are able to run the node, let's create a developer account. You can stop
 the node for now by using the keyboard combination `Control+C`.
 
-→ **Generate your private key**
+##### Generate your private key
 
 You will need a private key for authorizing ComposeDB CLI commands in the later stages of development. You can generate it using the command below:
 
@@ -546,7 +546,7 @@ Store your private key securely - the key allows changes to be made to your app.
 
 :::
 
-→ **Generate your account**
+##### Generate your account
 
 Indexing is one of the key features of ComposeDB. In order to notify the Ceramic node which models have to be indexed, the ComposeDB tools have to interact with the restricted Admin API. Calling the API requires an authenticated Decentralized Identifier (DID) to be provided in the node configuration file. Create a DID by running the following command, using the private key generated previously instead of the placeholder variable `your-private-key`:
 
@@ -581,7 +581,7 @@ cd ~/.ceramic
 Inside of this directory you should find the following files:
 
 - `daemon.config.json` - your Ceramic node configuration file
-- `statestore` - a local directory for [persisting the data](../protocol/js-ceramic/guides/ceramic-nodes/running-cloud#ceramic-state-store)
+- `statestore` - a local directory for [persisting the data](./guides/composedb-server/server-configurations#ceramic-state-store)
 
 Open the `daemon.config.json` file using your preferred code editor and provide the authenticated DID, generated in the [generate your account](#generate-your-account) step of this guide, in the `admin-dids` section of the file as shown in the example below:
 

docs/protocol/ceramic-one/concepts.mdx

@@ -18,8 +18,7 @@ you're interacting with directly.
 
 Events are atomic units of information, captured at a point in time and propagated throughout the
 Ceramic network. Events are organized into [streams](#streams), which group related events into a
-sequence and provide a [consistent ordering](#consistent-ordering) that all [consumers](#consumers)
-can agree upon and validate.
+sequence and provide a consistent ordering that all [consumers](#consumers) can agree upon and validate.
 
 Events include a `data` payload, which is a sequence of bytes whose structure and semantics are
 determined by applications building on the Ceramic protocol.

docs/protocol/js-ceramic/guides/ceramic-clients/authentication/did-jsonrpc.md

@@ -67,8 +67,8 @@ One option is installing and setting up one or more account providers that run l
 
 | Account | Supported Key Types | Provider libraries                                               |
 | ------- | ------------------- | ---------------------------------------------------------------- |
-| Key DID | Ed25519             | [`key-did-provider-ed25519`](./key-did.md#ed25519)     |
-| Key DID | Secp256k1           | [`key-did-provider-secp256k1`](./key-did.md#secp256k1) |
+| Key DID | Ed25519             | [`key-did-provider-ed25519`](./key-did#key-did-provider-ed25519)     |
+| Key DID | Secp256k1           | [`key-did-provider-secp256k1`](./key-did#key-did-provider-secp256k1) |
 
 <!-- | PKH DID | ?????????           | [`js-pkh-did-provider →`]()           | -->
 
@@ -274,4 +274,4 @@ console.log(await did.decryptDagJWE(dagJWE))
 ---
 
 - To support transactions, you'll need to set up your DID provider for authentication.
--->
+-->

docusaurus.config.ts

@@ -167,8 +167,7 @@ const config: Config = {
               "/reference/typescript/interfaces/_ceramicnetwork_common.AnchorValidator.html",
               "/reference/typescript/DEVELOPMENT.md",
               "/reference/typescript/docs-dev/UPGRADING.md",
-              "/reference/typescript/docs-dev/QUICKSTART.md",
-              "/reference/typescript/DEVELOPMENT.md"
+              "/reference/typescript/docs-dev/QUICKSTART.md"
             ]
           },
           {

sidebars.ts

@@ -212,7 +212,7 @@ const sidebars: SidebarsConfig = {
         },
         { type: "doc", id: "composedb/create-your-composite", label: "Create your composite" },
         { type: "doc", id: "composedb/interact-with-data", label: "Interact with data" },
-        { type: "doc", id: "composedb/core-concepts", label: "Core ComposeDBconcepts" },
+        { type: "doc", id: "composedb/core-concepts", label: "Core ComposeDB concepts" },
         { type: "doc", id: "composedb/next-steps", label: "Next Steps" }
       ]
     },