We have the experience your team expects.
Organic’s architecture and workflows grant autonomy to client engineers and contributors while preserving the stability of site’s content and user experience.
External engineers receive access to site-specific repositories in order to make business-specific frontend and backend changes, such as special blocks, widgets and custom promotional touts. With Organic‘s architecture, site-specific changes can be released in accordance with each client’s specific timelines and approval processes.
Any domain fully integrated with Organic (including the headless backend and DevOps management) has a site-specific Github repository for backend and frontend development. In addition, enterprise clients may have access to an additional backend plugin repository that impacts more than one domain across their business (commonly referred to as an “organization” repository).
Requests for changes to the core Organic CMS codebase (the organic-content repository) may be submitted to Organic for review and approval. It is recommended that contributors propose these changes to Organic before beginning development work to obtain preliminary concept approval.