Merge pull request #2943 from XRPLF/broken-links

Author: AKCodez

about/index.page.tsx

@@ -235,7 +235,7 @@ export default function XrplOverview() {
                   "Unlike most other blockchains, the XRP Ledger requires no mining and uses negligible energy, key to long-term growth and stability."
                 )}
               </p>
-              <a className="btn btn-primary btn-arrow" href="impact">
+              <a className="btn btn-primary btn-arrow" href="/about/impact">
                 {translate("Learn More")}
               </a>
             </div>
@@ -262,7 +262,7 @@ export default function XrplOverview() {
                   "With the XRPL, these developers are building innovative blockchain projects and applications across use cases including tokenization of assets, online gaming, asset custody, NFTs, and DeFi."
                 )}
               </p>
-              <a className="btn btn-primary btn-arrow mb-10-sm" href="uses">
+              <a className="btn btn-primary btn-arrow mb-10-sm" href="/about/uses">
                 {translate("Explore More")}
               </a>
             </div>
@@ -438,7 +438,7 @@ export default function XrplOverview() {
               </div>
             ))}
             <center>
-              <a className="btn btn-primary btn-arrow mt-20" href="faq">
+              <a className="btn btn-primary btn-arrow mt-20" href="/about/faq">
                 {translate("View Full FAQ")}
               </a>
             </center>

blog/2021/road-to-xrp-ledger-1-7-improving-efficiency-and-security.md

@@ -30,7 +30,7 @@ Proposed and agreed upon by XRPL server operators, the features in this latest r
 
 Today’s release is another step in the continuous evolution of the XRPL. Feature updates, such as those being introduced today, are reviewed and voted on by the XRPL’s network operators and help improve its capabilities.
 
-[The XRP Ledger Foundation](https://xrplf.org/)—whose goal is to accelerate the development and adoption of XRPL by engaging developers—will also play an active role in maintaining XRPL’s infrastructure and default [Unique Node List (UNL)](https://xrpl.org/faq.html#validators-and-unique-node-lists) in the future.
+[The XRP Ledger Foundation](https://xrplf.org/)—whose goal is to accelerate the development and adoption of XRPL by engaging developers—will also play an active role in maintaining XRPL’s infrastructure and default [Unique Node List (UNL)](https://xrpl.org/about/faq#validators-and-unique-node-lists) in the future.
 
 “Enhancements, such as today’s improvements to memory usage, are key to growth and innovation on the Ledger,” says Bharath Chari of the XRP Ledger Foundation. “We look forward to supporting the wider ecosystem, including the superb code development by the RippleX team. Testament to this will be our focus on producing an evolving list of validators and enhancing the core code and infrastructure behind the XRP Ledger."
 

blog/2022/dev-reflections-relaunch.md

@@ -23,10 +23,11 @@ In doing so, you join the growing list of XRPL developers currently featured and
 
 ### How can I get featured?
 
-Interested projects, companies and developers must submit their projects through the form featured on the [XRPL Community](/community) page (see “XRPL Community Spotlight”). Submissions will be reviewed for completeness and must meet the minimum word requirements to be featured on the blog. To help you get started, check out previous [Developer Reflections](https://xrpl.org/blog/label/developer-reflections.html):
+Interested projects, companies and developers must submit their projects through the form featured on the [XRPL Community](/community) page (see “XRPL Community Spotlight”). Submissions will be reviewed for completeness and must meet the minimum word requirements to be featured on the blog. To help you get started, check out previous Developer Reflections:
 
-- [XRPScan](https://xrpl.org/blog/2020/developer-reflections-xrpscan.html)
-- [XRP Toolkit](https://xrpl.org/blog/2020/developer-reflections-xrp-toolkit.html)
+- [XRPScan](https://xrpl.org/blog/2020/developer-reflections-xrpscan)
+- [XRP Toolkit](https://xrpl.org/blog/2020/developer-reflections-xrp-toolkit)
+- [Xrplorer](https://xrpl.org/blog/2020/developer-reflections-xrplorer)
 
 Projects seeking to be featured on the **[Use Cases page](/about/uses)** can also submit via the form. 
 

blog/2022/get-ready-for-nfts.md

@@ -28,40 +28,40 @@ If you operate an XRP Ledger server but don’t upgrade to version 1.9.2 (or hig
 
 If the NonFungibleTokensV1_1 amendment does not become enabled, then your server will not become amendment blocked and should continue to operate.
 
-For instructions on upgrading on supported platforms, see [Install `rippled`](https://xrpl.org/install-rippled.html).
+For instructions on upgrading on supported platforms, see [Install `rippled`](/docs/infrastructure/installation).
 
 ## Amendment Voting Summary
 
 For an amendment to the XRP Ledger protocol to become enabled, it must hold **over 80% support** from trusted validators continuously for two weeks.
 
 The exact amendment voting calculations depend on the quorum of validators that are currently online and participating in consensus, which means that the exact number of votes in favor of an amendment can fluctuate when validators go temporarily offline. If at any point its support drops below 80%, the timer resets and the amendment must wait a full two weeks again starting when it regains 80%+ support.
 
-Previously, the threshold for amendment voting was "at least 80%" but in some cases rounding in the reference server's calculations could cause this condition to be met with slightly below 80%. The [fixAmendmentMajorityCalc amendment](https://xrpl.org/known-amendments.html#fixamendmentmajoritycalc), which activated on 2021-04-08, changed the calculation to be **strictly greater than 80%**. Since there are currently 35 validators in all three [recommended UNLs](https://xrpl.org/faq.html#validators-and-unique-node-lists), and 28/35 is _exactly_ 80%, the threshold for voting to enable an amendment when all validators are online is at least 29 votes in favor.
+Previously, the threshold for amendment voting was "at least 80%" but in some cases rounding in the reference server's calculations could cause this condition to be met with slightly below 80%. The [fixAmendmentMajorityCalc amendment](/resources/known-amendments#fixamendmentmajoritycalc), which activated on 2021-04-08, changed the calculation to be **strictly greater than 80%**. Since there are currently 35 validators in all three [recommended UNLs](/about/faq#validators-and-unique-node-lists), and 28/35 is _exactly_ 80%, the threshold for voting to enable an amendment when all validators are online is at least 29 votes in favor.
 
-For a live view of amendment voting, you can use the [XRPScan Amendments Dashboard](https://xrpscan.com/amendments). For more discussion of the voting process, see [this blog by Ripple developer Nik B.](https://dev.to/ripplexdev/xrpl-amendments-to-vote-or-not-to-vote-5l3) as well as the [Amendments documentation](https://xrpl.org/amendments.html).
+For a live view of amendment voting, you can use the [XRPScan Amendments Dashboard](https://xrpscan.com/amendments). For more discussion of the voting process, see [this blog by Ripple developer Nik B.](https://dev.to/ripplexdev/xrpl-amendments-to-vote-or-not-to-vote-5l3) as well as the [Amendments documentation](https://xrpl.org/docs/concepts/networks-and-servers/amendments).
 
 ## NFT Functionality Summary
 
 Non-fungible tokens, or `NFToken` objects, are a new type of object on the XRP Ledger for representing assets that are each unique. The NonFungibleTokensV1_1 amendment enables new transaction types for minting, trading, and destroying these objects, with various settings that control the detailed behavior of the NFT.
 
 Tokens can have transfer fees that provide their creator with a share of the revenue when the NFT is bought and sold, and they can be part of a set of related NFTs that share a "taxon". Creators can also designate a broker who mints and sells the tokens on their behalf.
 
-The [**NonFungibleTokensV1_1** amendment](https://xrpl.org/known-amendments.html#nonfungibletokensv1_1) incorporates the original [NonFungibleTokensV1 amendment](https://xrpl.org/known-amendments.html#nonfungibletokensv1) as well as two bug fixes that were added in later releases, [fixNFTokenDirV1](https://xrpl.org/known-amendments.html#fixnftokendirv1) and [fixNFTokenNegOffer](https://xrpl.org/known-amendments.html#fixnftokennegoffer).
+The [**NonFungibleTokensV1_1** amendment](/resources/known-amendments#nonfungibletokensv1_1) incorporates the original [NonFungibleTokensV1 amendment](/resources/known-amendments#nonfungibletokensv1) as well as two bug fixes that were added in later releases, [fixNFTokenDirV1](/resources/known-amendments#fixnftokendirv1) and [fixNFTokenNegOffer](/resources/known-amendments#fixnftokennegoffer).
 
-For more information on NFTs, see the [NFT Conceptual Overview](https://xrpl.org/non-fungible-tokens.html) and related documentation.
+For more information on NFTs, see the [NFT Conceptual Overview](/docs/concepts/tokens/nfts) and related documentation.
 
 
 ## A Word of Caution
 
 Since the road to enabling native NFT support has been long, some members of the community have voiced concern regarding pent-up demand for minting NFTs and converting NFTs from the deprecated XLS-14d specification. When the NFT amendment becomes enabled, the onset of NFT minting may cause a temporary increase in traffic on the XRP Ledger network. Possible effects could include:
 
 - Outages of individual XRP Ledger servers, especially ones with older or weaker hardware
-- Increased [transaction costs](https://xrpl.org/transaction-cost.html) as a result of network load
+- Increased [transaction costs](/docs/concepts/transactions/transaction-cost) as a result of network load
 - Slower results from popular public API servers, or a higher rate of errors
 
 While performance testing has shown that the network is capable of handling the long-term effects of NFTs, the short-term impact on the actual, decentralized Mainnet and all the infrastructure built on top of it is more complex. Alloy Networks, a founding member of the XRP Ledger Foundation, [advises minters](https://twitter.com/alloynetworks/status/1561672954299269120) to be cautious and not mint or convert large collections of NFTs all at once.
 
-Users should also be careful not to burn more XRP than they intended on temporarily-elevated transaction costs. If you have an automated system for submitting transactions, now is a good time to review your code to make sure you [properly handle](https://xrpl.org/reliable-transaction-submission.html) `terQUEUED` and other non-final transaction results.
+Users should also be careful not to burn more XRP than they intended on temporarily-elevated transaction costs. If you have an automated system for submitting transactions, now is a good time to review your code to make sure you [properly handle](/docs/concepts/transactions/reliable-transaction-submission) `terQUEUED` and other non-final transaction results.
 
 
 ## Learn, ask questions, and discuss

blog/2024/how-to-mint-nfts.md

@@ -64,7 +64,7 @@ To view a list of NFTs associated with your account, simply click **Get NFTs**.
 
 ## Burning Your NFT
 
-[Burning an NFT](https://xrpl.org/docs/tutorials/python/modular-tutorials/nfts/mint-and-burn-nfts#mint-and-burn-nfts-using-python) is the process of permanently destroying the token. To burn an NFT:
+[Burning an NFT](https://xrpl.org/docs/tutorials/python/nfts/mint-and-burn-nfts) is the process of permanently destroying the token. To burn an NFT:
 
 1. Enter the Token ID of the NFT you wish to destroy.
 2. Click **Burn NFT** to remove it permanently from the ledger.

docs/concepts/networks-and-servers/peer-protocol.md

@@ -107,7 +107,7 @@ The pros and cons of each configuration are as follows:
 <tr><th>Discovered Peers</th>
   <td><ul>
     <li><p>Simplest configuration, with a low maintenance burden.</p></li>
-    <li><p>Creates the opportunity for a lot of direct peer connections. Having more direct peers comes with several benefits. Your server can <a href="ledger-history.html#fetching-history">fetch history</a> from multiple peers in parallel, both when syncing and when backfilling history. Since not all peers maintain full history, having access to more peers can also provide access to a wider range of historical data.</p></li>
+    <li><p>Creates the opportunity for a lot of direct peer connections. Having more direct peers comes with several benefits. Your server can <a href="ledger-history#fetching-history">fetch history</a> from multiple peers in parallel, both when syncing and when backfilling history. Since not all peers maintain full history, having access to more peers can also provide access to a wider range of historical data.</p></li>
     <li><p>Lowers the possibility of disconnecting from the network because your server can replace disconnected peers with new ones.</p></li>
   </ul></td>
   <td><ul>
@@ -119,7 +119,7 @@ The pros and cons of each configuration are as follows:
   <td><ul>
     <li><p>Most secure and reliable configuration when implemented effectively.</p></li>
     <li><p>As reliable and as redundant as you make it.</p></li>
-    <li><p>Can optimize the private server's performance with <a href="clustering.html">clustering</a>.</p></li>
+    <li><p>Can optimize the private server's performance with <a href="clustering">clustering</a>.</p></li>
     <li><p>Enables you to create as many direct peer connections as you want. Your private server can <a href="ledger-history.html#fetching-history">fetch history</a> from multiple peers in parallel. Since you run the peers, you also control how much ledger history each peer keeps.</p></li>
   </ul></td>
   <td><ul>

redirects.yaml

@@ -133,8 +133,11 @@ get-started.html:
 run-rippled-as-a-wallet-server.html:
     to: /docs/infrastructure/configuration/server-modes/run-rippled-as-a-stock-server
     type: 301
+faq:
+    to: /about/faq
+    type: 301
 faq.html:
-    to: /faq
+    to: /about/faq
     type: 301
 privacy-policy.html:
     to: /about/privacy-policy
@@ -143,7 +146,7 @@ privacy-policy/:
     to: /about/privacy-policy
     type: 301
 technical-faq.html:
-    to: /faq
+    to: /about/faq
     type: 301
 introduction.html:
     to: /docs/introduction/
@@ -1642,6 +1645,19 @@ report-a-scam.html:
 wallets.html:
     to: /docs/introduction/crypto-wallets
     type: 301
+blog/2014:
+    to: /blog
+    type: 301
+blog/2015:
+    to: /blog
+    type: 301
+
+blog/2020:
+    to: /blog
+    type: 301
+blog/2021:
+    to: /blog
+    type: 301
 blog/2024/rippled-2.2.0.html:
     to: /blog/2024/rippled-2.2.0
     type: 301
@@ -2437,7 +2453,10 @@ code_of_conduct.ja:
     to: /ja/docs/infrastructure/configuration/server-modes/run-rippled-as-a-stock-server
     type: 301
 /ja/faq.html:
-    to: /ja/faq
+    to: /ja/about/faq
+    type: 301
+/ja/faq:
+    to: /ja/about/faq
     type: 301
 /ja/privacy-policy.html:
     to: /ja/about/privacy-policy
@@ -2446,7 +2465,7 @@ code_of_conduct.ja:
     to: /ja/about/privacy-policy
     type: 301
 /ja/technical-faq.html:
-    to: /ja/faq
+    to: /ja/about/faq
     type: 301
 /ja/introduction.html:
     to: /ja/docs/introduction/

resources/dev-tools/tx-sender.page.tsx

@@ -260,7 +260,7 @@ function TxSenderBody(): React.JSX.Element {
                                     units: "drops of XRP",
                                     longerDescription: <div>{translate("Deliver a small amount of XRP with a large ")}
                                     <code>{translate("Amount")}</code>{translate(" value, to test your handling of ")}
-                                    <Link to="../../docs/concepts/payment-types/partial-payments">{translate("partial payments")}</Link>{translate(".")}</div>,
+                                    <Link to="/docs/concepts/payment-types/partial-payments">{translate("partial payments")}</Link>{translate(".")}</div>,
                                     buttonTitle: "(Please wait for partial payments setup to finish)",
                                 }}
                                 loadingBar={{
@@ -288,7 +288,7 @@ function TxSenderBody(): React.JSX.Element {
                                 {{
                                     buttonText: translate("Create Escrow"),
                                     units: translate("seconds"),
-                                    longerDescription: (<div>{translate("Create a ")}<Link to="../../docs/concepts/payment-types/escrow">{translate("time-based escrow")}</Link>
+                                    longerDescription: (<div>{translate("Create a ")}<Link to="/docs/concepts/payment-types/escrow">{translate("time-based escrow")}</Link>
                                     {translate(" of 1 XRP for the specified number of seconds.")}</div>),
                                 }}
                                 inputSettings={