Skip to content
Pume
Back to Lab

Editorial integration · Communication

Making an editorial integration understandable

Integration assessment

Different source platforms needed a clear route into an existing publishing flow. I brought together examples and maintainer knowledge to explain the input requirements, routing and publication choices, including where configuration ended and new integration work began.

Make the choices understandable

  1. Source platformContent and export examples
  2. Shared intake contractIdentifiers, assets and update rules
  3. Publication choiceReviewable draft or configured publication
A generic view of an existing integration. Assessment and documentation were the focus of this work.

An existing editorial intake route could receive content from different source platforms. Before presenting it more broadly, teams needed to understand what it accepted, what depended on publication configuration and which integrations still needed work.

I gathered material with colleagues, supplied export examples and assessed how the flow could be explained. The guidance distinguished source requirements and onboarding choices from the more detailed maintainer reference.

The resulting notes and diagrams described input contracts, import stages, routing and the distinction between editable drafts and configured automatic publication. I corrected drafts that made a proposal sound approved or included integrations that had not yet been worked out.

This was assessment and documentation of an existing platform. It made its choices and dependencies clearer, without claiming that every proposed source had been onboarded.