chore: add link check to GH action (#26)

# What 💻 
* Add a github action to check links for 404s
  * This *only* checks internal links

# Why ✋
* Ensure we don't provide links to broken pages

.github/workflows/deploy-preview.yml

@@ -19,9 +19,14 @@ jobs:
 
       - name: "Install dependencies"
         run: bun install
+
       - name: "Deploy target: staging"
         run: bun run generate
 
+      - uses: untitaker/[email protected]
+        with:
+          args: .output/public/ --sources content/
+
       - name: "Deploy preview"
         uses: matter-labs/action-hosting-deploy@main
         with:

content/00.build/40.tooling/10.zksync-cli/00.index.md

@@ -31,13 +31,13 @@ npm update -g zksync-cli
 
 ## Available Commands
 
-- [`dev`](./zksync-cli-dev.md): Start a local development environment with zkSync and Ethereum nodes.
-- [`create`](./zksync-cli-create.md): Scaffold new projects using templates for frontend, contracts, and scripting.
-- [`contract`](./zksync-cli-contract.md): Read and write data to zkSync contracts without building UI.
-- [`transaction`](./zksync-cli-transaction.md): Fetch and display detailed information about a specific transaction.
-- [`wallet`](./zksync-cli-wallet.md): Manage zkSync wallet assets, including transfers and balance checks.
-- [`bridge`](./zksync-cli-bridge.md): Perform deposits and withdrawals between Ethereum and zkSync.
-- [`config chains`](./zksync-cli-config-chains.md): Add or edit custom chains for flexible testing and development.
+- [`dev`](zksync-cli/zksync-cli-dev): Start a local development environment with zkSync and Ethereum nodes.
+- [`create`](zksync-cli/zksync-cli-create): Scaffold new projects using templates for frontend, contracts, and scripting.
+- [`contract`](zksync-cli/zksync-cli-contract): Read and write data to zkSync contracts without building UI.
+- [`transaction`](zksync-cli/zksync-cli-transaction): Fetch and display detailed information about a specific transaction.
+- [`wallet`](zksync-cli/zksync-cli-wallet): Manage zkSync wallet assets, including transfers and balance checks.
+- [`bridge`](zksync-cli/zksync-cli-bridge): Perform deposits and withdrawals between Ethereum and zkSync.
+- [`config chains`](zksync-cli/zksync-cli-config-chains): Add or edit custom chains for flexible testing and development.
 
 ## Further Assistance
 
@@ -46,6 +46,6 @@ to ask questions, share your experiences, and connect with the zkSync community.
 
 ## Source Code
 
-The [zkSync CLI project](%%zk_git_repo_zksync-cli)
+The [zkSync CLI project](%%zk_git_repo_zksync-cli%%)
 is open-source and available on GitHub under the MIT License.
 Feel free to contribute, report issues, or suggest new features to help us improve the tool for everyone.

content/00.build/40.tooling/10.zksync-cli/20.zksync-cli-create.md

@@ -22,7 +22,7 @@ Ensure you have the following installed before you start:
 Fast-track your UI development with our frontend templates, supporting popular frameworks like Vue, React, Next.js, Nuxt, and Vite.
 Options include viem, ethers, web3modal, rainbowkit, and more, equipping you with the necessary tools for dApp development.
 
-[zksync-frontend-templates repo](%%zk_git_repo_zksync-frontend-templates#readme)
+[zksync-frontend-templates repo](%%zk_git_repo_zksync-frontend-templates%%#readme)
 
 ### Contracts
 

content/10.zk-stack/10.components/30.shared-bridges.md

@@ -50,9 +50,9 @@ such as changes in consensus mechanisms, staking models, and data availability r
 
 The Shared Bridge and the associated smart contracts are foundational to the sustainable growth of the Hyperchain ecosystem.
 For further details on Hyperchains and their operational dynamics, refer to our [blog post on Hyperchains](https://blog.matter-labs.io/introduction-to-hyperchains-fdb33414ead7)
-or the section on [Hyperchains/Hyperscaling](/zk-stack/concepts/hyperchains-hyperscaling.md)
----
+or the section on [Hyperchains/Hyperscaling](/zk-stack/concepts/hyperchains-hyperscaling)
 
+---
 ## Architecture
 
 ![Contracts](/images/zk-stack/contracts-external.png)
@@ -203,15 +203,15 @@ Ether, the native gas token is part of the core system contracts, so deploying i
 smart contract, it needs to be deployed and initialised. This happens from the L1 WETH bridge. This deploys on L2 the
 corresponding bridge and ERC20 contract. This is deployed from L1, but the L2 address is known at deployment time.
 
-![deployWeth.png](../../assets/images/deploy-weth.png)
+![deployWeth.png](/images/zk-stack/deploy-weth.png)
 
 ## Components: Deposit WETH
 
 The user can deposit WETH into the ecosystem using the WETH bridge on L1. The destination chain ID has to be specified.
 The Bridgehub unwraps the WETH, and keeps the ETH, and send a message to the destination L2 to mint WETH to the
 specified address.
 
-![depositWeth.png](../../assets/images/deposit-weth.png)
+![depositWeth.png](/images/zk-stack/deposit-weth.png)
 
 ---