Integrations

An integration should have a specific purpose: improve publishing, reader access, distribution, measurement or editorial operations. Do not connect a service solely because it is available.

Scope before configuring

Document the owner, reader impact, data involved, publication surfaces and expected failure behaviour. Include editorial stakeholders early when an integration changes how an article appears, travels or is measured. Confirm that terms, permissions and privacy expectations are appropriate for the publisher.

Test the real path

Use a non-critical example to test the complete reader-facing result: a story is created, published, represented in the connected service and, where applicable, updated or withdrawn. Check mobile presentation and handover behaviour as well as a successful first delivery.

Operate and review

Keep a named owner for configuration and a contact route for editors when something looks wrong. Review integrations after major WordPress, template or service changes. Avoid recording secret values in editorial documentation or screenshots.