Concerns: pushword/api
This release extracts the REST API into a dedicated PushwordApiBundle and the editorial workflow into a PushwordPageWorkflowBundle. Register both in config/bundles.php:
Pushword\Api\PushwordApiBundle::class => ['all' => true],
Pushword\PageWorkflow\PushwordPageWorkflowBundle::class => ['all' => true],
Add the API and page-workflow route resources to config/routes.yaml:
pushword_api:
resource: "@PushwordApiBundle/ApiRoutes.yaml"
pushword_page_workflow:
resource: "@PushwordPageWorkflowBundle/PageWorkflowRoutes.yaml"
The single pushword_api import registers every API endpoint — including those contributed by optional bundles (conversation, flat, snippet, page-workflow). Those bundles no longer need their own API route import, and when pushword/api is not installed none of those routes (or their controllers) are loaded. pushword_page_workflow above is only for page-workflow's non-API (editorial) routes.