adityamparikh opened a new pull request, #143: URL: https://github.com/apache/solr-mcp/pull/143
## Summary Makes **solr-mcp the source of truth for the MCP documentation content**, so docs travel with the code — every feature PR can update its docs in the same review. This addresses @janhoy's request on [apache/solr-site#175](https://github.com/apache/solr-site/pull/175#issuecomment-4664039372): *"Ideally I'd like the mcp docs to live in the same repo as code, but be deployed to solr site."* Adds under `docs/site/content/`: - `pages/mcp/**` — the MCP documentation Markdown pages (Quick Start, per-client setup, Security, Observability, Features, Resources, …) - `doap/solr-mcp.rdf` — the DOAP project descriptor Plus `docs/site/README.md` describing the content/presentation split and the build-time assembly contract. ## How it gets deployed Content here is **plain Pelican Markdown** (front-matter selects a `template: mcp/*`). The **presentation layer** (Pelican templates, theme, CSS, `pelicanconf.py`) stays in [apache/solr-site](https://github.com/apache/solr-site), so the MCP pages keep the shared Solr site look and their published URLs (`https://solr.apache.org/mcp/...`) are unchanged. At site-build time, solr-site fetches this directory into its Pelican `content/` tree before rendering — mirroring how the Solr Reference Guide content is assembled into the site. That wiring (build.sh + Pelican CI + removal of the now-sourced content) is the companion change in **apache/solr-site#175**. ## Sequencing The solr-site fetch pulls from `apache/solr-mcp` `main`, so this PR should land first; then apache/solr-site#175 builds against it. ## Notes - Design doc: `docs/superpowers/specs/2026-06-09-license-notice-and-docs-deploy-design.md`. - No code or build changes — documentation content only. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
