LLMpediaThe first transparent, open encyclopedia generated by LLMs

XWiki

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: Atlassian Confluence Hop 4
Expansion Funnel Raw 85 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted85
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
XWiki
XWiki
XWiki Community · Public domain · source
NameXWiki
DeveloperXWiki SAS
Released2004
Programming languageJava
Operating systemCross-platform
LicenseLGPL

XWiki is an open-source, Java-based enterprise wiki and content management platform designed for collaborative documentation, knowledge management, and intranet development. It integrates a WYSIWYG editor, scripting, and extensions to support structured data, workflow, and application building for organizations ranging from small teams to large enterprises. The platform evolved through contributions from independent developers, corporate sponsors, and academic projects, positioning itself among other collaborative systems and content platforms.

History

The project began in the early 2000s amid a surge of interest in collaborative software alongside MediaWiki, Confluence (software), Tiki Wiki, DokuWiki, and TWiki. Early development overlapped with efforts by contributors associated with institutions such as University of Lorraine and companies like Sun Microsystems, with funding models resembling those used by Apache Software Foundation projects and commercial entities including Atlassian. Over the 2000s and 2010s the codebase incorporated ideas from Hibernate, Spring Framework, Lucene, and Maven to improve persistence, dependency injection, search, and build management. Community governance drew patterns from Free Software Foundation-aligned projects while commercial support mirrored offerings by Red Hat and Microsoft for enterprise adoption.

Features

XWiki provides collaborative editing comparable to Google Docs, with version control and branching similar to systems such as Git and Subversion. It supports rich-text editing with an experience akin to CKEditor or TinyMCE, and offers structured data handling influenced by concepts in Semantic Web initiatives like Wikidata and RDF. Search uses full-text engines related to Apache Lucene and Elasticsearch, and authentication integrates protocols used by OAuth, SAML, and LDAP directories such as OpenLDAP and Active Directory. Extensible scripting leverages languages with precedents in Groovy, JavaScript, and Python frameworks, allowing automation and macros similar to Jenkins pipelines or Ansible playbooks. Security and access control align with role-based models popularized by UNIX and enterprise products from Oracle and IBM.

Architecture

The platform is built on a component model influenced by OSGi modularity patterns and dependency architectures like Spring Framework. Persistence layers use paradigms from Hibernate ORM and relational databases including PostgreSQL, MySQL, and Oracle Database. Search and indexing reflect designs from Apache Lucene and Elasticsearch. Frontend technologies share lineage with HTML5, AJAX, and libraries such as jQuery and Bootstrap. Packaging and continuous integration practices follow models used by Maven, Gradle, Jenkins, and Travis CI, while deployment architectures often mirror containerization and orchestration patterns championed by Docker and Kubernetes.

Installation and Deployment

Deployment can target environments similar to those used by Apache Tomcat, Jetty, and WildFly application servers. Installers and packages are comparable to distributions offered by Debian, Ubuntu, and Red Hat Enterprise Linux ecosystems. Cloud deployments reflect practices used on Amazon Web Services, Microsoft Azure, and Google Cloud Platform, with backup and scaling strategies akin to patterns from HAProxy and NGINX reverse proxies. Administrators use concepts overlapping with Systemd, Ansible, and Puppet for service management, automation, and configuration.

Extensions and Ecosystem

An extensions model supports plugins and applications similar to ecosystems maintained by Eclipse, WordPress, and Jenkins. Integrations exist for third-party systems such as JIRA (software), GitHub, GitLab, Slack, and Microsoft Teams, enabling workflows comparable to those in Atlassian Confluence and SharePoint. The marketplace and community contributions reflect dynamics found in npm, Maven Central, and CPAN, while commercial support options parallel offerings from Red Hat-like vendors and boutique consulting firms. Documentation practices echo standards promoted by DocBook and OpenDocument ecosystems.

Use Cases and Adoption

Organizations deploy the platform for intranets, knowledge bases, product documentation, and project collaboration akin to use cases seen with Confluence (software), SharePoint, and MediaWiki. Sectors adopting the software include technology companies, research institutions such as CNRS, government agencies resembling deployments by European Commission bodies, and educational institutions like École Polytechnique and Massachusetts Institute of Technology for internal documentation and course materials. Case studies parallel implementations by enterprises using Atlassian stacks, GitLab-centric development, and DevOps practices integrating with CI/CD pipelines.

Category:Free software