cartesi · jplgarcia · Mar 20, 2025 · Mar 20, 2025 · Mar 20, 2025 · Mar 20, 2025
diff --git a/.github/workflows/deploy-staging.yml b/.github/workflows/deploy-staging.yml
@@ -0,0 +1,55 @@
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches:
+      - Staging
+  workflow_dispatch:
+
+permissions:
+  pages: write
+  id-token: write
+  contents: write
+
+jobs:
+  build:
+    name: Build and upload artifact
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        shell: bash
+        working-directory: ./docs
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+
+      - name: Clone submodules
+        run: |
+          git submodule init
+          git submodule update --init --recursive
+      - name: Install dependencies
+        run: yarn
+      - name: Build website
+        run: yarn build
+      - name: Setup Pages
+        uses: actions/configure-pages@v4
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: build
+
+  deploy:
+    name: Deploy to GitHub Pages
+    needs: build
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4
diff --git a/...ed_docs/version-0.8/api/graphql/basics.md → ...rchived_version-0.8/api/graphql/basics.md b/...ed_docs/version-0.8/api/graphql/basics.md → ...rchived_version-0.8/api/graphql/basics.md
diff --git a/...0.8/api/graphql/directives/_category_.yml → ...0.8/api/graphql/directives/_category_.yml b/...0.8/api/graphql/directives/_category_.yml → ...0.8/api/graphql/directives/_category_.yml
diff --git a/...0.8/api/graphql/directives/deprecated.mdx → ...0.8/api/graphql/directives/deprecated.mdx b/...0.8/api/graphql/directives/deprecated.mdx → ...0.8/api/graphql/directives/deprecated.mdx
diff --git a/...on-0.8/api/graphql/directives/include.mdx → ...on-0.8/api/graphql/directives/include.mdx b/...on-0.8/api/graphql/directives/include.mdx → ...on-0.8/api/graphql/directives/include.mdx
diff --git a/...rsion-0.8/api/graphql/directives/skip.mdx → ...rsion-0.8/api/graphql/directives/skip.mdx b/...rsion-0.8/api/graphql/directives/skip.mdx → ...rsion-0.8/api/graphql/directives/skip.mdx
diff --git a/...8/api/graphql/directives/specified-by.mdx → ...8/api/graphql/directives/specified-by.mdx b/...8/api/graphql/directives/specified-by.mdx → ...8/api/graphql/directives/specified-by.mdx
diff --git a/...docs/version-0.8/api/graphql/generated.md → ...ived_version-0.8/api/graphql/generated.md b/...docs/version-0.8/api/graphql/generated.md → ...ived_version-0.8/api/graphql/generated.md
diff --git a/...ion-0.8/api/graphql/inputs/_category_.yml → ...ion-0.8/api/graphql/inputs/_category_.yml b/...ion-0.8/api/graphql/inputs/_category_.yml → ...ion-0.8/api/graphql/inputs/_category_.yml
diff --git a/...n-0.8/api/graphql/inputs/input-filter.mdx → ...n-0.8/api/graphql/inputs/input-filter.mdx b/...n-0.8/api/graphql/inputs/input-filter.mdx → ...n-0.8/api/graphql/inputs/input-filter.mdx
diff --git a/...-0.8/api/graphql/inputs/notice-filter.mdx → ...-0.8/api/graphql/inputs/notice-filter.mdx b/...-0.8/api/graphql/inputs/notice-filter.mdx → ...-0.8/api/graphql/inputs/notice-filter.mdx
diff --git a/...-0.8/api/graphql/inputs/report-filter.mdx → ...-0.8/api/graphql/inputs/report-filter.mdx b/...-0.8/api/graphql/inputs/report-filter.mdx → ...-0.8/api/graphql/inputs/report-filter.mdx
diff --git a/...0.8/api/graphql/inputs/voucher-filter.mdx → ...0.8/api/graphql/inputs/voucher-filter.mdx b/...0.8/api/graphql/inputs/voucher-filter.mdx → ...0.8/api/graphql/inputs/voucher-filter.mdx
diff --git a/...on-0.8/api/graphql/objects/_category_.yml → ...on-0.8/api/graphql/objects/_category_.yml b/...on-0.8/api/graphql/objects/_category_.yml → ...on-0.8/api/graphql/objects/_category_.yml
diff --git a/.../api/graphql/objects/epoch-connection.mdx → .../api/graphql/objects/epoch-connection.mdx b/.../api/graphql/objects/epoch-connection.mdx → .../api/graphql/objects/epoch-connection.mdx
diff --git a/...on-0.8/api/graphql/objects/epoch-edge.mdx → ...on-0.8/api/graphql/objects/epoch-edge.mdx b/...on-0.8/api/graphql/objects/epoch-edge.mdx → ...on-0.8/api/graphql/objects/epoch-edge.mdx
diff --git a/...version-0.8/api/graphql/objects/epoch.mdx → ...version-0.8/api/graphql/objects/epoch.mdx b/...version-0.8/api/graphql/objects/epoch.mdx → ...version-0.8/api/graphql/objects/epoch.mdx
diff --git a/.../api/graphql/objects/input-connection.mdx → .../api/graphql/objects/input-connection.mdx b/.../api/graphql/objects/input-connection.mdx → .../api/graphql/objects/input-connection.mdx
diff --git a/...on-0.8/api/graphql/objects/input-edge.mdx → ...on-0.8/api/graphql/objects/input-edge.mdx b/...on-0.8/api/graphql/objects/input-edge.mdx → ...on-0.8/api/graphql/objects/input-edge.mdx
diff --git a/...version-0.8/api/graphql/objects/input.mdx → ...version-0.8/api/graphql/objects/input.mdx b/...version-0.8/api/graphql/objects/input.mdx → ...version-0.8/api/graphql/objects/input.mdx
diff --git a/...api/graphql/objects/notice-connection.mdx → ...api/graphql/objects/notice-connection.mdx b/...api/graphql/objects/notice-connection.mdx → ...api/graphql/objects/notice-connection.mdx
diff --git a/...n-0.8/api/graphql/objects/notice-edge.mdx → ...n-0.8/api/graphql/objects/notice-edge.mdx b/...n-0.8/api/graphql/objects/notice-edge.mdx → ...n-0.8/api/graphql/objects/notice-edge.mdx
diff --git a/...ersion-0.8/api/graphql/objects/notice.mdx → ...ersion-0.8/api/graphql/objects/notice.mdx b/...ersion-0.8/api/graphql/objects/notice.mdx → ...ersion-0.8/api/graphql/objects/notice.mdx
diff --git a/...ion-0.8/api/graphql/objects/page-info.mdx → ...ion-0.8/api/graphql/objects/page-info.mdx b/...ion-0.8/api/graphql/objects/page-info.mdx → ...ion-0.8/api/graphql/objects/page-info.mdx
diff --git a/...version-0.8/api/graphql/objects/proof.mdx → ...version-0.8/api/graphql/objects/proof.mdx b/...version-0.8/api/graphql/objects/proof.mdx → ...version-0.8/api/graphql/objects/proof.mdx
diff --git a/...api/graphql/objects/report-connection.mdx → ...api/graphql/objects/report-connection.mdx b/...api/graphql/objects/report-connection.mdx → ...api/graphql/objects/report-connection.mdx
diff --git a/...n-0.8/api/graphql/objects/report-edge.mdx → ...n-0.8/api/graphql/objects/report-edge.mdx b/...n-0.8/api/graphql/objects/report-edge.mdx → ...n-0.8/api/graphql/objects/report-edge.mdx
diff --git a/...ersion-0.8/api/graphql/objects/report.mdx → ...ersion-0.8/api/graphql/objects/report.mdx b/...ersion-0.8/api/graphql/objects/report.mdx → ...ersion-0.8/api/graphql/objects/report.mdx
diff --git a/...pi/graphql/objects/voucher-connection.mdx → ...pi/graphql/objects/voucher-connection.mdx b/...pi/graphql/objects/voucher-connection.mdx → ...pi/graphql/objects/voucher-connection.mdx
diff --git a/...-0.8/api/graphql/objects/voucher-edge.mdx → ...-0.8/api/graphql/objects/voucher-edge.mdx b/...-0.8/api/graphql/objects/voucher-edge.mdx → ...-0.8/api/graphql/objects/voucher-edge.mdx
diff --git a/...rsion-0.8/api/graphql/objects/voucher.mdx → ...rsion-0.8/api/graphql/objects/voucher.mdx b/...rsion-0.8/api/graphql/objects/voucher.mdx → ...rsion-0.8/api/graphql/objects/voucher.mdx
diff --git a/...on-0.8/api/graphql/queries/_category_.yml → ...on-0.8/api/graphql/queries/_category_.yml b/...on-0.8/api/graphql/queries/_category_.yml → ...on-0.8/api/graphql/queries/_category_.yml
diff --git a/...rsion-0.8/api/graphql/queries/epoch-i.mdx → ...rsion-0.8/api/graphql/queries/epoch-i.mdx b/...rsion-0.8/api/graphql/queries/epoch-i.mdx → ...rsion-0.8/api/graphql/queries/epoch-i.mdx
diff --git a/...version-0.8/api/graphql/queries/epoch.mdx → ...version-0.8/api/graphql/queries/epoch.mdx b/...version-0.8/api/graphql/queries/epoch.mdx → ...version-0.8/api/graphql/queries/epoch.mdx
diff --git a/...ersion-0.8/api/graphql/queries/epochs.mdx → ...ersion-0.8/api/graphql/queries/epochs.mdx b/...ersion-0.8/api/graphql/queries/epochs.mdx → ...ersion-0.8/api/graphql/queries/epochs.mdx
diff --git a/...version-0.8/api/graphql/queries/input.mdx → ...version-0.8/api/graphql/queries/input.mdx b/...version-0.8/api/graphql/queries/input.mdx → ...version-0.8/api/graphql/queries/input.mdx
diff --git a/...ersion-0.8/api/graphql/queries/inputs.mdx → ...ersion-0.8/api/graphql/queries/inputs.mdx b/...ersion-0.8/api/graphql/queries/inputs.mdx → ...ersion-0.8/api/graphql/queries/inputs.mdx
diff --git a/...ersion-0.8/api/graphql/queries/notice.mdx → ...ersion-0.8/api/graphql/queries/notice.mdx b/...ersion-0.8/api/graphql/queries/notice.mdx → ...ersion-0.8/api/graphql/queries/notice.mdx
diff --git a/...rsion-0.8/api/graphql/queries/notices.mdx → ...rsion-0.8/api/graphql/queries/notices.mdx b/...rsion-0.8/api/graphql/queries/notices.mdx → ...rsion-0.8/api/graphql/queries/notices.mdx
diff --git a/...ersion-0.8/api/graphql/queries/report.mdx → ...ersion-0.8/api/graphql/queries/report.mdx b/...ersion-0.8/api/graphql/queries/report.mdx → ...ersion-0.8/api/graphql/queries/report.mdx
diff --git a/...rsion-0.8/api/graphql/queries/reports.mdx → ...rsion-0.8/api/graphql/queries/reports.mdx b/...rsion-0.8/api/graphql/queries/reports.mdx → ...rsion-0.8/api/graphql/queries/reports.mdx
diff --git a/...rsion-0.8/api/graphql/queries/voucher.mdx → ...rsion-0.8/api/graphql/queries/voucher.mdx b/...rsion-0.8/api/graphql/queries/voucher.mdx → ...rsion-0.8/api/graphql/queries/voucher.mdx
diff --git a/...sion-0.8/api/graphql/queries/vouchers.mdx → ...sion-0.8/api/graphql/queries/vouchers.mdx b/...sion-0.8/api/graphql/queries/vouchers.mdx → ...sion-0.8/api/graphql/queries/vouchers.mdx
diff --git a/...on-0.8/api/graphql/scalars/_category_.yml → ...on-0.8/api/graphql/scalars/_category_.yml b/...on-0.8/api/graphql/scalars/_category_.yml → ...on-0.8/api/graphql/scalars/_category_.yml
diff --git a/...rsion-0.8/api/graphql/scalars/big-int.mdx → ...rsion-0.8/api/graphql/scalars/big-int.mdx b/...rsion-0.8/api/graphql/scalars/big-int.mdx → ...rsion-0.8/api/graphql/scalars/big-int.mdx
diff --git a/...rsion-0.8/api/graphql/scalars/boolean.mdx → ...rsion-0.8/api/graphql/scalars/boolean.mdx b/...rsion-0.8/api/graphql/scalars/boolean.mdx → ...rsion-0.8/api/graphql/scalars/boolean.mdx
diff --git a/...cs/version-0.8/api/graphql/scalars/id.mdx → ...ed_version-0.8/api/graphql/scalars/id.mdx b/...cs/version-0.8/api/graphql/scalars/id.mdx → ...ed_version-0.8/api/graphql/scalars/id.mdx
diff --git a/...s/version-0.8/api/graphql/scalars/int.mdx → ...d_version-0.8/api/graphql/scalars/int.mdx b/...s/version-0.8/api/graphql/scalars/int.mdx → ...d_version-0.8/api/graphql/scalars/int.mdx
diff --git a/...ersion-0.8/api/graphql/scalars/string.mdx → ...ersion-0.8/api/graphql/scalars/string.mdx b/...ersion-0.8/api/graphql/scalars/string.mdx → ...ersion-0.8/api/graphql/scalars/string.mdx
diff --git a/...version-0.8/api/graphql/sidebar-schema.js → ...version-0.8/api/graphql/sidebar-schema.js b/...version-0.8/api/graphql/sidebar-schema.js → ...version-0.8/api/graphql/sidebar-schema.js
diff --git a/...rsioned_docs/version-0.8/api/inspect.yaml → ...cs/_archived_version-0.8/api/inspect.yaml b/...rsioned_docs/version-0.8/api/inspect.yaml → ...cs/_archived_version-0.8/api/inspect.yaml
diff --git a/...ate-http-api-for-cartesi-rollups.info.mdx → ...ate-http-api-for-cartesi-rollups.info.mdx b/...ate-http-api-for-cartesi-rollups.info.mdx → ...ate-http-api-for-cartesi-rollups.info.mdx
diff --git a/...s/version-0.8/api/inspect/inspect.api.mdx → ...d_version-0.8/api/inspect/inspect.api.mdx b/...s/version-0.8/api/inspect/inspect.api.mdx → ...d_version-0.8/api/inspect/inspect.api.mdx
diff --git a/...ocs/version-0.8/api/json-rpc/sol-input.md → ...ved_version-0.8/api/json-rpc/sol-input.md b/...ocs/version-0.8/api/json-rpc/sol-input.md → ...ved_version-0.8/api/json-rpc/sol-input.md
diff --git a/...cs/version-0.8/api/json-rpc/sol-output.md → ...ed_version-0.8/api/json-rpc/sol-output.md b/...cs/version-0.8/api/json-rpc/sol-output.md → ...ed_version-0.8/api/json-rpc/sol-output.md
diff --git a/...ersioned_docs/version-0.8/api/rollup.yaml → ...ocs/_archived_version-0.8/api/rollup.yaml b/...ersioned_docs/version-0.8/api/rollup.yaml → ...ocs/_archived_version-0.8/api/rollup.yaml
diff --git a/...version-0.8/api/rollup/add-notice.api.mdx → ...version-0.8/api/rollup/add-notice.api.mdx b/...version-0.8/api/rollup/add-notice.api.mdx → ...version-0.8/api/rollup/add-notice.api.mdx
diff --git a/...version-0.8/api/rollup/add-report.api.mdx → ...version-0.8/api/rollup/add-report.api.mdx b/...version-0.8/api/rollup/add-report.api.mdx → ...version-0.8/api/rollup/add-report.api.mdx
diff --git a/...ersion-0.8/api/rollup/add-voucher.api.mdx → ...ersion-0.8/api/rollup/add-voucher.api.mdx b/...ersion-0.8/api/rollup/add-voucher.api.mdx → ...ersion-0.8/api/rollup/add-voucher.api.mdx
diff --git a/...i/rollup/cartesi-rollup-http-api.info.mdx → ...i/rollup/cartesi-rollup-http-api.info.mdx b/...i/rollup/cartesi-rollup-http-api.info.mdx → ...i/rollup/cartesi-rollup-http-api.info.mdx
diff --git a/...ocs/version-0.8/api/rollup/finish.api.mdx → ...ved_version-0.8/api/rollup/finish.api.mdx b/...ocs/version-0.8/api/rollup/finish.api.mdx → ...ved_version-0.8/api/rollup/finish.api.mdx
diff --git a/...0.8/api/rollup/register-exception.api.mdx → ...0.8/api/rollup/register-exception.api.mdx b/...0.8/api/rollup/register-exception.api.mdx → ...0.8/api/rollup/register-exception.api.mdx
diff --git a/...ed_docs/version-0.8/api/rollup/sidebar.ts → ...rchived_version-0.8/api/rollup/sidebar.ts b/...ed_docs/version-0.8/api/rollup/sidebar.ts → ...rchived_version-0.8/api/rollup/sidebar.ts
diff --git a/...ned_docs/version-0.8/api/typeDefs.graphql → ...archived_version-0.8/api/typeDefs.graphql b/...ned_docs/version-0.8/api/typeDefs.graphql → ...archived_version-0.8/api/typeDefs.graphql
diff --git a/...rsioned_docs/version-0.8/back-end-api.png → ...cs/_archived_version-0.8/back-end-api.png b/...rsioned_docs/version-0.8/back-end-api.png → ...cs/_archived_version-0.8/back-end-api.png
diff --git a/...cs/version-0.8/build-dapps/create-dapp.md → ...ed_version-0.8/build-dapps/create-dapp.md b/...cs/version-0.8/build-dapps/create-dapp.md → ...ed_version-0.8/build-dapps/create-dapp.md
diff --git a/...version-0.8/build-dapps/dapp-host-mode.md → ...version-0.8/build-dapps/dapp-host-mode.md b/...version-0.8/build-dapps/dapp-host-mode.md → ...version-0.8/build-dapps/dapp-host-mode.md
diff --git a/...ersion-0.8/build-dapps/deploying-dapps.md → ...ersion-0.8/build-dapps/deploying-dapps.md b/...ersion-0.8/build-dapps/deploying-dapps.md → ...ersion-0.8/build-dapps/deploying-dapps.md
diff --git a/..._docs/version-0.8/build-dapps/overview.md → ...hived_version-0.8/build-dapps/overview.md b/..._docs/version-0.8/build-dapps/overview.md → ...hived_version-0.8/build-dapps/overview.md
diff --git a/...s/version-0.8/build-dapps/requirements.md → ...d_version-0.8/build-dapps/requirements.md b/...s/version-0.8/build-dapps/requirements.md → ...d_version-0.8/build-dapps/requirements.md
diff --git a/..._docs/version-0.8/build-dapps/run-dapp.md → ...hived_version-0.8/build-dapps/run-dapp.md b/..._docs/version-0.8/build-dapps/run-dapp.md → ...hived_version-0.8/build-dapps/run-dapp.md
diff --git a/..._versioned_docs/version-0.8/components.md → ..._docs/_archived_version-0.8/components.md b/..._versioned_docs/version-0.8/components.md → ..._docs/_archived_version-0.8/components.md
diff --git a/...oned_docs/version-0.8/core-components.png → ..._archived_version-0.8/core-components.png b/...oned_docs/version-0.8/core-components.png → ..._archived_version-0.8/core-components.png
diff --git a/..._versioned_docs/version-0.8/dapp-arch.png → ..._docs/_archived_version-0.8/dapp-arch.png b/..._versioned_docs/version-0.8/dapp-arch.png → ..._docs/_archived_version-0.8/dapp-arch.png
diff --git a/...ned_docs/version-0.8/dapp-architecture.md → ...archived_version-0.8/dapp-architecture.md b/...ned_docs/version-0.8/dapp-architecture.md → ...archived_version-0.8/dapp-architecture.md
diff --git a/...ioned_docs/version-0.8/dapp-life-cycle.md → .../_archived_version-0.8/dapp-life-cycle.md b/...ioned_docs/version-0.8/dapp-life-cycle.md → .../_archived_version-0.8/dapp-life-cycle.md
diff --git a/...sioned_docs/version-0.8/front-end-api.png → ...s/_archived_version-0.8/front-end-api.png b/...sioned_docs/version-0.8/front-end-api.png → ...s/_archived_version-0.8/front-end-api.png
diff --git a/...ps_versioned_docs/version-0.8/http-api.md → ...ed_docs/_archived_version-0.8/http-api.md b/...ps_versioned_docs/version-0.8/http-api.md → ...ed_docs/_archived_version-0.8/http-api.md
diff --git a/..._docs/version-0.8/offchain-components.png → ...hived_version-0.8/offchain-components.png b/..._docs/version-0.8/offchain-components.png → ...hived_version-0.8/offchain-components.png
diff --git a/...d_docs/version-0.8/onchain-components.png → ...chived_version-0.8/onchain-components.png b/...d_docs/version-0.8/onchain-components.png → ...chived_version-0.8/onchain-components.png
diff --git a/...ioned_docs/version-0.8/onchain-phases.png → .../_archived_version-0.8/onchain-phases.png b/...ioned_docs/version-0.8/onchain-phases.png → .../_archived_version-0.8/onchain-phases.png
diff --git a/...ned_docs/version-0.8/onchain-timeline.png → ...archived_version-0.8/onchain-timeline.png b/...ned_docs/version-0.8/onchain-timeline.png → ...archived_version-0.8/onchain-timeline.png
diff --git a/...ps_versioned_docs/version-0.8/overview.md → ...ed_docs/_archived_version-0.8/overview.md b/...ps_versioned_docs/version-0.8/overview.md → ...ed_docs/_archived_version-0.8/overview.md
diff --git a/...ned_docs/version-0.8/sequence-diagram.png → ...archived_version-0.8/sequence-diagram.png b/...ned_docs/version-0.8/sequence-diagram.png → ...archived_version-0.8/sequence-diagram.png
diff --git a/...ned_docs/version-0.8/sequence-diagram.txt → ...archived_version-0.8/sequence-diagram.txt b/...ned_docs/version-0.8/sequence-diagram.txt → ...archived_version-0.8/sequence-diagram.txt
diff --git a/...ups_versioned_docs/version-0.8/stages.png → ...ned_docs/_archived_version-0.8/stages.png b/...ups_versioned_docs/version-0.8/stages.png → ...ned_docs/_archived_version-0.8/stages.png
diff --git a/...ed_docs/version-0.9/api/graphql/basics.md → ...rchived_version-0.9/api/graphql/basics.md b/...ed_docs/version-0.9/api/graphql/basics.md → ...rchived_version-0.9/api/graphql/basics.md
diff --git a/...0.9/api/graphql/directives/_category_.yml → ...0.9/api/graphql/directives/_category_.yml b/...0.9/api/graphql/directives/_category_.yml → ...0.9/api/graphql/directives/_category_.yml
diff --git a/...0.9/api/graphql/directives/deprecated.mdx → ...0.9/api/graphql/directives/deprecated.mdx b/...0.9/api/graphql/directives/deprecated.mdx → ...0.9/api/graphql/directives/deprecated.mdx
diff --git a/...on-0.9/api/graphql/directives/include.mdx → ...on-0.9/api/graphql/directives/include.mdx b/...on-0.9/api/graphql/directives/include.mdx → ...on-0.9/api/graphql/directives/include.mdx
diff --git a/...rsion-0.9/api/graphql/directives/skip.mdx → ...rsion-0.9/api/graphql/directives/skip.mdx b/...rsion-0.9/api/graphql/directives/skip.mdx → ...rsion-0.9/api/graphql/directives/skip.mdx
diff --git a/...9/api/graphql/directives/specified-by.mdx → ...9/api/graphql/directives/specified-by.mdx b/...9/api/graphql/directives/specified-by.mdx → ...9/api/graphql/directives/specified-by.mdx
diff --git a/...docs/version-0.9/api/graphql/generated.md → ...ived_version-0.9/api/graphql/generated.md b/...docs/version-0.9/api/graphql/generated.md → ...ived_version-0.9/api/graphql/generated.md
diff --git a/...ion-0.9/api/graphql/inputs/_category_.yml → ...ion-0.9/api/graphql/inputs/_category_.yml b/...ion-0.9/api/graphql/inputs/_category_.yml → ...ion-0.9/api/graphql/inputs/_category_.yml
diff --git a/...n-0.9/api/graphql/inputs/input-filter.mdx → ...n-0.9/api/graphql/inputs/input-filter.mdx b/...n-0.9/api/graphql/inputs/input-filter.mdx → ...n-0.9/api/graphql/inputs/input-filter.mdx
diff --git a/...on-0.9/api/graphql/objects/_category_.yml → ...on-0.9/api/graphql/objects/_category_.yml b/...on-0.9/api/graphql/objects/_category_.yml → ...on-0.9/api/graphql/objects/_category_.yml
diff --git a/.../api/graphql/objects/input-connection.mdx → .../api/graphql/objects/input-connection.mdx b/.../api/graphql/objects/input-connection.mdx → .../api/graphql/objects/input-connection.mdx
diff --git a/...on-0.9/api/graphql/objects/input-edge.mdx → ...on-0.9/api/graphql/objects/input-edge.mdx b/...on-0.9/api/graphql/objects/input-edge.mdx → ...on-0.9/api/graphql/objects/input-edge.mdx
diff --git a/...version-0.9/api/graphql/objects/input.mdx → ...version-0.9/api/graphql/objects/input.mdx b/...version-0.9/api/graphql/objects/input.mdx → ...version-0.9/api/graphql/objects/input.mdx
diff --git a/...api/graphql/objects/notice-connection.mdx → ...api/graphql/objects/notice-connection.mdx b/...api/graphql/objects/notice-connection.mdx → ...api/graphql/objects/notice-connection.mdx
diff --git a/...n-0.9/api/graphql/objects/notice-edge.mdx → ...n-0.9/api/graphql/objects/notice-edge.mdx b/...n-0.9/api/graphql/objects/notice-edge.mdx → ...n-0.9/api/graphql/objects/notice-edge.mdx
diff --git a/...ersion-0.9/api/graphql/objects/notice.mdx → ...ersion-0.9/api/graphql/objects/notice.mdx b/...ersion-0.9/api/graphql/objects/notice.mdx → ...ersion-0.9/api/graphql/objects/notice.mdx
diff --git a/...graphql/objects/output-validity-proof.mdx → ...graphql/objects/output-validity-proof.mdx b/...graphql/objects/output-validity-proof.mdx → ...graphql/objects/output-validity-proof.mdx
diff --git a/...ion-0.9/api/graphql/objects/page-info.mdx → ...ion-0.9/api/graphql/objects/page-info.mdx b/...ion-0.9/api/graphql/objects/page-info.mdx → ...ion-0.9/api/graphql/objects/page-info.mdx
diff --git a/...version-0.9/api/graphql/objects/proof.mdx → ...version-0.9/api/graphql/objects/proof.mdx b/...version-0.9/api/graphql/objects/proof.mdx → ...version-0.9/api/graphql/objects/proof.mdx
diff --git a/...api/graphql/objects/report-connection.mdx → ...api/graphql/objects/report-connection.mdx b/...api/graphql/objects/report-connection.mdx → ...api/graphql/objects/report-connection.mdx
diff --git a/...n-0.9/api/graphql/objects/report-edge.mdx → ...n-0.9/api/graphql/objects/report-edge.mdx b/...n-0.9/api/graphql/objects/report-edge.mdx → ...n-0.9/api/graphql/objects/report-edge.mdx
diff --git a/...ersion-0.9/api/graphql/objects/report.mdx → ...ersion-0.9/api/graphql/objects/report.mdx b/...ersion-0.9/api/graphql/objects/report.mdx → ...ersion-0.9/api/graphql/objects/report.mdx
diff --git a/...pi/graphql/objects/voucher-connection.mdx → ...pi/graphql/objects/voucher-connection.mdx b/...pi/graphql/objects/voucher-connection.mdx → ...pi/graphql/objects/voucher-connection.mdx
diff --git a/...-0.9/api/graphql/objects/voucher-edge.mdx → ...-0.9/api/graphql/objects/voucher-edge.mdx b/...-0.9/api/graphql/objects/voucher-edge.mdx → ...-0.9/api/graphql/objects/voucher-edge.mdx
diff --git a/...rsion-0.9/api/graphql/objects/voucher.mdx → ...rsion-0.9/api/graphql/objects/voucher.mdx b/...rsion-0.9/api/graphql/objects/voucher.mdx → ...rsion-0.9/api/graphql/objects/voucher.mdx
diff --git a/...on-0.9/api/graphql/queries/_category_.yml → ...on-0.9/api/graphql/queries/_category_.yml b/...on-0.9/api/graphql/queries/_category_.yml → ...on-0.9/api/graphql/queries/_category_.yml
diff --git a/...version-0.9/api/graphql/queries/input.mdx → ...version-0.9/api/graphql/queries/input.mdx b/...version-0.9/api/graphql/queries/input.mdx → ...version-0.9/api/graphql/queries/input.mdx
diff --git a/...ersion-0.9/api/graphql/queries/inputs.mdx → ...ersion-0.9/api/graphql/queries/inputs.mdx b/...ersion-0.9/api/graphql/queries/inputs.mdx → ...ersion-0.9/api/graphql/queries/inputs.mdx
diff --git a/...ersion-0.9/api/graphql/queries/notice.mdx → ...ersion-0.9/api/graphql/queries/notice.mdx b/...ersion-0.9/api/graphql/queries/notice.mdx → ...ersion-0.9/api/graphql/queries/notice.mdx
diff --git a/...rsion-0.9/api/graphql/queries/notices.mdx → ...rsion-0.9/api/graphql/queries/notices.mdx b/...rsion-0.9/api/graphql/queries/notices.mdx → ...rsion-0.9/api/graphql/queries/notices.mdx
diff --git a/...ersion-0.9/api/graphql/queries/report.mdx → ...ersion-0.9/api/graphql/queries/report.mdx b/...ersion-0.9/api/graphql/queries/report.mdx → ...ersion-0.9/api/graphql/queries/report.mdx
diff --git a/...rsion-0.9/api/graphql/queries/reports.mdx → ...rsion-0.9/api/graphql/queries/reports.mdx b/...rsion-0.9/api/graphql/queries/reports.mdx → ...rsion-0.9/api/graphql/queries/reports.mdx
diff --git a/...rsion-0.9/api/graphql/queries/voucher.mdx → ...rsion-0.9/api/graphql/queries/voucher.mdx b/...rsion-0.9/api/graphql/queries/voucher.mdx → ...rsion-0.9/api/graphql/queries/voucher.mdx
diff --git a/...sion-0.9/api/graphql/queries/vouchers.mdx → ...sion-0.9/api/graphql/queries/vouchers.mdx b/...sion-0.9/api/graphql/queries/vouchers.mdx → ...sion-0.9/api/graphql/queries/vouchers.mdx
diff --git a/...on-0.9/api/graphql/scalars/_category_.yml → ...on-0.9/api/graphql/scalars/_category_.yml b/...on-0.9/api/graphql/scalars/_category_.yml → ...on-0.9/api/graphql/scalars/_category_.yml
diff --git a/...rsion-0.9/api/graphql/scalars/big-int.mdx → ...rsion-0.9/api/graphql/scalars/big-int.mdx b/...rsion-0.9/api/graphql/scalars/big-int.mdx → ...rsion-0.9/api/graphql/scalars/big-int.mdx
diff --git a/...rsion-0.9/api/graphql/scalars/boolean.mdx → ...rsion-0.9/api/graphql/scalars/boolean.mdx b/...rsion-0.9/api/graphql/scalars/boolean.mdx → ...rsion-0.9/api/graphql/scalars/boolean.mdx
diff --git a/...s/version-0.9/api/graphql/scalars/int.mdx → ...d_version-0.9/api/graphql/scalars/int.mdx b/...s/version-0.9/api/graphql/scalars/int.mdx → ...d_version-0.9/api/graphql/scalars/int.mdx
diff --git a/...ersion-0.9/api/graphql/scalars/string.mdx → ...ersion-0.9/api/graphql/scalars/string.mdx b/...ersion-0.9/api/graphql/scalars/string.mdx → ...ersion-0.9/api/graphql/scalars/string.mdx
diff --git a/...version-0.9/api/graphql/sidebar-schema.js → ...version-0.9/api/graphql/sidebar-schema.js b/...version-0.9/api/graphql/sidebar-schema.js → ...version-0.9/api/graphql/sidebar-schema.js
diff --git a/...rsioned_docs/version-0.9/api/inspect.yaml → ...cs/_archived_version-0.9/api/inspect.yaml b/...rsioned_docs/version-0.9/api/inspect.yaml → ...cs/_archived_version-0.9/api/inspect.yaml
diff --git a/...ate-http-api-for-cartesi-rollups.info.mdx → ...ate-http-api-for-cartesi-rollups.info.mdx b/...ate-http-api-for-cartesi-rollups.info.mdx → ...ate-http-api-for-cartesi-rollups.info.mdx
diff --git a/...s/version-0.9/api/inspect/inspect.api.mdx → ...d_version-0.9/api/inspect/inspect.api.mdx b/...s/version-0.9/api/inspect/inspect.api.mdx → ...d_version-0.9/api/inspect/inspect.api.mdx
diff --git a/...d_docs/version-0.9/api/json-rpc/basics.md → ...chived_version-0.9/api/json-rpc/basics.md b/...d_docs/version-0.9/api/json-rpc/basics.md → ...chived_version-0.9/api/json-rpc/basics.md
diff --git a/...pi/json-rpc/portals/ERC1155BatchPortal.md → ...pi/json-rpc/portals/ERC1155BatchPortal.md b/...pi/json-rpc/portals/ERC1155BatchPortal.md → ...pi/json-rpc/portals/ERC1155BatchPortal.md
diff --git a/...i/json-rpc/portals/ERC1155SinglePortal.md → ...i/json-rpc/portals/ERC1155SinglePortal.md b/...i/json-rpc/portals/ERC1155SinglePortal.md → ...i/json-rpc/portals/ERC1155SinglePortal.md
diff --git a/...n-0.9/api/json-rpc/portals/ERC20Portal.md → ...n-0.9/api/json-rpc/portals/ERC20Portal.md b/...n-0.9/api/json-rpc/portals/ERC20Portal.md → ...n-0.9/api/json-rpc/portals/ERC20Portal.md
diff --git a/...-0.9/api/json-rpc/portals/ERC721Portal.md → ...-0.9/api/json-rpc/portals/ERC721Portal.md b/...-0.9/api/json-rpc/portals/ERC721Portal.md → ...-0.9/api/json-rpc/portals/ERC721Portal.md
diff --git a/...n-0.9/api/json-rpc/portals/EtherPortal.md → ...n-0.9/api/json-rpc/portals/EtherPortal.md b/...n-0.9/api/json-rpc/portals/EtherPortal.md → ...n-0.9/api/json-rpc/portals/EtherPortal.md
diff --git a/...9/api/json-rpc/relays/DAppAddressRelay.md → ...9/api/json-rpc/relays/DAppAddressRelay.md b/...9/api/json-rpc/relays/DAppAddressRelay.md → ...9/api/json-rpc/relays/DAppAddressRelay.md
diff --git a/...ocs/version-0.9/api/json-rpc/sol-input.md → ...ved_version-0.9/api/json-rpc/sol-input.md b/...ocs/version-0.9/api/json-rpc/sol-input.md → ...ved_version-0.9/api/json-rpc/sol-input.md
diff --git a/...cs/version-0.9/api/json-rpc/sol-output.md → ...ed_version-0.9/api/json-rpc/sol-output.md b/...cs/version-0.9/api/json-rpc/sol-output.md → ...ed_version-0.9/api/json-rpc/sol-output.md
diff --git a/...ersioned_docs/version-0.9/api/rollup.yaml → ...ocs/_archived_version-0.9/api/rollup.yaml b/...ersioned_docs/version-0.9/api/rollup.yaml → ...ocs/_archived_version-0.9/api/rollup.yaml
diff --git a/...version-0.9/api/rollup/add-notice.api.mdx → ...version-0.9/api/rollup/add-notice.api.mdx b/...version-0.9/api/rollup/add-notice.api.mdx → ...version-0.9/api/rollup/add-notice.api.mdx
diff --git a/...version-0.9/api/rollup/add-report.api.mdx → ...version-0.9/api/rollup/add-report.api.mdx b/...version-0.9/api/rollup/add-report.api.mdx → ...version-0.9/api/rollup/add-report.api.mdx
diff --git a/...ersion-0.9/api/rollup/add-voucher.api.mdx → ...ersion-0.9/api/rollup/add-voucher.api.mdx b/...ersion-0.9/api/rollup/add-voucher.api.mdx → ...ersion-0.9/api/rollup/add-voucher.api.mdx
diff --git a/...i/rollup/cartesi-rollup-http-api.info.mdx → ...i/rollup/cartesi-rollup-http-api.info.mdx b/...i/rollup/cartesi-rollup-http-api.info.mdx → ...i/rollup/cartesi-rollup-http-api.info.mdx
diff --git a/...ocs/version-0.9/api/rollup/finish.api.mdx → ...ved_version-0.9/api/rollup/finish.api.mdx b/...ocs/version-0.9/api/rollup/finish.api.mdx → ...ved_version-0.9/api/rollup/finish.api.mdx
diff --git a/...0.9/api/rollup/register-exception.api.mdx → ...0.9/api/rollup/register-exception.api.mdx b/...0.9/api/rollup/register-exception.api.mdx → ...0.9/api/rollup/register-exception.api.mdx
diff --git a/...ed_docs/version-0.9/api/rollup/sidebar.ts → ...rchived_version-0.9/api/rollup/sidebar.ts b/...ed_docs/version-0.9/api/rollup/sidebar.ts → ...rchived_version-0.9/api/rollup/sidebar.ts
diff --git a/...ned_docs/version-0.9/api/typeDefs.graphql → ...archived_version-0.9/api/typeDefs.graphql b/...ned_docs/version-0.9/api/typeDefs.graphql → ...archived_version-0.9/api/typeDefs.graphql
diff --git a/...ioned_docs/version-0.9/assets-handling.md → .../_archived_version-0.9/assets-handling.md b/...ioned_docs/version-0.9/assets-handling.md → .../_archived_version-0.9/assets-handling.md
diff --git a/...rsioned_docs/version-0.9/back-end-api.png → ...cs/_archived_version-0.9/back-end-api.png b/...rsioned_docs/version-0.9/back-end-api.png → ...cs/_archived_version-0.9/back-end-api.png
diff --git a/...cs/version-0.9/build-dapps/create-dapp.md → ...ed_version-0.9/build-dapps/create-dapp.md b/...cs/version-0.9/build-dapps/create-dapp.md → ...ed_version-0.9/build-dapps/create-dapp.md
diff --git a/...version-0.9/build-dapps/dapp-host-mode.md → ...version-0.9/build-dapps/dapp-host-mode.md b/...version-0.9/build-dapps/dapp-host-mode.md → ...version-0.9/build-dapps/dapp-host-mode.md
diff --git a/...ersion-0.9/build-dapps/deploying-dapps.md → ...ersion-0.9/build-dapps/deploying-dapps.md b/...ersion-0.9/build-dapps/deploying-dapps.md → ...ersion-0.9/build-dapps/deploying-dapps.md
diff --git a/...ocs/version-0.9/build-dapps/guidelines.md → ...ved_version-0.9/build-dapps/guidelines.md b/...ocs/version-0.9/build-dapps/guidelines.md → ...ved_version-0.9/build-dapps/guidelines.md
diff --git a/..._docs/version-0.9/build-dapps/overview.md → ...hived_version-0.9/build-dapps/overview.md b/..._docs/version-0.9/build-dapps/overview.md → ...hived_version-0.9/build-dapps/overview.md
diff --git a/...s/version-0.9/build-dapps/requirements.md → ...d_version-0.9/build-dapps/requirements.md b/...s/version-0.9/build-dapps/requirements.md → ...d_version-0.9/build-dapps/requirements.md
diff --git a/..._docs/version-0.9/build-dapps/run-dapp.md → ...hived_version-0.9/build-dapps/run-dapp.md b/..._docs/version-0.9/build-dapps/run-dapp.md → ...hived_version-0.9/build-dapps/run-dapp.md
diff --git a/..._versioned_docs/version-0.9/components.md → ..._docs/_archived_version-0.9/components.md b/..._versioned_docs/version-0.9/components.md → ..._docs/_archived_version-0.9/components.md
diff --git a/...oned_docs/version-0.9/core-components.png → ..._archived_version-0.9/core-components.png b/...oned_docs/version-0.9/core-components.png → ..._archived_version-0.9/core-components.png
diff --git a/..._versioned_docs/version-0.9/dapp-arch.png → ..._docs/_archived_version-0.9/dapp-arch.png b/..._versioned_docs/version-0.9/dapp-arch.png → ..._docs/_archived_version-0.9/dapp-arch.png
diff --git a/...ned_docs/version-0.9/dapp-architecture.md → ...archived_version-0.9/dapp-architecture.md b/...ned_docs/version-0.9/dapp-architecture.md → ...archived_version-0.9/dapp-architecture.md
diff --git a/...ioned_docs/version-0.9/dapp-life-cycle.md → .../_archived_version-0.9/dapp-life-cycle.md b/...ioned_docs/version-0.9/dapp-life-cycle.md → .../_archived_version-0.9/dapp-life-cycle.md
diff --git a/...sioned_docs/version-0.9/front-end-api.png → ...s/_archived_version-0.9/front-end-api.png b/...sioned_docs/version-0.9/front-end-api.png → ...s/_archived_version-0.9/front-end-api.png
diff --git a/...ps_versioned_docs/version-0.9/http-api.md → ...ed_docs/_archived_version-0.9/http-api.md b/...ps_versioned_docs/version-0.9/http-api.md → ...ed_docs/_archived_version-0.9/http-api.md
diff --git a/...lups_versioned_docs/version-0.9/input.png → ...oned_docs/_archived_version-0.9/input.png b/...lups_versioned_docs/version-0.9/input.png → ...oned_docs/_archived_version-0.9/input.png
diff --git a/...ps_versioned_docs/version-0.9/inspect.png → ...ed_docs/_archived_version-0.9/inspect.png b/...ps_versioned_docs/version-0.9/inspect.png → ...ed_docs/_archived_version-0.9/inspect.png
diff --git a/...rsioned_docs/version-0.9/main-concepts.md → ...cs/_archived_version-0.9/main-concepts.md b/...rsioned_docs/version-0.9/main-concepts.md → ...cs/_archived_version-0.9/main-concepts.md
diff --git a/...ion-0.9/migration-guides/from-08-to-09.md → ...ion-0.9/migration-guides/from-08-to-09.md b/...ion-0.9/migration-guides/from-08-to-09.md → ...ion-0.9/migration-guides/from-08-to-09.md
diff --git a/..._docs/version-0.9/offchain-components.png → ...hived_version-0.9/offchain-components.png b/..._docs/version-0.9/offchain-components.png → ...hived_version-0.9/offchain-components.png
diff --git a/...d_docs/version-0.9/onchain-components.png → ...chived_version-0.9/onchain-components.png b/...d_docs/version-0.9/onchain-components.png → ...chived_version-0.9/onchain-components.png
diff --git a/...ioned_docs/version-0.9/onchain-phases.png → .../_archived_version-0.9/onchain-phases.png b/...ioned_docs/version-0.9/onchain-phases.png → .../_archived_version-0.9/onchain-phases.png
diff --git a/...ned_docs/version-0.9/onchain-timeline.png → ...archived_version-0.9/onchain-timeline.png b/...ned_docs/version-0.9/onchain-timeline.png → ...archived_version-0.9/onchain-timeline.png
diff --git a/...ps_versioned_docs/version-0.9/outputs.png → ...ed_docs/_archived_version-0.9/outputs.png b/...ps_versioned_docs/version-0.9/outputs.png → ...ed_docs/_archived_version-0.9/outputs.png
diff --git a/...ps_versioned_docs/version-0.9/overview.md → ...ed_docs/_archived_version-0.9/overview.md b/...ps_versioned_docs/version-0.9/overview.md → ...ed_docs/_archived_version-0.9/overview.md
diff --git a/...ioned_docs/version-0.9/reading-outputs.md → .../_archived_version-0.9/reading-outputs.md b/...ioned_docs/version-0.9/reading-outputs.md → .../_archived_version-0.9/reading-outputs.md
diff --git a/...oned_docs/version-0.9/sending-requests.md → ..._archived_version-0.9/sending-requests.md b/...oned_docs/version-0.9/sending-requests.md → ..._archived_version-0.9/sending-requests.md
diff --git a/...ned_docs/version-0.9/sequence-diagram.png → ...archived_version-0.9/sequence-diagram.png b/...ned_docs/version-0.9/sequence-diagram.png → ...archived_version-0.9/sequence-diagram.png
diff --git a/...ned_docs/version-0.9/sequence-diagram.txt → ...archived_version-0.9/sequence-diagram.txt b/...ned_docs/version-0.9/sequence-diagram.txt → ...archived_version-0.9/sequence-diagram.txt
diff --git a/...ups_versioned_docs/version-0.9/stages.png → ...ned_docs/_archived_version-0.9/stages.png b/...ups_versioned_docs/version-0.9/stages.png → ...ned_docs/_archived_version-0.9/stages.png
diff --git a/cartesi-rollups_versioned_docs/version-1.0/api/graphql/basics.md b/cartesi-rollups_versioned_docs/version-1.0/api/graphql/basics.md
@@ -1,6 +1,6 @@
 # Overview
 
-In order to query the state of a Cartesi Rollups instance, front-end clients can make use of a [GraphQL API](https://graphql.org/learn/) that is exposed by the [Cartesi Nodes](../../components.md#cartesi-nodes).
+In order to query the state of a Cartesi Rollups instance, front-end clients can make use of a [GraphQL API](https://graphql.org/learn/) that is exposed by the [Cartesi Nodes](/cartesi-rollups/1.0/main-concepts/#cartesi-nodes).
 
 Essentially, this API allows any client to retrieve outputs produced by a dApp's back-end, and to link those outputs to the corresponding inputs that triggered them. Outputs can generally come in the form of [vouchers](./objects/voucher.mdx), [notices](./objects/notice.mdx) and [reports](./objects/report.mdx), and allow clients to both receive dApp updates and enforce consequences on the base layer, such as asset transfers.
 

diff --git a/cartesi-rollups_versioned_docs/version-1.0/api/json-rpc/basics.md b/cartesi-rollups_versioned_docs/version-1.0/api/json-rpc/basics.md
@@ -97,7 +97,7 @@ In this example, the command will fetch and display the balance as shown below:
 
 ##### getNumberOfInputs
 
-The following example is a cast command that shows how to get the number of inputs using the function [getNumberOfInputs](./sol-input.md#addInput):
+The following example is a cast command that shows how to get the number of inputs using the function [getNumberOfInputs](/cartesi-rollups/1.0/api/json-rpc/sol-input/#getnumberofinputs):
 
 ```shell
 cast call <INPUTBOX_ADDRESS> getNumberOfInputs(address) <DAPP_ADDRESS>
@@ -111,7 +111,7 @@ The result of this JSON-RPC call is the number of inputs for the dApp, returned
 
 ##### addInput
 
-The following example is a cast command that shows how to send an input using the function [addInput](./sol-input.md#addInput) of the [`InputBox`](./sol-input.md) smart contract:
+The following example is a cast command that shows how to send an input using the function [addInput](/cartesi-rollups/1.0/api/json-rpc/sol-input/#addinput) of the [`InputBox`](/cartesi-rollups/1.0/api/json-rpc/sol-input) smart contract:
 
 ```shell
 cast send <INPUTBOX_ADDRESS> addInput(_dapp,_input) <DAPP_ADDRESS> <INPUT>

diff --git a/cartesi-rollups_versioned_docs/version-1.0/api/json-rpc/sol-output.md b/cartesi-rollups_versioned_docs/version-1.0/api/json-rpc/sol-output.md
@@ -3,8 +3,8 @@ id: sol-output
 title: CartesiDApp
 ---
 
-The **CartesiDApp** contract acts as the base layer incarnation of a dApp running on the execution layer. The dApp is hereby able to interact with other smart contracts through the execution of [vouchers](../../components.md#vouchers)
-and the validation of [notices](../../components.md#notices). These outputs are generated by the [dApp back-end](../../dapp-architecture.md#back-end) on the execution layer and can be proven in the base layer thanks to claims submitted by a consensus contract.
+The **CartesiDApp** contract acts as the base layer incarnation of a dApp running on the execution layer. The dApp is hereby able to interact with other smart contracts through the execution of [vouchers](/cartesi-rollups/1.0/main-concepts/#vouchers)
+and the validation of [notices](/cartesi-rollups/1.0/main-concepts/#notices). These outputs are generated by the [dApp back-end](/cartesi-rollups/1.0/dapp-architecture/#back-end) on the execution layer and can be proven in the base layer thanks to claims submitted by a consensus contract.
 
 A **voucher** is a one-time message call to another contract. It can encode asset transfers, approvals,
 or any other message call that doesn't require Ether to be sent along. A voucher will only be consumed

diff --git a/...-rollups_versioned_docs/version-1.0/api/rollup/cartesi-rollup-http-api.info.mdx b/...-rollups_versioned_docs/version-1.0/api/rollup/cartesi-rollup-http-api.info.mdx
@@ -85,7 +85,7 @@ while True:
 ```
 
 In production mode, if the dApp exits the Rollups initialization script will register a Rollup Exception.
-See [/exception](#api-Default-registerException).
+See [/exception](/cartesi-rollups/1.0/api/rollup/register-exception/).
 
 In host mode, the Cartesi Rollups infrastructure is not able to detect that the dApp exited.
 It is up to the dApp developer to re-launch the dApp.

diff --git a/cartesi-rollups_versioned_docs/version-1.0/assets-handling.md b/cartesi-rollups_versioned_docs/version-1.0/assets-handling.md
@@ -8,10 +8,10 @@ Assets exist on the base layer, which is where they have actual meaning and valu
 
 Asset handling in Cartesi dApps involves the following procedures:
 
-1. Locking assets on the base layer by calling deposit methods on special contracts called [Portals](./components.md#portals), which will effectively transfer asset ownership to the target dApp contract. There are specific portals for each kind of asset (Ether, ERC-20, ERC-721, ERC-1155).
+1. Locking assets on the base layer by calling deposit methods on special contracts called [Portals](/cartesi-rollups/1.0/api/json-rpc/portals/), which will effectively transfer asset ownership to the target dApp contract. There are specific portals for each kind of asset (Ether, ERC-20, ERC-721, ERC-1155).
 2. The Cartesi Rollups framework notifies the dApp back-end of the deposit by sending it a special input.
 3. The dApp's back-end code needs to recognize and handle the special input, in order to process the deposit according to its own logic (e.g., by storing each user's balance in a hash table or database).
-4. When appropriate (e.g., when a game ends and the winner wishes to withdraw their funds), the back-end generates a [voucher](./components.md#vouchers) that encodes a transfer of assets on the base layer, from the dApp to the target user. The actual withdrawal will take effect on the base layer when the voucher is executed. This is a secure process because it can only be done when the voucher has an associated validity proof ensuring that the validator nodes have reached consensus about its contents.
+4. When appropriate (e.g., when a game ends and the winner wishes to withdraw their funds), the back-end generates a [voucher](/cartesi-rollups/1.0/main-concepts/#vouchers) that encodes a transfer of assets on the base layer, from the dApp to the target user. The actual withdrawal will take effect on the base layer when the voucher is executed. This is a secure process because it can only be done when the voucher has an associated validity proof ensuring that the validator nodes have reached consensus about its contents.
 
 ## Ethereum ABI encoding for asset operations
 
@@ -94,7 +94,7 @@ For the above example, we would have the following decoded values:
 
 #### Encoding withdrawals
 
-In the case of a withdrawal, the back-end code needs to create a [voucher](./components.md#vouchers) that encodes a transfer of assets from the dApp to the target recipient address. For ERC-20, this transfer can be performed by encoding a call to the [transfer(address,uint256)](https://eips.ethereum.org/EIPS/eip-20#transfer) method of the appropriate ERC-20 contract on the base layer.
+In the case of a withdrawal, the back-end code needs to create a [voucher](/cartesi-rollups/1.0/main-concepts/#vouchers) that encodes a transfer of assets from the dApp to the target recipient address. For ERC-20, this transfer can be performed by encoding a call to the [transfer(address,uint256)](https://eips.ethereum.org/EIPS/eip-20#transfer) method of the appropriate ERC-20 contract on the base layer.
 
 ```python
 TRANSFER_FUNCTION_SELECTOR = b'\xa9\x05\x9c\xbb'
@@ -170,7 +170,7 @@ For the above example, we would have the following decoded values:
 
 #### Encoding withdrawals
 
-Withdrawals for ERC-721 are again very similar to what is done for ERC-20. Once more, a [voucher](./components.md#vouchers) must be emitted that encodes a transfer of the intended asset from the dApp to a target recipient address.
+Withdrawals for ERC-721 are again very similar to what is done for ERC-20. Once more, a [voucher](/cartesi-rollups/1.0/main-concepts/#vouchers) must be emitted that encodes a transfer of the intended asset from the dApp to a target recipient address.
 In the case of ERC-721 tokens, the voucher should encode a call to the [safeTransferFrom(address,address,uint256)](https://eips.ethereum.org/EIPS/eip-721#specification) method on the base layer token contract.
 
 ```python

diff --git a/cartesi-rollups_versioned_docs/version-1.0/build-dapps/deploying-dapps.md b/cartesi-rollups_versioned_docs/version-1.0/build-dapps/deploying-dapps.md
@@ -6,7 +6,7 @@ tags: [deploy, quickstart, dapps, developer]
 
 Cartesi Rollups dApps are intended to be deployed to public blockchains, so that they can be accessed by users. This can be done by taking advantage of a cloud-based infrastructure provided by Cartesi.
 
-As happens with any blockchain application, the act of "deploying a dApp" involves publishing its smart contract so that it is publicly available and usable by clients or [front-end applications](../dapp-architecture.md#front-end). In the context of a Cartesi dApp, the smart contract is represented by an arbitrary [back-end program](../dapp-architecture.md#back-end) that runs on Linux inside a [Cartesi Node](../components.md#cartesi-nodes). This means that deploying Cartesi dApps basically corresponds to first deploying a smart contract that represents your dApp on-chain and then instantiating Cartesi Nodes that run the intended back-end logic of the application.
+As happens with any blockchain application, the act of "deploying a dApp" involves publishing its smart contract so that it is publicly available and usable by clients or [front-end applications](/cartesi-rollups/1.0/dapp-architecture/#front-end). In the context of a Cartesi dApp, the smart contract is represented by an arbitrary [back-end program](/cartesi-rollups/1.0/dapp-architecture/#back-end) that runs on Linux inside a [Cartesi Node](/cartesi-rollups/1.0/main-concepts/#cartesi-nodes). This means that deploying Cartesi dApps basically corresponds to first deploying a smart contract that represents your dApp on-chain and then instantiating Cartesi Nodes that run the intended back-end logic of the application.
 
 In order to facilitate the instantiation of such nodes, Cartesi provides an infrastructure for easily getting them running in the cloud. Developers are thus invited to take advantage of this convenience service in order to jump-start bringing their applications to public blockchains.
 

diff --git a/cartesi-rollups_versioned_docs/version-1.0/build-dapps/guidelines.md b/cartesi-rollups_versioned_docs/version-1.0/build-dapps/guidelines.md
@@ -14,14 +14,14 @@ This article explains common practices for developing dApps using the Cartesi Ro
 Please, check the [dApp architecture](../dapp-architecture.md) article to explore more essential topics such as the [back-end](../dapp-architecture.md#back-end) and [front-end](../dapp-architecture.md#front-end) components, and the [communication](../dapp-architecture.md#communication) between them.
 :::
 
-Cartesi dApps communicate between the front-end and back-end using the Rollups framework via a [set of HTTP APIs](..//http-api.md). The Cartesi dApp back-end contains the application's business logic and executes within the Cartesi Rollups framework. The back-end produces outputs in the form of [vouchers](../main-concepts.md#vouchers), [notices](../main-concepts.md#notices), or [reports](../main-concepts.md#reports), which provide vital information about the application's status. The Cartesi dApp front-end is responsible for presenting information and collecting user inputs. The front-end communicates with the back-end via APIs, and Cartesi provides a range of APIs that you can use to interact with the Rollups framework.
+Cartesi dApps communicate between the front-end and back-end using the Rollups framework via a [set of HTTP APIs](/cartesi-rollups/1.0/http-api/). The Cartesi dApp back-end contains the application's business logic and executes within the Cartesi Rollups framework. The back-end produces outputs in the form of [vouchers](/cartesi-rollups/1.0/main-concepts/#vouchers), [notices](/cartesi-rollups/1.0/main-concepts/#notices), or [reports](/cartesi-rollups/1.0/main-concepts/#reports), which provide vital information about the application's status. The Cartesi dApp front-end is responsible for presenting information and collecting user inputs. The front-end communicates with the back-end via APIs, and Cartesi provides a range of APIs that you can use to interact with the Rollups framework.
 
 When it comes to dApp architecture and APIs, several points are important to highlight:
 
-- The [Cartesi Machine](/machine/intro) serves as the back-end for the dApp, and it is managed by a [Cartesi Node](../components.md#cartesi-nodes), providing a secure and efficient environment for running the dApp
+- The [Cartesi Machine](/get-started/cartesi-machine/) serves as the back-end for the dApp, and it is managed by a [Cartesi Node](/cartesi-rollups/1.0/main-concepts#cartesi-nodes), providing a secure and efficient environment for running the dApp
 - All inputs are sent to the L1 smart contracts
-- You can query the Rollups state using a [GraphQL API](../api/graphql/basics.md). This state includes the received inputs and the associated outputs produced in the form of notices, vouchers and reports
-- You can retrieve arbitrary application state via the [Inspect HTTP API](../api/inspect/inspect.api.mdx). It allows you to implement a REST-like API on the back-end of your dApp to return arbitrary information about it, much like what web2 applications are used to
+- You can query the Rollups state using a [GraphQL API](/cartesi-rollups/1.0/api/graphql/basics/). This state includes the received inputs and the associated outputs produced in the form of notices, vouchers and reports
+- You can retrieve arbitrary application state via the [Inspect HTTP API](/cartesi-rollups/1.0/api/inspect/inspect/). It allows you to implement a REST-like API on the back-end of your dApp to return arbitrary information about it, much like what web2 applications are used to
 
 ## General recommendations
 
@@ -43,8 +43,8 @@ The Cartesi Machine is a deterministic RISC-V emulator that runs software in an
 
 The dApp front-end clients have two ways of retrieving information:
 
-- [Inspect HTTP API](../api/inspect/inspect.api.mdx)
-- [GraphQL API](../api/graphql/basics.md)
+- [Inspect HTTP API](/cartesi-rollups/1.0/api/inspect/inspect/)
+- [GraphQL API](/cartesi-rollups/1.0/api/graphql/basics/)
 
 The **Inspect API** provides enhanced flexibility and aligns better with the conventions of modern web2 applications. Enabling the implementation of a REST-like API on the back-end allows for the retrieval of a variety of information about the dApp.
 

diff --git a/cartesi-rollups_versioned_docs/version-1.0/build-dapps/run-dapp.md b/cartesi-rollups_versioned_docs/version-1.0/build-dapps/run-dapp.md
@@ -102,7 +102,7 @@ You can inspect the [full code of the Echo Python dApp](https://github.com/carte
 
 ## Overview
 
-The Echo-Python dApp simply copies (or "echoes") each input received as a corresponding output [notice](../components.md#notices). The dApp's back-end is written in _Python_, and its front-end is a [simple console application](https://github.com/cartesi/rollups-examples/tree/main/frontend-console) written in _Typescript_ that can be executed from a terminal.
+The Echo-Python dApp simply copies (or "echoes") each input received as a corresponding output [notice](/cartesi-rollups/1.0/main-concepts/#notices). The dApp's back-end is written in _Python_, and its front-end is a [simple console application](https://github.com/cartesi/rollups-examples/tree/main/frontend-console) written in _Typescript_ that can be executed from a terminal.
 
 The **Quick Start** guide consists of 5 main steps:
 

diff --git a/cartesi-rollups_versioned_docs/version-1.0/challenges/overview.md b/cartesi-rollups_versioned_docs/version-1.0/challenges/overview.md
@@ -10,7 +10,7 @@ Cartesi Rollups are shaped by the contributions and collaborative efforts of its
 - [Disputes](#disputes)
 - [Large data as input](#large-data-as-input)
 - [Composability](#composability)
-- [Convenience layer: Front-end](#convenience-layer-front-end)
+- [Convenience layer: Front-end](#convenience-layers)
 - [Design for upgradability](#design-for-upgradability)
 
 ## Transaction scalability

diff --git a/cartesi-rollups_versioned_docs/version-1.0/dapp-architecture.md b/cartesi-rollups_versioned_docs/version-1.0/dapp-architecture.md
@@ -19,7 +19,7 @@ Here, the black boxes represent the parts that the developer needs to implement
 
 The back-end of a Cartesi dApp contains the business logic of the application, similar to what traditional systems would run inside a server. The difference here — and the reason for using blockchain technology in general — is that decentralized applications need this back-end logic to be verifiable and hence trustless. As such, it is executed inside the Cartesi Rollups framework.
 
-The back-end stores and updates the application state as user input is received and produces corresponding outputs. These outputs can come in the form of [vouchers](./components.md#vouchers) (transactions that can be carried out on L1, such as a transfer of assets), [notices](./components.md#notices) (informational statements, such as the resulting score of a game), or [reports](./components.md#reports) (application logs and diagnostic information, such as error or warning messages).
+The back-end stores and updates the application state as user input is received and produces corresponding outputs. These outputs can come in the form of [vouchers](/cartesi-rollups/1.0/main-concepts/#vouchers) (transactions that can be carried out on L1, such as a transfer of assets), [notices](/cartesi-rollups/1.0/main-concepts/#notices) (informational statements, such as the resulting score of a game), or [reports](/cartesi-rollups/1.0/main-concepts/#reports) (application logs and diagnostic information, such as error or warning messages).
 
 In practical terms, a Cartesi dApp back-end can be seen as an advanced smart contract.
 
@@ -38,7 +38,7 @@ The sequence diagram below illustrates how all of this works:
 ![img](./sequence-diagram.png)
 
 :::note
-The Cartesi Rollups framework provides a set of APIs to specify how the dApp's front-end and back-end should communicate with it. These APIs are explained in detail in the [next section](./http-api.md).
+The Cartesi Rollups framework provides a set of APIs to specify how the dApp's front-end and back-end should communicate with it. These APIs are explained in detail in the [next section](/cartesi-rollups/1.0/http-api/).
 :::
 
 ## Other components