Fix links

blog/2023-06-20-federation-sandbox.md

@@ -80,7 +80,7 @@ You are within your rights to disable Watchtower auto-updates, but we strongly e
 
 # Learn more about atproto federation
 
-Check out the [high-level view of federation](https://blueskyweb.xyz/blog/5-5-2023-federation-architecture).
+Check out the [high-level view of federation](/docs/advanced-guides/federation-architecture).
 
 Dive deeper with the [atproto docs](https://atproto.com/docs).
 

blog/2023-08-03-call-for-developers.md

@@ -8,4 +8,4 @@ Bluesky is an open social network built on the AT Protocol, a flexible technolog
 
 **If you're a developer interested in building on atproto, we'd love to email you an invite code.** Simply share your GitHub (or similar) profile with us via [this form](https://forms.gle/gHe4cyBrGCGRzqZt7).
 
-Read more about the AT Protocol [here](https://atproto.com/) and check out some third-party developer projects [here](https://atproto.com/community/projects).
+Read more about the AT Protocol [here](https://atproto.com/) and check out some third-party developer projects [here](/showcase).

blog/2023-08-08-feature-skyfeed/index.md

@@ -52,4 +52,4 @@ In summary: Make SkyFeed (apps, builder and more) the ultimate power user experi
 
 You can follow redsolver on Bluesky [here](https://bsky.app/profile/redsolver.dev), SkyFeed for project updates [here](https://bsky.app/profile/skyfeed.app), and be sure to try out SkyFeed yourself [here](https://skyfeed.app/).
 
-*Note: Use an [App Password](https://atproto.com/community/projects#app-passwords) when logging in to third-party tools for account security and read our [disclaimer](https://atproto.com/community/projects#disclaimer) for third-party applications.*
+*Note: Use an App Password when logging in to third-party tools for account security and read our [disclaimer](/showcase) for third-party applications.*

blog/2023-08-11-create-post.md

@@ -8,7 +8,7 @@ tags: ['feature', 'guide']
 *This blog post may become outdated as new features are added to [atproto](https://atproto.com) and the Bluesky [application schemas](https://github.com/bluesky-social/atproto/tree/main/lexicons).*
 
 ---
-First, you'll need a [Bluesky account](https://atproto.com/blog/call-for-developers). We'll create a session with [HTTPie](https://httpie.io/docs/cli/pypi) (`brew install httpie`).
+First, you'll need a [Bluesky account](https://bsky.app). We'll create a session with [HTTPie](https://httpie.io/docs/cli/pypi) (`brew install httpie`).
 
 ```sh
 http post https://bsky.social/xrpc/com.atproto.server.createSession \
@@ -26,7 +26,7 @@ http post https://bsky.social/xrpc/com.atproto.repo.createRecord \
     record:="{\"text\": \"Hello world! I posted this via the API.\", \"createdAt\": \"`date -u +"%Y-%m-%dT%H:%M:%SZ"`\"}"
 ```
 
-Posts can get a lot more complicated with replies, mentions, embedding images, and more. This guide will walk you through how to create these more complex posts in Python, but there are many [API clients and SDKs for other programming languages](https://atproto.com/community/projects#at-protocol-implementations) and Bluesky PBC publishes atproto code in [TypeScript](https://github.com/bluesky-social/atproto) and [Go](https://github.com/bluesky-social/indigo) as well.
+Posts can get a lot more complicated with replies, mentions, embedding images, and more. This guide will walk you through how to create these more complex posts in Python, but there are many [API clients and SDKs for other programming languages](/showcase) and Bluesky PBC publishes atproto code in [TypeScript](https://github.com/bluesky-social/atproto) and [Go](https://github.com/bluesky-social/indigo) as well.
 
 Skip the steps below and get the full script <a href="https://github.com/bluesky-social/atproto-website/blob/main/examples/create_bsky_post.py">here</a>. It was tested with Python 3.11, with the <code>requests</code> and <code>bs4</code> (BeautifulSoup) packages installed.
 

blog/2023-08-24-repo-sync-update.mdx

@@ -6,7 +6,7 @@ tags: ['updates']
 
 We’re excited to announce that we’re rolling out a new version of atproto [repositories](https://atproto.com/guides/data-repos) that removes history from the canonical structure of repositories, and replaces it with a logical clock. We’ll start rolling out this update next week (August 28, 2023).
 
-For most developers with projects subscribed to the [firehose](https://atproto.com/community/projects#firehose), such as feed generators, this change shouldn’t affect you. These will only affect you if you’re doing commit-aware repo sync (a good rule of thumb is if you’ve ever passed `earliest` or `latest` to the `com.atproto.sync.getRepo` method) or are explicitly checking the repo version when processing commits.
+For most developers with projects subscribed to the [firehose](/showcase?tags=firehose), such as feed generators, this change shouldn’t affect you. These will only affect you if you’re doing commit-aware repo sync (a good rule of thumb is if you’ve ever passed `earliest` or `latest` to the `com.atproto.sync.getRepo` method) or are explicitly checking the repo version when processing commits.
 
 ### Removing Repository History 
 

blog/2023-09-15-rate-limits-pds-v3/index.md

@@ -4,7 +4,7 @@ title: Rate Limits, PDS Distribution v3, and More
 tags: ['updates']
 ---
 
-To get future blog posts directly in your email, you can now subscribe to Bluesky’s Developer Mailing List [here](/blog/rate-limits-pds-v3#subscribe-for-developer-updates).
+To get future blog posts directly in your email, you can now subscribe to Bluesky’s Developer Mailing List [here](/docs/support/mailing-list).
 
 ### Adding Rate Limits
 
@@ -91,6 +91,6 @@ If that still isn’t working for you, file a support ticket through the app (
 
 ### Subscribe for Developer Updates
 
-You can subscribe to Bluesky’s Developer Mailing List below to receive future updates in your email. If you received your invite code from the [developer waitlist](https://atproto.com/blog/call-for-developers), you’re already subscribed. Each email will have the option to unsubscribe.
+You can subscribe to Bluesky’s Developer Mailing List [here](/docs/support/mailing-list) to receive future updates in your email. If you received your invite code from the developer waitlist, you’re already subscribed. Each email will have the option to unsubscribe.
 
 We’ll continue to publish updates to our [technical blog](https://atproto.com/blog) as well as on the app from [@atproto.com](https://bsky.app/profile/atproto.com).

blog/2023-10-06-bgs-and-did-doc.md

@@ -6,7 +6,7 @@ tags: ['updates']
 
 We have a number of protocol and infrastructure changes rolling out in the next three months, and want to keep everybody in the loop.
 
-*This update was also emailed to the developer mailing list, which you can subscribe to at the bottom of this update.*
+*This update was also emailed to the developer mailing list, which you can subscribe to [here](/docs/support/mailing-list).*
 
 ## TL;DR
 
@@ -25,7 +25,7 @@ Your existing cursor for bsky.social will not be in sync with bsky.network, so c
 The Bluesky services themselves are moving to a federated deployment, with multiple Bluesky (the company) PDS instances aggregated by a BGS, and the AppView downstream of that. As of yesterday, the Bluesky Appview instance (`api.bsky.app`) consumes from a Bluesky PBC BGS (`bsky.network`), which consumes from the Bluesky PDS (`bsky.social`). Until now, the AppView consumed directly from the PDS. 
 
 ### How close are we to federation?
-Technically, the main network BGS could start consuming from independent PDS instances today, the same as the sandbox BGS does. We have configured it not to do so until we finish implementing some more details, and do our own round of security hardening. If you want to bang on the BGS implementation (written in Go, code in the [indigo github repository](https://github.com/bluesky-social/indigo)), please do so in the [sandbox environment](https://atproto.com/blog/federation-developer-sandbox), not the main network.
+Technically, the main network BGS could start consuming from independent PDS instances today, the same as the sandbox BGS does. We have configured it not to do so until we finish implementing some more details, and do our own round of security hardening. If you want to bang on the BGS implementation (written in Go, code in the [indigo github repository](https://github.com/bluesky-social/indigo)), please do so in the [sandbox environment](/blog/federation-sandbox), not the main network.
 
 ### This change impacts devs in two ways:
 

blog/2023-10-11-building-on-atproto.md

@@ -11,26 +11,26 @@ In this blog post, we’ll share what you can already build on atproto, and what
 
 ## Getting Started with the AT Protocol
 
-In June of this year, we launched the [federation sandbox environment](https://atproto.com/blog/federation-developer-sandbox) for developers to begin exploring, as we prepare to launch federation in the production environment as well.
+In June of this year, we launched the [federation sandbox environment](/blog/federation-sandbox) for developers to begin exploring, as we prepare to launch federation in the production environment as well.
 
 Currently, the AT Protocol is under active development, and the Bluesky beta app is a microblogging client built on top of it. We’re using the Bluesky beta to drive and inform protocol development. 
 
 While the production network isn’t federated quite yet, developers can already currently build:
 
 * Feed generators
     * Third-party developers have built algorithmic feeds, community-based feeds, topic-based feeds, and more that hundreds of thousands of users view every day.
-    * Get started with our [feed generator starter kit](https://github.com/bluesky-social/feed-generator). 
+    * Get started with our [feed generator starter kit](/docs/starter-templates/custom-feeds). 
 * Bots
     * Over the last few months, developers have created MTA Alert bots, earthquake bots, chat bots, and other interactive experiences on the network.
-    * Here’s a [starter script for a TypeScript bot ](https://github.com/bluesky-social/cookbook/tree/main/ts-bot)in our new cookbook GitHub repo.
+    * Get started with a template for a Bluesky bot [here](/docs/starter-templates/bots).
 * Bluesky clients
     * Because the AT Protocol is open, third-party developers can create entirely separate frontends for the network too.
-    * Check out alternative Bluesky clients [here](https://atproto.com/community/projects#clients).
+    * Here's a [starter template](/docs/starter-templates/clients) for building a Bluesky client.
 
-You can read about more third-party projects and check them out [here](https://atproto.com/community/projects). [Let us know](https://atproto.com/community/projects#submit-your-project) what you build!
+You can read about more third-party projects and check them out [here](/showcase). Let us know what you build!
 
 ## What to Expect
 
 We’ve still only scratched the surface of what’s possible on atproto. Currently, microblogging is the only content type that’s integrated, but we’re excited to for apps for forums, photo-centric platforms, long-form writing, and more to exist on atproto. 
 
-In the meantime, we’ve published a [protocol roadmap here](https://docs.bsky.app/blog/2023-protocol-roadmap) to give you a sense of our priorities and what’s coming in the future.  
+In the meantime, we’ve published a [protocol roadmap here](/blog/protocol-roadmap) to give you a sense of our priorities and what’s coming in the future.  

blog/2023-10-11-protocol-roadmap.md

@@ -15,7 +15,7 @@ Feel free to share your thoughts via Github Discussions [here](https://github.co
 
 ## Getting to Federation
 
-The AT Protocol is designed as a federated social web protocol. While we have an [open federated sandbox network](https://atproto.com/blog/federation-developer-sandbox) for developers to experiment with, the main Bluesky services are currently still not federated. Our current development priority is to resolve any final protocol issues or decisions that would impede federation with independent PDS instances. Some of these points are listed below.
+The AT Protocol is designed as a federated social web protocol. While we have an [open federated sandbox network](/blog/federation-sandbox) for developers to experiment with, the main Bluesky services are currently still not federated. Our current development priority is to resolve any final protocol issues or decisions that would impede federation with independent PDS instances. Some of these points are listed below.
 
 **Account Migration:** One of the differentiating features of atproto is seamless migration of both identity and public content from one PDS instance to another. The foundations for this feature were set in place from the start, but there are some details and behaviors to decide on and document.
 

docusaurus.config.js

@@ -133,6 +133,10 @@ const config = {
                 label: "Community-run Discord",
                 href: "https://discord.gg/3srmDsHSZJ",
               },
+              {
+                label: "Mailing List",
+                href: "/docs/support/mailing-list",
+              },
             ],
           },
           {