From 5bbe44a42df7c3117424767caf0659820546ddca Mon Sep 17 00:00:00 2001
From: Tadas Antanavicius <3900899+tadasant@users.noreply.github.com>
Date: Thu, 12 Jun 2025 10:32:17 -0700
Subject: [PATCH] Add more links

---
 docs/README.md | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/docs/README.md b/docs/README.md
index 30b24af..2fffb8b 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -1,7 +1,19 @@
 # Official Registry Documentation
 
+## Project Documentation
+
+[`design_principles.md`](./design_principles.md) - Core constraints and principles guiding the registry design
+
+[`faq.md`](./faq.md) - Frequently asked questions about the MCP Registry
+
+[`roadmap.md`](./roadmap.md) - High-level roadmap for the MCP Registry development
+
+[`MCP Developers Summit 2025 - Registry Talk Slides.pdf`](./MCP%20Developers%20Summit%202025%20-%20Registry%20Talk%20Slides.pdf) - Slides from a talk given at the MCP Developers Summit on May 23, 2025, with an up-to-date vision of how we are thinking about the official registry.
+
+## API & Technical Specifications
+
 [`openapi.yaml`](./openapi.yaml) - OpenAPI specification for the official registry API
 
 [`api_examples.md`](./api_examples.md) - Examples of what data will actually look like coming from the official registry API
 
-[`MCP Developers Summit 2025 - Registry Talk Slides.pdf`](./MCP%20Developers%20Summit%202025%20-%20Registry%20Talk%20Slides.pdf) - Slides from a talk given at the MCP Developers Summit on May 23, 2025, with an up-to-date vision of how we are thinking about the official registry.
\ No newline at end of file
+[`architecture.md`](./architecture.md) - Technical architecture, deployment strategies, and data flows
\ No newline at end of file