Fix links (#2407)

* fix: hardcode project name * fix: links * fix: links * fix: links * fix: links --------- Co-authored-by: Guillermo Alejandro Gallardo Diez <[email protected]>
near · Jan 4, 2025 · c2d4f99 · c2d4f99
1 parent 53a9299
commit c2d4f99
Show file tree

Hide file tree

Showing 16 changed files with 19 additions and 19 deletions.
diff --git a/docs/1.concepts/protocol/account-model.md b/docs/1.concepts/protocol/account-model.md
@@ -14,7 +14,7 @@ By signing [transactions](./transactions.md) with their account, users can:
 4. Help onboard new users by **covering the costs** of their transactions (gas fees)
 
 :::tip Want to create an account?
-You have multiple ways to create an account, you can [sign-up using your email](https://dev.near.org/signup), get a mobile wallet through [telegram](https://web.telegram.org/k/#@herewalletbot), or create a [web wallet](wallet.meteorwallet.app)
+You have multiple ways to create an account, you can [sign-up using your email](https://dev.near.org/signup), get a mobile wallet through [telegram](https://web.telegram.org/k/#@herewalletbot), or create a [web wallet](https://wallet.meteorwallet.app)
 :::
 
 ---

diff --git a/docs/1.concepts/web3/economics.md b/docs/1.concepts/web3/economics.md
@@ -47,6 +47,6 @@ Similarly to NFTs, fungible tokens are also just a piece of data stored in a sma
 Smart Contracts can define allowed operations - like transfer or payment using this token. [NEAR defines a standard](https://nomicon.io/Standards/FungibleToken/Core) for fungible tokens and provides a [default implementation](https://docs.rs/near-contract-standards/latest/near_contract_standards/fungible_token/index.html).
 
 Since an application is fully in control over emission and circulation of such tokens, a full fledged application economy can be created. For example, users can earn FTs for performing actions, and spend them to buy or mint new NFTs. 
-Another exciting option is creation of [Decentralized Autonomous Organizations](https://near.org/use-cases/dao/) (DAOs), in which FTs can be used as a membership (or governance) tool. In such scenarios, tokens are awarded to members and can be used to vote on decisions or participate in community events. 
+Another exciting option is creation of [Decentralized Autonomous Organizations](../../2.build/5.primitives/dao.md) (DAOs), in which FTs can be used as a membership (or governance) tool. In such scenarios, tokens are awarded to members and can be used to vote on decisions or participate in community events. 
 
 But we can push our tokens even further, by tying them to other cryptocurrencies and giving them a real-life monetary value. That’s where [Decentralized Finance](https://www.investopedia.com/decentralized-finance-defi-5113835) (DeFi), and especially [Decentralized Exchanges](https://en.wikipedia.org/wiki/Decentralized_exchange) (DEX) come into play. We won’t go into details here, but at the core a [liquidity pool](https://academy.binance.com/en/articles/what-are-liquidity-pools-in-defi) for a Fungible Token can be created on DEX, which allows trades of this token for other tokens or [stablecoins](https://en.wikipedia.org/wiki/Stablecoin). This opens the door for a new gaming model - [Play-to-Earn](https://en.wikipedia.org/wiki/Blockchain_game), where players can earn real-life money just by playing a game.
diff --git a/docs/1.concepts/web3/nfts.md b/docs/1.concepts/web3/nfts.md
@@ -478,7 +478,7 @@ If we need read-level access only, we can simply use the [REST API](https://docs
 * In case of a Functional Call key, it can be obtained from the wallet and used directly by the client.
 * In case of a Full Access key, the user should be redirected to the wallet to approve a transaction.
 
-A [JavaScript API](/tools/near-api-js/quick-reference) exists to cover all of these scenarios. It has all of the necessary functionality to integrate Web/Node.JS applications with blockchain. This SDK is a perfect choice for the Web-based clients, but it’s not suitable for desktop or mobile based clients. Other libraries can be used for them:
+A [JavaScript API](../../4.tools/near-api.md) exists to cover all of these scenarios. It has all of the necessary functionality to integrate Web/Node.JS applications with blockchain. This SDK is a perfect choice for the Web-based clients, but it’s not suitable for desktop or mobile based clients. Other libraries can be used for them:
 
 
 

diff --git a/docs/2.build/4.web3-apps/chain-ui-tutorial.md b/docs/2.build/4.web3-apps/chain-ui-tutorial.md
@@ -154,11 +154,10 @@ react-example deployment calculated to cost 4.08204 N {
 ? Estimated cost to deploy is 4.08204 N. Continue? (y/N)
 ```
 
-Once you've deployed your frontend, you can load the web application at `https://chain-hosted-ui.near.dev//<FILE_CONTRACT>/<DEPLOYER_ACCOUNT.near>/<APPLICATION-NAME>`
+Once you've deployed your frontend, you can load the web application at `gateway-url//<FILE_CONTRACT>/<DEPLOYER_ACCOUNT.near>/<APPLICATION-NAME>`
  - `<FILE_CONTRACT>`: `v1.chain-hosted-ui.testnet` or `v1.chainui.near`
  - `<DEPLOYER_ACCOUNT.near>`: the NEAR account used to deploy, e.g. `myaccount.testnet`
  - `<APPLICATION-NAME>`: the application name you defined, e.g. `react-example`
- - [Check this deployed example](https://chain-hosted-ui.near.dev/v1.chain-hosted-ui.testnet/solops2.testnet/react-example)
 
 ### Redeployment
 

diff --git a/docs/2.build/4.web3-apps/integrate-contracts.md b/docs/2.build/4.web3-apps/integrate-contracts.md
@@ -330,4 +330,4 @@ NEAR API JS does not limit itself to simply calling methods in a contract. In fa
 - **[Create batch transactions](https://github.com/near/near-api-js/tree/master/packages/cookbook/transactions/batch-transactions.ts)**: this enables to link multiple [actions](../../1.concepts/protocol/transaction-anatomy.md#actions) (e.g. multiple function calls). If one of the transactions fails, then they are all reverted.
 - **[Create accounts](https://github.com/near/near-api-js/tree/master/packages/cookbook/accounts/create-testnet-account.ts)**: deploy accounts for your users!
 
-Check the [cookbook](/tools/near-api-js/cookbook) to learn how to supercharge your web-app.
+Check the [NEAR API](../../4.tools/near-api.md) section to learn how to supercharge your web-app.
diff --git a/docs/2.build/6.data-infrastructure/lake-framework/near-lake.md b/docs/2.build/6.data-infrastructure/lake-framework/near-lake.md
@@ -16,7 +16,7 @@ You can find the Lake Indexer source code in [this GitHub repository](https://gi
 
 :::tip
 
-[Pagoda Inc.](https://pagoda.co) runs NEAR Lake nodes to store the data in JSON format on AWS S3.
+[Pagoda Inc.](https://www.pagoda.co) runs NEAR Lake nodes to store the data in JSON format on AWS S3.
 There is no need to run your own NEAR Lake unless you have specific reasons to do that.
 
 :::

diff --git a/docs/3.tutorials/crosswords/01-basics/04-simple-frontend.md b/docs/3.tutorials/crosswords/01-basics/04-simple-frontend.md
@@ -11,7 +11,7 @@ import nearReactFriends from '/docs/assets/crosswords/near-and-react--dakila.nea
 
 # Add a simple frontend
 
-This will be the final section in this chapter, where we'll add a simple frontend using React and [`near-api-js`](https://docs.near.org/tools/near-api-js/quick-reference) to communicate with the smart contract.
+This will be the final section in this chapter, where we'll add a simple frontend using React and [`near-api-js`](../../../4.tools/near-api.md) to communicate with the smart contract.
 
 <figure>
     <img src={nearReactFriends} alt="Two characters hanging out, NEAR and React. Art created by dakila.near" width="600"/>

diff --git a/docs/4.tools/explorer.md b/docs/4.tools/explorer.md
@@ -41,7 +41,6 @@ Created by the community, [NearBlocks](https://nearblocks.io/) enables to check
 ![DappLooker](/docs/assets/explorers/dapplooker.png)
 *Main page of [DappLooker](https://dapplooker.com/)*
 
-
 <hr className="subsection"/>
 
 ## Pikespeak

diff --git a/docs/4.tools/indexing-tools.md b/docs/4.tools/indexing-tools.md
@@ -14,7 +14,7 @@ Here's a quick overview of Indexer projects on the NEAR ecosystem:
 
 - [Indexer.xyz Multichain Indexer](https://indexer.xyz/): Indexer.xyz is an application layer that you can build your NFT or DeFi applications entirely on top of. In addition to raw transaction indexing, Indexer.xyz provides you with a standardized GraphQL API layer to easily tap into transactions across contracts and chains.
 
-- [Pagoda NEAR Lake](https://docs.pagoda.co/near-lake): with this fully managed solution by [Pagoda Inc.](https://pagoda.co), you don't need to run your own NEAR Lake Nodes and AWS S3 buckets.
+- [Pagoda NEAR Lake](https://docs.pagoda.co/near-lake): with this fully managed solution by [Pagoda Inc.](https://www.pagoda.co), you don't need to run your own NEAR Lake Nodes and AWS S3 buckets.
 
 - [The Graph](https://thegraph.com/docs/en/cookbook/near/): development tools to process blockchain events and make the resulting data easily available via a GraphQL API, known individually as a subgraph. [Graph Node](https://github.com/graphprotocol/graph-node) is able to process NEAR events, which means that NEAR developers can build subgraphs to index their smart contracts.
 

diff --git a/docs/4.tools/welcome.md b/docs/4.tools/welcome.md
@@ -10,4 +10,4 @@ In this page you will find:
 1. [Wallets](https://www.mynearwallet.com/) to handle your assets.
 2. [Explorers](explorer.md) to quickly obtain information from the blockchain.
 3. Websites to simplify creating and participating on governance projects.
-4. Developer tools to deploy and interact with contracts such as the [NEAR CLI](cli.md) and [NEAR JavaScript API](/tools/near-api-js/quick-reference).
+4. Developer tools to deploy and interact with contracts such as the [NEAR CLI](cli.md) and [NEAR API](./near-api.md).
diff --git a/docs/5.api/rpc/introduction.md b/docs/5.api/rpc/introduction.md
@@ -8,7 +8,7 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
 The RPC API allows you to communicate directly with the NEAR network. For example,
-tools such as [near-api-js](/tools/near-api-js/quick-reference) are just abstractions making RPC calls.
+tools such as [near-api](../../4.tools/near-api.md) are just abstractions making RPC calls.
 
 <hr className="subsection" />
 

diff --git a/docs/5.api/rpc/setup.md b/docs/5.api/rpc/setup.md
@@ -53,8 +53,8 @@ After that is set up, just copy/paste the `JSON object` example snippets below i
 
 All of the queries listed in this documentation page can be called using [`near-api-js`](https://github.com/near/near-api-js).
 
-- For `near-api-js` installation and setup please refer to `near-api-js` [quick reference documentation](/tools/near-api-js/quick-reference).
-- All JavaScript code snippets require a `near` object. For examples of how to instantiate, [**click here**](/tools/near-api-js/quick-reference#connect).
+- For `near-api-js` installation and setup please refer to `near-api-js` [quick reference documentation](../../4.tools/near-api.md).
+- All JavaScript code snippets require a `near` object. For examples of how to instantiate, [**click here**](../../4.tools/near-api.md#connecting-to-near-connect).
 
 ---
 ## HTTPie Setup {#httpie-setup}

diff --git a/docs/6.integrations/faq.md b/docs/6.integrations/faq.md
@@ -238,7 +238,7 @@ Accounts don’t have associated resources. Gas amount is predetermined for all
 
 ### How do we know how much gas to add to a transaction?
 
-- See reference documentation here: https://nomicon.io/Economics/
+- See reference documentation here: https://nomicon.io/Economics/Economic
 - See API documentation for [discovering gas price via RPC here](/api/rpc/gas#gas-price).
 
 The issuer of a transaction should attach some amount of gas by taking a guess at budget which will get the transaction processed. The contract knows how much to fund different cross contract calls. Gas price is calculated and fixed per block, but may change from block to block depending on how full / busy the block is. If blocks become more than half full then gas price increases.

diff --git a/docs/pagoda/rpc/setup.md b/docs/pagoda/rpc/setup.md
@@ -89,7 +89,7 @@ http post https://near-testnet.api.pagoda.co/rpc/v1/ jsonrpc=2.0 id=dontcare met
 All of the queries listed in this documentation page can be called using [`near-api-js`](https://github.com/near/near-api-js).
 
 :::tip
-For `near-api-js` installation and setup please refer to `near-api-js` [quick reference documentation](https://docs.near.org/tools/near-api-js/quick-reference#install).
+For `near-api-js` installation and setup please refer to `near-api-js` [quick reference documentation](../../4.tools/near-api.md).
 :::
 
 Add the following code to get started:
@@ -126,7 +126,7 @@ getState(ACCOUNT_ID);
 ```
 
 :::info
-All JavaScript code snippets require a `near` object. For examples of how to instantiate, [click here](https://docs.near.org/tools/near-api-js/quick-reference#connect).
+All JavaScript code snippets require a `near` object. For examples of how to instantiate, [click here](../../4.tools/near-api.md#connecting-to-near-connect).
 :::
 
 ## Rust Setup

diff --git a/website/linkinator.config.json b/website/linkinator.config.json
@@ -49,6 +49,8 @@
     "https://near.org/privacy",
     "https://stackoverflow.com/*",
     "https://near.social/zavodil.near/widget/Lido",
-    "https://learn.microsoft.com/en-us/windows/wsl/setup/environment"
+    "https://learn.microsoft.com/en-us/windows/wsl/setup/environment",
+    "https://www.pagoda.co/",
+    "https://testnet.nearblocks.io/*"
   ]
 }
diff --git a/website/src/theme/Footer/index.js b/website/src/theme/Footer/index.js
@@ -329,7 +329,7 @@ function Footer() {
                   className="footer-menu list-reset mt-5 text-16 md:text-16"
                 >
                   <li className="menu-item menu-item-type-post_type menu-item-object-page menu-item-2045">
-                    <a href="/tools/near-api-js/quick-reference">
+                    <a href="/tools/near-api">
                       API
                     </a>
                   </li>
-Original file line number
+Diff line change
@@ Expand Up @@
     :::tip
-    [Pagoda Inc.](https://pagoda.co) runs NEAR Lake nodes to store the data in JSON format on AWS S3.
+    [Pagoda Inc.](https://www.pagoda.co) runs NEAR Lake nodes to store the data in JSON format on AWS S3.
     There is no need to run your own NEAR Lake unless you have specific reasons to do that.
     :::
@@ Expand Down @@