productivityContext + MediaWiki
Transform your MediaWiki knowledge base into a connected enterprise knowledge graph spanning every tool in your organization
OVERVIEW
MediaWiki is the most battle-tested wiki platform in existence, powering Wikipedia and thousands of enterprise, government, and academic installations worldwide. Its extensibility, structured data capabilities through Semantic MediaWiki, and proven scalability to millions of pages make it the platform of choice for organizations that need a robust, self-hosted knowledge base capable of handling complex taxonomies and large content volumes. Government agencies, defense contractors, research institutions, and large enterprises rely on MediaWiki installations to document everything from standard operating procedures and technical specifications to regulatory compliance frameworks and institutional history.
Despite its power, MediaWiki's native search capabilities are limited to full-text keyword matching within the wiki itself. For organizations where critical knowledge spans multiple systems -- project management in Redmine, code in GitLab, communications in Mattermost, and documentation in MediaWiki -- searching within a single tool only reveals a fraction of the relevant context. Talk page discussions that shaped article content, category structures that encode organizational taxonomies, and revision histories that document the evolution of policies are all rich sources of knowledge that remain disconnected from the broader organizational context.
Context connects to your MediaWiki instance and builds a comprehensive knowledge graph from articles, talk pages, categories, templates, and revision histories. Every article edit, talk page discussion, and category assignment becomes a node in your enterprise knowledge graph, linked to related content in your other tools. When a compliance officer asks "what is our current policy on data retention for classified materials?", Context surfaces the MediaWiki article documenting the policy, the talk page discussion where the policy was last revised, the Redmine issue that initiated the review, and the Mattermost thread where the legal team provided guidance. All of this runs entirely on your infrastructure with zero data exfiltration.
KEY CAPABILITIES
Key Capabilities
- 01Article and content indexing -- extract and index all MediaWiki articles with full wikitext parsing, template expansion, and structured data from Semantic MediaWiki properties
- 02Talk page discussion extraction -- capture the deliberation process behind articles by indexing talk page threads and linking discussions to the content they shaped
- 03Category and taxonomy mapping -- understand your MediaWiki category hierarchy and use it to enhance knowledge graph relationships and search relevance
- 04Revision history analysis -- track article evolution over time, connecting edits to contributors and the organizational events that triggered content changes
- 05Template and infobox data extraction -- parse structured data from MediaWiki templates and infoboxes to enrich the knowledge graph with typed relationships
- 06Interwiki and cross-reference linking -- follow internal links, interwiki references, and external URLs to map relationships between MediaWiki content and other knowledge sources
USE CASES
Use Cases
Institutional Policy Knowledge Management
A government agency maintains thousands of policy documents in MediaWiki, with talk page discussions documenting the rationale behind policy decisions. Context indexes articles and talk pages together, linking policy content to the discussions that shaped it, the Redmine issues that initiated policy reviews, and the Mattermost conversations where stakeholders provided input. Policy analysts can trace the complete history of any policy decision across all organizational tools.
Technical Documentation Discovery
A defense contractor uses MediaWiki for technical documentation across multiple programs. Engineers working on a new program need to find relevant prior work documented in the wiki. Context's knowledge graph connects MediaWiki articles to related GitLab repositories, Jira issues, and Slack discussions, enabling engineers to discover not just the documentation but the full context of how and why systems were designed the way they were.
Regulatory Compliance Knowledge Base
An organization uses MediaWiki to document compliance requirements, audit procedures, and regulatory interpretations. Context links compliance articles to the Redmine issues tracking implementation, the GitLab merge requests implementing controls, and the evidence artifacts stored in Nextcloud. During audits, compliance teams can quickly assemble complete evidence packages by querying the knowledge graph.
Research Knowledge Synthesis
A research institution uses MediaWiki to document experimental methods, equipment specifications, and literature reviews. Context connects wiki articles to related discussions in team communication tools, data repositories, and project tracking systems. Researchers can ask questions like "what methods have been used for quantum error correction benchmarking?" and receive answers synthesized from wiki documentation, team discussions, and project records.
HOW IT WORKS
How It Works
DATA FLOW
SECURITY & COMPLIANCE
Security & Compliance
SOC 2 Type II
GDPR
HIPAA
ISO 27001DEPLOYMENT
Deployment Options
DEPLOYMENT ARCHITECTURE
FREQUENTLY ASKED QUESTIONS
Frequently Asked Questions
Does Context work with self-hosted MediaWiki in air-gapped environments?
Yes. Context deploys entirely on your infrastructure with no outbound network dependencies. The MediaWiki connector communicates with your MediaWiki instance over your internal network and uses the recent changes API for incremental updates. No data leaves your firewall.
What MediaWiki content does Context index?
Context indexes articles (main namespace), talk pages, categories, templates, user pages, and any custom namespaces you configure. For Semantic MediaWiki installations, Context also extracts structured property data. Revision histories are indexed to track content evolution. You can configure which namespaces to include or exclude.
Does Context support Semantic MediaWiki?
Yes. Context extracts structured data from Semantic MediaWiki properties, forms, and queries. This structured data enriches the knowledge graph with typed relationships -- for example, linking a system specification article to the component articles it references through semantic properties. This provides significantly richer search and discovery capabilities.
How does Context handle MediaWiki access controls?
Context respects MediaWiki's namespace-level and page-level access restrictions. When users query Context, results are filtered based on their MediaWiki group memberships and permissions. Restricted namespaces and protected pages are only visible to users with appropriate access levels.
Can Context handle large MediaWiki installations with hundreds of thousands of pages?
Yes. Context is designed for large-scale deployments. Initial sync processes pages in parallel with configurable concurrency limits. Incremental updates via the recent changes feed ensure new edits are indexed promptly. For very large installations, you can configure namespace and category filters to prioritize critical content and expand coverage over time.
Does Context parse MediaWiki templates and transclusions?
Yes. Context expands templates and transclusions during indexing to ensure that the full rendered content of each page is captured in the knowledge graph. This includes infobox data, navigation templates, and any dynamically included content. Template parameters are also extracted as structured data when possible.
SETUP OVERVIEW
Setup Overview
Install the Context MediaWiki connector using Helm or deploy it on bare metal. Create a MediaWiki bot account with read access to the namespaces you want to index. Configure the connector with your MediaWiki instance URL and bot credentials. For air-gapped deployments, provide internal CA certificates if needed. Context will perform an initial sync and then poll for updates via the recent changes feed. Instances with up to 100,000 pages are typically fully indexed within several hours.
RELATED INTEGRATIONS
Related Integrations
Confluence
Connect Context to Confluence to link documentation, design decisions, and team knowledge to every tool in your stack. Permission-aware indexing with on-premise deployment.
Wiki.js
Connect Wiki.js to Context and transform your self-hosted wiki pages, comments, and documentation into a searchable enterprise knowledge graph. Fully compatible with on-premise Wiki.js deployments in regulated environments.
Notion
Connect Notion workspaces to your on-premise knowledge graph. Context indexes pages, databases, and nested content structures to surface cross-tool relationships across your entire organization.
Redmine
Connect Redmine to Context and transform issues, wikis, project plans, and time-tracking data into a searchable enterprise knowledge graph. Fully compatible with self-hosted Redmine instances in government and defense environments.
SharePoint
Connect SharePoint to Context and cut through millions of documents across site collections and permission boundaries. Works with SharePoint Online, SharePoint Server on-premises, and hybrid deployments.
Ready to connect MediaWiki?
See Context + MediaWiki in action with a 30-minute technical walkthrough tailored to your environment.
BOOK A DEMO