updated links, added Tutorials folder (#1759)

eric-stacks · web-flow · commit f5a41af521f2 · 2026-01-05T15:16:13.000-05:00
diff --git a/docs/build/get-started/build-a-frontend/authentication.md b/docs/build/get-started/build-a-frontend/authentication.md
@@ -66,4 +66,4 @@ function App() {
 
 The `connect()` method comes with the ability to configure how you want the wallet selector modal to appear for your app. You can decide which wallets to have only appear as an option or allow any wallet that follows the SIP-030 standard to appear as an available Stacks wallet.
 
-For the complete guides check out the [Stacks Connect](/broken/pages/JLRpUuDHPMxXaInZ9Vll) section.
+For the complete guides check out the [Stacks Connect](../../stacks-connect/connect-wallet.md) section.
diff --git a/docs/build/get-started/build-a-frontend/post-conditions.md b/docs/build/get-started/build-a-frontend/post-conditions.md
@@ -15,7 +15,7 @@ Put simply, post conditions are a set of conditions that must be met before a us
 They are sent as part of the transaction when the user initiates it, meaning we need to implement post-conditions on the frontend. Whenever you are transferring an asset (fungible or non-fungible) from one address to another, you should take advantage of post conditions.
 
 {% hint style="info" %}
-Head to the dedicated section on [post-conditions](/broken/pages/0KPrPPKItMGZZL2u4tiF) for more in-depth information.
+Head to the dedicated section on [post-conditions](../../post-conditions/overview.md) for more in-depth information.
 {% endhint %}
 
 We're going to use [stacks.js](https://github.com/stx-labs/stacks.js/tree/master/packages/transactions#post-conditions) to familiarize ourselves with constructing post-conditions on the frontend. And there are several different ways to construct post-conditions based on asset type.
@@ -103,5 +103,5 @@ After transaction confirmation and broadcasting, users are also able to see what
 
 ### Additional Resources
 
-* \[[Post-Conditions](/broken/pages/0KPrPPKItMGZZL2u4tiF)] Dedicated section on post-conditions in these docs
+* \[[Post-Conditions](../../post-conditions/overview.md)] Dedicated section on post-conditions in these docs
 * \[[Hiro YT](https://youtu.be/xXgQB8NfdEY?si=eSZp4tlLOCkkqGRS)] ELI5: Post-Conditions on Stacks
diff --git a/docs/build/get-started/build-a-frontend/sending-transactions.md b/docs/build/get-started/build-a-frontend/sending-transactions.md
@@ -85,4 +85,4 @@ let response = await request('stx_transferSip10Ft', {
 
 ### Additional Resources
 
-* \[[Learn Stacks.js](/broken/pages/dH5waQhE6Vb7rhcrUG7z)] Head to the Learn Stacks.js section to see more examples&#x20;
+* \[[Learn Stacks.js](../../stacks.js/overview.md)] Head to the Learn Stacks.js section to see more examples&#x20;
diff --git a/docs/build/get-started/clarity-crash-course.md b/docs/build/get-started/clarity-crash-course.md
@@ -290,7 +290,7 @@ Smart contracts are immutable once deployed. Bugs are permanent. Test them thoro
 {% endhint %}
 
 * [Rendezvous Fuzz Testing](../rendezvous/overview.md): Use Rendezvous to hammer your contract with random inputs. It helps expose edge cases and vulnerabilities.
-* [Unit Testing in Clarinet](/broken/pages/xKpkZWiNCO3dwHoA9AeB): Unit testing verifies that individual contract functions behave as expected.&#x20;
+* [Unit Testing in Clarinet](../clarinet/testing-with-clarinet-sdk.md): Unit testing verifies that individual contract functions behave as expected.&#x20;
 
 ***
 
diff --git a/docs/build/more-guides/verify-bitcoin-transactions-clarity/creating-btc-tx.md b/docs/build/more-guides/verify-bitcoin-transactions-clarity/creating-btc-tx.md
@@ -5,7 +5,7 @@ For usage with the `clarity-bitcoin-lib` contract or if you just want to learn h
 Using Stacks Connect and with a Stacks-supported wallet, you can initiate a simple Bitcoin transaction from a frontend app in a few lines of code. With this Bitcoin transaction, you can then use to verify it's inclusion in a Bitcoin block through Clarity.
 
 {% hint style="info" %}
-Check out the [Stacks Connect](/broken/pages/JLRpUuDHPMxXaInZ9Vll) guides for more info on setup and wallet connection.
+Check out the [Stacks Connect](../../stacks-connect/connect-wallet.md) guides for more info on setup and wallet connection.
 {% endhint %}
 
 {% stepper %}
diff --git a/docs/learn/block-production/mining.md b/docs/learn/block-production/mining.md
@@ -87,7 +87,7 @@ Stacks miners function similarly to sequencers in L2 systems in that they are on
 
 It's important to note that there are two primary parties involved in the block production process on Stacks: miners and stackers.
 
-These two roles serve complementary relationships in the [block production process](file:///), and stackers drastically reduce any potential destructive power miners have over the chain.
+These two roles serve complementary relationships in the block production process, and stackers drastically reduce any potential destructive power miners have over the chain.
 
 Miners cannot reorganize the chain. In the worst case, all miners can do is omit (some kinds of) transactions, and all that is required to address this is to run your own miner.
 
diff --git a/docs/learn/stacks-101/proof-of-transfer.md b/docs/learn/stacks-101/proof-of-transfer.md
@@ -2,7 +2,7 @@
 
 <figure><picture><source srcset="../.gitbook/assets/pox-light.png" media="(prefers-color-scheme: dark)"><img src="../.gitbook/assets/pox.png" alt=""></picture><figcaption></figcaption></figure>
 
-In the previous sections, we took a look at the vision and ethos of Stacks and talked a lot about it being connected to Bitcoin and how it enables expanding functio nality without modifying Bitcoin itself.
+In the previous sections, we took a look at the vision and ethos of Stacks and talked a lot about it being connected to Bitcoin and how it enables expanding functionality without modifying Bitcoin itself.
 
 In this section, we'll run through the block production mechanism that makes that happen, Proof of Transfer.
 
diff --git a/docs/operate/run-a-signer/signer-quickstart.md b/docs/operate/run-a-signer/signer-quickstart.md
@@ -18,8 +18,6 @@ If you want to get up and running as an active signer as quickly as possible, he
 
 If you are not familiar with how signing works yet, be sure to check out the [Signing concept guide](https://app.gitbook.com/s/H74xqoobupBWwBsVMJhK/block-production/signing).
 
-If you would like a more detailed walkthrough of all of these steps, take a look at the [Running a Signer](file:///) guide.
-
 {% hint style="danger" %}
 The CLI examples below may show outdated release versions. For the latest releases, always refer to the links above in the top info block.
 {% endhint %}
diff --git a/docs/operate/stacking-stx/operate-a-stacking-pool.md b/docs/operate/stacking-stx/operate-a-stacking-pool.md
@@ -585,5 +585,3 @@ Once a pool has enough delegated STX to become a signer, the pool admin needs to
   * Max amount
 
 Once this transaction has been confirmed, the pool operator is eligible to be a signer for an upcoming reward cycle.
-
-For more on the relationship between automated signing and manual stacking transactions, be sure to check out the main [Stack STX](file:///) doc.
diff --git a/docs/reference/README.md b/docs/reference/README.md
@@ -1,7 +1,7 @@
 # Stacks Node Configuration
 
 {% hint style="info" %}
-Note that these config fields are for a Stacks follower node. If you are running a signer alongside your Stacks node, you'll want to use the sample file found on the [Signer Configuration](/broken/pages/8ea1fa91cfa819c25f545b0aca9bfc16c8c3ad28) page as it contains additional parameters needed for your signer and Stacks node to function properly.
+Note that these config fields are for a Stacks follower node. If you are running a signer alongside your Stacks node, you'll want to use the sample file found in the [Signer Configuration](node-operations/signer-configuration.md) page as it contains additional parameters needed for your signer and Stacks node to function properly.
 {% endhint %}
 
 ### Usage
diff --git a/docs/reference/clarity/example-contracts/stacking.md b/docs/reference/clarity/example-contracts/stacking.md
@@ -14,10 +14,6 @@ There are a few utilities that make interacting with this contract easier includ
 
 Hiro has a [detailed guide](https://docs.hiro.so/stacks.js/guides/how-to-integrate-stacking) available for stacking using this library as well as a [Nakamoto guide](https://docs.hiro.so/nakamoto/stacks-js) specifically for the additions made to work with `pox-4`.
 
-### Prerequisites
-
-If you are not familiar with stacking as a concept, it will be useful to [familiarize yourself with that first](/broken/pages/3df1d5b76fd4f047544069a38895455776fc228f) before diving into the contract.
-
 ***
 
 ## Solo Stacking
@@ -92,8 +88,8 @@ First let's cover the needed parameters.
 * `pox-addr` is a tuple that encodes the Bitcoin address to be used for the PoX rewards, details below.
 * `start-burn-ht` is the Bitcoin block height you would like to begin stacking. You will receive rewards in the reward cycle following `start-burn-ht`. Importantly, `start-burn-ht` may not be further into the future than the current reward cycle, and in most cases should be set to the current burn block height.
 * `lock-period` sets the number of reward cycles you would like you lock your STX for, this can be between 1 and 12.
-* `signer-sig` is a unique generated signature that proves ownership of this signer. Further details for its role and how to generate it can be found in the [How to Stack](/broken/pages/930b16324611cdbf3451ca2b306ada93a1be367e) document.
-* `signer-key` is the public key of your signer, more details in the [How to Run a Signer](/broken/pages/5baf2f4c67696dbef7258f50d4cbf103b3e014d1) document.
+* `signer-sig` is a unique generated signature that proves ownership of this signer.
+* `signer-key` is the public key of your signer.
 * `max-amount` sets the maximum amount allowed to be stacked during the provided stacking period.
 * `auth-id` is a unique string to prevent re-use of this stacking transaction.
 
@@ -413,7 +409,7 @@ How to fix: verify that the signer signature was generated using the exact same
 
 This error means the contract lookup for a partially stacked entry failed. The stacking contract looks up partially stacked STX (after `delegate-stack-stx`) by the key `(pox-addr, stx-address, reward-cycle)`. If any of those parameters are wrong when generating the signature or calling `stack-aggregation-commit`, the lookup will fail.
 
-How to fix: check that the `pox-addr`, `stacker` principal (stx address), and `reward-cycle` values match exactly what was used in `delegate-stack-stx` / the signature generation. See the [stacking guide](/broken/pages/930b16324611cdbf3451ca2b306ada93a1be367e#delegator-initiates-delegation) for delegation flow details.
+How to fix: check that the `pox-addr`, `stacker` principal (stx address), and `reward-cycle` values match exactly what was used in `delegate-stack-stx` / the signature generation.
 
 </details>
 
diff --git a/docs/tutorials/.gitkeep b/docs/tutorials/.gitkeep

Original file line number	Diff line number	Diff line change
`@@ -66,4 +66,4 @@ function App() {`
`66`	`66`
`67`	`67`	The `connect()` method comes with the ability to configure how you want the wallet selector modal to appear for your app. You can decide which wallets to have only appear as an option or allow any wallet that follows the SIP-030 standard to appear as an available Stacks wallet.
`68`	`68`
`69`		`-For the complete guides check out the [Stacks Connect](/broken/pages/JLRpUuDHPMxXaInZ9Vll) section.`
	`69`	`+For the complete guides check out the [Stacks Connect](../../stacks-connect/connect-wallet.md) section.`
Original file line number	Diff line number	Diff line change
`@@ -85,4 +85,4 @@ let response = await request('stx_transferSip10Ft', {`
`85`	`85`
`86`	`86`	`### Additional Resources`
`87`	`87`
`88`		`-* \[[Learn Stacks.js](/broken/pages/dH5waQhE6Vb7rhcrUG7z)] Head to the Learn Stacks.js section to see more examples `
	`88`	`+* \[[Learn Stacks.js](../../stacks.js/overview.md)] Head to the Learn Stacks.js section to see more examples `