chore: renamed product name

Author: vaachii

.github/workflows/deploy.yml

@@ -39,7 +39,7 @@ jobs:
         env:
           SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}
         with:
-          channel_id: 'C01C9NKCXMF' # '#01_unid'
+          channel_id: 'C01C9NKCXMF' # '#01_nodex'
           status: SUCCESS
           color: good
 
@@ -48,6 +48,6 @@ jobs:
         env:
           SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}
         with:
-          channel_id: 'C01C9NKCXMF' # '#01_unid'
+          channel_id: 'C01C9NKCXMF' # '#01_nodex'
           status: FAILED
           color: danger

README.md

@@ -8,8 +8,8 @@ This document follows the [Sphinx](https://www.sphinx-doc.org) documentation fra
 
 **Clone the repository**
 ```bash
-git clone https://github.com/getunid/unid-docs.git
-cd unid-docs
+git clone https://github.com/getnodex/nodex-docs.git
+cd nodex-docs
 git switch -c sphinx origin/sphinx
 ```
 
@@ -25,7 +25,7 @@ make watch
 
 ## Contributing
 
-[Click here](https://github.com/getunid/unid-docs/issues/new/choose) for `bug report` and `feature request` regarding the contents of this document. Thanks for your feedback to help us to improve.
+[Click here](https://github.com/getnodex/nodex-docs/issues/new/choose) for `bug report` and `feature request` regarding the contents of this document. Thanks for your feedback to help us to improve.
 
 ## License
 

source/_assets/nodex_logo.svg

@@ -45,6 +45,7 @@ code.docutils * {
     font-family: ui-monospace,SFMono-Regular,SF Mono,Menlo,Consolas,Liberation Mono,monospace;
     font-weight: bold;
 }
+.highlight *,
 .highlight-js *,
 .highlight-json * {
     font-size: 12px;

source/_assets/nodex_logo_full.svg

@@ -98,13 +98,13 @@ Execute the above command and make sure that the version of Rust is 1.65.0 or la
 - **NodeX EDGE: Getting the GitHub repository (clone)**
 
 ```
-[user@linux]$ git clone https://github.com/getunid/unid.git
+[user@linux]$ git clone https://github.com/getnodex/nodex.git
 ```
 
 - **Go to NodeX EDGE directory**
 
 ```
-[user@linux]$ cd unid/
+[user@linux]$ cd nodex/
 ```
 
 - **Commit head start (checkout)**
@@ -134,7 +134,7 @@ warning: `panic` setting is ignored for `test` profile
 
 (SNIP)
 
-warning: `unid` (bin "unid-agent") generated 78 warnings
+warning: `nodex` (bin "nodex-agent") generated 78 warnings
     Finished release [optimized] target(s) in 4m 31s
 ```
 
@@ -149,34 +149,34 @@ drwxrwxr-x 134 parallels parallels    12288 Nov  4 16:25 build/
 drwxrwxr-x   2 parallels parallels   126976 Nov  4 16:33 deps/
 drwxrwxr-x   2 parallels parallels     4096 Nov  4 15:57 examples/
 drwxrwxr-x   2 parallels parallels     4096 Nov  4 15:57 incremental/
--rwxrwxr-x   2 parallels parallels 12499616 Nov  4 16:33 unid-agent*
--rw-rw-r--   1 parallels parallels     2688 Nov  4 16:33 unid-agent.d
+-rwxrwxr-x   2 parallels parallels 12499616 Nov  4 16:33 nodex-agent*
+-rw-rw-r--   1 parallels parallels     2688 Nov  4 16:33 nodex-agent.d
 ```
 
 These steps will complete the build of NodeX EDGE. Verify that the build artifacts exist in the following path
 
-- **target/x86_64-unknown-linux-musl/release/unid-agent**
+- **target/x86_64-unknown-linux-musl/release/nodex-agent**
 
-The build artifact (unid-agent) can be executed by properly deploying it on the execution environment specified at build time; the API reference provided by NodeX EDGE is described in subsequent chapters.
+The build artifact (nodex-agent) can be executed by properly deploying it on the execution environment specified at build time; the API reference provided by NodeX EDGE is described in subsequent chapters.
 
 ## First time starting up
 
 The NodeX EDGE built in the previous steps should be moved to any directory on the LinuxOS (generally /usr/local/bin is a good place to put it).
 
 ```
-[user@linux]$ sudo mv target/x86_64-unknown-linux-musl/release/unid-agent /usr/local/bin
+[user@linux]$ sudo mv target/x86_64-unknown-linux-musl/release/nodex-agent /usr/local/bin
 ```
 
 NodeX EDGE has a daemon startup function in the binary itself and can be started in a daemon state by specifying options. The following snippet shows how to start NodeX EDGE in a non-daemon state.
 
 ```
-[user@linux]$ unid-agent
+[user@linux]$ nodex-agent
 ```
 
 The following snippet shows how to start NodeX EDGE in daemon state.
 
 ```
-[user@linux]$ unid-agent --daemonize
+[user@linux]$ nodex-agent --daemonize
 ```
 
 There is no difference in the functionality provided by NodeX EDGE in either method, and other applications capable of IPC (Unix Domain Socket) communication can still make requests to the NodeX EDGE Agent.
@@ -187,8 +187,8 @@ To verify that it was installed correctly, run the following snippet. If the res
 
 ```
 curl -X GET H 'content-type: application/json' \
-    --unix-socket /usr/local/bin/unid-agent.sock \
-    'http:/local/identifiers/did:unid:test:ey………'
+    --unix-socket /usr/local/bin/nodex-agent.sock \
+    'http:/local/identifiers/did:nodex:test:ey………'
 ```
 
 Please refer to the API Reference page for more information on how to use NodeX EDGE.

source/_assets/unid_overview_2022.svg renamed to source/_assets/nodex_overview_2022.svg

@@ -1,13 +1,14 @@
 # Welcome to NodeX Documentation!
 
-```{image} _assets/unid_u_logo.svg
+```{image} _assets/nodex_logo.svg
 :align: center
+:width: 100
 ```
 
 <h1 style="text-align: center;">
 NodeX
 
-[![Release Pipeline](https://github.com/getunid/unid/actions/workflows/release-pipeline.yml/badge.svg?branch=main)](https://github.com/getunid/unid/actions/workflows/release-pipeline.yml) [![Coverage Status](https://coveralls.io/repos/github/getunid/unid/badge.svg)](https://coveralls.io/github/getunid/unid) [![Crates](https://img.shields.io/crates/v/unid.svg)](https://crates.io/crates/unid) [![Semantic Release](https://img.shields.io/badge/semantic--release-rust-B7410E?logo=semantic-release)](https://github.com/semantic-release/semantic-release)
+[![Release Pipeline](https://github.com/nodecross/nodex-agent/actions/workflows/release-pipeline.yml/badge.svg?branch=main)](https://github.com/nodecross/nodex-agent/actions/workflows/release-pipeline.yml) [![Coverage Status](https://coveralls.io/repos/github/nodecross/nodex-agent/badge.svg)](https://coveralls.io/github/nodecross/nodex-agent) [![Semantic Release](https://img.shields.io/badge/semantic--release-rust-B7410E?logo=semantic-release)](https://github.com/semantic-release/semantic-release)
 </h1>
 
 <hr />
@@ -17,12 +18,10 @@ NodeX is an open-source toolkit for building end-to-end secure messaging between
 ```{toctree}
 :hidden:
 introduction/index.md
-unid/index.md
-unid_edge/index.md
+nodex/index.md
+nodex_edge/index.md
 build_guide/linux/index.md
-api_reference/index.md
 rpc_reference/index.md
 interface_definitions/index.md
 glossary/index.md
-preview/index.md
 ```

source/_static/css/style.css

@@ -5,39 +5,39 @@ This chapter defines the API interface required for development when replacing o
 ## True random number generation
 
 ```
-Method: unid_err_t unid_read_trng(void *result_ptr)
+Method: nodex_err_t nodex_read_trng(void *result_ptr)
 ```
 
-This is implemented when replacing the process of generating true random numbers. Accesses its own TRNG module inside the shared library, and links true random numbers to NodeX EDGE through a pointer. The return value of the method follows the definition of unid_err_t.
+This is implemented when replacing the process of generating true random numbers. Accesses its own TRNG module inside the shared library, and links true random numbers to NodeX EDGE through a pointer. The return value of the method follows the definition of nodex_err_t.
 
 ## Save private keys
 
 ```
-Method: unid_err_t unid_write_private_key(char *private_key)
+Method: nodex_err_t nodex_write_private_key(char *private_key)
 ```
 
-Implement this when replacing the private key storage process. The private key is stored inside the shared library using a proprietary cipher, etc. The return value of the method follows the definition of unid_err_t. The return value of the method follows the definition of unid_err_t.
+Implement this when replacing the private key storage process. The private key is stored inside the shared library using a proprietary cipher, etc. The return value of the method follows the definition of nodex_err_t. The return value of the method follows the definition of nodex_err_t.
 
 ## Find private keys
 
 ```
-Method: unid_err_t unid_read_private_key(void *result_ptr)
+Method: nodex_err_t nodex_read_private_key(void *result_ptr)
 ```
 
-This function is implemented when the process of reading out the private key is replaced. The private key is read out using a unique cipher or other device inside the shared library, and the private key is linked to the NodeX EDGE through a pointer. The return value of the method follows the definition of unid_err_t.
+This function is implemented when the process of reading out the private key is replaced. The private key is read out using a unique cipher or other device inside the shared library, and the private key is linked to the NodeX EDGE through a pointer. The return value of the method follows the definition of nodex_err_t.
 
 ## Encryption Data
 
 ```
-Method: unid_err_t unid_encrypt_message(char *message, void *result_ptr)
+Method: nodex_err_t nodex_encrypt_message(char *message, void *result_ptr)
 ```
 
 (TBD)
 
 ## Decryption Data
 
 ```
-Method: unid_err_t unid_decrypt_message(char *message, void *result_ptr)
+Method: nodex_err_t nodex_decrypt_message(char *message, void *result_ptr)
 ```
 
 (TBD)