Teams, Events, and Layout Controls for Real Church Workflows
This update is about making the parts of a church website that staff touch every week feel less fragile: team pages, event feeds, resource archives, service planning, and the small frontend details visitors notice immediately.
The work since version 5.6.9 has not been one single giant feature. It has been a steady set of improvements that make Digital Church easier to run without turning every change into a developer ticket.
Teams Get a Cleaner Native Editor
What changed: Teams now have a native Gutenberg-style editor shell under the title, using the shared Digital Church tab pattern. Team details, files, and positions moved into a focused editing interface while SEO controls keep their existing behavior.
Why it matters: Church team pages often carry more than a name and photo. Staff may need positions, files, biographies, ministry roles, and planning context in one place.
The new Teams editor gives those details clearer homes. Positions are no longer a flat afterthought; they now have a list-first planning view and per-position assignment details, which makes team organization easier to understand before it becomes a public page.
Events Become Better at Pointing People to the Right Place
What changed: Imported event feeds can now capture the first event URL from an ICS description, use it as the single-event action button, and optionally redirect imported event posts to that source URL. Plain-text links in imported descriptions are converted into clickable links during import.
Why it matters: Many churches already maintain calendars in Google Calendar, Planning Center, or another source. When those calendars feed the website, the imported event should not trap visitors on a thin local page if the real registration or information page lives somewhere else.
This update lets imported events carry people to the best next step while still keeping the church website calendar current. It also reduces the cleanup work staff used to face when feed descriptions included raw URLs instead of readable links.
Guides and Resources Respect Real Content Hierarchies
What changed: Guide Collections and Resource Categories now preserve nested hierarchy during drag ordering. Guides sidebar navigation renders child Collections under their parents, and Resources archive tabs, child pills, and default-tab settings follow the saved category order.
Why it matters: Church content rarely stays flat for long. A discipleship guide, volunteer resource library, or ministry help center needs parent categories, child collections, and a visible order that makes sense to a reader.
These updates keep ordering tools from flattening carefully organized content. Editors can arrange siblings without accidentally breaking the structure around them, and visitors see navigation that matches how the material is actually grouped.
Services Gain a Real Order Planning Workflow
What changed: The Services editor Order tab now includes a sortable service order planner for songs, scriptures, prayers, announcements, offerings, communion, messages, and custom elements. Each element can store a leader from People, notes, and media-library attachments.
Why it matters: A service plan is not just a title and a start time. It is a sequence of ministry moments with people, files, notes, and responsibilities attached.
Moving service order planning into structured post meta gives churches a better place to prepare the details that support Sunday. Worship, preaching, media, and administrative teams can work from the same organized plan instead of scattering the information across documents and messages.
Archives and Frontend Details Feel More Consistent
What changed: Digital Church added a reusable compact archive pagination component and started rolling it across Stories, Emails, Sermon Series, sermon taxonomies, Ministries, Campaigns, Groups, Teams, Locations, and Resources. The same update cycle improved announcement bars, auth modals, event color precedence, toolbar shortcuts, and post-content background controls.
Why it matters: Visitors should not have to relearn the interface from one archive to the next. Staff should not need separate styling workarounds every time a content type gets a new listing page.
The shared pagination pattern gives archives the same previous/next controls, editable page number, total page count, result label, and per-page selector. The surrounding polish makes common frontend moments look more intentional: announcement bars use space better, auth modals align more reliably, event dots inherit better color rules, and post layouts can pick up site-level design choices.
What This Means for Churches
This release cycle is about practical control. Teams can manage staff pages with better structure. Event feeds can point visitors to the right next step. Guides and Resources can stay organized as libraries grow. Services can carry real planning details instead of living in disconnected notes.
That is the direction Digital Church should keep moving: make the common ministry workflow clearer, keep risky settings harder to misconfigure, and give church teams tools that live where the work already happens.
If your church wants to clean up team pages, improve imported event links, organize a resource library, or plan services with richer structure, reach out. We can help turn on the right pieces and fit them to the way your team already works.