Adopt pattern for custom overrides on non-staged sites
While some sites will be managed through staging, and thus will require a higher level of developer access, our most basic model is: we have a fully hosted solution that locks down most configuration options and modules and instead exposes just a small subset of configuration for management on the site.
One possible model is outlined in the blog post Dynamically override a configuration with Drupal 8. This approach involves:
- Expose specific configuration options via custom forms and save them to custom settings.
- Use the dynamic configuration override system to layer on these overrides.