Change Log

Updates for blocks on sites that use the frontend design.

1. Image blocks now have position and transform controls. There's also a new transform origin control.

2. Two new hover effects which are similar but slightly different

• Straigten - turns a rotated block upright

• Tilt - turns the block by an angle, added to its Rotate value. Tilt also has a block instance level override for the Angle value. Fallback to the preset value when blank

3. A new motion control: Parallax

Blocks on sites that use the frontend design (ex: Adventist Review) can now move.

What you can do

• Hover effects: a block reacts when a visitor points at it. You can pick Lift up, Slide forward, Grow slightly, Dim, Image zoom, Soft shadow or Darker background.

• Hover a card, move its parts: a Box, Section, Container or Grid can play effects on the blocks inside it. For example, when a visitor points at an article card, its image zooms and its headline slides forward.

• Entrances: a block fades, slides or zooms in when the page loads, or when it scrolls into view.

• Stagger: repeated cards, such as a list of articles, come in one after another.

Where to find it

• Page editor: select a block and open the Motion tab. It works on Box, Section, Container, Grid, Simple Text, Image and Button. When you point at an effect, the block previews it.

• Site Appearance → Site preset → Motion: set the speed and strength of each effect once, and every block follows. You can also choose which effects authors can pick.

Good to know

• Keyboard users get the same effects as mouse users.

• Visitors who ask their device for less motion see the blocks without movement.

• Motion is switched on only for the frontend design.

A banner tells you when AWE is updated

When a new release of Web Engine deploys, while Web Engine is open, a blue banner shows at the top. It will display the message: “A new version is available”. Select Reload page to switch to the new version.

• Web Engine checks for a new version every few minutes, and when you return to the browser tab.

• If you have unsaved changes, Web Engine asks before it reloads, so you can save first.

• You cannot close the banner. An old version can fail to open the next screen, so reload when you can.

This replaces the broken screen or “failed to load” error that some of you saw right after a release.

Get prompted when leaving the screen and work is not saved.

When an author changes something and tries to leave before saving, the CMS now asks first. This applies to Articles, Persons, Site settings, Page settings, translations and all edit screens.

• Click a link (sidebar, breadcrumb, another menu item): the CMS shows “Leave without saving?”. Staying keeps the changes. Leaving the page (without saving) discards changes.

• Close or reload the browser tab: the browser shows its own warning.

• “New version available” banner: Reload asks first when there are unsaved changes.

• No question: when nothing changed, in the Logs search box, on the Login, Forgot password and Reset password screens, and in Event additional fields, which save automatically.

Known issue: a tab switch inside the pages screen does not ask yet. A fix is planned.

Entities can now share their events, and other entities can display those syndicated events on their websites. Nothing is copied, a shared event always links to the event owner's event page, and visitors register on the event owners website.

How to start:

1. Managers need the right to:

   1. configure Events settings (to share).

   2. the new "Syndicate" permission under Events (to pick other entities' events).

2. Share your events:

   1. go to Events > Settings > Sharing.

   2. turn on "Allow other entities to list this entity's events"

   3. choose your canonical event page (the page on your website that shows a single event),

   4. save.

   5. note: to keep a single event private, open it and tick "Do not share this event".

3. Pick events from others:

   1. go to Events > Discover.

   2. events from entities closest in the organization come first, and events in your language come first among equally close ones.

   3. click "Syndicate" on an event.

   4. event then appears in your Events list, marked "Syndicated from".

4. Show them on your website:

   1. the Event list block shows your own and your syndicated events together.

   2. tick "Leave out syndicated events" to show only your own.

   3. the Events feed and Events repeater blocks can show all shared events of one other entity. Choose it under "Events from".

On the DACH design, events from other entities show a small external-link icon, because they open the owner's website in a new tab.

Help: Help > Events > Share and syndicate events.

The File Manager now knows about every file the Web Engine stores, and shows you how much space they use.

All your files are in the File Manager: Images and documents used in articles, episodes, pages, people, courses and more now appear in the File Manager, with their real upload dates. Open a file and choose Usages to see exactly where it is used. A file that is still in use is protected from being deleted by accident.

Storage at the bottom of the File Manager: Under Images and Documents you now see how much storage your organization uses, with a bar and a warning when you get close to the limit. Open Details to see the space per folder, plus publication files, fonts, AI assistant knowledge bases and social media images.

Other stored files: Some files belong to one single record, for example a publication’s PDF, a site’s fonts or the files in a secure file list. They are not reusable, so they stay out of the File Manager lists. Click Other stored files at the bottom of the File Manager to see them, with what they are used for and where.

Limits per organization: Under File Manager > Settings, administrators can set the largest image and document size their organization may upload, and when the storage warning appears.

Faster, checked uploads: Files now upload straight to storage and are checked before they are saved, with a clear message if a file is too large or the wrong type. AVIF images are now accepted too.

Preview images for documents: A document can now have a preview image. Link lists and secure file lists can show it: turn on Show preview images in the block settings.

Tip: files added this way have no title yet. You can add a caption in the file’s details.

Form responses: search, filters and CSV export

The Responses tab of every form has new tools:

• Search finds a response by any answer, such as a name, an email or a word from a message.

• Filters narrow the list by language, by site, and by submission date.

• Columns let you choose which answers show in the table. Your choice is remembered per form.

• Export CSV (top right, on the Responses tab) downloads the responses as a spreadsheet file. Before the download, a short summary shows how many responses will be exported and which filters apply, and you can pick the columns. The file contains exactly what you see in the list, with times in your own time zone.

New in the CMS: the Pages manager

The Pages screens are now split in two. Managing pages and editing content each get the full screen.

PAGES MANAGER (open Pages on any Site)

• One table with every page of the Site: status, translations and last update.

• Search by name, title, slug or path.

• Filters with counts: Hidden, Scheduled, Members / password, No content, Missing translations, Outdated translations.

• Translation chips show each language: up to date, may be out of date, hidden or missing.

• Quick edit: change the title, slug, visibility, menus, sitemap, description and publish dates in the row.

• Drag a page to change the order or to make it a subpage.

CONTENT EDITOR

• The page tree is gone!! A tab strip shows the pages you opened.

• Press ⌘P (Mac) or Ctrl+P (Windows) to jump to any page, also while you edit.

• On a page's settings, click the page name in the breadcrumbs to switch to another page.

GOOD TO KNOW

• Save before you switch pages. The editor does not warn about unsaved changes yet (follow-up: awe#6498).

You can now check your pages for accessibility issues.

These are problems which make a page hard to use for people who are blind, have low vision, or use a screen reader. Each check gives a score from 0 to 100 and a list of what to fix.

Where to find it

• Whole site: open the site and select Accessibility. Then select Check whole site. It checks up to 200 pages, usually in a few minutes.

• One page: in the page editor, open the Accessibility tab in the sidebar. Then select Check this page. You can also open the page menu in the page tree and select Accessibility.

• Layouts: in the Layout editor, open the Accessibility tab. Then select Check this Layout. One fix there helps every page that uses the Layout.

• Block Presets and Page Presets: open the Accessibility tab in the preset editor. It checks the preset each time you open the tab and after each save.

What it checks

• Images with no alternative text

• Links, buttons and form fields with no name

• Link texts that do not say where the link goes

• Page title, H1, and headings that skip a level. (Ex. Page is an H1, next heading is H3.)

• Contrast of text colors

What you get

• A score and three sub-scores: Structure, Screen reader and Low vision

• A list of issues, with the biggest fix first. Jump to Block selects the Block to fix.

• History: give a check a label, for example "Before the redesign". Then use Compare on two checks to see what is fixed, what is new, and what is still there.

• A WCAG 2.2 / WCAG 2.1 switch

• AI suggestions for clearer link texts, headings, page titles and plain language. They show only when Enable AI web features is on. They never change your page.

Good to know

• Save first. The check reads the saved page, not the editor.

• It also checks pages behind a login or a password, and pages that are not published yet.

• The score helps you, but it does not prove that a page is accessible. It looks at parts of 5 of the 55 WCAG 2.2 criteria. A person must still check the site.

• On a design with no Design Preset (for example the Hope design), contrast shows under Needs review, and Low vision shows No score. This is expected.

• It does not check the keyboard, design code, or the Articles and Episodes that a dynamic page shows.

• To read results, you need the right to see pages. To check a whole site, you need the right to change site settings. To check a page, you need the right to edit pages.

• Full guides are in the CMS help: Check a whole site for accessibility, Check a page for accessibility and Check a Layout for accessibility.

At the site level (Settings/Advanced/Social Media, it is now possible to add an Instagram profile (Facebook support is coming). There are two ways to use this on the frontend:

1. Repeater: A Collection called Social Media Items is created, pulling data from the profile. The Collection Repeater block can use this data with all the advantages that block offers (design is handled by the designer).

2. Predefined social media blocks (Grid, Slideshow, Carousel, Wall) — ready to use out of the box, but with limited design flexibility.

Once a student has started a course, the course structure is locked to protect their progress.

You can no longer add, delete, disable or reorder lessons and slides (lesson order stays free in free-order courses). You also can no longer change a slide's type, add or remove questions, change answer options, or change the progression mode.

You can still edit all texts and content, grading and retry settings, and question points.

The following up dates have been made to the Content editor:

1. Copy and paste of an Accordion works

• Before, a pasted Accordion lost the content of its items.

• Now the pasted copy has all items and all their content.

• This applies to every block that contains an Accordion, such as a Box or a Grid around it.

• One Undo removes the whole paste.

2. Cleaner Structure tab

• Before, some rows showed a trash icon or a drag handle that did nothing, for example the content area inside an Accordion item.

• Now these rows have no trash icon and no drag handle.

• Normal blocks still show both. Delete and move work the same as before.

Saved pages do not change. Editors do not need to do anything.

Press ⌘K (Mac) or Ctrl+K (Windows) anywhere in the CMS to open the new entity switcher.

• Start typing to search by name, short name or code (e.g. "GC"), then press Enter.

• Before you type, your recent entities are at the top, so going back to where you just were is ⌘K → Enter.

• Back to default entity and Manage your entity are in the list too.

• The sidebar entity menu still works as before.

Bonus: short names and codes now work in every entity search field in the CMS, not just in the switcher.

The Accordion and AccordionItem blocks now render on the frontend design (apps/frontend).

What's new

• Accordion + AccordionItem render on frontend sites. You can mark items "open by default."

• "Open one at a time": a new checkbox on the Properties tab. When you open one item, the others close.

• Accordion look in the Design Preset (components.accordion): each preset and site controls its own accordion styling, so pages match without per-block tweaks.

• Block Presets keep their content: an accordion saved as a Block Preset now keeps its items when you place it.

• Breakpoint-hidden items: an item hidden at a breakpoint no longer breaks the spacing between the other items.

Good to know

• On frontend, the block's Spacing setting has no effect, so the editor hides it. The Design Preset controls the spacing.

Map block on the frontend design, with Map styling in Design Presets

The Map block now works on sites that use the frontend design. It has the same features as the Adventist Map.

What authors can do

• Add a Map block to a frontend-design page. It has location markers with popovers, pins from Forms and Brevo in all three marker styles, counters, Auto Tour, search, geolocate, zoom controls and ctrl-to-zoom.

• Show markers from a record source:

– the current record on a dynamic page (Article, Episode or Event), or

– a Collection of Articles, Episodes or Events (up to 250 records).

You no longer need a separate ArticleMap, EpisodeMap or EventLocationMap for new work.

What designers can do (Design Presets → Map tab)

• Set the Map colors in light and dark mode: pins, clusters, markers and popovers.

• Set a Basemap Style for light and dark mode (a Mapbox style URL). A style set on the block still takes priority.

• Pick a Marker Icon. The icon shows inside the marker pin.

Also in this release: Design Preset CSS safety

• Preset values with broken CSS are now refused on save and import. This includes comments, unclosed brackets or quotes, and font names with an apostrophe (for example O'Hara Sans). No existing live data was affected.

The Player block on the new frontend design has more styling options, and it can now play a video in a lightbox. You set most of the look once per site, in the Design Preset (Player tab). Every Player block on the site then uses it.

New in the Design Preset → Player:

• Custom play icon: pick one from the icon library, or upload your own SVG

• Play icon background: a colored circle behind the icon, with its own hover color

• Opacity for the icon and the circle, at rest and on hover

• Play icon size per screen size (mobile, tablet, desktop)

• Corner radius for the player

• Poster hover fade: you can now set how much the poster dims on hover. It was fixed at 50% before.

New on the Player block:

• "Lightbox" variant: the poster shows on the page. A click opens the video in a dialog, and it starts to play. Cookie consent still applies inside the dialog.

• The lightbox needs an uploaded poster image. A Player without one plays inline as before.

Good to know:

• This applies only to sites on the frontend design. The legacy designs (Adventist, Hope, DACH, Paul) do not change.

• Custom icons that you upload to a preset now show on public sites and in the icon pickers.

Events now allows one consent for all sensitive fields.

In an event's Extra fields → Sensitive data consent, organizers can now switch to a single consent checkbox that covers every sensitive question on the registration form (for example health questions), instead of one checkbox per question. The consent text is set once per event, with a default you can edit or translate. It is off by default, so existing events are unchanged.

New: merge duplicate persons.

When the same person exists twice (after WordPress or RSS imports, or with name variants such as "Max Mustermann" / "Max A. Mustermann"), open either person, go to Danger Zone → Merge with another person… and pick the duplicate.

A short wizard lets you choose which record stays, which values and bios to keep, and shows the final result before you confirm. Articles, episodes, shows, movies, events, sermons and roles move to the kept person automatically.

The merge cannot be undone, so check the review step carefully. Guide: Help → Persons → Merge two persons.

Updates to Design Presets

You can now save a Design Preset to a file and turn a file back into a preset. Use it to copy a look between entities, send a preset to a designer, or let Claude write one from a Figma file.

WHAT'S NEW IN THE BACKEND

• Export JSON: from a preset card's "⋯" menu (system presets too), the Details page header, or the new Export JSON tab in the editor.

• Import JSON: in the Design Presets header. Creates a new entity or site preset from a file (1 MB max).

• Replace from JSON: editor → Danger zone. Overwrites all content of an entity, site, or app preset. Name and description stay. The file must use the same system preset (generic or editorial).

• Checked before save: a bad file is refused, and every problem is listed with its place in the file. Warnings, such as low text contrast, do not block the import.

• Short files are fine: only colors and fonts are required. AWE fills in the rest from the system preset.

New: extended event information

Events can now carry seven extra kinds of information for the days the event is actually running. You'll find them as new sections on an event's General tab, under the existing contact section:

• Schedule items — the program, one entry per session

• Exhibitors — the organizations staffing stands

• Meal plan — what's served, per event day

• Restaurants — places to eat nearby

• Emergency contacts

• FAQ

• Translation and interpretation — which languages, where equipment is to be picked up

On the public site: these are seven separate blocks an author drops onto a page, the same way as any other block. Currently only the German (DACH) design renders them — the other designs have no renderer, so the blocks aren't available there.

• Rich text supports more media providers. Page Rich Text blocks and Article bodies can embed YouTube, Vimeo, Jetstream, Jetstream Live, and Cloudflare Stream video, plus SoundCloud and Jetstream audio. All other rich-text fields (newsletter, descriptions, etc.) keep the previous settings.

• The media dialog has a new provider picker. The editor picks a provider button, then enters the ID. A "Video URL" button lets them paste a watch/embed URL instead — the system detects the provider and fills the ID. An unrecognized URL now shows a clear error instead of doing nothing.

• Audio can now be inserted. The rich-text toolbar has an Audio option next to Video.

• Jetstream IDs are auto-corrected. A bare ID gets its jsv: / jsl: / jsa: prefix when the editor leaves the field. Pasting a jstre.am embed URL also works.

• New: link media from the Media Library. In page Rich Text blocks and Article bodies, the media dialog has a "Media library" source: pick a Video or an Episode (filter by Channel, then Show). The page always plays the record's current source — if someone later fixes the video on the record, every page that links it updates too. Note: public pages pick the change up after the cache refreshes, not instantly.

• Linked media fails silent, never broken. If a linked Video/Episode is deleted, disabled, or outside its video-on-demand window, the embed simply does not render — visitors never see a broken player. Early Access episodes DO play when embedded (by design, like a direct link).

• Show screens got the same picker. Trailer and Preview video on Shows use the new provider buttons + paste-URL flow. Stored data is unchanged; Preview video is still Cloudflare-only (existing policy).

• Cookie consent fixes. On the adventist and paul designs, Jetstream live/audio embeds were loading without consent — now properly gated. New providers are listed in the consent banner.

Known limits (expected behavior, not bugs):

• A library Episode used as audio plays only if it has a Jetstream audio link; plain MP3 files are not supported in rich text yet.

• RSS feeds show only the caption for library-linked media, not the player.

Updates to File Manager and page-editor

• Files can now open in the browser instead of downloading. Each document in the File Manager has a new setting: "Download" (default, nothing changed for existing files) or "Open in the browser". Set to "Open in the browser", a PDF opens in the tab and a video plays instead of downloading. Only safe file types can be switched (PDF, common video/audio, images) — other types always download.

• The File Manager action follows the setting. A file set to "Open in the browser" shows "Open" instead of "Download" in the asset menu and opens in a new tab. If someone reports "the Download button is gone" — it's now "Open" because of that file's setting.

• New "Copy path" action on assets. It copies a link that works in site content on every site (for example inside an HTML embed). Note for support: this path does not open anything inside the CMS itself, and if a file's content is replaced later, copied paths to the old file stop working.

• Videos as page backgrounds. In the page editor, Box, Container, Section and Grid blocks can now use a File Manager video as their background (Background → type "Video" → File Manager). Available on sites using the frontend and hope designs; other designs come later. The video must be set to "Open in the browser" — the editor shows a warning if it isn't, and after changing the setting the author must pick the video again. Background videos are muted, loop, and stay on their first frame for visitors with "reduce motion" enabled.

• Video playback fix. Videos served through our sites can now be scrubbed/seeked properly (this also makes them play in Safari).

Known limitation: after switching a file between "Download" and "Open in the browser", the old behavior can persist for a while on public sites because of CDN caching.

New: programme details in the TV schedule (weekly and daily)

Click any program in the weekly or daily schedule and a panel opens at the bottom of the page. It shows the picture, the show and episode name, the air time and length, a short description, a "Watch now" button and sharing buttons.

The schedule stays open behind the panel, so you can click from one program straight to the next.

See it in action:

Weekly Schedule

https://hopetv.de/tv-programm/diese-woche?broadcastId=6a952ea529f53aa67fdc346d

https://hopetv.de/tv-programm

1. Imported images land in the File Manager

Every image the import pulls in — featured image, body images, galleries — is now becomes a File Manager Asset with usage tracking, not an untracked blob. A re-run adopts blobs from earlier imports instead of duplicating them.

2. Import a date range by hand

Now possible to set From and To dates. Set either one and the run imports only posts published in that window. A ranged run ignores Import all and does not move the last-run marker, so you can re-import one period without disturbing the scheduled import.

Also fixed: the incremental sync now tracks the WordPress modified date. Edits made to already-imported posts are picked up.

3. Bylines become Person records

Three new field-mapping targets: Author person, Author person photo, Author person bio.

• The byline is stored as the Person's full name, exactly as WordPress has it. It is never split into first/last, so "Jane Doe and John Doe" stays one shared Person — a single source field cannot tell one author from two.

• Later imports reuse that Person: first by import ID, then by name within the entity.

• Photo and bio fill in only while empty. Edits made in AWE are never overwritten.

4. Subtitle mapping

New Subtitle target. WordPress has no subtitle field, so map a custom one (e.g. acf.sub_title). A blank value leaves the current subtitle unchanged. Deleting the field in WordPress does not wipe an editor's subtitle in AWE.

Additional: a non-string mapped value for title/abstract/body used to lose the whole post. It is now handled safely.

New XML field — the schedule file can now include an optional <abstract> for each program. Existing files keep working unchanged.

Broadcasts in the Backend — the abstract is stored on the broadcast, so you can also type or correct it by hand under Media library → channel → Schedule.

On the website — it shows in the program detail panel of the TV schedule, but only when that program has no matching Episode in the media library; if it has one, the Episode's own abstract is used.

Example XML schedule file

It is now possible to import content from netAdventist websites. The import pulls articles from a netAdventist site into an Web Engine site. The article images are saved to File Manager. Any linked files (PDFs, docs, audio, archives) are saved to the File manager and links get rewritten in the article, so nothing breaks once the old server is retired!

Dry-run mode lets you preview what would import, before the import is actually run.

The Rerun option only retrieves and updates what changed since last time.

• Build your form in the Forms module.

• Add a form block to the webpage (Web Module).

• Pick an existing form from the list.

• Save the changes.

• Form responses viewable in Form module.

Brevo attribute fields can now have text fields render a Country select widget or then just default to an input like before.

Brevo Category and Multichoice type fields are now supported. Category renders a Select, while Multichoice renders a Multiselect.

Advanced settings has a new layout. Instead of one long page of stacked sections, the advanced tab of a site now shows a sidebar where you pick the section you want. You can also link users directly to a specific section, which is handy in support replies.

Translations are clearer. The translations panel now distinguishes two kinds of site translations: translations generated from the source site, and linked separate sites. A switcher at the top toggles between the two views. When a linked site is set for a language, it replaces the source-based translation in the site's language switcher. Moved the linked site translations to their own view. Search bar also functions as filter for the existing, not just to add new ones.

Domains: Typos and invalid domains get rejected immediately with a clear validation error. Domain registration errors now show up properly in the site's domain error list.

Several major improvements have been made to Block Presets, making them faster to create and easier to manage.

Create presets directly from the editor — You can now turn any block (and everything inside it) into a preset directly from the block menu in the content editor. No more rebuilding presets from scratch.

Editable properties — Preset authors can now mark specific block properties as editable, so users filling in a preset only see and edit what is relevant to them — keeping things simple and focused.

Live preset preview — Block presets now have a live preview, so you can see exactly how a preset will look before using it on a page. (Frontend design)

Reusable, entity-scoped Forms

• Forms are now their own thing, managed in a dedicated Forms section — build a form once and reuse it across any site in the same entity.

• The Form Block has two modes: manual (drop fields directly on a page, as before) or picker (reference a saved Form). Picker mode is available on designs that opt in (adventist, hope).

monday.com integration

• Connect one or more monday.com accounts per entity via OAuth (Forms → Settings). Each connection is locked to a single monday workspace.

• Any picker-mode form can push its submissions straight onto a monday board as new items.

• Map form fields to board columns visually (by column, not by name — so renaming a column in monday won't break anything). You can also import a board's columns to auto-generate matching form fields.

• Pushes are best-effort: a submission always saves even if monday is down, and the admin view shows each response as synced / partial / failed so nothing gets silently lost.

We're rolling out a new AI assistant in the CMS that helps authors create and improve pages much faster. Here's what you need to know:

What it does:

• Generate a page from a description: The author answers a few short questions ("what's this page for, who's it for, what's the main call to action?") and the AI drafts a complete, well-structured page for them — headline, sections, columns, and real written copy — ready to edit.

• Improve an existing page by chatting: Inside the page editor, the author can open a chat and ask for changes in plain words — e.g. "make the top section punchier" or "add a testimonials section before the button." The changes appear right in the editor.

What stays in the author's control:

• The AI produces a draft/starting point — nothing goes live automatically. The author reviews, edits, and publishes through the normal flow.

• When improving a page, the AI won't rewrite the author's own text or remove their images by default — it only reworks layout/structure unless the author explicitly asks it to touch the wording.

• Every change can be undone in the editor, just like any manual edit.

Good to know / current limits:

• Only supported on the "frontend" design. This will be the primary design, where we plan to migrate to other designs, and "training" the AI on the other designs will take too much time and effort.

• The AI writes copy and builds structure, but doesn't add the actual images — it leaves clearly marked image spots for the author to fill in.

• It's a helper, not a replacement for a human eye — authors should review the draft before publishing.

Most likely question: "Why don't I see the AI option?"

This almost always means AI isn't switched on for that customer's account yet — usually one of:

• The website's design is not supported.

• AI isn't enabled for their entity, or no AI provider is set up for them.

• Their user doesn't have the AI permission.

(If a customer expects it and doesn't see it, check those first before treating it as a bug.)

You can now create brand-new images from a text description and edit existing ones directly inside the File Manager — no external tools needed.

Generate a new image — When selecting an image, a new "AI Generated" tab is available in the picker. Enter a text prompt, choose a style, aspect ratio, and quality, optionally add a reference image, and select how many variations to generate. Results appear in a gallery so you can compare and pick the best one. A caption can be written manually or suggested automatically from your prompt.

Edit an existing image — Open any image's quick view and use the AI editing options: Reframe to change the aspect ratio, Remove background, or Modify with AI to describe a change and get a new version. Every edit is saved as a separate version, so you can always roll back to the original.

AI-generated images are stored as normal File Manager assets — searchable, reusable, and versioned — and are marked with a ✨ badge on the thumbnail.

Please note: This feature is disabled by default and must be enabled by an admin in Entity Settings → AI Image Settings. A provider (Google Gemini, Ideogram, or OpenAI) with a valid API key is required. Costs are charged to the customer's own provider account per image generated. Note that OpenAI may refuse prompts containing religious terms such as "Bible", "Jesus", or "Christianity" — switching to Google Gemini or Ideogram is recommended in those cases.

Managing frontend user approvals is now faster and easier. Users who are pending approval are now listed in a separate "Waiting on approval" tab, making them easy to find without searching through the full user list. Administrators can approve users directly from the list with a single click — no need to open each user's detail page. A new Pending Approval block is also available to add to the pending approval page, so users are clearly informed of their status while waiting.

Course editors can now close enrollment for a course without hiding it from the website. This is useful in two situations: when a course is still being prepared but should already be visible, or when a course should no longer accept new students while allowing already-enrolled students to continue.

When enrollment is set to Closed, the "Start Course" button is removed from the course detail page. Courses with closed enrollment are also visually indicated in the courses list with a lock icon.

A new Organization field is now available in the Hope design registration form. When signing up, users can select their origin organization by choosing their Division, Union, and Conference in order. This information is saved to their profile and can be viewed and updated later in the Profile tab of their account.

A brand new File Manager is now available in Web Engine, giving every organization a central place to store, organize, and reuse all their images and documents.

Asset library — All images and documents are now stored in one browsable, searchable library per organization. No more re-uploading the same logo or PDF multiple times.

Pick or upload, everywhere — Wherever you previously uploaded an image or file, you now get a picker to either reuse an existing file from the library or upload a new one.

Folders and Collections — A file lives in one folder (its home), but can belong to multiple collections — great for grouping files like "all sermon PDFs" or "campaign images" without moving them.

See where a file is used — Each asset shows exactly where it is being used (pages, blocks, records). Files that are still in use or belong to a collection cannot be deleted until they are freed — protecting against accidental deletion.

Storage overview — Each organization can see their image and document storage usage at a glance.

Move to File Manager — Older files uploaded before the library existed can be registered into the library with one click — no re-upload needed.

Please note that some upload areas (avatars, site logo/favicon, fonts, audio uploads, and publication files) are not part of the File Manager and will continue to work as before.

Logged-in users on the Hope design now have access to a user menu, giving them quick access to their account settings and the option to sign out — consistent with the experience already available on other designs.

Several new data protection features have been added to the Events module to help organizers handle participant data responsibly and in compliance with privacy regulations.

Sensitive fields — Additional fields can now be marked as sensitive (e.g. allergies, dietary requirements, health data). When marked, participants will see a consent checkbox they must tick before submitting that information. The sensitive data type and consent text are fully configurable.

Data retention settings — In the Event Settings under the Data Protection tab, organizers can configure how long participant data is retained after an event ends. Sensitive data is deleted earlier than standard personal data. By default, personal data is anonymised 3 months after the event, and sensitive data is deleted after 6 weeks.

Incident reporting — To prevent accidental deletion of data linked to ongoing issues (e.g. payment disputes, allergy reactions, legal matters), organizers can flag a participant by reporting an incident. The participant's data will only be deleted once the incident has been resolved and removed.

Several new features have been added to the Events module to give organizers more flexibility:

Conditional additional fields — Additional fields can now be set to only appear based on the answer to a previous field. For example, a "Flight Number" field can be configured to only show when a participant selects "Aircraft" as their mode of transportation.

Comments on price, accommodation and meal options — You can now collect extra information when a participant selects a specific price, accommodation, or meal option. For example, asking "Who do you want to room with?" when a shared room is selected.

More additional fields — The limit for additional fields has been increased from 10 to 20.

Payment routing by delegation — You can now control which payment method is available based on a participant's answer to a select field. Certain options can be restricted to alternate payment only, others to Stripe only, or both can remain available as default.

You can now set a button or menu item to point to a dynamic page, such as a Category or Person page. After selecting the dynamic page, simply choose the specific record (e.g. a category like "Theology > Teachings") as the linked record — the URL is then resolved automatically.

This means that if a slug changes or a category moves in the hierarchy, the link will always stay up to date without any manual adjustments needed.

You can now choose to display the video player's own default poster instead of the Web Engine uploaded image on the Episode Player and Article Linked Episode Player blocks. When enabled, the player's native UI is shown — including features like Jetstream's premiere label, which displays the scheduled premiere date and time. This option is available in the block's Properties panel under "Use the player's default poster".

Working with sourced fields in the block editor is now faster and more intuitive. The field path, name, and formatting are now clearly visible at a glance in both the block preview and settings panel. Toggling a sourced field on or off is now a direct action on the field itself, removing the need to go through the settings cog first. Editing the source value works similarly to before, and a fallback value can be set if needed. Turning the source off restores the standard input for that field.

The Hero Carousel block is now available for the Adventist design, allowing you to display multiple hero slides in a rotating carousel. Each carousel item supports responsive image selection and responsive style settings per breakpoint, so you can fine-tune how each slide looks across different screen sizes. Items can also be duplicated or hidden directly from the carousel settings, making it easy to manage and reorder your content.

The Adventist Design homepage hero now supports a rotating carousel, and a new full-screen button gives you the maximum canvas while building.

• Add as many carousel slides as you need, each independently editable

• Auto-rotation with a configurable duration per slide

• Edit, duplicate, hide, or delete individual carousel items

• Full-screen mode collapses all menus for maximum editing space

Small addition to the Adventist (and Paul designs while I was at it). A Box can now have an optional link. This allows for things like custom “Card” elements to act as a single clickable area. This is feature parity with the DACH design. However, there are some differences:

• Link type selection is supported

• The link renders as a layer that covers the box. The Box children are not inside the link. Otherwise it can easily create invalid DOM structures (such as a <button> inside a <a>)

• Because of the above, there is a link label field for screen readers

• Also because of the above, any interactive elements placed inside the box will not work without manually adding a z-index. The link layer covers the whole box so it captures the click area fully otherwise.

The Jetstream video player has been upgraded on the Adventist and Paul designs, bringing a smoother and more reliable video experience. This update delivers better responsiveness when playing or pausing videos, more consistent behavior across different video types and playlists, and single-click unmuted playback for Web Engine posters. While the visual change is subtle, the improvements under the hood lay a strong foundation for future video enhancements.

A brand new Analytics view is now available in Adventist Web Engine, offering a cleaner and more intuitive interface for understanding your website's performance. The update brings real-time traffic insights, improved visitor and page tracking, better visibility into traffic sources and audience behavior, and detailed statistics on devices, browsers, and locations. Enhanced comparison and reporting views are also included. This update also lays a stronger foundation for future analytics improvements.

To find it, expand your website, look for the Analytics submodule. Click on Analytics, and the view will open on the right side, where you normally edit webpages.

The Sermon Planner now supports exporting schedules as PDF files, in addition to the CSV and Excel export options that were already available. Please note that PDF export is currently only available for websites using the DACH design.

The Article Filters block on the Adventist design now includes a new "Quarter" variant, which adds a from/to date filter to help visitors narrow down articles by a specific time period.

Several optimizations have been made to improve the loading speed of websites running on Web Engine. Testing shows a response time improvement of at least 35%, and up to 62% in some cases — meaning your website should feel noticeably faster for visitors.

The course module now supports certificates! A built-in certificate builder lets you create and configure certificates for your courses. In the courses list, an icon indicates which courses have certificates enabled.

Students can download their certificate in three ways: immediately after completing a course, at any time from their completed courses dashboard, or directly from the course detail page.

When adding an image to a component like the Hero block — where different images can be set per screen size — the image is only added to the breakpoint you are currently working at. For example, if you add an image at laptop width, smaller screen sizes like mobile will have no image.

A warning will now appear to let you know when this happens. You can either copy the image and paste it to the smaller breakpoints, or ignore the warning if you intentionally don't want the image to show on smaller screens.

The WordPress import tool now converts WordPress image galleries into the RTE Image Gallery plugin. Currently, only the images themselves are imported — galleries with captions on individual images are not yet supported.

Please note that the RTE Image Gallery plugin is not available in all designs yet, including the DACH design.

A couple of small features for the Adventist design SiteHeader block:

1. Support for controlling the Primary menu text size. This applies to the Minimal and News variants only. I didn’t add it to the Alps variant on purpose, since that is not part of the ALPS design system. There are three sizes: Small, Medium and Large. These can be applied responsively as well, although for mobile, it doesn’t have an affect, since the mobile menu uses the drawer which I left as is. As a side note, the menu styles were moved to the Styles tab. They are no longer a popover of the menus on the properties tab

2. Support for controlling the logo height. This allows more control over sizing the logo

In some media libraries, media links for translated episodes were not being displayed, even when a value was present. This happened when the translated media link differed from the original language link due to imported content. This has now been fixed and translation media links are correctly shown.

A new Courses Collection Repeater block is now available for the Adventist design, allowing you to create custom course listings by repeating course collections as a data source. A source site option is also available, working similarly to the Articles, Episodes, and Events Feed blocks — the source site becomes the provider of available courses and collections. Course links will automatically point to the source site using absolute URLs.

The background layer display in the backend has been updated to better reflect how backgrounds are actually rendered on your site. Layers are now shown stacked from bottom to top, so what you see in the editor matches what appears on the page. The "Add background" button and sorting controls have also moved to below the list of backgrounds to keep things consistent.

The Language Menu block on the base design has been updated — you can now configure the colors of the menu items to better match your site's style.

The Articles Feed and Episodes Feed blocks now include a language selection option, allowing you to choose which language the feed content is displayed in. The available languages are based on what the source site has enabled. If no language is selected, the feed will default to the source site's default language.

The Newsletter editor has been updated with support for Rich Text blocks, giving editors more flexibility when creating newsletter content.

Rich Text (RTE) blocks can now be added to newsletter templates and marked as editable, meaning issue editors can customize the content of each block per issue — previously, only the Collection Repeater was editable. Each RTE block should have a label set for clarity, and a unique code is automatically generated.

In the issue editor, editable RTE blocks appear in document order, making it easy to add and manage content in context. Styling is intentionally kept simple — only basic text formatting is available, with images and other plugins disabled to maintain a clean, consistent newsletter layout. The final content of RTE blocks is fully rendered in the generated newsletter HTML.

A new Events Repeater block is now available, working similarly to other repeater blocks — its child blocks are automatically repeated for each event.

A wide range of event fields are available as data sources, giving you flexibility in what information is displayed. A new currency format option has also been added for number fields, allowing prices and other numeric values to be displayed as properly formatted currency. The currency used is pulled directly from the event's own currency field.

The DACH design now supports the Modal block. Additionally, for DACH, Adventist, and Paul designs, several new options are available in the Modal settings:

1. Prevent dismissal — When enabled, the modal cannot be closed by pressing "Esc" or clicking outside of it. The user must actively close it using the close button or a button inside the modal set to "Close modal dialog". Make sure the "Show close button" option is enabled in the Styles tab.

2. Auto open — The modal opens automatically when a user lands on the page, without any interaction needed.

3. Auto open delay — Controls how long after the page loads before the modal appears. The default is 1 second.

4. Dismissal duration — When a user closes an auto-opening modal, the browser remembers this so the modal doesn't keep reappearing on every visit or reload. You can set how long this is remembered (in minutes). The default is 24 hours.

The Sermon Planner now includes navigation buttons, making it easier to move horizontally through your content without having to scroll manually:

Your website now looks great on large screens, including Full HD, QHD, and 4K displays. For example, the Hero section automatically adjusts its proportions to fit bigger screens.

A new Social Media Links block is now available for the Paul and Adventist designs. This block automatically reads and displays the social media links configured in your site's Appearance → Social Links settings, making it easy to keep your social media presence consistent and up to date across your website.

In the Base design, the Newsletter subscription block now supports three new fields:

• Terms label: label for terms checkbox

• Terms link label: text when link used

• Terms description: information for terms checkbox

The base design now has a FormBuilder component in the frontend.

Bugfix:

Attribute fields for newsletters: the placeholder is now passed to the frontend.