WordPress adapter

Coming soon, shipping in Inka's core. Follow progress in pull request #371.

The same Inka editor works over WordPress, unchanged: the site chooses the adapter, and the editor never needs to know which CMS it is talking to. It passes all 98 contract tests, run against a real WordPress.

An adapter is a plugin installed in Inka, not in the CMS. It carries:

• reading and writing each page's blocks, held as JSON in Inka's own format
• the CMS's other fields, so editors change them in the same place
• permissions, so each editor sees only what they may do
• the workflow steps open to that person, each with the dialog it needs
• the fields and operations the CMS can query, so listings and dashboards offer exactly what it supports

Workflow, users, scheduling and translation stay the CMS's job. Inka presents them in the same editing screen.

Adapters are honest about what they support. A capability an adapter doesn't advertise is refused, not half-done, and one test suite checks every adapter against the same contract.