fix: update old spec links (#22)

* fix: update old spec links

* add pr template

.github/workflows/pull_request_template.md

@@ -0,0 +1,7 @@
+## Changes proposed in this pull request
+
+<!-- Provide a succinct description of what this pull request entails. -->
+
+## Context
+
+<!-- What were you trying to do? Link issues here -  using `fixes #number` -->

astro.config.mjs

@@ -102,23 +102,6 @@ export default defineConfig({
       ],
     }),
   ],
-  redirects: {
-    "/rfcs/0027-interledger-protocol-4/":
-      "/developers/rfcs/interledger-protocol",
-    "/rfcs/0015-ilp-addresses/": "/developers/rfcs/ilp-addresses/",
-    "/rfcs/0029-stream/": "/developers/rfcs/stream-protocol/",
-    "/rfcs/0009-simple-payment-setup-protocol/":
-      "/developers/rfcs/simple-payment-setup-protocol/",
-    "/rfcs/0030-notes-on-oer-encoding/": "/developers/rfcs/oer-encoding/",
-    "/rfcs/0031-dynamic-configuration-protocol/":
-      "/developers/rfcs/dynamic-configuration-protocol/",
-    "/rfcs/0032-peering-clearing-settlement/":
-      "/developers/rfcs/peering-clearing-settling/",
-    "/rfcs/0038-settlement-engines/": "/developers/rfcs/settlement-engines/",
-    "/rfcs/0035-ilp-over-http/": "/developers/rfcs/ilp-over-http/",
-    "/rfcs/0036-spsp-pull-payments/": "/developers/rfcs/spsp-pull-payments/",
-    "/rfcs/0039-stream-receipts/": "/developers/rfcs/stream-receipts/",
-  },
   server: {
     port: 1103,
   },

src/content/docs/get-started.md

@@ -52,28 +52,28 @@ Interledger is a network of computers that enables the sending of value across i
 
 ## How does Interledger work?
 
-At the core of Interledger is the [Interledger Protocol (ILPv4)](https://interledger.org/rfcs/0027-interledger-protocol-4/), which is a set of rules that define how nodes should send value over the Interledger network. ILPv4 is a *request/response* protocol, where requests and responses are ILPv4 packets. Typically, a single aggregate payment from source to destination is split into multiple ILP packets. Each ILP packet contains transaction information, which is private to the nodes participating in the transaction. ILPv4 has three packet types - *Prepare*, *Fulfill*, and *Reject*.
+At the core of Interledger is the [Interledger Protocol (ILPv4)](https://interledger.org/developers/rfcs/interledger-protocol/), which is a set of rules that define how nodes should send value over the Interledger network. ILPv4 is a *request/response* protocol, where requests and responses are ILPv4 packets. Typically, a single aggregate payment from source to destination is split into multiple ILP packets. Each ILP packet contains transaction information, which is private to the nodes participating in the transaction. ILPv4 has three packet types - *Prepare*, *Fulfill*, and *Reject*.
 
 ![ILP Packets](/developers/img/ilp-packets.png)
 
 The sender constructs and sends a Prepare packet as a request to the connecting router. The routers forward the packet until it reaches the receiver. The receiver then accepts or rejects the packet by sending a Fulfill packet or a Reject packet as the response. The routers relay the response from the receiver back to the sender. When the sender receives a Fulfill packet, it knows that the packet was successfully delivered to the receiver. The sender then continues to send the remaining Prepare packets until the value is fully transferred.
 
 Interledger does not rely on any single payment network for processing value transactions. You can connect with an ILPv4 router at any time to join the network. Furthermore, Interledger sends value as tiny data packets, which makes transactions fast, secure, and inexpensive.
 
-**Tip:** For a deeper dive into how ILPv4 works, see [ILPv4 Flow](https://interledger.org/rfcs/0027-interledger-protocol-4/#prerequisites).
+**Tip:** For a deeper dive into how ILPv4 works, see [ILPv4 Flow](https://interledger.org/developers/rfcs/interledger-protocol#prerequisites).
 
 ## Building on Interledger
 
 Build payments into your apps or other protocols without tying yourself to a specific currency or payment network. Create accounts on our demo ledgers and start sending Interledger payments with the client libraries.
 
 ## Interledger architecture
 
-Interledger enables payments across many different types of ledgers. The Interledger Protocol Suite is comprised of four layers: the Application, Transport, Interledger, and Link protocols. To learn more, see the Interledger [Architecture Overview](https://interledger.org/rfcs/0001-interledger-architecture/).
+Interledger enables payments across many different types of ledgers. The Interledger Protocol Suite is comprised of four layers: the Application, Transport, Interledger, and Link protocols. To learn more, see the Interledger [Architecture Overview](https://interledger.org/developers/rfcs/interledger-architecture).
 
 ## Protocol specs and APIs
 
 To dive into the technical specs, see the [Interledger RFCs](https://github.com/interledger/rfcs). Also see the documentation for the components of the reference implementation.
 
 ## Security
 
-Interledger enables secure, multi-hop payments using [Hashed Timelock Agreements](https://interledger.org/rfcs/0022-hashed-timelock-agreements/). As of Interledger version 4, these conditions are not enforced by the ledger, as it would be too costly and slow. Instead, participants in the network use these hashlocks to perform accounting with their peers. This accounting is used to determine in-flight balances, which are periodically settled with on-ledger transfers or payment channel claims. For a detailed description of how this works, read the [Peering, Clearing, and Settlement](https://interledger.org/rfcs/0032-peering-clearing-settlement/) documentation.
+Interledger enables secure, multi-hop payments using [Hashed Timelock Agreements](https://interledger.org/developers/rfcs/hashed-timelock-agreements). As of Interledger version 4, these conditions are not enforced by the ledger, as it would be too costly and slow. Instead, participants in the network use these hashlocks to perform accounting with their peers. This accounting is used to determine in-flight balances, which are periodically settled with on-ledger transfers or payment channel claims. For a detailed description of how this works, read the [Peering, Clearing, and Settlement](https://interledger.org/developers/rfcs/peering-clearing-settling/) documentation.

src/content/docs/rfcs/hashed-timelock-agreements.mdx

@@ -0,0 +1,19 @@
+---
+title: Hashed-Timelock Agreements
+---
+
+import Rfc from "/src/components/Rfc.astro";
+
+<Rfc source="https://raw.githubusercontent.com/interledger/rfcs/main/0022-hashed-timelock-agreements/0022-hashed-timelock-agreements.md">
+
+## Background on Hashed-Timelock Contracts (HTLCs)
+
+## HTLAs Without Ledger Support
+
+## Interledger Across Diverse HTLAs
+
+## Spectrum of HTLA Types
+
+## Appendix: Additional HTLA Types
+
+</Rfc>

src/content/docs/rfcs/interledger-architecture.mdx

@@ -0,0 +1,13 @@
+---
+title: Interledger Architecture
+---
+
+import Rfc from "/src/components/Rfc.astro";
+
+<Rfc source="https://raw.githubusercontent.com/interledger/rfcs/master/0001-interledger-architecture/0001-interledger-architecture.md">
+
+## Core Concepts
+
+## Interledger Security
+
+</Rfc>

src/pages/hacktoberfest.astro

@@ -11,7 +11,7 @@ import Section from '../components/lander/Section.astro';
 				<img src="/developers/img/lander/hacktober10.svg" alt="Hacktoberfest10" class="logo--hacktober" />
 				<div class="vision">
 					<p>Our vision is a world where sending payments is as easy as sending an email. This means transactions are not limited to particular banks, mobile money providers, or borders.</p>
-					<p>Because we strive to be open, inclusive, and innovative in everything we do, we have provided a neutral home for the <a href="https://interledger.org/rfcs/0027-interledger-protocol-4/">Interledger Protocol</a> and the <a href="https://openpayments.guide/">Open Payments</a> and <a href="https://webmonetization.org/">Web Monetization</a> standards.</p>
+					<p>Because we strive to be open, inclusive, and innovative in everything we do, we have provided a neutral home for the <a href="https://interledger.org/developers/rfcs/interledger-protocol/">Interledger Protocol</a> and the <a href="https://openpayments.guide/">Open Payments</a> and <a href="https://webmonetization.org/">Web Monetization</a> standards.</p>
 				</div>
 			</header>
 		</Section>
@@ -20,7 +20,7 @@ import Section from '../components/lander/Section.astro';
 			<div class="intro-grid">
 				<div class="intro-grid__text1">
 					<p>
-            The <a href="https://interledger.org/rfcs/0027-interledger-protocol-4/">Interledger Protocol</a> has arisen from a need to solve the complexity of global payments. It’s an open, neutral protocol for transferring money based on TCP/IP, the protocol that defines the Internet. It was designed for sending cross-border, cross-currency, instant payments. We provide standards (like <a href="https://openpayments.guide/">Open Payments</a> and <a href="https://webmonetization.org/">Web Monetization</a>) and tools (like <a href="https://rafiki.dev/">Rafiki</a>) that lower the barrier for financial services to adopt ILP and increase access to digital financial services.
+            The <a href="https://interledger.org/developers/rfcs/interledger-protocol/">Interledger Protocol</a> has arisen from a need to solve the complexity of global payments. It’s an open, neutral protocol for transferring money based on TCP/IP, the protocol that defines the Internet. It was designed for sending cross-border, cross-currency, instant payments. We provide standards (like <a href="https://openpayments.guide/">Open Payments</a> and <a href="https://webmonetization.org/">Web Monetization</a>) and tools (like <a href="https://rafiki.dev/">Rafiki</a>) that lower the barrier for financial services to adopt ILP and increase access to digital financial services.
           </p>
         </div>
         <div class="intro-grid__text2">