Index Drupal wiki pages and documentation so teams get cited answers without digging through the CMS, unified with other knowledge sources.
Representative data is enough. No production access required for the first demo.Drupal Wiki connects through an admin-defined boundary. Each object type below lists what Linkence reads, the scope condition that applies and the limitation you should know about before the first sync. Your Drupal Wiki account remains the system of record.
Page content and taxonomy
Approved sectionsFind · Prepare · Act
Pair Drupal Wiki with Mediawiki, Web, Confluence and the answer stops being a search result. Evidence arrives from every connected system, and the next step waits for your approval.
A cited answer that opens the exact Drupal page
Bring one of these to the demo on representative data. Every answer arrives with citations that open the original Drupal Wiki record.
Every answer reflects the verified connector behaviour, never generalised.
Admin-approved content types and sections; Scheduled sync of pages; Citations to the exact page.
Draft revisions; Writing back into Drupal; Sections outside the approved scope.
Scheduled sync through the Linkence indexing pipeline. Scope: Admin-approved content types and sections.
The Drupal Wiki connector is read-focused. Writes happen through connected companions, for example a grounded reply in mail or an approved update in chat, always with approval.
We will show how Linkence finds the relevant context, presents the work and keeps every sensitive change under your team's control.
Representative data is enough for the first demo. No production access required.