Skip to content

Integration roadmap

Everything on this page is planned: none of these are installable packages yet, and no package names or release dates are promised. Native HTTP and the shared widget are building blocks, not proof of a finished integration; delivery is tracked in the repository’s TODO.md. Shipped integrations live in the Search & CMS integration guide.

On this page

Today, use the native HTTP API from any language, or the documented widget/component for an existing frontend. The integrations directory keeps native interfaces first, followed by search adapters, CMS platforms, frameworks, documentation sites and language clients.

CMS platforms

The eight CMS targets are WordPress, Shopify, Wix, Squarespace, Joomla, Webflow, Drupal and Strapi. WordPress’s source plugin is implemented; the remaining seven need dedicated connectors. This list combines widely used platforms with a headless CMS target, rather than claiming a strict top-eight ranking. W3Techs adoption data was reviewed on October 7, 2026. Astro is covered separately as a framework with a native component.

Every content connector must cover initial ingestion, update/delete propagation, canonical URLs, publication state and appropriate viewer access. Do not silently index drafts, private pages or member content into public search.

Shopify

Planned. Build a theme app extension and server-held ingestion configuration; synchronize published products/pages, updates and deletes. Keep storefront search scoped to deliberately public content.

Wix

Planned. Build a Velo backend bridge and site search component; synchronize published CMS collections and exclude private/member-only content unless viewer authorization is enforced.

Squarespace

Planned. Validate code-injection availability by Squarespace plan, bundle a public search widget and document a supported published-content crawl/export refresh strategy.

Joomla

Planned. Build an installable module/plugin, article ingestion and update/delete hooks; preserve Joomla access levels and canonical source routes.

Webflow

Planned. Build a CMS publish/update/delete ingestion bridge and site embed recipe; keep tokens server-side and index only intended public items.

Drupal

Planned. Build a Drupal module with entity/revision sync, a search block and access-aware retrieval; cover unpublish/delete events and canonical URLs.

Strapi

Planned. Build lifecycle/webhook ingestion for published entries and media, including update/delete propagation; keep draft/private entries outside public search.

Documentation sites

Docusaurus

Planned. Build a Docusaurus plugin/theme integration with public search UI, build-time ingestion, version/locale routing and canonical document URLs. Validate keyboard behavior and deployment base paths.

Slate

Planned. Build a Slate/Middleman recipe for generated HTML ingestion and search UI. Preserve section anchors, language tabs, deployment base paths and keyboard behavior.

Language SDKs

Each client needs upload/URL ingestion, run waiting, cited search/chat, typed errors, retries that respect rate limits, cancellation and streaming with a nonstreaming fallback. Preserve server-side credentials, organization/workspace scope, usage metadata and executable examples. Validate a real indexed corpus before calling a package supported.

Python SDK

Planned. Typed sync/async client, upload, wait, search, chat and streaming fallback; wheel/sdist packaging. Distribution target: PyPI. Account setup.

Rust SDK

Planned. Typed async client, streaming/multipart upload, cancellation and error enums; Cargo/crates.io release. Distribution target: crates.io. Account setup.

Go / Golang SDK

Planned. Context cancellation, io.Reader uploads, typed errors and streaming fallback; tagged Go module. Distribution target: Go modules. Account setup.

Elixir SDK

Planned. OTP-friendly HTTP client, tagged errors, uploads and run watching; Hex package and ExDoc. Distribution target: Hex. Account setup.

.NET / C# SDK

Planned. Async client with CancellationToken, streaming upload and typed results; NuGet package. Distribution target: NuGet. Account setup.

Java / Kotlin · JDK SDK

Planned. JDK HTTP client, typed models, futures/streaming and Kotlin usage; Maven Central namespace/release. Distribution target: Maven Central. Account setup.

Smalltalk SDK

Planned. Pharo-first HTTP/JSON client, stream uploads, errors and a Metacello baseline; assess other dialects explicitly. Distribution target: Metacello / source. Account setup.

Modern C++ SDK

Planned. C++20 client, cancellation/streaming, typed errors and CMake exports; Conan/vcpkg distribution recipes. Distribution target: CMake · Conan / vcpkg. Account setup.

PHP SDK

Planned. Reusable Composer client beyond the WordPress proxy; PSR-compatible HTTP, upload and typed responses. Distribution target: Packagist. Account setup.

Ruby SDK

Planned. Gem with streaming uploads, run waiting, cited search and errors; Rails/server examples. Distribution target: RubyGems. Account setup.

Registry account setup

These links are for maintainers preparing distribution; consuming public packages or calling DocSlurp HTTP does not require publisher registration. No accounts are created by this guide.

Package names, namespace ownership, release CI and registry metadata are part of each SDK’s delivery work. Follow the repository’s release policy rather than publishing from a copied integration prompt.

Jump to