WordPress support (future goal)

[nikosdion]

This is added here as a note on what we can do in the future.

Connector

We can definitely create a connector WordPress plugin using WordPress' JSON API.

Authentication is performed with Basic Authentication. You can use either the user's password, or (since WordPress 5.6) an Application Password. Wirdly enough, application passwords can be used with or without the spaces. That is to say, both Wuij 6UI8 DGHf 8sfl X5sd cU8Y and Wuij6UI8DGHf8sflX5sdcU8Y are acceptable.

The documentation of the existing API is a bit sketchy in places.

We can [create our own endpoints and routes](see https://developer.wordpress.org/rest-api/extending-the-rest-api/routes-and-endpoints/).

Challenges

Wording has to be chosen carefully to no longer imply it's Joomla! only.

In places where we need to list the CMS version we should check the cmsType configuration parameter (e.g. $site->getConfig()->get('cmsType', 'joomla')) which will be automatically set to wordpress when the site is detected to be of that type. We should display the appropriate CMS name and/or icon. This may lead to language string deprecation.

The current director and update tasks for Joomla! core and extensions must filter sites by CMS type so that they only apply to Joomla! sites.

All controller tasks for refreshing information, updating Joomla!, updating extensions, interacting with Admin Tools, and interacting with Akeeba Backup must check for the CMS type. We need to write their symmetric versions for WordPress.

All controller tasks and view templates offering integration with template overrides must be limited to Joomla! sites.