Further changes to structure

Author: TinaKT

source/mainnet/conf.py

@@ -389,7 +389,7 @@
     "./net/smart-contracts/general/images/smart-contract-lifecycle.png": "docs/smart-contracts/images/smart-contract-lifecycle.png",
     "./net/references/manage-accounts": "docs/protocol/manage-accounts.html",
     "./net/images/concepts/account-creation.png": "docs/protocol/images/account-creation.png",
-    "./net/smart-contracts/guides/setup-tools": "docs/smart-contracts/guides/setup-tools.html",
+    "./net/smart-contracts/guides/setup-tools": "docs/smart-contracts/guides/build-contract.html",
     "./net/smart-contracts/guides/setup-contract": "docs/smart-contracts/guides/setup-contract.html",
     "./net/smart-contracts/guides/compile-module": "docs/smart-contracts/guides/compile-module.html",
     "./net/smart-contracts/guides/build-schema": "docs/smart-contracts/guides/build-schema.html",
@@ -401,4 +401,18 @@
     "./net/smart-contracts/guides/unit-test-contract": "docs/smart-contracts/guides/unit-test-contract.html",
     "./net/smart-contracts/guides/development": "docs/smart-contracts/guides/development.html",
     "./net/smart-contracts/guides/costs": "docs/smart-contracts/guides/costs.html",
+    "./net/guides/company-identities": "docs/protocol/company-identities.html",
+    ".net/images/company-id-request.png": "docs/protocol/images/company-id-request.png",
+    ".net/images/company-id-create.png": "docs/protocol/images/company-id-create.png",
+    ".net/images/company-id-acct-keys.png": "docs/protocol/images/company-id-acct-keys.png",
+    ".net/images/company-id-recover.png": "docs/protocol/images/company-id-recover.png",
+    ".net/concepts/concepts-transactions": "docs/protocol/concepts-transactions.html",
+    ".net/concepts/concepts-baker": "docs/protocol/concepts-baker.html",
+    ".net/concepts/concepts-delegation": "docs/protocol/concepts-delegation.html",
+    ".net/images/concepts/baker-process1.png": "docs/protocol/images/baker-process1.png",
+    ".net/images/concepts/baker-process2.png": "docs/protocol/images/baker-process2.png",
+    ".net/smart-contracts/guides/initialize-contract": "docs/smart-contracts/guides/initialize-contract.html",
+    ".net/smart-contracts/guides/interact-instance": "docs/smart-contracts/guides/interact-instance.html",
+    ".net/smart-contracts/guides/inspect-instance": "docs/smart-contracts/guides/inspect-instance.html",
+    ".net/smart-contracts/guides/invoke-instance": "docs/smart-contracts/guides/invoke-instance.html"
     }

source/mainnet/docs/index.rst

@@ -10,12 +10,14 @@ This is the documentation
    What is the Concordium Protocol? <protocol/introduction>
    Identities <protocol/id-accounts>
    Accounts <protocol/manage-accounts>
+   Transactions <protocol/transactions>
+   Network <protocol/network>
 
 .. toctree::
    :caption: Smart Contracts
 
    What is a smart contract? <smart-contracts/introduction>
-   QuickStart <smart-contracts/guides/quick-start>
+   QuickStart to smart contract deployment <smart-contracts/guides/quick-start>
    Build a smart contract <smart-contracts/guides/build-contract>
    Deploy a smart contract <smart-contracts/guides/deploy-module>
 

…ainnet/net/guides/company-identities.rst …net/docs/protocol/company-identities.rstsource/mainnet/net/guides/company-identities.rst renamed to source/mainnet/docs/protocol/company-identities.rst source/mainnet/net/guides/company-identities.rst renamed to source/mainnet/docs/protocol/company-identities.rst

@@ -27,7 +27,7 @@ Request identity
 
 #. Write down or save your seedphrase by clicking the copy button to copy your seedphrase to the clipboard and remember to go to the clipboard and save the file. Keep your seedphrase secure as you will need it to create accounts or recover the identity. Click **Proceed**.
 
-   .. image:: ../images/company-id-request.png
+   .. image:: ../protocol/images/company-id-request.png
       :alt: company id tool screen showing identities related to seedphrase and option to select
 
 #. Enter your seedphrase to verify that you have recorded it correctly. Click **Proceed**.
@@ -51,7 +51,7 @@ After obtaining the ``id-object.json`` identity object from the identity provide
 
 #. Enter your seedphrase in the Enter seedphrase field. In the Identity object file field click to navigate to the location of the stored ``id-object.json`` file. Click **Get Accounts**.
 
-   .. image:: ../images/company-id-create-acct.png
+   .. image:: ../protocol/images/company-id-create-acct.png
       :alt: company id tool screen showing seedphrase field and file selection box
 
 #. On the next screen, click **Create Account** to create an account with this company identity. When prompted, save the ``account-keys.json`` in a secure location as you will need them to interact with the account on-chain. You can click **Create account** again to create another account.
@@ -60,7 +60,7 @@ After obtaining the ``id-object.json`` identity object from the identity provide
 
    If you are trying to recover the ``account-keys.json`` file(s), you can also use **Create Account**. After entering your seedphrase and selecting your ``id-object.json`` file you will see a list of account associated with this seedphrase and ID object. Click **Save** to save the ``account-keys.json`` for that account.
 
-   .. image:: ../images/company-id-acct-keys.png
+   .. image:: ../protocol/images/company-id-acct-keys.png
       :alt: company id tool screen showing seedphrase field and file selection box
 
 .. dropdown:: Format of the key files
@@ -139,7 +139,7 @@ If the identity object used to create credentials is lost, it can be recovered f
 
 #. You see a list of accounts associated with the seedphrase. It is possible to save the account keys that can be ussed to interact with the account on the chain. Indices that are to the left of the account address are pointing to the identity index, being the first value and the account index being the second value (0,0). In the Identities to recover drop-down, select the identity you want to recover. There will always be one additional index on the list for selection to be sure that request can be generated for more than one identity. This is mainly useful in cases where first identity object was lost or unused to create accounts. Click **Generate recovery request**. The command outputs the ``recovery-request.json`` file. The request should be sent to the identity provider through a trusted channel. When the request has been verified successfully, you will receive an email with an identity object. Store this file securely as you need it to create accounts on the chain.
 
-   .. image:: ../images/company-id-recover.png
+   .. image:: ../protocol/images/account-creation.png
       :alt: company id tool screen showing identities related to seedphrase and option to select
 
 - For Mainnet requests: Send the file to [email protected] together with any other required identity data as described in the `entity verification instructions <https://notaben.notion.site/Entity-verification-next-1b4fbcd8e32042e1ac3b0018a3cc27bc>`_.

…/mainnet/net/concepts/concepts-baker.rst …mainnet/docs/protocol/concepts-baker.rstsource/mainnet/net/concepts/concepts-baker.rst renamed to source/mainnet/docs/protocol/concepts-baker.rst source/mainnet/net/concepts/concepts-baker.rst renamed to source/mainnet/docs/protocol/concepts-baker.rst

@@ -33,12 +33,12 @@ Overview of the validation process
 
 #. If the combined effective stake of the validators who sign the block is *greater than or equal to* two-thirds of the total stake, the block gets a :term:`Quorum Certificate` (QC) that certifies that this is a valid block. Without the QC the new round cannot progress.
 
-.. image:: ../images/concepts/baker-process1.png
+.. image:: ../protocol/images/baker-process1.png
    :alt: diagram of validator process
 
 6. The next validator (Alice) now uses the QC to produce the next block. The new block can only extend the previous block when a QC is presented to Alice.
 
-.. image:: ../images/concepts/baker-process2.png
+.. image:: ../protocol/images/baker-process2.png
    :alt: diagram of validator process
 
 If there are no issues, the protocol repeats this process from step 3.

…net/net/concepts/concepts-delegation.rst …et/docs/protocol/concepts-delegation.rstsource/mainnet/net/concepts/concepts-delegation.rst renamed to source/mainnet/docs/protocol/concepts-delegation.rst source/mainnet/net/concepts/concepts-delegation.rst renamed to source/mainnet/docs/protocol/concepts-delegation.rst

@@ -2,7 +2,7 @@
 .. _transactions-overview:
 
 =====================
-Transactions overview
+Transaction anatomy
 =====================
 
 A transaction on the Concordium blockchain is an operation which applies some change to the chain. All transactions are recorded on the chain and once recorded, they are immutable. A transaction always has one sender :term:`account` and is signed using the :term:`keys<private keys>` of this account.

…t/net/concepts/concepts-transactions.rst …/docs/protocol/concepts-transactions.rstsource/mainnet/net/concepts/concepts-transactions.rst renamed to source/mainnet/docs/protocol/concepts-transactions.rst source/mainnet/net/concepts/concepts-transactions.rst renamed to source/mainnet/docs/protocol/concepts-transactions.rst

@@ -80,5 +80,6 @@ For information about accounts, see :ref:`Accounts<managing_accounts>`.
    :hidden:
    :maxdepth: 1
 
-   ../guides/company-identities
+   company-identities
+