And thanks to Payload’s code-based nature, this is only the beginning. Over time, Hope will add more and more functionality to its site, which will allow it to continue to provide ROI to the organization for years to come.

The organization consists of 8 “service lines” and hundreds of pages of content. Among the content models are Subsites, Forms, Housing, Locations, People, Redirects, and much more.

Hope Network has 8 distinct “service lines” which required their own content, navigation, color scheme, and more. And each service line is managed by entirely separate teams, which need to log into the CMS and only be allowed to edit their own service line’s content.

However, the Hope marketing team should be able to log in and control everything—across the entire site. From global content to a specific service line’s content, Hope needed a system of access control that could scale with their ever-expanding team’s needs.

Payload’s Access Control stood up to the task. Hope editors can log in and see only their own service line’s content, seamlessly. They are limited to control only their own site’s navigation, content, and more.

The trick to building an enterprise CMS is all about how much control to give editors. You want the site to remain branded and deliberate, but allow editors to author experiences that can be incredibly flexible in nature.

Give too much control and the site starts to look like a kaleidoscope. Too little, and you’ll have editors harping on the dev team to create more features.

The Hope site makes heavy use of Payload’s Blocks field to craft pages not on a template basis—rather, dynamically based on the layout and content that the page requires. The site features 21 distinct layout-building blocks, each of which are flexible and usable, yet bulletproof and impossible to uglify.