Exploring Content Approval Cycles in a Headless CMS Environment

[emran-alhaddad]

Hello Statamic Community!

Our team is embarking on a new project that involves adopting a headless CMS approach with a focus on content approval cycles. We're using Laravel Statamic as our CMS, which supports GraphQL.

Our goal is to implement an approval cycle for content publishing within the Statamic ecosystem. While Statamic is a fantastic CMS, it doesn't provide a built-in solution for content approval workflows.

We're interested in exploring how to achieve content approval cycles effectively and efficiently using Statamic or other compatible tools within the Laravel ecosystem. We believe this topic could greatly benefit the community, and your insights would be invaluable.

We're open to discussing various approaches, customizations, and integrations that can help us achieve our goal while maintaining the flexibility and ease of use that Statamic offers. If you have experience or ideas related to content approval workflows in a headless CMS context, we'd love to hear from you.

Our aim is to gather insights and potential solutions as we work towards implementing a content approval cycle by January 18th. Your input will contribute to our collective knowledge and help us create a more efficient and robust headless CMS system.

Thank you for being part of this discussion, and we look forward to your contributions!

Best regards,
Emran Alhaddad