26-Jul-2026 — Create a walk photo album in-app, with vendor-neutral AI write-up #312

build 795 — commit 4f056d4

What's new

Walk admins can create a photo album for a walk from the walk view. One action builds the carousel album and CMS page, rewrites the walk description into a short past-tense report, then opens a focused album workflow so the walk report and photo upload are on the same screen. On phones, a collapsible report and a fixed bottom bar (Library, Camera, Save and return) keep the flow thumb-friendly. When photos are saved, AI can pick a strong group cover image from the album. If an album already exists for that walk, Edit album reopens the same workflow rather than the full site-edit tabset.

At a glance

How it works

1. Open the album from the walk

On a walk you lead or administer, use Create album (first time) or Edit album (when one already exists). The control sits with the other walk actions and opens the walk report plus photo upload.

On the walk page, content editors see Create album. The tooltip explains that it opens the walk report and photo upload.

2. Add photos

Drag and drop images, or use Photo library / Take photo on a phone. Photos stay on your site. While images are still uploading or unsaved, the editor shows how many are ready to save.

Add photos from your library or camera roll. Unsaved images are counted so you know when to save.

3. Save when you are done

Use Save to keep working, or Save changes and exit / Save and return to walk to finish and go back to the walk. You can return later with Edit album to add more photos.

While photos upload, progress is shown and Save stays disabled until the upload finishes. Unsaved images are counted so you know when to save.

4. Deleting an album page

If you delete the CMS page for an album, you get clear warnings first: whether the page is listed in photo indexes, and whether to keep or permanently delete the linked image list.

If you delete the album page, the site warns when the page is listed in photo indexes.

You can delete the page only, or delete the page and its linked album image list.

ci+release-notes: tolerate history rewrites when generating notes (#312)

What's new

After a force-push, release notes no longer fail the main build because the previous GitHub SHA is not on the new history. The job falls back to the latest commits instead of aborting with an invalid git range.

At a glance