Skip to main content
Core sitectl knows how to drive any stack — building, starting, stopping, deploying, and inspecting services, plus shared services like Traefik, MariaDB, and Solr. Application plugins add the commands and guided create flows for a specific application on top of that foundation: Drupal, Islandora, WordPress, OJS, Omeka, and ArchivesSpace. You install only the plugins for the apps you work with. A plugin is just a binary named sitectl-<app> on your $PATH — once it is there, sitectl <app> ... works and sitectl create <app> can scaffold a new stack. No configuration file is needed. 
# the OJS plugin binary on your PATH unlocks these
sitectl create ojs        # scaffold an OJS stack
sitectl ojs tool upgrade  # OJS-specific helpers
General lifecycle stays in the core CLI (sitectl compose, sitectl deploy, sitectl create), so every stack shares the same operational contract regardless of which application plugin is installed. See Plugins for how discovery, inclusion, and command routing work across all plugin types.

​
Choose your application

Drupal

Drupal-oriented workflows: drush execution, user login links, and database and config sync between environments.

Islandora

Islandora workflows: guided site creation, component management, Fedora and Blazegraph sync, and migration utilities. Includes the Drupal plugin.

WordPress

WordPress workflows: template creation, WP-CLI, Composer, plugin/theme maintenance, cache, and database helpers.

OJS

Open Journal Systems workflows: template creation, OJS PHP tools, PKP tools, scheduled tasks, jobs, and import/export helpers.

Omeka Classic

Omeka Classic workflows: template creation and REST API helpers for collection, item, file, tag, user, and metadata operations.

Omeka S

Omeka S workflows: template creation and REST API helpers for resources, media, sites, modules, and vocabularies.

ArchivesSpace

ArchivesSpace workflows: template creation, API helpers, search, job inspection, diagnostics, and container script wrappers.