From cb3eb9607071f48e8fcd33f988369422ae2929b9 Mon Sep 17 00:00:00 2001
From: ovari123 <ovari123@zoho.com>
Date: Fri, 24 Jan 2025 20:48:55 -0400
Subject: [PATCH] developer/jami-concepts/index.md: fix toctree and ref
Follow up to patch: https://review.jami.net/c/jami-docs/+/30005
Change-Id: Ic72e3d8dd7f3a0354f2fe169e66068213e7b784b
---
developer/jami-concepts/index.md | 58 ++++++++++++++++----------------
1 file changed, 29 insertions(+), 29 deletions(-)
diff --git a/developer/jami-concepts/index.md b/developer/jami-concepts/index.md
index 11e812d6..ae67e6aa 100644
--- a/developer/jami-concepts/index.md
+++ b/developer/jami-concepts/index.md
@@ -10,31 +10,31 @@ So, a Jami account consists of a chain of certificates (CA, account, and device)
The account is stored on the user's device, not on a server.
For this, here is the page that explains how it works:
-* :ref:`account-management`
-* :ref:`jami-identifiers`
+* {ref}`account-management`
+* {ref}`jami-identifiers`
After the user account is created, the user can contact other people by sending connection requests through a DHT (<https://opendht.net>) after finding the contact ID
(directly known or by looking up the name server).
If both parties agree, they will first try to create a P2P TCP link (with the ICE protocol), then encrypt it via TLS and use it as a multiplexed socket to transmit data for various protocols, cf.:
-* :ref:`contact-management`
-* :ref:`banned-contacts`
-* :ref:`connection-manager`
-* :ref:`name-server-protocol`
+* {ref}`contact-management`
+* {ref}`banned-contacts`
+* {ref}`connection-manager`
+* {ref}`name-server-protocol`
When both peers are in their contact list, a conversation is created.
This conversation is a **swarm** based on **Swarm Technology**.
A **swarm** is synced between all devices in a conversation via the `git` protocol (it's a Git repository), and connections across devices in a conversation are routed by a component called the **DRT** (distributed routing table).
-* :ref:`swarm`
-* :ref:`drt`
+* {ref}`swarm`
+* {ref}`drt`
Then, the connection can be used to send messages, files, or to make calls (1:1 or conferences).
-* :ref:`calls`
-* :ref:`calls-in-swarm`
-* :ref:`file-transfer`
-* :ref:`conference-protocol`
+* {ref}`calls`
+* {ref}`calls-in-swarm`
+* {ref}`file-transfer`
+* {ref}`conference-protocol`
```{note}
Only calls using Jami accounts are based on Swarm Technology.
@@ -42,24 +42,24 @@ Then, the connection can be used to send messages, files, or to make calls (1:1
Finally, a user can have multiple devices, and a lot of information is synced between them.
-* :ref:`synchronizing-profiles`
-* :ref:`synchronization-protocol`
+* {ref}`synchronizing-profiles`
+* {ref}`synchronization-protocol`
```{toctree}
- :maxdepth: 1
+:maxdepth: 1
- account-management
- banned-contacts
- calls-in-swarm
- calls
- conference-protocol
- connection-manager
- contact-management
- drt
- file-transfer
- jami-identifiers
- name-server-protocol
- swarm
- synchronization-protocol
- synchronizing-profiles
+account-management
+banned-contacts
+calls-in-swarm
+calls
+conference-protocol
+connection-manager
+contact-management
+drt
+file-transfer
+jami-identifiers
+name-server-protocol
+swarm
+synchronization-protocol
+synchronizing-profiles
```
\ No newline at end of file
--
GitLab