Repository navigation
docs(hub): put connecting an AI assistant first on the docs - #23
Merged
Merged
Conversation
The landing page named the MCP guide without linking it, and the nav placed it fourth under Build with the DFO. The landing page now opens with the server address and a link to the guide, and the MCP section is a top-level nav entry after Home. The unpublished draft get-started/connect-your-assistant.md duplicated the ai repo's guide with placeholder values, so it is removed. Co-authored-by: Claude <noreply@anthropic.com>
Claude takes a link that fills in the connector. ChatGPT, Gemini, and Le Chat take three or four steps each, linked to the settings page where one exists. Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Claude <noreply@anthropic.com>
jm-rivera
marked this pull request as ready for review
November 9, 2026 15:26
Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Readers report that they cannot find how to connect an AI assistant to the DFO. The landing page named the MCP guide in plain text with no link, and the nav placed the guide fourth under Build with the DFO. This change opens the landing page with the server address and steps for Claude, ChatGPT, Gemini, and Le Chat, and gives the MCP section its own top-level nav entry, which shows as a tab in the docs header.
Changes
content/hub/index.md: new "Connect your AI assistant" section after the intro, withhttps://developmentfinance.org/mcpin a code block and one tab per assistant. The Claude tab links to a pre-filled connector dialog. ChatGPT, Gemini, and Le Chat have no such link, so their tabs give the steps and link to the settings page. The MCP row moves to the top of "Where to start", the MCP and API rows link to their guides, the account note covers the MCP server and the API, and "Next" leads with the guide.hub.yaml: thedfo-aimount moves from Build with the DFO to the top level, after Home.sources.yaml: thedfo-aititle matches the section's new name.content/hub/get-started/connect-your-assistant.md: removed. It was an unpublished draft that duplicated the ai repo's guide with a placeholder host and a token step the live server does not use.Notes for reviewers
The section and page titles come from the ai repo's
mkdocs.yml, renamed in DevelopmentFinanceObservatory/ai#162. The Le Chat tab and the Gemini Enterprise route in the full guide come from DevelopmentFinanceObservatory/ai#163. The Le Chat steps have not been run in Le Chat, and #163 explains the open question.Testing:
scripts/build.pyexits 0 with the MCP section second in the manifest nav, lychee reports 0 errors across 516 links in the built corpus, andpytestpasses 819 tests.Co-authored-by: Claude noreply@anthropic.com