trilitech · timothymcmackin · Feb 17, 2025 · Feb 14, 2025 · Feb 14, 2025 · Feb 14, 2025
diff --git a/docs/architecture.md b/docs/architecture.md
@@ -38,7 +38,7 @@ Nodes reach consensus on the next block before adding it to the chain.
 
 As shown in the diagram, the data inside a Tezos block includes the hash of the previous block in the chain and many operations, such as transactions that transfer tez or call smart contracts.
 Blocks also include operations that are necessary for the management of the chain, including nodes' attestations that blocks are valid, called _consensus operations_, and votes on changes to the protocol, called _voting operations_.
-For more information on the operations that can be included in blocks, see [Blocks and operations](https://tezos.gitlab.io/alpha/blocks_ops.html) in the Octez documentation.
+For more information on the operations that can be included in blocks, see [Blocks and operations](https://octez.tezos.com/docs/active/blocks_ops.html) in the Octez documentation.
 
 ### Tezos clients and servers
 

diff --git a/docs/architecture/bakers.md b/docs/architecture/bakers.md
@@ -87,6 +87,6 @@ To start delegating and staking, use the app at https://stake.tezos.com.
 
 To start baking, use our [tutorial for bakers](/tutorials/join-dal-baker).
 
-For more information about the different options to participate to the Tezos network (baking, staking, or delegating), see [Running Octez](https://tezos.gitlab.io/introduction/howtorun.html) in the Octez documentation.
+For more information about the different options to participate to the Tezos network (baking, staking, or delegating), see [Running Octez](https://octez.tezos.com/docs/introduction/howtorun.html) in the Octez documentation.
 
 To learn more about baking and the related concepts, see [Node and Baking](https://opentezos.com/node-baking/baking/introduction/) on opentezos.com.
diff --git a/docs/architecture/data-availability-layer.md b/docs/architecture/data-availability-layer.md
@@ -14,7 +14,7 @@ For a tutorial on how to use the DAL, see [Implement a file archive with the DAL
 
 The DAL depends on individual people running nodes, just like Tezos layer 1.
 
-- If you are already a Tezos baker, you can add a DAL node to your setup with the instructions in [Running a DAL attester node](https://tezos.gitlab.io/shell/dal_run.html).
+- If you are already a Tezos baker, you can add a DAL node to your setup with the instructions in [Running a DAL attester node](https://octez.tezos.com/docs/shell/dal_run.html).
 - For step-by-step instructions on running a DAL node, accessible to anyone, see [Join the DAL as a baker in 5 steps](/tutorials/join-dal-baker).
 
 ## How the DAL works
@@ -156,4 +156,4 @@ if 0 < bytes_read {
 
 ## Reference
 
-For more information about the DAL, see [DAL overview](https://tezos.gitlab.io/shell/dal_overview.html) in the Octez documentation.
+For more information about the DAL, see [DAL overview](https://octez.tezos.com/docs/shell/dal_overview.html) in the Octez documentation.
diff --git a/docs/architecture/governance.md b/docs/architecture/governance.md
@@ -79,5 +79,5 @@ At the end of the Adoption period, Mainnet automatically enables the new protoco
 
 ## References
 
-- [The Amendment (and Voting) Process](https://tezos.gitlab.io/active/voting.html) in the Octez documentation
+- [The Amendment (and Voting) Process](https://octez.tezos.com/docs/active/voting.html) in the Octez documentation
 - [Amending Tezos](https://medium.com/tezos/amending-tezos-b77949d97e1e) on Medium
diff --git a/docs/architecture/governance/amendment-history.md b/docs/architecture/governance/amendment-history.md
diff --git a/docs/architecture/nodes.md b/docs/architecture/nodes.md
@@ -26,7 +26,7 @@ In order to meet these requirements, the software that nodes run is structured a
 
 Nodes cooperate with clients and with each other through an [RPC interface](#the-rpc-interface).
 
-The Octez suite, which is an implementation of the Tezos node and other executables, instantiates these principles in the [Octez software architecture](https://tezos.gitlab.io/shell/the_big_picture.html).
+The Octez suite, which is an implementation of the Tezos node and other executables, instantiates these principles in the [Octez software architecture](https://octez.tezos.com/docs/shell/the_big_picture.html).
 
 For instructions on running a node, see the tutorial [Run a Tezos node in 5 steps](/tutorials/join-dal-baker).
 
@@ -79,7 +79,7 @@ Tezos nodes act as servers and accept HTTP requests from clients and other nodes
 
 Tezos RPC uses JSON to send and receive data, but it does not adhere to the JSON-RPC specification.
 
-All the RPCs served by the Tezos node are described as an OpenAPI specification at [Octez Node RPCs](https://tezos.gitlab.io/api/openapi.html#octez-node) in the Octez documentation.
+All the RPCs served by the Tezos node are described as an OpenAPI specification at [Octez Node RPCs](https://octez.tezos.com/docs/api/openapi.html#octez-node) in the Octez documentation.
 
 ### Public and private RPC nodes
 

diff --git a/docs/architecture/smart-rollups.md b/docs/architecture/smart-rollups.md
@@ -20,7 +20,7 @@ In this way, multiple nodes can run the same rollup and each node can verify the
 
 For a tutorial on Smart Rollups, see [Deploy a Smart Rollup](/tutorials/smart-rollup).
 
-For reference on Smart Rollups, see [Smart Optimistic Rollups](https://tezos.gitlab.io/active/smart_rollups.html) in the Octez documentation.
+For reference on Smart Rollups, see [Smart Optimistic Rollups](https://octez.tezos.com/docs/active/smart_rollups.html) in the Octez documentation.
 
 This diagram shows a high-level view of how Smart Rollups interact with layer 1:
 
@@ -212,7 +212,7 @@ When a commitment includes layer 1 transactions, these transactions go into the
 
 After the commitment is cemented, clients can trigger transactions in the outbox with the Octez client `execute outbox message` command.
 When they trigger a transaction, it runs like any other call to a smart contract.
-For more information, see [Triggering the execution of an outbox message](https://tezos.gitlab.io/shell/smart_rollup_node.html?highlight=triggering) in the Octez documentation.
+For more information, see [Triggering the execution of an outbox message](https://octez.tezos.com/docs/shell/smart_rollup_node.html#triggering-the-execution-of-an-outbox-message) in the Octez documentation.
 
 ### Bailout process
 
@@ -222,7 +222,7 @@ Nodes that post commitments cannot stop immediately without risking their bonds
 For this reason, nodes can switch to bailout mode to prepare to shut down without risking their bonds.
 In bailout mode, nodes defend their existing commitments without posting new commitments.
 When their final commitment is cemented, they can shut down safely.
-For more information about node modes, see [Smart rollup node](https://tezos.gitlab.io/shell/smart_rollup_node.html) in the Octez documentation.
+For more information about node modes, see [Smart rollup node](https://octez.tezos.com/docs/shell/smart_rollup_node.html) in the Octez documentation.
 
 ## Examples
 

diff --git a/docs/architecture/tokens/FA1.2.md b/docs/architecture/tokens/FA1.2.md
@@ -21,7 +21,7 @@ You can verify that a contract follows the FA1.2 standard by running the followi
 octez-client check contract $CONTRACT_ADDRESS implements fa1.2
 ```
 
-The Octez client also supports other interactions with FA1.2 contracts, such as transferring tokens or checking balances, as described at [FA1.2 support](https://tezos.gitlab.io/user/fa12.html) in the Octez documentation.
+The Octez client also supports other interactions with FA1.2 contracts, such as transferring tokens or checking balances, as described at [FA1.2 support](https://octez.tezos.com/docs/user/fa12.html) in the Octez documentation.
 
 ## Allowances
 

diff --git a/docs/developing.md b/docs/developing.md
@@ -59,7 +59,7 @@ See https://taqueria.io/.
 To test smart contracts and dApps, you can use these test environments:
 
 - Test networks behave like Tezos Mainnet but have differences that make it easier to test on them, such as faucets that provide free tokens and reduced block times for faster testing.
-- Sandbox environments like [Flextesa](https://tezos.gitlab.io/flextesa/) run Tezos nodes locally on your computer in a sandbox mode.
+- Sandbox environments like Flextesa and Tezbox run Tezos nodes locally on your computer in a sandbox mode; see [Using a local sandbox](/developing/sandbox).
 - You can also set up your own private test network.
 
 For more information about test environments, see [Testing on testnets](/developing/testnets) and [Using a local sandbox](/developing/sandbox).

diff --git a/docs/developing/octez-client.md b/docs/developing/octez-client.md
@@ -15,5 +15,5 @@ Developers use the Octez client for many tasks, including:
 Other parts of Octez allow you to host, manage, and monitor nodes, bake blocks, and host RPC nodes.
 
 This documentation is an overview of the Octez client for Tezos smart contract and dApp developers.
-For more detailed information, see the [Octez documentation](https://tezos.gitlab.io/) and opentezos.com.
-For system requirements, see the documentation for the latest release of the Octez suite here: https://tezos.gitlab.io/releases/latest.html.
+For more detailed information, see the [Octez documentation](https://octez.tezos.com/docs/) and opentezos.com.
+For system requirements, see the documentation for the latest release of the Octez suite here: https://octez.tezos.com/docs/releases/latest.html.
diff --git a/docs/developing/octez-client/installing.md b/docs/developing/octez-client/installing.md
@@ -38,7 +38,7 @@ Then, initialize it to use the RPC node of your choice:
       dnf install -y tezos-client
       ```
 
-   For more local installation options, see [How to get Tezos](https://tezos.gitlab.io/introduction/howtoget.html) in the Octez documentation.
+   For more local installation options, see [Installing Octez](https://octez.tezos.com/docs/introduction/howtoget.html) in the Octez documentation.
 
 1. Verify that the Octez client is installed by running this command:
 
@@ -47,7 +47,7 @@ Then, initialize it to use the RPC node of your choice:
    ```
 
    If you see a message with the version of Octez that you have installed, the Octez client is installed correctly.
-   For help on Octez, run `octez-client --help` or see the [Octez documentation](http://tezos.gitlab.io/index.html).
+   For help on Octez, run `octez-client --help` or see the [Octez documentation](http://octez.tezos.com/docs/index.html).
 
 1. Initialize the client's configuration file by running this command:
 
@@ -98,4 +98,4 @@ octez-client --version
 
 Then set the RPC node for the client as described above.
 
-For more information about using the Docker image, see [Using Docker Images And Docker-Compose](https://tezos.gitlab.io/introduction/howtoget.html#using-docker-images-and-docker-compose) in the Octez documentation.
+For more information about using the Docker image, see [Using Docker images](https://octez.tezos.com/docs/introduction/howtoget.html#using-docker-images) in the Octez documentation.
diff --git a/docs/developing/sandbox.md b/docs/developing/sandbox.md
@@ -22,8 +22,8 @@ Here are some options for running local Tezos sandboxes:
 
 The Octez client sandboxed and mockup modes run a local version of the Tezos network.
 
-- [Sandboxed mode](https://tezos.gitlab.io/user/sandbox.html) runs a local network with one or more nodes.
-- [Mockup mode](https://tezos.gitlab.io/user/mockup.html) runs a light version of the network without nodes.
+- [Sandboxed mode](https://octez.tezos.com/docs/user/sandbox.html) runs a local network with one or more nodes.
+- [Mockup mode](https://octez.tezos.com/docs/user/mockup.html) runs a light version of the network without nodes.
 
 ## Tezbox
 
@@ -51,7 +51,7 @@ Tezbox provides sample accounts in the `/tezbox/context/accounts.json` file.
 
 ## Flextesa
 
-The [Flextesa](https://tezos.gitlab.io/flextesa/) is also a simulated Tezos environment that runs in a container.
+[Flextesa](https://tezos.gitlab.io/flextesa/) is also a simulated Tezos environment that runs in a container.
 
 The Flextesa image has different scripts that start different versions of the Tezos protocol.
 For example, to start a Flextesa sandbox with the Oxford protocol, run this command:

diff --git a/docs/developing/testing.md b/docs/developing/testing.md
@@ -11,7 +11,7 @@ Tezos smart contracts are immutable after deployment, so you must rigorously tes
 
 - The Michelson interpreter is an OCaml function that can be used by tools to simulate a call to any entry point of any smart contract, given an initial value of the storage and parameters. Some programming languages like LIGO or SmartPy use this as part of their testing frameworks.
 
-- The mockup mode of `octez-client` can be used to test contract calls and other features such as some RPC calls, all without running an actual node, saving the time of going through the consensus mechanism and waiting to get blocks created and validated. Tools like Completium, built by the team behind the Archetype language, use this for their testing framework. Find out more in the [documentation of the mockup mode](https://tezos.gitlab.io/user/mockup.html).
+- The mockup mode of `octez-client` can be used to test contract calls and other features such as some RPC calls, all without running an actual node, saving the time of going through the consensus mechanism and waiting to get blocks created and validated. Tools like Completium, built by the team behind the Archetype language, use this for their testing framework. Find out more in the [documentation of the mockup mode](https://octez.tezos.com/docs/user/mockup.html).
 
    For example, when you compile the contract in the tutorial [Create a smart contract](/tutorials/smart-contract) to Michelson, its first line defines the parameter type that the contract accepts:
 
@@ -101,7 +101,7 @@ For more information about avoiding flaws in contracts, see [Avoiding flaws](htt
 
 ## Implementation details
 
-- Michelson: [Mockup mode](https://tezos.gitlab.io/user/mockup.html)
+- Michelson: [Mockup mode](https://octez.tezos.com/docs/user/mockup.html)
 - Archetype: [Completium test scenario](https://completium.com/docs/contract/test-scenario)
 - SmartPy: [Test scenarios](https://smartpy.io/manual/scenarios/test_scenarios)
 - LIGO: [Testing LIGO](https://ligolang.org/docs/next/testing/)

diff --git a/docs/developing/testnets.md b/docs/developing/testnets.md
@@ -139,5 +139,5 @@ See the [Private blockchain](https://opentezos.com/private) section on OpenTezos
 
 ## More information
 
-- [Test networks by Nomadic Labs](https://tezos.gitlab.io/introduction/test_networks.html)
+- [Test networks](https://octez.tezos.com/docs/user/multinetwork.html#test-networks)
 - Medium post: [Introducing Ghostnet](https://medium.com/the-aleph/introducing-ghostnet-1bf39976e61f)
diff --git a/docs/overview/index.md b/docs/overview/index.md
@@ -21,7 +21,7 @@ This site includes:
 - A brief introduction to Tezos for end users (non-technical users)
 - A presentation of the main Tezos concepts and features for technical users, including developers and bakers
 
-For more details on installing, using, or contributing to the platform, see the Octez documentation at https://tezos.gitlab.io/index.html.
+For more details on installing, using, or contributing to the platform, see the Octez documentation at https://octez.tezos.com/docs/.
 
 For interactive learning material (including exercises) about Tezos concepts, the underlying technology, application development, and the ecosystem, see https://opentezos.com.
 
@@ -102,7 +102,7 @@ The proof-of-stake consensus mechanism eliminates the need for high energy use,
 
 Tezos's proof-of-stake mechanism improves scalability and encourages cooperation via incentives. It also increases the cost of consensus attacks and avoids environmentally wasteful proof-of-work. Tezos launched in June 2018 as one of the first major proof-of-stake networks.
 
-For more information about how Tezos handles proof of stake, see https://tezos.gitlab.io/alpha/proof_of_stake.html.
+For more information about how Tezos handles proof of stake, see https://octez.tezos.com/docs/active/proof_of_stake.html.
 For more information about delegating and staking, see [Bakers](/architecture/bakers).
 
 ### Tezos accepts multiple languages

diff --git a/docs/overview/resources.md b/docs/overview/resources.md
@@ -12,7 +12,7 @@ This site is not exhaustive. It covers the main topics that concern Tezos develo
 More detailed developer and user documentation on Tezos in general or on specific tools in the Tezos ecosystem is available at these sites:
 
 - https://opentezos.com/ is a complete course for learning Tezos concepts, mainly for developers but also for bakers and other users, in the form of tutorials with exercises
-- https://tezos.gitlab.io/ is the official documentation of the Octez suite, which contains a complete implementation of the Tezos platform (including a node, a baker, a client, and other tools)
+- https://octez.tezos.com/docs/ is the official documentation of the Octez suite, which contains a complete implementation of the Tezos platform (including a node, a baker, a client, and other tools)
 - https://taqueria.io/docs/intro/ is the official documentation of [Taqueria](https://taqueria.io/), a flexible framework for building Web3 applications on Tezos
 - https://tezostaquito.io/docs/quick_start is the official documentation of [Taquito](https://tezostaquito.io/), a TypeScript library for developing Tezos applications faster and easier
 - https://ligolang.org/docs/intro/introduction is the official documentation of the [LIGO](https://ligolang.org/) language for writing Tezos smart contracts

diff --git a/docs/reference/style-guide.md b/docs/reference/style-guide.md
@@ -20,7 +20,7 @@ You can say that Tezos has advantages over other blockchains, but don't say that
 
 - Do not use the term "initial coin offering (ICO)" or refer to Tezos "investors."
 Instead, refer to the Tezos fundraiser.
-See https://tezos.gitlab.io/user/key-management.html#getting-keys-for-fundraiser-accounts.
+See https://octez.tezos.com/docs/user/key-management.html#getting-keys-for-fundraiser-accounts.
 
 ## Blockchain terminology
 

diff --git a/docs/smart-contracts.mdx b/docs/smart-contracts.mdx
@@ -104,6 +104,6 @@ A smart contract can be called by a classic account or by a smart contract accou
 
 Users can call smart contracts from different platforms, including:
 
-- The Octez command-line program, which is provided by Tezos to send transactions to Tezos and interact with the chain in other ways, including hosting a node. For more information about the Octez client, see https://tezos.gitlab.io/.
+- The Octez command-line program, which is provided by Tezos to send transactions to Tezos and interact with the chain in other ways, including hosting a node. For more information about the Octez client, see https://octez.tezos.com/docs/.
 - Remote Procedure Calls (RPCs) via HTTP.
 - SDKs such as [Taquito](https://tezostaquito.io/).
diff --git a/docs/smart-contracts/constants.md b/docs/smart-contracts/constants.md
@@ -15,6 +15,6 @@ It can be used to store code, types, or data.
 
 ## Implementation details
 
-- Michelson: [Global constants](https://tezos.gitlab.io/active/global_constants.html)
+- Michelson: [Global constants](https://octez.tezos.com/docs/active/global_constants.html)
 - LIGO: [Global constants](https://ligolang.org/docs/protocol/hangzhou#global-constant)
 - Archetype: [Global constants](https://archetype-lang.org/docs/cli/contract/)