Request a Content Sync

Non-technical users can request a content sync through Linear without running any commands.

Steps

1. Create a Linear ticket in the Product team using the “Strapi content sync” template
2. Fill out the required fields:
   • Slug of the content to sync (double-check it matches the Strapi entry exactly)
   • Changes summary — describe what changed in as much detail as possible
3. Review the created ticket and move the status to Refined
4. The request is automatically forwarded on Slack to the relevant team:
   • #product-team-growth for signups
   • #product-team-platform for claims, cancellations, adjustments, and policy details pages
5. After a couple of minutes, the ticket status changes to In Review — the relevant team has been requested to review on GitHub
6. Follow the Linear ticket for status updates: In Review -> On Staging -> In Production

Caution

Providing details of what you have built or changed is essential. Sometimes a seemingly small change will require development effort to ensure compatibility with the broader system.

Important notes

• Always create a fresh issue from scratch using the template. Do not duplicate existing tickets.
• To sync quote screen changes, re-sync the corresponding questionnaire.
• Syncing vertical changes is not possible via this automation. Use the #birdhouse Slack channel or create a Triage product ticket instead.
• A seemingly small change may require development effort (e.g., adding or removing a question requires backend schema updates).

Note

Have feedback, questions, or ideas about the sync process? Reach out in the #birdhouse Slack channel.

See also

• Sync a Questionnaire – run a questionnaire sync manually
• Sync Verticals – run a vertical sync manually
• Syncing & Previewing – full tutorial on the preview-to-sync workflow