-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Fleet for OpenStation turns one OpenStation install into a working desktop for every WordPress site an agency manages. The project README explains the problem Fleet solves and what the experience feels like. This wiki holds setup instructions, operating guides, technical details, and contributor documentation.
- Getting started walks through installing Fleet, connecting the first site, reconnecting, and disconnecting.
- Managing sites explains the fleet-wide Inbox, Search, client Workspaces, dedicated site windows, and Explorer.
- Current scope documents what the preview manages today and what remains outside Fleet.
- Security documents permissions, encrypted Application Password storage, request boundaries, and revocation.
- Troubleshooting covers login prompts, connection, installation, API, and disconnection failures.
- Architecture explains hub and managed-site roles, Core approval, automatic OpenStation installation, and remote requests.
- Development covers repository layout, tests, packaging, and the two-site acceptance pass.
Fleet is an experimental feature plugin whose user experience may graduate into OpenStation core after real-world validation. It works today without modifying OpenStation.
The product stays WordPress-native. There is no hosted Fleet service, target-site Fleet agent, custom database table, or replacement permission system. WordPress Core supplies connection approval, credentials, HTTP safety, plugin installation, REST controllers, and capability enforcement. OpenStation supplies the hub's desktop window and is installed automatically on managed sites.