Clarify Headless CMS Schema Updates for Content Devs

You're extending Strapi, Directus, or other headless CMS with custom fields, API endpoints, or webhooks. Ensure content editors understand how your code changes impact content structuring and input.

Try free → See pricing

The problem

Developers extending headless CMS platforms like Strapi or Directus with custom fields, content types, or API endpoints frequently struggle to explain these changes to content editors. A new field for an "author bio" or a modification to a "product gallery" component's data structure needs precise communication. Vague PRs lead to content editors misunderstanding new input options, mis-entering data, or confusion about API consumption, causing delays in content publishing and potential data integrity issues across multiple channels.

Manually crafting detailed PR descriptions that bridge the gap between backend schema changes and a content editor's workflow is a laborious task. Explaining how a change to a Directus collection's foreign key impacts related content, or what a new Strapi webhook means for content syndication, takes significant developer time. This overhead slows down critical content model updates and creates a communication bottleneck between engineering and editorial teams, hindering content velocity.

How Pullscribe solves it

Automatically generate PR descriptions explaining new CMS fields and API changes for content editors.

Ensure consistent documentation for changes affecting content structuring, input, and data consumption.

Accelerate deployment of new content models by reducing manual PR writing time.

Concrete example

  Pullscribe PR Summary for Headless CMS:

  - Adds new 'SEO Description' rich text field to 'Article' content type (Strapi).

  - Updates 'Product' collection to include 'SKU' field (Directus).

  - Refactors custom API endpoint for faster article retrieval.

  - Impact for Content Editors: New data entry options & improved content organization.

Ready to try Pullscribe?

Turn any GitHub diff into a reviewer-ready PR description in seconds.

Get started → See pricing

Frequently asked questions

Can Pullscribe explain new custom fields added to content types in Strapi or Directus?

Yes, Pullscribe analyzes your schema migrations and code diffs, translating them into clear explanations of new fields, their types, and their purpose. This helps content editors understand where and how to input new data.

How does it handle changes to existing content models or relationships?

Pullscribe will outline modifications to existing content types, such as changing a field type or updating a relationship between collections. It clarifies for content managers how these changes might affect their current content or data entry workflows.

Is Pullscribe useful for documenting custom API endpoints or webhook changes?

Absolutely. When you add or modify custom API endpoints or webhooks in your headless CMS, Pullscribe details their functionality, expected payloads, or trigger conditions. It ensures front-end developers consuming the API understand the updated data structures.