WiKiss

WiKiss is a lightweight, PHP‑based wiki engine that emphasizes simplicity and rapid deployment. Built as a fork of the long‑abandoned TigerWiki, it keeps the core features expected from a modern wiki—markup parsing, revision history, password protection, automatic table of contents, and XHTML 1.0 Transitional output—while stripping away unnecessary complexity. The result is a self‑contained application that requires only a web server with PHP support and a writable directory, making it an attractive choice for developers who need a quick knowledge base without the overhead of a full CMS.

Technical Stack & Architecture

• Language: PHP 5.x/7.x (the codebase is written in plain procedural PHP with a few object‑oriented helpers).
• Frameworks: None; WiKiss ships as a single monolithic PHP application that can be dropped into any directory.
• Database: Optional. By default it uses the file system for storage (plain text files with a simple revision log). An SQLite driver is available, and developers can extend it to use MySQL or PostgreSQL via the provided plugin hooks.
• Templating: The engine uses a minimal templating layer based on PHP include statements. Themes are simply collections of CSS and optional header/footer templates, allowing developers to override the default look without touching core code.
• Markup Engine: A custom lightweight parser that supports a subset of wiki syntax (headings, lists, links, tables). The parser is exposed as a function so that developers can reuse it in other projects or extend it with additional syntax elements.

Core Capabilities & APIs

• Revision Management: Every edit creates a new version file. The diff algorithm is built on PHP’s diff functions, producing side‑by‑side HTML diffs.
• Password Protection: Page‑level authentication via a simple .htpasswd‑style file. Developers can hook into the login flow to integrate with external authentication systems.
• Automatic Table of Contents: Generated on the fly by scanning heading tags; the TOC is inserted as a <div> that can be styled or positioned via CSS.
• Plugin System: A plugin interface allows developers to register callbacks for events such as onPageLoad, onPageSave, or onSearch. Existing plugins include RSS feed generation, table handling, and optional integration with external search indexes.
• Webhooks & RSS: The change log is exposed as an RSS feed; developers can subscribe or parse it programmatically. Custom webhooks can be added through plugins to notify external services on page updates.

Deployment & Infrastructure

• Self‑Hosting: No database setup is required for the default file‑based mode. The application can run on any LAMP stack, or even on a simple static hosting service that supports PHP.
• Scalability: For larger deployments, the SQLite or MySQL backends can be enabled. The architecture is stateless beyond the storage layer, making it trivial to scale horizontally behind a load balancer.
• Containerization: A Dockerfile is available in the repository, enabling quick spin‑up of a container with pre‑configured PHP and web server. Developers can also build their own images to match corporate security policies.

Integration & Extensibility

• Custom Themes: Replace the default CSS and template files to match corporate branding or integrate with existing front‑end frameworks.
• API Hooks: The plugin system exposes a small API surface that can be used to add custom REST endpoints, integrate with LDAP for authentication, or embed the wiki content into other applications.
• Webhooks: By listening to the onPageSave event, developers can trigger CI pipelines, update search indexes, or push changes to a Git repository.
• External Search: While the core search is simple full‑text, plugins can hook into Solr or ElasticSearch to provide advanced querying.

Developer Experience

• Configuration: A single config.php file holds all adjustable parameters (storage path, authentication settings, plugin list).
• Documentation: The README and inline comments provide a clear overview of the architecture. Additional wiki pages cover syntax, plugin development, and deployment tips.
• Community: Although the original project is no longer actively maintained, forks and community discussions on mailing lists provide a modest support network. The GPLv2 license allows unrestricted modification and redistribution, encouraging custom extensions.

Use Cases

1. Internal Knowledge Base – Small teams can host a quick wiki for documentation, SOPs, or project notes without installing a full CMS.
2. Documentation Hub for Open‑Source Projects – The file‑based storage makes it easy to version control the wiki content alongside source code.
3. Prototype or Demo Sites – Developers can spin up a temporary wiki to showcase documentation concepts during demos.
4. Embedded Documentation in Applications – By exposing the markup parser, developers can embed wiki‑style help pages directly into desktop or mobile apps.

Advantages Over Alternatives