pubky · 86667 · Aug 12, 2026 · Aug 12, 2026
diff --git a/src/content/docs/architecture.md b/src/content/docs/architecture.md
@@ -398,13 +398,3 @@ Users → Enterprise Homeserver + Custom Aggregator + Private Nexus → Internal
 ```
 
 **Best for**: Organizations with custom requirements
-
----
-
-## See Also
-
-- [Getting started with Pubky](/getting-started/)
-- [Pubky protocol Overview](/explore/pubky-protocol/introduction/)
-- [SDK documentation for building applications](/explore/pubky-protocol/sdk/)
-- [How Pubky differs from alternatives](/comparisons/)
-- [FAQ](/faq/)
diff --git a/src/content/docs/comparisons.md b/src/content/docs/comparisons.md
@@ -314,13 +314,3 @@ Ethereum Address → On-chain Registry → Hubs (P2P) → Apps
 - ✅ Content-addressed data model fits
 - ✅ Deduplication is valuable
 
----
-
-## See Also
-
-- **[Main Documentation](/)**: Complete Pubky knowledge base
-- **[Getting Started](/getting-started/)**: Get started with Pubky
-- **[FAQ](/faq/)**: Frequently asked questions
-- **[Vision](/the-vision-of-pubky/)**: Why we're building Pubky
-- **[Pubky protocol](/explore/pubky-protocol/introduction/)**: Technical overview
-
diff --git a/src/content/docs/explore/pubky-apps/indexing-and-aggregation/pubky-nexus.md b/src/content/docs/explore/pubky-apps/indexing-and-aggregation/pubky-nexus.md
@@ -294,11 +294,3 @@ If you're building a social client application to consume the Nexus API:
 - **Data Model Specification**: Use [pubky-app-specs](https://www.npmjs.com/package/pubky-app-specs) as your authoritative reference for data structures and validation rules
 - **Web App**: [pubky.app](/explore/pubky-apps/reference-app/pubky-app/) ([github.com/pubky/pubky-app](https://github.com/pubky/pubky-app)) — the production reference implementation
 - **API Exploration**: Use the [Swagger UI](https://nexus.pubky.app/swagger-ui/) to explore available endpoints and test queries
-
-## See Also
-
-- [Aggregators](/explore/pubky-apps/indexing-and-aggregation/aggregator/) - Event collection and filtering
-- [Indexers](/explore/pubky-apps/indexing-and-aggregation/indexer/) - Data normalization and transformation
-- [Web Servers](/explore/pubky-apps/indexing-and-aggregation/web-server/) - API serving layer
-- [Custom Backend Architecture](/explore/pubky-apps/app-architectures/custom-backend/) - Overall architecture pattern
-- [Homeservers](/explore/pubky-protocol/homeserver/) - Data source and storage layer
diff --git a/src/content/docs/explore/pubky-protocol/introduction.md b/src/content/docs/explore/pubky-protocol/introduction.md
@@ -8,7 +8,7 @@ title: "Pubky: Open Protocol for Decentralized Web Applications"
 
 ## Overview
 
-The Pubky protocol combines a [censorship-resistant public-key-based alternative to DNS](https://github.com/pubky/pkarr) ([PKARR](/explore/pubky-protocol/pkarr/introduction/)) with conventional, tried-and-tested web technologies. This keeps users in control of their identities and data while enabling developers to build software with the availability of web apps, without the costs of managing a central database.
+Pubky combines a [censorship-resistant public-key-based alternative to DNS](https://github.com/pubky/pkarr) ([PKARR](/explore/pubky-protocol/pkarr/introduction/)) with conventional, tried-and-tested web technologies. This keeps users in control of their identities and data while enabling developers to build software with the availability of web apps, without the costs of managing a central database.
 
 **The Core Philosophy:**
 > "The Web, long centralized, must decentralize; Long decentralized, must centralize."
@@ -19,34 +19,6 @@ The Pubky protocol provides the infrastructure for building truly decentralized
 - Applications remain interoperable
 - No single entity can control or censor
 
-## What Pubky?
-
-The Pubky protocol consists of three main components:
-
-### 1. Protocol Specification
-The open protocol that defines:
-- Public key-based authentication
-- Capability-based authorization
-- Key-value storage semantics
-- Homeserver discovery via [PKARR](/explore/pubky-protocol/pkarr/introduction/)
-- RESTful API standards
-
-### 2. [Pubky Homeserver](/explore/pubky-protocol/homeserver/)
-A production-ready server application that:
-- Hosts user data in a filesystem
-- Provides RESTful HTTP API
-- Handles authentication and sessions
-- Publishes to [PKARR](/explore/pubky-protocol/pkarr/introduction/) for discovery
-- Stores user files separately from PostgreSQL-backed homeserver metadata
-- Includes admin and metrics endpoints
-
-### 3. SDK (Software Development Kit)
-Client libraries for developers:
-- **Rust**: Full-featured native SDK
-- **JavaScript/WASM**: Browser and Node.js support
-- **iOS/Android**: Native mobile bindings
-- Examples and documentation
-
 ## Core Concepts
 
 ### [Homeserver](/explore/pubky-protocol/homeserver/)
@@ -233,14 +205,4 @@ For [Synonym](https://synonym.to/) as lead of this project, the goal is to:
 - Integration libraries
 - Documentation improvements
 
-## Related Technologies
-
-- **[Pubky Ring](/explore/technologies/pubky-ring/)**: Identity manager app
-- **[Pubky Backup](/explore/technologies/pubky-backup/)**: Desktop backup for published Homeserver data
-- **[Paykit](/explore/technologies/paykit/)**: Payment protocol (WIP)
-- **[Pubky Noise](/explore/technologies/pubky-noise/)**: Encrypted communication (WIP)
-- **[Pubky App](/explore/pubky-apps/introduction/)**: Social media application
-
----
-
 **Pubky provides the foundation for building truly decentralized applications. Join us in creating a more open web!**
diff --git a/src/content/docs/explore/technologies/dns.md b/src/content/docs/explore/technologies/dns.md
@@ -97,11 +97,3 @@ Pubky uses DNS technology in innovative ways:
 2. **Hybrid approach**: Supports both traditional ICANN domains and public-key domains
 3. **[DoH](/explore/technologies/doh/) integration**: Provides encrypted DNS resolution
 4. **Homeserver discovery**: PKARR records contain DNS-like entries pointing to [Homeservers](/explore/pubky-protocol/homeserver/)
-
-## See Also
-
-- **[PKDNS](/explore/technologies/pkdns/)**: Public-key DNS implementation
-- **[PKARR](/explore/pubky-protocol/pkarr/introduction/)**: Public key addressable resource records
-- **[Mainline DHT](/explore/technologies/mainline-dht/)**: Distributed hash table powering PKDNS
-- **[DoH](/explore/technologies/doh/)**: DNS over HTTPS for encrypted queries
-- **[HTTPS](/explore/technologies/https/)**: Secure HTTP protocol
diff --git a/src/content/docs/explore/technologies/homegate.md b/src/content/docs/explore/technologies/homegate.md
@@ -605,10 +605,3 @@ Potential improvements for Homegate:
 - **Prelude Documentation**: [https://docs.prelude.so/](https://docs.prelude.so/)
 - **PhoenixD Documentation**: [https://github.com/ACINQ/phoenixd](https://github.com/ACINQ/phoenixd)
 
-## See Also
-
-- [Homeserver](/explore/pubky-protocol/homeserver/) - Pubky Homeserver documentation
-- [Pubky protocol](/explore/pubky-protocol/introduction/) - Core protocol and SDK
-- [FAQ#Q50](/faq/#q50) - How users join Pubky App
-- [Censorship](/explore/concepts/censorship/) - Censorship resistance principles
-
diff --git a/src/content/docs/explore/technologies/http-relay.md b/src/content/docs/explore/technologies/http-relay.md
@@ -47,9 +47,3 @@ The previous `/link` channel used synchronous producer/consumer pairing. The new
 The relay is designed to be self-hostable for reduced latency, privacy, and reliability. Use the [`pubky-http-relay`](https://github.com/pubky/pubky-http-relay) crate as a dependency in your Rust project.
 
 Apps can specify a custom relay URL via the [SDK](/explore/pubky-protocol/sdk/).
-
-## Related Components
-
-- **[Pubky Ring](/explore/technologies/pubky-ring/)**: The authenticator that sends tokens through the relay
-- **[Pubky SDK](/explore/pubky-protocol/sdk/)**: Client library that subscribes to relay channels
-- **[Pubky Homeserver](/explore/pubky-protocol/homeserver/)**: Verifies tokens and issues sessions
diff --git a/src/content/docs/explore/technologies/mainline-dht.md b/src/content/docs/explore/technologies/mainline-dht.md
@@ -73,9 +73,3 @@ From the PKARR project's perspective, Mainline DHT was chosen because:
 - **Examples**: [github.com/pubky/mainline/tree/main/examples](https://github.com/pubky/mainline/tree/main/examples)
 - **Wikipedia**: [Mainline DHT](https://en.wikipedia.org/wiki/Mainline_DHT)
 - **Kademlia Protocol**: [Wikipedia](https://en.wikipedia.org/wiki/Kademlia)
-
-## Related Documentation
-
-- [PKARR](/explore/pubky-protocol/pkarr/introduction/) - Public Key Addressable Resource Records built on Mainline DHT
-- [PKDNS](/explore/technologies/pkdns/) - DNS server that resolves public-key domains via DHT queries
-- [DHT](/explore/technologies/dht/) - General Distributed Hash Table concepts
diff --git a/src/content/docs/explore/technologies/pkdns.md b/src/content/docs/explore/technologies/pkdns.md
@@ -463,11 +463,3 @@ pkdns -f 1.1.1.1:53  # Cloudflare DNS
 - **[pkdns-vanity](https://github.com/jphastings/pkdns-vanity)**: Generate vanity public-key domains
 - **[awesome-pubky](https://github.com/aljazceru/awesome-pubky)**: Curated list of Pubky resources
 
-## See Also
-
-- [PKARR](/explore/pubky-protocol/pkarr/introduction/) - Public Key Addressable Resource Records
-- [Mainline DHT](/explore/technologies/mainline-dht/) - Distributed hash table powering PKDNS
-- [DNS](/explore/technologies/dns/) - Traditional Domain Name System
-- [DoH](/explore/technologies/doh/) - DNS over HTTPS protocol
-- [Pubky protocol](/explore/pubky-protocol/introduction/) - Core protocol and infrastructure
-
diff --git a/src/content/docs/explore/technologies/pubky-cli.md b/src/content/docs/explore/technologies/pubky-cli.md
@@ -313,10 +313,3 @@ pubky-cli user signup $HOMESERVER_PK ./recovery
 - **Repository**: [github.com/pubky/pubky-cli](https://github.com/pubky/pubky-cli)
 - **CI Status**: [GitHub Actions](https://github.com/pubky/pubky-cli/actions)
 - **Pubky SDK**: [docs.rs/pubky](https://docs.rs/pubky)
-
-## Related Documentation
-
-- [Pubky SDK](/explore/pubky-protocol/sdk/) - Client libraries for all platforms
-- [Pubky Homeservers](/explore/pubky-protocol/homeserver/) - Homeserver deployment and configuration
-- [Pubky Docker](/explore/technologies/pubky-docker/) - Full stack Docker environment
-- [Pubky Homeserver API](/explore/pubky-protocol/api/) - HTTP API specification
diff --git a/src/content/docs/explore/technologies/pubky-explorer.md b/src/content/docs/explore/technologies/pubky-explorer.md
@@ -343,11 +343,3 @@ Potential improvements for Pubky Explorer:
 - **SolidJS Documentation**: [https://solidjs.com](https://solidjs.com)
 - **Vite Documentation**: [https://vitejs.dev](https://vitejs.dev)
 
-## See Also
-
-- [Homeserver](/explore/pubky-protocol/homeserver/) - Data storage explained
-- [Pubky SDK](/explore/pubky-protocol/sdk/) - How data access works
-- [Pubky Homeserver API](/explore/pubky-protocol/api/) - Homeserver HTTP API
-- [PKARR](/explore/pubky-protocol/pkarr/introduction/) - Public key resolution
-- [FAQ#Q17](/faq/#q17) - FAQ entry about exploring data
-
diff --git a/src/content/docs/explore/technologies/pubky-noise.md b/src/content/docs/explore/technologies/pubky-noise.md
@@ -240,8 +240,3 @@ Pubky Noise is a **communication layer** for Pubky:
 - **Repository**: [github.com/pubky/pubky-noise](https://github.com/pubky/pubky-noise) (WIP)
 - **Noise Protocol Framework**: [https://noiseprotocol.org/](https://noiseprotocol.org/)
 
-## Related Documentation
-
-- [Paykit](/explore/technologies/paykit/) - Uses Pubky Noise for payment negotiation channels
-- [Pubky Ring](/explore/technologies/pubky-ring/) - Manages Noise endpoints and sessions
-
diff --git a/src/content/docs/troubleshooting.md b/src/content/docs/troubleshooting.md
@@ -355,13 +355,3 @@ pubky-cli user get /pub/test ./recovery.file
 # Admin diagnostics
 PUBKY_ADMIN_PASSWORD=admin pubky-cli admin info
 ```
-
----
-
-## See Also
-
-- **[Getting Started](/getting-started/)**: Setup guides
-- **[FAQ](/faq/)**: Frequently asked questions
-- **[SDK Documentation](/explore/pubky-protocol/sdk/)**: Detailed API docs
-- **[PKDNS](/explore/technologies/pkdns/)**: DNS resolution details
-- **[Homeserver](/explore/pubky-protocol/homeserver/)**: Homeserver administration