Starting 🏀 🏀 🏀

The previous staff page build was hardcoded. Here are some takes on why this is causing friction / headwind:

• High Maintenance Overhead:
  Any time staff details change — such as new hires / fires, title, photo, bio...the page code must be manually updated.

• Technical Barrier:
  Only developers or technically proficient staff can make these changes. And then update the git / codebase as well. This creates a bottleneck and delays updates when non-technical staff need to manage content.

• Error Risk:
  Manual HTML edits increase the risk of introducing errors or breaking the layout. +++ The staff page is llooooooooong when hardcoded.

• Inefficient Workflow:
  Updates that should take minutes in a CMS require dev team involvement, pull requests, and deploys.

Why This Matters

The staff page is a frequently visited resource for both congregation members and internal staff. Delayed or inaccurate information is undesirable and easy enough to get right!

Goal

Move staff data management into the CRM (Rock RMS Content Channels), so non-technical staff can update information directly through the admin interface, reducing maintenance overhead and improving accuracy through time while freeing devs to remove technical debt. Said another way: Wouldn't it be nice if there was a staff Content Resource Managment System? 🏀 🏀 🏀