📝 Update docs structure, design

documentation/docs/fuzzing/execute/debug.md

@@ -0,0 +1,10 @@
+# Debug
+
+To debug your program with values from a crash file:
+
+```bash
+# fuzzer will run the <TARGET_NAME> with the specified <CRASH_FILE_PATH>
+trident fuzz run-debug <TARGET_NAME> <CRASH_FILE_PATH>
+# for example:
+trident fuzz run-debug fuzz_0 trident-tests/fuzz_tests/fuzzing/fuzz_0/cr1.fuzz
+```

documentation/docs/fuzzing/fuzzing-run-debug.md → documentation/docs/fuzzing/execute/run.md

@@ -1,7 +1,6 @@
-# Run and Debug
+# Run
 
-## Run
-Once you have finished the implementation of the Fuzz Test, you can run the Test as follows:
+To execute the desired fuzz test, run:
 
 ```bash
 # Replace <TARGET_NAME> with the name of particular
@@ -54,31 +53,17 @@ allow_duplicate_txs = false
 fuzzing_with_stats = true
 ```
 
-Or you can pass any parameter via [environment variables](https://github.com/rust-fuzz/honggfuzz-rs#environment-variables).
+??? note
 
-A list of hongfuzz parameters can be found in honggfuzz [usage documentation](https://github.com/google/honggfuzz/blob/master/docs/USAGE.md#cmdline---help). The parameters passed via **environment variables** have **higher priority**. For example:
+    Or you can pass any parameter via [environment variables](https://github.com/rust-fuzz/honggfuzz-rs#environment-variables).
 
-```bash
-# Time-out: 10 secs
-# Number of concurrent fuzzing threads: 1
-# Number of fuzzing iterations: 10000
-# Display Solana logs in the terminal
-HFUZZ_RUN_ARGS="-t 10 -n 1 -N 10000 -Q" trident fuzz run <TARGET_NAME>
-```
-
-### Fuzzing statistics
-Sometimes, it's useful to know how often a particular instruction has been invoked and how many times it has succeeded or failed. To display these statistics when fuzzing is finished or interrupted, set the `fuzzing_with_stats` option to `true` in the `[fuzz]` section of the Trident.toml configuration file. Please note that this option is disabled by default because it impacts performance.
-
-The statistics show the total number of invocations for each instruction, which is the sum of successful and failed invocations. Successful invocations are those that return an `Ok()` result. Failed invocations are those that return an `Err()` result. Additionally, the statistics also show as `Check Failed` the number of successful invocations that did not pass the user-defined invariants check. Note that unhandled panics are currently logged only as crashes and are not displayed in the fuzzing statistics table.
+    A list of hongfuzz parameters can be found in honggfuzz [usage documentation](https://github.com/google/honggfuzz/blob/master/docs/USAGE.md#cmdline---help). The parameters passed via **environment variables** have **higher priority**. For example:
 
-Keep in mind that the number of fuzz iterations does not directly correspond to the total number of invocations. In one fuzz iteration, the fuzzer might be unable to deserialize fuzz data into instructions, causing the entire iteration to be skipped.
+    ```bash
+    # Time-out: 10 secs
+    # Number of concurrent fuzzing threads: 1
+    # Number of fuzzing iterations: 10000
+    # Display Solana logs in the terminal
+    HFUZZ_RUN_ARGS="-t 10 -n 1 -N 10000 -Q" trident fuzz run <TARGET_NAME>
+    ```
 
-## Debug
-To debug your program with values from a crash file:
-
-```bash
-# fuzzer will run the <TARGET_NAME> with the specified <CRASH_FILE_PATH>
-trident fuzz run-debug <TARGET_NAME> <CRASH_FILE_PATH>
-# for example:
-trident fuzz run-debug fuzz_0 trident-tests/fuzz_tests/fuzzing/fuzz_0/cr1.fuzz
-```

documentation/docs/fuzzing/execute/statistics.md

@@ -0,0 +1,25 @@
+# Fuzzing statistics
+
+!!! important
+
+    In order to show statistics of fuzzing session (statistics are displayed after the fuzzing session ended), set `fuzzing_with_stats` within the Trident.toml to `true`.
+
+    ```toml
+    [fuzz]
+    # ...
+    fuzzing_with_stats = true
+    # ...
+    ```
+
+
+Currently exported statistics from the Fuzzing Session
+
+#### Simple
+
+- Number of invocations of each instruction during the fuzzing session.
+- Number of successful invocations of each instruction during the fuzzing session.
+- Number of failed invariants checks for each instruction during the fuzzing session.
+
+??? note
+
+    Keep in mind that the number of fuzz iterations does not directly correspond to the total number of invocations. In one fuzz iteration, the fuzzer might be unable to deserialize fuzz data into instructions, causing the entire iteration to be skipped.

documentation/docs/fuzzing/extra/examples.md

@@ -0,0 +1,75 @@
+---
+hide:
+  - toc
+---
+
+# Trident by Examples
+
+<div class="grid cards" markdown>
+
+-   :material-hand-wave:{ .lg .middle } __Hello World!__
+
+    ---
+
+    Hello World example with Trident.
+
+    [hello_world](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/hello_world)
+
+-   :octicons-bug-16:{ .lg .middle } __Possible vulnerabilities and bugs__
+
+    ---
+
+    Check the possible attack vectors and bugs that can be detected using Trident.
+
+    [Unchecked Arithmetic](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/unchecked-arithmetic-0)
+
+    [Incorrect Instruction Sequence](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/incorrect-ix-sequence-1)
+
+    [Unauthorized Access](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/unauthorized-access-2)
+
+    [Incorrect Integer Arithmetic](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/incorrect-integer-arithmetic-3)
+
+-   :octicons-tools-24:{ .lg .middle } __Customize with Arbitrary__
+
+    ---
+
+    You can use Arbitrary crate to your advantage and limit or customize the data that are sent to the instructions.
+
+    [Custom Data Types](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/arbitrary-custom-types-4)
+
+
+    [Limiting Instructions Inputs](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/arbitrary-limit-inputs-5)
+
+-   :material-call-made:{ .lg .middle } __Cross-Program Invocation__
+
+    ---
+
+    Trident supports Cross-Program Invocation, you can fuzz your programs and create NFTs at the same time.
+
+    [Simple CPI](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/simple-cpi-6)
+
+    [CPI with Metaplex Metadata Program](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/cpi-metaplex-7)
+
+</div>
+
+<!-- ### Hello World! Example
+- [hello_world](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/hello_world)
+
+### Possible vulnerabilities and bugs
+- [unchecked-arithmetic-0](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/unchecked-arithmetic-0)
+- [incorrect-ix-sequence-1](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/incorrect-ix-sequence-1)
+- [unauthorized-access-2](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/unauthorized-access-2)
+- [incorrect-integer-arithmetic-3](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/incorrect-integer-arithmetic-3)
+
+### Example usage of Arbitrary Trait with Custom Data type as Instruction parameter
+- [arbitrary-custom-types-4](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/arbitrary-custom-types-4)
+
+### Example usage of limiting the Instruction data structure with the Arbitrary trait
+- [arbitrary-limit-inputs-5](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/arbitrary-limit-inputs-5)
+
+### Example usage of CPI with available source code to the callee program
+- [simple-cpi-6](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/simple-cpi-6)
+
+
+### Example usage of CPI with unavailable source code to the callee program (i.e. callee as SBF)
+- [cpi-metaplex-7](https://github.com/Ackee-Blockchain/trident/tree/master/examples/fuzz-tests/cpi-metaplex-7) -->

documentation/docs/fuzzing/initialization/fuzzing-initialization-fuzz.md → documentation/docs/fuzzing/first-steps/fuzz-test-initialization.md

@@ -1,6 +1,6 @@
-# Fuzz test-only
+# Initialize Fuzz Test
 
-If you are interested only in generating templates for fuzz tests run
+For initialization of workspace for fuzz tests, call:
 ```bash
 trident init fuzz
 ```
@@ -21,3 +21,10 @@ project-root
 ├── Trident.toml
 └── ...
 ```
+
+## Add new Fuzz Test
+
+If you wish to generate template for a new fuzz test, call:
+```bash
+trident fuzz add
+```

documentation/docs/fuzzing/first-steps/writing-fuzz-test.md

@@ -0,0 +1,31 @@
+# Writing Fuzz Test
+
+!!! important
+
+    At the current development stage, there are some manual steps required to start the Fuzzing Session. In principle:
+
+    **Prerequisites:**
+
+     - Add dependencies specific to your program to `trident-tests/fuzz_tests/Cargo.toml` (such as anchor-spl etc.).
+     - Add necessary `use` statements into `trident-tests/fuzz_tests/<FUZZ_TEST_NAME>/accounts_snapshots.rs` to import missing types.
+
+    **Writing Fuzz Tests**
+
+     1. Include desired Programs [Include Programs](../writing-fuzz-test/programs.md).
+     2. Specify pseudo-random accounts to re-use [Accounts to re-use](../writing-fuzz-test/accounts.md).
+     3. Specify instruction data [Instruction Data](../writing-fuzz-test/instruction-data.md).
+     4. Specify instruction accounts [Instruction Accounts](../writing-fuzz-test/instruction-accounts.md).
+
+    **Run and Debug**
+
+     1. Execute desired fuzz test [Run](../execute/run.md)
+     2. See the found crash with more details [Debug](../execute/debug.md)
+
+!!! note
+
+    For better fuzzing results and experience you can also manually adjust the following:
+
+     1. Define Invariants checks [Invariants Checks](../writing-fuzz-test-extra/invariants-checks.md).
+     2. Specify instruction sequences[Instruction sequences](../writing-fuzz-test-extra/instruction-sequences.md).
+     3. Specify custom data types[Custom Data types](../writing-fuzz-test-extra/custom-data-types.md).
+     4. Well structured data[Arbitrary](../writing-fuzz-test-extra/arbitrary.md).

documentation/docs/fuzzing/writing-fuzz-test-extra/accounts-snapshots.md

@@ -0,0 +1,3 @@
+# AccountsSnapshots
+
+TBD

documentation/docs/fuzzing/howto/fuzzing-howto-p7.md → documentation/docs/fuzzing/writing-fuzz-test-extra/arbitrary.md

@@ -1,4 +1,4 @@
-# How to use Arbitrary crate
+# Structured Data
 
 The [Arbitrary](https://docs.rs/arbitrary/latest/arbitrary/) crate in Rust is used for generating well-typed, structured instances of data from raw byte buffers, making it useful for fuzzing by producing random but structured data for tests.
 

documentation/docs/fuzzing/howto/fuzzing-howto-p6.md → documentation/docs/fuzzing/writing-fuzz-test-extra/custom-data-types.md

@@ -1,4 +1,4 @@
-# How to use Custom Data Types
+# Custom Data Types
 
 If you use Custom Types as Instruction data arguments, you may encounter a problem that the Custom Type does not implement
 

documentation/docs/fuzzing/howto/fuzzing-howto-p5.md → documentation/docs/fuzzing/writing-fuzz-test-extra/instruction-sequences.md

@@ -1,8 +1,10 @@
-# Customize instructions generation
+# Instruction sequences
 
 It is possible to customize how the instructions are generated and which instructions will be executed at the beginning (`pre_ixs`), in the middle (`ixs`) and at the end (`post_ixs`) of each fuzz iteration. This can be useful for example if your program needs an initialization or you want to fuzz some specific program state.
 
-- Go to the `trident-tests/fuzz_tests/<FUZZ_TEST_NAME>/test_fuzz.rs` and implement the corresponding optional method of the `FuzzDataBuilder<FuzzInstruction>` trait. For example, in order to always call the `initialize` instruction, modify the trait's implementation as follows:
+!!! important
+
+    - Go to the `trident-tests/fuzz_tests/<FUZZ_TEST_NAME>/test_fuzz.rs` and implement the corresponding optional method of the `FuzzDataBuilder<FuzzInstruction>` trait. For example, in order to always call the `initialize` instruction, modify the trait's implementation.
 
 ```rust
 impl FuzzDataBuilder<FuzzInstruction> for MyFuzzData {