Kordiam

Kordiam is editorial planning software for newsrooms and content marketing teams. This plugin connects a Kordiam account to one or several WordPress sites and keeps the two in step: what the desk plans in Kordiam appears in WordPress, and what the site publishes shows up on the story lists in Kordiam. Two ways of working are supported.

• Planned content. A story is planned and given its meta-data in Kordiam. Kordiam creates the matching post in WordPress, and later changes on either side are synced.
• Breaking news. A story starts as a post in WordPress. The plugin sends the relevant data to Kordiam so the story lists stay complete.

The following is kept in sync:

• Slug and story description
• Publishing date and time
• Statuses, matched to WordPress post statuses you choose
• Categories, matched to WordPress categories or to a custom field
• Authors, matched by email address
• Links back and forth between the two systems
• Custom fields, both story-level and publication-level
• Tasks and their assignees
• Text, pictures, video and other files planned in Kordiam

Nothing is synced until you have said what maps to what. Every mapping has an explicit "do not import" option, and each of the ten settings screens is a plain two-column table: what Kordiam sends, and where it should go. The plugin works with both the block editor and the classic editor. In either one, a panel next to the post shows the story description and a link straight to the story in Kordiam. You need a Kordiam account to use this plugin. Teams of 15 or more users can request a free test account on the Kordiam website. Relationship to the Desk-Net plugin Desk-Net has been renamed Kordiam, and this plugin is the successor to the Desk-Net plugin. It is a separate plugin rather than an update, so nothing changes until you install it and switch over. When you activate Kordiam on a site that has Desk-Net data in its database, the settings, mappings and story links are copied across automatically. The Desk-Net data is copied, never moved or deleted, so deactivating Kordiam and going back to Desk-Net leaves you exactly where you were. Do not run both plugins at once. While the Desk-Net plugin is still active, Kordiam shows a notice and keeps its own sync switched off, so that a single story cannot be sent to Kordiam twice.

You need an active Kordiam account and its API credentials. Once you have an account, request the API credentials from support@kordiam.io.

1. Install the plugin through the Plugins screen in WordPress, or upload its folder to /wp-content/plugins/.
2. Activate it on the Plugins screen. If the older Desk-Net plugin is active, deactivate it first.
3. A "Kordiam" entry appears in the admin menu, below Posts.
4. Open it and work through the sub-pages to connect Kordiam to WordPress and set up the mappings.
5. We strongly recommend reading this support article before changing the settings.

1.0.1

• Fixed: publication times are converted with the offset valid on the publication date, so stories scheduled across a daylight saving change land on the right hour.
• Fixed: a story without a publication time is scheduled at 23:59 in the site's timezone, not in UTC.
• Fixed: times sent from WordPress to Kordiam are sent in UTC, so they no longer shift on every sync.
• Fixed: headlines and custom fields mapped to the post title are transferred in full. Only a story description used as the title is still shortened to 77 characters.
• Fixed: when Kordiam reports that it has no custom fields, statuses, categories or formats, the plugin forgets the lists cached from a previous organisation and resets the mappings pointing at them. Before, it kept sending them, and Kordiam refused every story, for example with "Custom fields don't exist for this organization".

1.0.0

• First release of the Kordiam plugin, the successor to the Desk-Net plugin.