Index MediaWiki pages so long-standing internal documentation answers questions with citations, unified with chat, tickets and projects.
Representative data is enough. No production access required for the first demo.MediaWiki 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 MediaWiki account remains the system of record.
Page content and categories
Approved namespacesFind · Prepare · Act
Pair MediaWiki with Confluence, Bookstack, Wikipedia 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 wiki page
Bring one of these to the demo on representative data. Every answer arrives with citations that open the original MediaWiki record.
Every answer reflects the verified connector behaviour, never generalised.
Admin-approved namespaces and categories; Scheduled sync of pages; Citations to the exact page.
Talk and history pages; Writing back into MediaWiki; Namespaces outside scope.
Scheduled sync through the Linkence indexing pipeline. Scope: Admin-approved namespaces and categories.
The MediaWiki 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.