You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Editing lesson content inside a plan is too hard to discover and too hard to use. On a live support call (2026-08-05) a church couldn't figure out how to remove text from a loaded Ark lesson — and even experienced users struggle. The current flow requires knowing a chain of hidden steps:
Click a section row to open a dialog, then find Expand to Actions
Delete action rows one at a time via pencil → Delete → confirm
Know that text inside an action can't be edited at all — and that adding text means + → Item (also hidden)
None of this is guessable. Every step was a support call waiting to happen.
Request: redesign the lesson editing experience around three principles
1. Make content types visually obvious. In the service order, a volunteer-facing script line and a slide/media item should look clearly different (e.g., text lines rendered as editable text; slides as thumbnails). Today everything is a uniform row and users can't tell what will display on screen vs. what will print as instructions.
2. Super simple script editing. Click any text line to edit it in place — change wording, delete the line, or add a new line right where the cursor is. No Customize step, no Expand to Actions, no dialogs. Provider content gets a local override (original preserved upstream; "restore original" available). Editing should feel like editing a document, not managing database rows.
3. Edits apply everywhere. Whatever the plan shows is what the volunteer app shows and what every print format prints (see #979 — lesson print formats currently ignore plan edits entirely).
The problem
Editing lesson content inside a plan is too hard to discover and too hard to use. On a live support call (2026-08-05) a church couldn't figure out how to remove text from a loaded Ark lesson — and even experienced users struggle. The current flow requires knowing a chain of hidden steps:
None of this is guessable. Every step was a support call waiting to happen.
Request: redesign the lesson editing experience around three principles
1. Make content types visually obvious. In the service order, a volunteer-facing script line and a slide/media item should look clearly different (e.g., text lines rendered as editable text; slides as thumbnails). Today everything is a uniform row and users can't tell what will display on screen vs. what will print as instructions.
2. Super simple script editing. Click any text line to edit it in place — change wording, delete the line, or add a new line right where the cursor is. No Customize step, no Expand to Actions, no dialogs. Provider content gets a local override (original preserved upstream; "restore original" available). Editing should feel like editing a document, not managing database rows.
3. Edits apply everywhere. Whatever the plan shows is what the volunteer app shows and what every print format prints (see #979 — lesson print formats currently ignore plan edits entirely).
What already exists to build on
textOverridecolumn keeps overrides local to DoingApiRelated