New sidebar

Restructure sidebar

Author: ciaranightingale

docs/pages/aztec-nr/advanced-features/custom-notes.md

@@ -4,8 +4,8 @@ This guide shows you how to create custom note types for storing specialized pri
 
 ## Prerequisites
 
-- Basic understanding of [Aztec private state](../../concepts/storage/state_model.md)
-- Familiarity with [notes and UTXOs](../../concepts/storage/index.md)
+- Basic understanding of Aztec private state
+- Familiarity with notes and UTXOs
 - Aztec development environment set up
 
 ## Why create custom notes?
@@ -329,11 +329,10 @@ fn get_order(owner: AztecAddress, target_id: Field) -> OrderNote {
 
 ## Further reading
 
-- [What the `#[note]` macro does](../../concepts/smart_contracts/functions/attributes.md#implementing-notes)
-- [Note lifecycle and nullifiers](../../concepts/advanced/storage/indexed_merkle_tree.mdx)
-- [Advanced note patterns](./advanced/how_to_retrieve_filter_notes.md)
-- [Note portals for L1 communication](./how_to_communicate_cross_chain.md)
-- [Macros reference](../../reference/smart_contract_reference/macros.md)
-- [Keys, including npk_m_hash](../../concepts/accounts/keys.md)
+- What the `#[note]` macro does - See concepts section
+- Note lifecycle and nullifiers - See concepts section
+- Advanced note patterns - See advanced features
+- Note portals for L1 communication - See cross-chain interactions
+- Macros reference - See reference section
+- Keys, including npk_m_hash - See concepts section
 
-<!-- docs:end:how_to_implement_custom_notes -->

docs/pages/aztec-nr/compile.md

@@ -87,4 +87,3 @@ After compilation, use the generated artifacts to:
 - Interact with deployed contracts using type-safe interfaces
 - Import contracts in other Aztec.nr projects
 
-<!-- docs:end:compile_contracts -->

docs/pages/aztec-nr/debugging.md

@@ -185,6 +185,6 @@ Check hex errors against [Errors.sol](https://github.com/AztecProtocol/aztec-pac
 
 ## Related Resources
 
-- [Circuit Architecture](../../concepts/advanced/circuits/index.md)
-- [Private-Public Execution](../../concepts/smart_contracts/functions/public_private_calls.md)
-- [Aztec.nr Dependencies](../../reference/smart_contract_reference/dependencies.md)
+- Circuit Architecture - See concepts section
+- Private-Public Execution - See concepts section
+- Aztec.nr Dependencies - See reference section

docs/pages/aztec-nr/getting-started.md

@@ -2,7 +2,6 @@
 
 ## Noir VSCode Extension
 
-<!-- docs:start:installing_noir_lsp -->
 
 Install the [Noir Language Support extension](https://marketplace.visualstudio.com/items?itemName=noir-lang.vscode-noir) to get syntax highlighting, syntax error detection and go-to definitions for your Aztec contracts. 
 
@@ -16,7 +15,6 @@ which aztec-nargo
 
 To specify a custom nargo executable, go to the VSCode settings and search for "noir", or click extension settings on the `noir-lang` LSP plugin. Update the `Noir: Nargo Path` field to point to your desired `aztec-nargo` executable.
 
-<!-- docs:end:installing_noir_lsp -->
 
 ## Creating an Aztec.nr Project
 

docs/pages/aztec-nr/installation.md

@@ -15,7 +15,7 @@ Before learning how to create Aztec smart contracts, we must first install some
 
 - [Docker](https://docs.docker.com/get-docker/)
 
-## Install Aztec Tools
+## Install Aztec Tools
 
 1. Docker needs to be running in order to install the sandbox.
 
@@ -33,7 +33,6 @@ aztec --version
 
 ## Noir VSCode Extension
 
-<!-- docs:start:installing_noir_lsp -->
 
 Install the [Noir Language Support extension](https://marketplace.visualstudio.com/items?itemName=noir-lang.vscode-noir) to get syntax highlighting, syntax error detection and go-to definitions for your Aztec contracts. 
 
@@ -47,7 +46,6 @@ which aztec-nargo
 
 To specify a custom nargo executable, go to the VSCode settings and search for "noir", or click extension settings on the `noir-lang` LSP plugin. Update the `Noir: Nargo Path` field to point to your desired `aztec-nargo` executable.
 
-<!-- docs:end:installing_noir_lsp -->
 
 ## Creating an Aztec.nr Project
 

docs/pages/aztec-nr/introduction-to-private-smart-contracts/index.md

@@ -8,8 +8,8 @@ Private smart contracts on Aztec allow you to build applications where transacti
 
 ## Getting Started
 
-- [A Simple Aztec Smart Contract](./simple-contract) - Start with a basic example
-- [Example Aztec Smart Contracts](./examples) - Explore more complex patterns
+- A Simple Aztec Smart Contract - Start with a basic example
+- Example Aztec Smart Contracts - Explore more complex patterns
 
 ## Key Concepts
 

docs/pages/aztec-nr/language-description/authentication-witness.md

@@ -1,6 +1,5 @@
 # Authentication Witness
 
-<!-- docs:start:use_authwit -->
 
 Authentication witnesses (authwit) allow other contracts to execute actions on behalf of your account. This guide shows you how to implement and use authwits in your Aztec smart contracts.
 
@@ -10,7 +9,7 @@ Authentication witnesses (authwit) allow other contracts to execute actions on b
 - Understanding of private and public functions in Aztec
 - Access to the `authwit` library in your contract
 
-For conceptual background, see [Authentication Witnesses](../../concepts/advanced/authwit.md).
+For conceptual background, see Authentication Witnesses in the concepts section.
 
 ## Set up the authwit library
 
@@ -91,4 +90,3 @@ fn _approve_and_execute_action(
 }
 ```
 
-<!-- docs:end:use_authwit -->

docs/pages/aztec-nr/language-description/calling-other-contracts.md

@@ -20,7 +20,6 @@
             - Stealthifying Addresses
                 - Custom Stealth Addresses
 
-<!-- docs:start:call_contracts -->
 
 This guide shows you how to call functions in other contracts from your Aztec smart contracts, enabling contract composability and interaction.
 
@@ -83,11 +82,10 @@ OtherContract::at(contract_address)
 ```
 
 :::info
-Public functions always execute after private execution completes. Learn more in the [concepts overview](../../concepts/index.md).
+Public functions always execute after private execution completes. Learn more in the concepts overview.
 :::
 
 ### Use other call types
 
-Explore additional call types for specialized use cases in the [call types reference](../../concepts/call_types.md).
+Explore additional call types for specialized use cases in the call types reference.
 
-<!-- docs:end:call_contracts -->

docs/pages/aztec-nr/language-description/contract-structure.md

@@ -8,7 +8,7 @@
     - Events
         - See the dedicated section below
 
-A contract is a collection of persistent state variables and [functions](./functions/index.md) which may manipulate these variables. Functions and state variables within a contract's scope are said to belong to that contract. A contract can only access and modify its own state. If a contract wishes to access or modify another contract's state, it must make a call to an external function of the other contract. For anything to happen on the Aztec network, an external function of a contract needs to be called.
+A contract is a collection of persistent state variables and functions which may manipulate these variables. Functions and state variables within a contract's scope are said to belong to that contract. A contract can only access and modify its own state. If a contract wishes to access or modify another contract's state, it must make a call to an external function of the other contract. For anything to happen on the Aztec network, an external function of a contract needs to be called.
 
 ## Contract
 

docs/pages/aztec-nr/language-description/cross-chain-interactions.md

@@ -13,7 +13,7 @@
 - An Aztec contract project set up with `aztec-nr` dependency
 - Understanding of Aztec L1/L2 architecture
 - Access to Ethereum development environment for L1 contracts
-- Deployed portal contract on L1 (see [token bridge tutorial](../../tutorials/js_tutorials/token_bridge.md))
+- Deployed portal contract on L1 (see token bridge tutorial)
 
 ## Send messages from L1 to L2
 
@@ -195,6 +195,5 @@ bytes memory message = abi.encodeWithSignature(
 
 ## Next steps
 
-Follow the [cross-chain messaging tutorial](../../tutorials/js_tutorials/token_bridge.md) for a complete implementation example.
+Follow the cross-chain messaging tutorial for a complete implementation example.
 
-<!-- docs:end:communicate_cross_chain -->