domma-cms 1.71.0 → 1.72.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +16 -0
- package/admin/js/lib/sidebar-frequent.js +1 -1
- package/admin/js/templates/docs/usage-tools.html +1 -1
- package/docs/DommaFeatures.md +47 -12
- package/package.json +1 -1
- package/plugins/_lib/admin/mail/body-menu.js +1 -1
- package/plugins/_lib/admin/mail/cms-host.js +1 -1
- package/plugins/_lib/admin/mail/compose-window.js +76 -3
- package/plugins/_lib/admin/mail/contacts.js +1 -1
- package/plugins/_lib/admin/mail/diagnostics-section.js +1 -1
- package/plugins/_lib/admin/mail/drag-drop.js +1 -1
- package/plugins/_lib/admin/mail/folder-tree.js +1 -1
- package/plugins/_lib/admin/mail/font-controls.js +1 -1
- package/plugins/_lib/admin/mail/fonts.js +1 -1
- package/plugins/_lib/admin/mail/host-context.js +1 -1
- package/plugins/_lib/admin/mail/identity.js +1 -1
- package/plugins/_lib/admin/mail/image-senders-section.js +1 -1
- package/plugins/_lib/admin/mail/keyboard.js +1 -1
- package/plugins/_lib/admin/mail/mail.html +1 -1
- package/plugins/_lib/admin/mail/message-actions.js +1 -1
- package/plugins/_lib/admin/mail/oauth-panel.js +1 -1
- package/plugins/_lib/admin/mail/panes.js +1 -1
- package/plugins/_lib/admin/mail/reader-kit.js +1 -1
- package/plugins/_lib/admin/mail/reader-runtime.js +11 -2
- package/plugins/_lib/admin/mail/reader-view.js +1 -1
- package/plugins/_lib/admin/mail/resizable.js +1 -1
- package/plugins/_lib/admin/mail/restore-spam.js +1 -1
- package/plugins/_lib/admin/mail/rules.js +1 -1
- package/plugins/_lib/admin/mail/scheduling.js +1 -1
- package/plugins/_lib/admin/mail/section-kit.js +1 -1
- package/plugins/_lib/admin/mail/security-note.js +1 -1
- package/plugins/_lib/admin/mail/settings-section.js +1 -1
- package/plugins/_lib/admin/mail/templates.js +1 -1
- package/plugins/_lib/admin/mail/threads.js +1 -1
- package/plugins/_lib/admin/mail/vacation.js +1 -1
- package/plugins/_lib/admin/mail/when-closed.js +1 -1
- package/plugins/_lib/admin/ui/dates.js +1 -1
- package/plugins/_lib/admin/ui/resizable.js +1 -1
- package/plugins/_lib/admin/ui/rich-field.js +291 -0
- package/plugins/_lib/domma-mail.lock.json +83 -80
- package/plugins/_lib/mail/accountFileStore.js +1 -1
- package/plugins/_lib/mail/accountRepository.js +1 -1
- package/plugins/_lib/mail/accountRoutes.js +1 -1
- package/plugins/_lib/mail/bodyTokenProvider.js +1 -1
- package/plugins/_lib/mail/bodyTokens.js +1 -1
- package/plugins/_lib/mail/compose.js +1 -1
- package/plugins/_lib/mail/defaults.js +1 -1
- package/plugins/_lib/mail/envelope.js +1 -1
- package/plugins/_lib/mail/folderActions.js +1 -1
- package/plugins/_lib/mail/folderRuntime.js +1 -1
- package/plugins/_lib/mail/folders.js +1 -1
- package/plugins/_lib/mail/imapPoolRuntime.js +1 -1
- package/plugins/_lib/mail/mbox.js +1 -1
- package/plugins/_lib/mail/message-action.js +1 -1
- package/plugins/_lib/mail/messageSecurity.js +1 -1
- package/plugins/_lib/mail/messageSecurityProvider.js +1 -1
- package/plugins/_lib/mail/networkAddresses.js +1 -1
- package/plugins/_lib/mail/networkPolicy.js +1 -1
- package/plugins/_lib/mail/oauthAccounts.js +1 -1
- package/plugins/_lib/mail/oauthRouteRuntime.js +1 -1
- package/plugins/_lib/mail/oauthRuntime.js +1 -1
- package/plugins/_lib/mail/pollSchedule.js +1 -1
- package/plugins/_lib/mail/poller.js +1 -1
- package/plugins/_lib/mail/pollerRuntime.js +1 -1
- package/plugins/_lib/mail/priority.js +1 -1
- package/plugins/_lib/mail/publicMailbox.js +1 -1
- package/plugins/_lib/mail/readRuntime.js +1 -1
- package/plugins/_lib/mail/render.js +1 -1
- package/plugins/_lib/mail/ruleRunner.js +1 -1
- package/plugins/_lib/mail/schedulerRuntime.js +1 -1
- package/plugins/_lib/mail/secretProvider.js +1 -1
- package/plugins/_lib/mail/secretbox.js +1 -1
- package/plugins/_lib/mail/senderAuth.js +1 -1
- package/plugins/_lib/mail/sieve.js +1 -1
- package/plugins/_lib/mail/smtpService.js +1 -1
- package/plugins/_lib/mail/snoozeRuntime.js +1 -1
- package/plugins/_lib/mail/store.js +1 -1
- package/plugins/_lib/mail/subscriptions.js +1 -1
- package/plugins/_lib/mail/syncPlan.js +1 -1
- package/plugins/_lib/mail/syncRuntime.js +1 -1
- package/plugins/_lib/mail/syncSelection.js +1 -1
- package/plugins/_lib/mail/unreadBadge.js +1 -1
- package/plugins/_lib/mail/unsubscribe.js +1 -1
- package/plugins/_lib/mail/vacationRuntime.js +1 -1
- package/plugins/_lib/mail/write.js +1 -1
- package/plugins/_lib/public/rich-text.mjs +104 -0
- package/plugins/_lib/rich-text.js +153 -0
- package/server/services/sidebarFrequent.js +1 -1
- package/server/services/wpImport/redirects.js +7 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,21 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [1.72.0] - 2026-11-17
|
|
4
|
+
|
|
5
|
+
### Added
|
|
6
|
+
|
|
7
|
+
- **Mail compose takes an edition's own panel** (Domma Mail core 0.31.0). The shared compose window has a slot above the message that a Tool can fill and add fields to Save and Send; Email Pro uses it for its branding picker. Nothing changes without such a Tool.
|
|
8
|
+
|
|
9
|
+
## [1.71.1] - 2026-11-17
|
|
10
|
+
|
|
11
|
+
### Changed
|
|
12
|
+
|
|
13
|
+
- **Frequent holds 24** places in the sidebar, up from 16.
|
|
14
|
+
|
|
15
|
+
### Fixed
|
|
16
|
+
|
|
17
|
+
- **Import a site: a pasted redirect that says only 410 is read as gone.** In "The old site's redirects", a line such as `/old-page -> 410` (or a sheet row with 410 or "gone" as its second column) was read as a redirect to an address called "410". It is now a 410, as `/old-page -> / 410` already was.
|
|
18
|
+
|
|
3
19
|
## [1.71.0] - 2026-11-16
|
|
4
20
|
|
|
5
21
|
### Added
|
|
@@ -1 +1 @@
|
|
|
1
|
-
export const FREQUENT_KEY="frequent",FREQUENT_MAX=
|
|
1
|
+
export const FREQUENT_KEY="frequent",FREQUENT_MAX=24;export function findLeaf(e,t){for(const r of e||[])if(!(!r||r.type||r.hidden)){if(Array.isArray(r.items)&&r.items.length){const n=findLeaf(r.items,t);if(n)return n}else if(r.url===t)return r}return null}export function frequentFolder(e,t,{hidden:r=!1}={}){const n=[];for(const o of Array.isArray(t)?t:[]){const i=typeof o=="string"&&o?findLeaf(e,o):null;i&&n.push({text:i.text,url:i.url,...i.icon&&{icon:i.icon},...i.colour&&{colour:i.colour}})}return n.length?{text:"Frequent",key:FREQUENT_KEY,icon:"star",items:n,frequent:!0}:r?null:{text:"Frequent",key:FREQUENT_KEY,icon:"star",items:[],frequent:!0,empty:!0}}export function addFrequent(e,t){const r=(Array.isArray(e)?e:[]).filter(n=>typeof n=="string"&&n);return!t||r.includes(t)||r.length>=24?r:[...r,t]}export function removeFrequent(e,t){return(Array.isArray(e)?e:[]).filter(r=>r!==t)}export function moveFrequent(e,t,r){const n=Array.isArray(e)?[...e]:[],o=n.indexOf(t),i=o+r;return o<0||i<0||i>=n.length||([n[o],n[i]]=[n[i],n[o]]),n}export function storageKey(e){const t=e&&(e.id||e._id||e.email);return`sidebar.frequent.${t?String(t):"anon"}`}export function readFrequent(e){try{const t=S.get(storageKey(e));return Array.isArray(t)?t.filter(r=>typeof r=="string"&&r):[]}catch{return[]}}export function readFrequentHidden(e){try{return S.get(`${storageKey(e)}.hidden`)===!0}catch{return!1}}export function writeFrequentHidden(e,t){try{return S.set(`${storageKey(e)}.hidden`,!!t),!0}catch{return!1}}export function writeFrequent(e,t){try{return S.set(storageKey(e),Array.isArray(t)?t:[]),!0}catch{return!1}}let u=null;export function resetFrequentSync(){u=null}export function saveFrequent(e,t){return e.put("/sidebar/frequent",{urls:readFrequent(t),hidden:readFrequentHidden(t)})}export async function syncFrequent(e,t){const r=t&&(t.id||t._id||t.email);if(!r||u===String(r))return;const n=await e.get("/sidebar/frequent");if(!(!n||typeof n!="object")){if(u=String(r),!n.saved){(readFrequent(t).length||readFrequentHidden(t))&&await saveFrequent(e,t);return}writeFrequent(t,Array.isArray(n.urls)?n.urls:[]),writeFrequentHidden(t,n.hidden===!0)}}
|
|
@@ -24,7 +24,7 @@
|
|
|
24
24
|
<p><strong>Frequent</strong> is the folder at the top of the sidebar for the Tools you use most.
|
|
25
25
|
<strong>Right-click any Tool</strong> in the sidebar and choose <strong>Add to Frequent</strong>;
|
|
26
26
|
right-click it again for <strong>Move up</strong>, <strong>Move down</strong> or
|
|
27
|
-
<strong>Remove from Frequent</strong>. It holds up to
|
|
27
|
+
<strong>Remove from Frequent</strong>. It holds up to 24, with their count badges. Until you
|
|
28
28
|
add one it shows a short hint - right-click the folder and choose <strong>Hide Frequent until I
|
|
29
29
|
add a Tool</strong> if you would rather not see it. Frequent is yours alone: it is kept in this
|
|
30
30
|
browser, changes nobody else's sidebar, and only ever shows Tools you are allowed to open.
|
package/docs/DommaFeatures.md
CHANGED
|
@@ -39,16 +39,16 @@ Code was treated as the truth. Where docs disagree with it, the disagreement is
|
|
|
39
39
|
| `blog` | free | 1.9.6 | Public-facing blog with posts, categories and comments - layouts and listings built from editable blocks. |
|
|
40
40
|
| `blog-pro` | paid | 0.7.0 | Several blogs on one site, each with its own address, look and settings - dozens of layouts, self-hosted fonts, colours, page transitions, author pages, and privacy-first media: videos, audio, galleries, link cards and maps. |
|
|
41
41
|
| `calendar` | paid | 2.0.1 | Events, appointments, availability and Google Calendar in one Tool. Includes the former Booking and Booking Pro features: classes, waiting lists, repeat bookings, linked staff and rooms, booking questions and online appointments. |
|
|
42
|
-
| `campaigns-pro` | paid | 1.
|
|
42
|
+
| `campaigns-pro` | paid | 1.13.1 | Marketing campaigns, one paid Tool: compose a message, send it to Contacts groups (read live when it sends) or an audience of its own (shared with Surveys), from the site's sending or your own Email mailbox (small lists), schedule sends, attach an offer that closes by a date or a claim limit. Opens and clicks (cookieless), links tagged for Analytics, a linked Shop discount code, send a survey as a campaign, follow-up sequences, resend to non-openers, A/B subject tests, and a version-1 stats feed other Tools read. A check before sending, and with AI Assist: subject line ideas, a first draft from a brief, Rewrite (keeping every placeholder) and themes from the replies to a mailbox campaign. |
|
|
43
43
|
| `media-pro` | paid | 0.2.0 | Media, properly organised: folders inside folders, choose from them anywhere, and move or rename anything without breaking a page. Select several, see where each file is used, find what is unused or duplicated, shrink big pictures, alt text and credits with each file, Trash, and a whole folder as a gallery. Works on the same files as the built-in Tool. |
|
|
44
44
|
| `contacts-pro` | paid | 0.13.0 | Contacts, with more to them: send a campaign to a group or the selected contacts (with Campaigns Pro), your own custom fields, birthdays and ages with the ones coming up and a reminder in the sidebar, and groups with their own emblem and colours. Share a contact, several, or a whole group with people or roles - to view, or to edit. Call a contact now on a video call on your site. Works over the same contacts as the built-in Tool, so nothing moves and nothing is lost. |
|
|
45
45
|
| `crossword` | paid (giftable) | 1.5.1 | Crosswords on your site: type the answers and clues and the grid lays itself out (live preview, Another layout). Players type a name and race the server's clock, checks and wrong guesses cost time, fastest solvers on a leaderboard. Hints for a time penalty, personal best and Share, animations, export and import. Test it from the Tool - a test go never reaches the board. Rotation (a new quiz every day or week from a queue, off by default) and fresh quizzes from Domma for review. |
|
|
46
46
|
| `daily-word` | paid (giftable) | 1.3.0 | One hidden word a day, the same for everyone: six guesses, each letter marked right place, in the word or not; real words only (a bundled dictionary, switchable), an archive of past days, streaks, Share as coloured squares, a calendar of what is coming. Fewest guesses tops the day's board, then the fastest. |
|
|
47
47
|
| `data-transfer` | paid | 1.3.3 | Move collections between file and MongoDB storage, back them up and restore them (all or some, merged or replaced) - keeping every entry's id - and clone them (cloned entries get new ids, so references stay unambiguous). Every restore and transfer takes a safety snapshot first. |
|
|
48
48
|
| `docs` | paid | 2.13.1 | Document editor: Home and editor screens, sharing with Viewers/Editors, public links, import/export, send to page/blog/email, edit lock, Trash, version history, templates. PDF documents (2.13): a PDF kept as it is, shown in the browser's viewer, searchable inside, versioned on replace. |
|
|
49
|
-
| `docs-pro` | paid | 0.
|
|
50
|
-
| `email-pro` | paid | 0.
|
|
51
|
-
| `feedback` | free | 1.
|
|
49
|
+
| `docs-pro` | paid | 0.15.0 | Domma Spaces (publish a Docs folder at `/spaces` with a Kindle-style reader), Cloud copies (Google Drive, OneDrive, Dropbox, S3), Signatures (emailed signing links, typed or drawn, signed copy with a certificate page; 0.10: boxes placed on a PDF document's pages, the signed PDF stamped with pdf-lib), PDF tools (0.11: fill the PDF's own form, annotate, pages) and protected public links (expiry date, password). With AI Assist, Summarise this document puts a summary and key points at the top. Adds to Docs. |
|
|
50
|
+
| `email-pro` | paid | 0.18.0 | Full mail (and Campaigns Pro's "send from my mailbox"): read, write, send and search, over a synchronised store. Search, threads, rules, scheduled sends, snooze and vacation replies need MongoDB; without it, reading, filing and sending still work. With AI Assist: summarise a conversation, suggest a reply, draft from a few words and rewrite, with personal details taken out first. |
|
|
51
|
+
| `feedback` | free | 1.4.0 | Tell Domma what is broken, missing or good - straight from your admin - and see what became of it: seen, planned, in progress, done, with Domma's reply. On the Domma server, AI Assist groups the inbox into themes. |
|
|
52
52
|
| `garage` | paid | 1.4.3 | UK vehicle management with DVLA API lookup, save vehicles, and search history. |
|
|
53
53
|
| `group-four` | paid (giftable) | 1.0.0 | Sixteen tiles hide four groups of four: pick four, a wrong guess costs a mistake, a close call says so. Single puzzles or a daily set with streaks and an archive; the server holds the groups. |
|
|
54
54
|
| `hangman` | paid (giftable) | 1.0.0 | Guess the hidden word or phrase letter by letter before the drawing is finished - a stick figure, or balloons that pop for family sites. Random rounds or the same words for everyone each day; hints, leaderboards, personal best, Share, export and import. |
|
|
@@ -70,12 +70,13 @@ Code was treated as the truth. Where docs disagree with it, the disagreement is
|
|
|
70
70
|
| `scratch-card` | paid (giftable) | 1.0.0 | Instant-win scratch cards, the partner to Prize Wheel: prizes with odds and stock, codes (shared, unique, or single-use Shop codes), a reveal or match-three card, email and consent capture. The server draws at the deal; the result arrives as the card is scratched. |
|
|
71
71
|
| `security` | free | 1.1.3 | Keeps a Domma CMS site safe: a health check of what is weak and how to fix it, sign-in lockout after repeated wrong passwords, password rules, a log of every sign-in, and blocking of the scanners that probe every site for WordPress, .env files and the like. |
|
|
72
72
|
| `security-pro` | paid | 1.3.2 | Everything in Security, plus two-factor sign-in (authenticator apps, recovery codes, required per role), a firewall that bans scanners for longer each time they return, per-route rate limits, country rules for the admin, breached-password checks and every signed-in session in one place. |
|
|
73
|
-
| `seo-pro` | paid | 0.
|
|
73
|
+
| `seo-pro` | paid | 0.9.0 | More for SEO: Google Search Console in the admin (with your own Google client) - searches, clicks, positions and where to win more; structured data for rich results (FAQ, how-to, product, event, local business); links worth adding between pages, pages competing for one search, readability, near duplicates and image checks; every title and description in one grid, and moving an old site's addresses across as redirects; a not-found log with one-click redirects; a scheduled check of every link; SEO history and notices. With AI Assist: suggested titles, descriptions and focus keyphrases in Bulk, Fill from the page for rich results, and Make simpler for hard-going sentences. Adds to SEO, which is built into Domma CMS (0.90 and later). |
|
|
74
74
|
| `sheets` | paid | 0.4.1 | A spreadsheet in your admin: workbooks with formulas, sorting and filters; import CSV, JSON or Excel, export CSV or Excel, print. Feed a sheet live from Contacts, collections, forms, Surveys, Campaigns, Analytics or the Shop - rows kept even if the source goes away. |
|
|
75
75
|
| `shopping-cart` | free | 1.6.1 | Sell from your site: products with options, stock and pictures, a storefront and a cart that follows shoppers from page to page, and checkout with Stripe, PayPal or payment offline. Orders to fulfil in the sidebar, refunds from the order. |
|
|
76
76
|
| `shopping-cart-pro` | paid | 0.3.2 | More for the Shop: discount codes (other Tools such as Prize Wheel can make single-use ones), shipping zones with rates by weight or order value, tax by country and class, branded order emails from confirmation to dispatch, and Insights - takings by week, best sellers, repeat customers and abandoned checkouts you can nudge. Adds to the free Shopping Cart; a lapsed licence leaves the Cart and every order just as they were. |
|
|
77
77
|
| `sliding-puzzle` | paid (giftable) | 1.0.0 | The tile-sliding puzzle, 3x3 to 6x6, numbers or a Media picture. Same board for everyone, a new board each go, or a daily puzzle; every move checked by the server. Fewest moves or fastest time wins. |
|
|
78
78
|
| `social-media-pro` | paid | 0.4.0 | How the site looks when it is shared, and posting it: share cards per page for Facebook, X, LinkedIn, WhatsApp and Slack with previews; a share image drawn for every page that has none, in the site's colours; share and follow buttons; posting to Bluesky, Mastodon and LinkedIn (through the site's own LinkedIn app, with a reminder before its 60-day sign-in runs out) - now, scheduled, or drafted automatically for every new blog post or page - with links tagged for Analytics and the posts on the Calendar; and LinkedIn conversions - chosen forms reported to LinkedIn's Conversions API when a visitor who accepted marketing cookies sends one. Sold with SEO Pro. |
|
|
79
|
+
| `support` | free | 1.3.0 | Help from Domma in the admin: Domma's email, phone and hours always to hand, and a request as a conversation with the Domma team, urgent ones first. On the Domma server, AI Assist summarises a request, suggests a reply and groups waiting requests into themes. |
|
|
79
80
|
| `surveys` | paid | 1.19.0 | Targeted surveys over the Forms engine: shared audiences and Contacts groups, tokenised invites, reminders, NPS, star, smiley and number scales, quiz mode with scores, closing rules, and Results with charts, filters, Live refresh, a printable PDF report and (with AI Assist) themed summaries of free-text answers. |
|
|
80
81
|
| `sweepstake` | paid (giftable) | 1.0.0 | Office, pub and club sweepstakes for any event: picks, entry fee and prizes, entrants by name with paid ticks, and one recorded, repeatable draw revealed live on the page, then who has what and the money. |
|
|
81
82
|
| `theme-roller` | paid | 1.1.3 | Make your own themes: start from any built-in theme, change its colours, fonts, spacing and borders with a live preview, and save it. Saved themes join the built-in ones everywhere a theme is chosen - the site, the admin, day and night, a region of a page. Needs Domma CMS 0.73 or later to use them. |
|
|
@@ -1051,7 +1052,7 @@ Where: `server/services/presetCollections.js` (`PRESETS`, `seedAll()`), `server/
|
|
|
1051
1052
|
- **Dashboard Pro (paid) - a widget board** - with the Dashboard Pro Tool, `#/` becomes a board of widgets instead of the fixed Dashboard. **Add widget** opens a gallery of every widget the user may add, grouped by Tool and searchable; cards drag by their grip (Domma `E.sortable`, indicator mode on a wrapping grid), size Small / Medium / Large / Full width and move or go from their ⋮ / right-click menu (Alt+arrows and Delete on a focused card). Each user's layout is their own (`content/dashboard/layouts/<user>.json`, ignored in a site repo); **Reset** returns to the site default, which an admin sets with **Make this the default** (`content/dashboard/default.json`). Widgets: core's six (traffic, visitors now, needs attention, recent activity, site health, top pages - `GET /api/dashboard/widget/:name`), one `count` widget for every sidebar badge (so Email, Booking, Support... arrive without changes), and any a plugin declares in `admin.widgets`. The board is core code switched on only by a paid, closed-source Tool calling `hooks.enableDashboardPro()` (the instant-calls contract); without it every widget route answers 404. `server/services/widgets.js`, `server/routes/api/widgets.js`, `admin/js/views/dashboard-board.js`, `admin/js/lib/dashboard-board-arrange.js`, `admin/js/lib/widget-render.js`; plugin docs under "Dashboard widgets" in `docs/plugin-development.md`.
|
|
1052
1053
|
- **The cog** (banner): per person - the Dashboards name (banner, tab title and the sidebar's `#/` entry, relabelled by `/api/sidebar/menu` and `/registered-items` while it still says "Dashboard"), greeting, 3/4/6 columns (wide screens; narrow cards drop their icon and wrap the title), compact cards, updates live/slower (3x)/paused, and "open on my boards" (`/api/auth/permissions` answers `adminHome: /dashboards` for an unconfined user; the Overview tab gets past it once via `allowOverviewOnce()`); kept in `content/dashboard/prefs/<user>.json` (ignored). For everyone (admins) - the board's default name and **lock the layout**: non-admins get the site default (`source: locked`), PUT/DELETE of their layout answer 423, and the board offers fold and refresh only; `content/dashboard/site.json`. `server/services/dashboardSettings.js`, routes `GET/PUT /api/dashboard/settings`, `PUT /api/dashboard/settings/site`.
|
|
1053
1054
|
- **Dashboards (1.5)** - with Dashboard Pro, one sidebar entry (Overview > Dashboards, the `#/` item relabelled) and tabs: **Overview** first and fixed - whichever view owns `#/` (the core Dashboard, or a Tool's, like the fleet manager's), wrapped in `app.js` by `withDashboardStrip()` so its strip needs nothing from the Tool - then the person's boards at `#/dashboards?board=<id>` (`views/dashboards.js` -> `dashboard-board.js`). `#/my-dashboard` redirects there; `overview` is reserved and never a board id. Pure: `admin/js/lib/dashboards-arrange.js` (tabs, addresses, label); strip and banner: `admin/js/lib/dashboards-strip.js`.
|
|
1054
|
-
- **Sidebar right-click menu and Frequent** - right-click any Tool in the sidebar for Open, Open in a new tab, Add to / Remove from Frequent and Copy link; right-click a folder to open or close it, or every folder at once. **Frequent** is each admin's own folder at the top of the sidebar (up to
|
|
1055
|
+
- **Sidebar right-click menu and Frequent** - right-click any Tool in the sidebar for Open, Open in a new tab, Add to / Remove from Frequent and Copy link; right-click a folder to open or close it, or every folder at once. **Frequent** is each admin's own folder at the top of the sidebar (up to 24 Tools, in their order - Move up / Move down inside it, Clear Frequent on the folder). It is personal, kept on the server per user (`content/sidebar/frequent/<user id>.json`, via `GET`/`PUT /api/sidebar/frequent`) so it follows them to any browser, never written into the shared `admin-sidebar` menu, and built from the sidebar after permission filtering, so it can only ever list Tools that user may open. Count badges show on both copies. `admin/js/lib/sidebar-frequent.js` (pure, tested), wired in `sidebar-renderer.js` (`wireSidebarMenu`).
|
|
1055
1056
|
- **Hotkeys and the palette** - **G then a letter** opens a Tool from anywhere (G E Email, G D Dashboards; built-in letters in `CORE_HOTKEYS`, a plugin declares `hotkey` on its `admin.sidebar` entry), **G then 1-9** the Frequent folder's Tools in order, **Ctrl+K or Ctrl+D** (Cmd on a Mac) a palette that finds any Tool by name, initials or folder, and **?** the list of every hotkey. Pausing after G shows a hint chip (Frequent numbers, then letters; `chipEntries`) until the letter or the lapse. Shown on hover in the sidebar and beside Open in a Tool's right-click menu. Built-ins claim first, then sidebar order; a later claimant goes without. Keys wait while typing; the sequence and palette listen in the capture phase and claim their key, so a Tool's own single-letter keys (Email's S) never hear the second key, while `?` gives way to a Tool that claims it. `admin/js/lib/hotkeys.js` (pure, tested) and `hotkeys-ui.js`.
|
|
1056
1057
|
- **Arrange the sidebar in place** - a six-dot button in the sidebar header (users who may update menus) turns on Arrange: the sidebar's items are set aside and the `admin-sidebar` menu is shown as draggable rows, hidden items dimmed, Tools where they will appear. Drag to move, drop on the middle of a row to put it inside, the eye hides or shows (locked Tools show a padlock), Alt+arrows move the focused row. Done saves the menu and redraws the sidebar for everyone; Cancel or Esc leaves it untouched, asking first if anything moved. It edits exactly what the Menus editor edits (same rows, same drops via `admin/js/lib/menu-drag.js`, same save shape); labels, icons, badges and visibility stay in the Menus editor. `admin/js/lib/sidebar-arrange.js`.
|
|
1057
1058
|
- **Tools that cannot be lost** - Dashboard, Menus, Users and My Profile can be moved but not hidden or removed. If a menu edit hides one, the sidebar puts it back, so an admin can always find a way back.
|
|
@@ -1266,6 +1267,7 @@ The four Tools below were plugins until 0.67.0 and are now part of the CMS. They
|
|
|
1266
1267
|
- Admin: **Content > Chats** (`#/launchers/chats`, `#/launchers/chats/:id`) - the inbox, waiting first, the live thread (3s poll), replies with per-chat drafts, end/delete/email in a context menu, Available switch, settings cog; sidebar badge `/api/chats/_count` (live while someone waits, red after 5 minutes). **Chats > Knowledge** (`#/launchers/knowledge`) - entries with an editor slideover (question, other ways of asking, keywords, Markdown answer, up to five buttons, on/off), Try the bot with scores, and the Unanswered list (Make an entry, add to the closest entry, dismiss). Visitor panel `public/js/launcher-chat.mjs` `mountChat(container, {launcherId, title, chat})` + `public/css/launcher-chat.css`, domma-reactive.
|
|
1267
1268
|
- Permission `chats` (`read`, `reply`, `manage`) in the Tools group; Admin is granted it once. All of it is behind the Launchers switch.
|
|
1268
1269
|
- AI Assist (unreleased): the paid `ai-assist` Tool (Pro plan) calls `hooks.enableAiAssist()` (`services/aiAssist.js`, paid + closedSource only, off when the Tool is disabled). Without it `aiAvailable()` is false (chat config says `ai: false`, nothing is asked) and the admin assistant is unavailable (`requestAdminAnswer` 403). `GET /api/launchers/items` says `aiAssist`, and the launcher editor notes under AI answers when it is off. The Manager checks the `ai-assist` licence (no longer the Site Builder's).
|
|
1270
|
+
- AI Assist in Tools (Manager 0.37.69, 2026-11-16): Tools' writing help and summaries go to the Manager's `POST /api/fleet/ai-text` (fleet token, `ai-assist` licence; dcm's own Tools in-process through `globalThis[Symbol.for('domma.ai-text')]`; Claude Haiku 5.5 in `tools/launcher-chat`), one route for every task: `themes` (survey answers, campaign replies, feedback or support requests), `subjects`, `draft`, `rewrite` (shorter, friendlier, more formal, clearer, simpler; every placeholder kept), `summary` (a document, an email thread or a support request), `reply` (a support or email reply), `seo` and `structured`. **One allowance: 500 requests per site per month, shared by every Tool** (`data/ai-text-usage.json`, counts only); Surveys' answer summaries, which had 300 of their own, now draw on it (`POST /api/fleet/survey-themes` unchanged; the month's survey counts carried across). Used by Surveys 1.19.0, Campaigns Pro 1.13.0, Email 0.18.0, Docs Pro 0.15.0 and SEO Pro 0.9.0 on sites, and Feedback 1.4.0 and Support 1.3.0 on the Manager only (those two are customer-to-Domma Tools, so their AI runs on the receiving side). Every one needs AI Assist (Pro plan), shows only when the site has it, asks once per visit before anything is sent, says how much of the month is used after each request, and never sends, saves or publishes anything by itself.
|
|
1269
1271
|
- Della's AI answers (unreleased; Pro plan, hosted sites): when the matcher says `none`, `services/chat/ai.js` `aiAnswer()` asks the Manager (`MANAGER_URL` + `FLEET_TOKEN`, `POST /api/fleet/launcher-chat`; on dcm the in-process registry `Symbol.for('domma.launcher-chat')`) with the site's name, `assistantBrief()` (site.json `assistant.context`/`rules` from Site Settings > General > AI assistant, plus the launcher's `chat.aiContext`/`aiRules`), the enabled non-sample Knowledge (most used first, 48,000 characters), the last 10 visitor/bot messages and the question. A non-empty answer is stored as a bot message with `ai: true` (`misses` reset); empty or refused falls back to the usual "do not know". The question is still logged as unanswered. A 403 (no licence) backs off 10 minutes, a 429 (month used) 30 minutes, anything else 1 minute. Per launcher `chat.ai` (default on), `chat.aiUseSite` (default on; off = the launcher's own context only - the site's rules always apply), `chat.aiMaxPerChat` (20; `aiCount` on the session); the default bot name is now Della. A character's chat is called by the character's name, or by `chat.characterName` when set (admin: **Call her** under Use Della) - `characterChat()` in `public/js/characters.mjs` - so Della can be "Dash" on one launcher with her own artwork. Packs in `CHARACTERS`: dot, daisy, della, dash (Job Board) and remy (health care, Regimen; unreleased), each a 3x2 atlas in `public/images/characters/<id>-poses.png`. `aiContext`/`aiRules` never reach the page (`publicLauncher`). `/api/chat/config` says `ai` so the panel can say Della is an AI assistant. Manager side: `plugins/site-manager/services/launcherChatRoutes.js` (fleet token, the `ai-site-builder` licence, 2,000 answers per site per month counting "do not know", 4 at once) and `tools/launcher-chat` (Claude Haiku 5.5, low effort; fixed cached system prompt, then the owner's context and rules as a second system block; the visitor's words only in the user message; `LAUNCHER_CHAT_ANTHROPIC_KEY` read by the job alone).
|
|
1270
1272
|
- Saved chats (unreleased): preset `chat-saved` (in `CHAT_PRESET_SLUGS`, `chats.manage` through the generic API, kept out of site repos) - a copy of a chat with `note`, `outcome` (to look at / looking into it / done), visitor, page, dates, who saved it, `transcript` (plain text) and `messages`. `POST /api/chats/:id/save` (reply), `GET /api/chats/saved` and `/saved/:sid` (read), `PUT /saved/:sid` (reply; note, outcome), `DELETE /saved/:sid` (manage); at most 2,000 per site. Chats inbox: a **Saved** tab, the context-menu item **Save for a closer look…**, and an outcome/note bar on an open saved chat (`services/chat/saved.js`, `arrangeSaved()`).
|
|
1271
1273
|
- Visitor panel look (unreleased): bot and staff avatars, runs of messages grouped (name on the first, avatar on the last), gradient visitor bubbles, soft chips for links and choices, a rounded composer with the send button inside, messages easing in (still for reduced motion), and in a launcher panel the bot's avatar (with a dot while someone answers) and the status under the title. Panel 400 x 600. Per-chat branding: `chat.accent` / `chat.accentText` (a theme token or hex, `launcherColour`) and `chat.avatar` (a site address only, `launcherAvatar()`), in the page's chat block and `/api/chat/config`; the panel sets `--chat-accent` / `--chat-accent-text` on itself (`launcherChatAccentCss()`: a hex accent with no text colour gets black or white by contrast, a token its `--dm-<token>-text`), and the bot's picture replaces its initial in the heading, the typing row and its messages.
|
|
@@ -2032,7 +2034,7 @@ A document editor inside the admin. Documents are private until shared: share wi
|
|
|
2032
2034
|
|
|
2033
2035
|
### Docs Pro (`docs-pro`)
|
|
2034
2036
|
|
|
2035
|
-
Tier: paid (closed source) · Version: 0.
|
|
2037
|
+
Tier: paid (closed source) · Version: 0.15.0 · Requires: Domma CMS 1.67.2+ (`minCmsVersion`); `docs` 2.6+ (2.8+ for context editing; feature-detected); no MongoDB (Spaces, pages and cloud copy settings are JSON files under the plugin's `data/`); optional `puppeteer-core` + a host Chrome for PDF copies · Adds to Docs through its registry (no `supersedes`)
|
|
2036
2038
|
|
|
2037
2039
|
**Domma Spaces**: publish a Docs folder as a section of the site - a staff handbook, help centre or set of guides - with a page tree, search and a Kindle-style reader. Pages are snapshots: a document reaches the site only when published, and later edits stay private until it is published again. A lapsed licence takes the Spaces offline; documents in Docs are untouched and Spaces are kept.
|
|
2038
2040
|
|
|
@@ -2058,12 +2060,13 @@ Tier: paid (closed source) · Version: 0.8.0 · Requires: `docs` 2.6+ (2.8+ for
|
|
|
2058
2060
|
- **Suggested changes** (0.5.0): **Suggest changes** on the document menu (owners and editors) or share as **Suggester** - typing becomes green underlined insertions, deleting strikes words in red, typing over a selection is one replacement; formatting and layout are off while suggesting; its own undo. **Suggestions** panel and chip: who, when, what ("Replace X with Y"), Accept / Reject / all (while editing), Take back for the author; click to find it. The server only saves a Suggester's own suggestions (checked against the stored text). Owner notified of new suggestions, authors when theirs are reviewed (source `docs-pro:suggestions`). Suggestions never reach readers until accepted.
|
|
2059
2061
|
- **Context editing in the body** (0.7.0): right-click selected words while editing - bold, italic, underline, strikethrough, highlight, link, clear formatting, or Comment on the selection, right there in the page. The td/th table menu still wins inside tables; with nothing selected the browser's own menu (spellcheck) opens; while suggesting only Comment is offered. Needs Docs 2.8.0 (`editor.applyNamed`).
|
|
2060
2062
|
- **Ready-made templates** (0.6.0): twelve in Docs' Templates place - Letter, Quote, Proposal, Simple service agreement, Meeting notes, Project brief, Weekly update, Policy, How-to procedure, Handbook page, Job description, Press release - most with merge fields, so using one opens Fill in the fields at once (Your name prefilled). In-app help popovers on the Comments, Suggestions and Fill-in panels.
|
|
2063
|
+
- **Summarise this document** (0.15.0, with AI Assist): in the document editor's ⋮ menu for anyone who can edit the document (wiki pages too, as they open in the same editor). Claude reads the title and text (email addresses masked; nothing about who owns or shares it; no pictures) and writes a short summary with up to five key points, inserted at the top as an ordinary quote block headed "Summary" with a line saying AI Assist wrote it - edit, move or delete it like any text, Undo takes it out, and it is saved when the document is. Summarising again replaces a summary that is still first on the page, after asking. Not offered while suggesting, for PDF documents, documents in Trash or protected wiki pages; documents under about 200 characters are not summarised. `GET /api/plugins/docs-pro/ai`, `POST /api/plugins/docs-pro/summary/:docId`. Asks once per visit; counts towards the shared AI Assist allowance.
|
|
2061
2064
|
|
|
2062
2065
|
**Where:** Docs -> **Spaces**, **Cloud copies** and **Signatures** in the rail (`#/plugins/docs`); the reader at `/spaces`, `/spaces/<space>`, `/spaces/<space>/<page>`, `/spaces/<space>/search?q=`; the sign-in return address `/api/plugins/docs-pro/cloud/oauth/callback`; guide under **Documentation > Plugins > Docs Pro**.
|
|
2063
2066
|
|
|
2064
2067
|
### Email (`email-pro`)
|
|
2065
2068
|
|
|
2066
|
-
Tier: paid (closed source) · Version: 0.
|
|
2069
|
+
Tier: paid (closed source) · Version: 0.18.0 · Requires: MongoDB for the message store's extras (without it reading, starring, moving, deleting, folders and sending still work; search, conversations, rules, undo send, send later, snooze and the away message need MongoDB and say so); npm `imapflow` ^2.0.5, `mailparser` ^3.9.28, `nodemailer` 8.0.5; `minCmsVersion` 1.34.0 (Contacts switch-off handling core 0.88) · Uses: `contacts` (recipient suggestions and group expansion in compose; Add sender to contacts) · Supersedes: `mail-reader`
|
|
2067
2070
|
|
|
2068
2071
|
A full email client in the admin: connect your own IMAP mailboxes, read, write, send, search and file mail. Chosen folders are mirrored (envelopes and flags, never bodies) into MongoDB so big mailboxes open instantly, and on top come identities, templates, rules, an away responder, undo send, send later, snooze, threads and one-click hand-off of messages into the CMS.
|
|
2069
2072
|
|
|
@@ -2083,8 +2086,11 @@ A full email client in the admin: connect your own IMAP mailboxes, read, write,
|
|
|
2083
2086
|
- Unsubscribe: RFC 8058 one-click performed server-side; other methods handed back to open or compose.
|
|
2084
2087
|
- Hand-off to the CMS: save an attachment to Media, turn a message into a draft page, file a message as a collection entry; Add sender to contacts.
|
|
2085
2088
|
- Emails on a contact's card (0.9.0, engine 1.8.8+): the contact slideover in Contacts (and Contacts Pro) lists your ten newest emails to or from the contact's main, billing and additional addresses - Received/Sent, unread, and the mailbox when you have several - each opening the message in Email. Your own mailboxes and mirrored folders only; needs MongoDB, and is absent without it.
|
|
2089
|
+
- **AI Assist (0.18.0)**: **Summarise** above a message (a short summary of the conversation and what is still waiting on you; not saved), **Suggest a reply** with an optional "What do you want to say?" (opens in the reply window above the quoted message, with the mailbox's own signature - the suggestion leaves the sign-off to it - and unknowns left as [square-bracket notes]; never sent by itself), **Draft from a few words** in an empty message (body, and the subject if blank) and **Rewrite** (shorter, friendlier, more formal, clearer; only your own words, with Undo or Keep). Before anything goes, quoted earlier messages (HTML and many languages), signatures and contact blocks, greetings and sign-offs, email addresses, phone numbers, street addresses, postcodes and the people's names are taken out (Rewrite puts names, addresses and numbers back afterwards; more than 10 different ones cannot be rewritten); headers and display names are never sent; encrypted mail never is. Nothing is read for AI Assist until the user has agreed in that visit. Routes `/api/plugins/email-pro/ai`, `/ai/check`, `/ai/summary`, `/ai/reply`, `/ai/draft`, `/ai/rewrite` (`routes/ai.js`). Counts towards the shared allowance.
|
|
2090
|
+
- **Replies for Campaigns Pro (0.18.0)**: Campaigns Pro can summarise the replies to a campaign sent from the mailbox - Email finds them in that mailbox's inbox by the Message-IDs they answer and hands over only their words and dates, never who wrote them; out-of-office answers are left out and nothing is marked read or moved.
|
|
2086
2091
|
- Keyboard shortcuts: j/k or arrows to move, Enter open, u read/unread, s star, r reply, Shift+R or a reply all, f forward, c compose, `/` search, x select, Shift+A select all, `!` spam, `#` or Delete delete, Esc, `?` help.
|
|
2087
2092
|
- Sidebar badge (`/unread`): unread in Inbox (counted from the store).
|
|
2093
|
+
- **Branding (unreleased)**: Settings > **Branding** keeps up to 20 personal brandings - header artwork (width, position, description, strapline, header background), a backdrop (solid colour, 15 gradients - Surveys' 8 plus Midnight, Navy, Teal, Sand, Rose gold, Charcoal and Aurora - a pattern, or a picture darkened and blurred on the server), font (safe fonts and Google web fonts with named fallbacks) and weight, text/accent/message colours, and a footer (plain, an accent band, or an overlay on the backdrop) with photo, name, role, company, return email, phone, website, up to four links, address and small print. Pictures come from Media, the File Store or an upload (resized, metadata stripped, served publicly at an unguessable address). Which branding a message gets: chosen in the compose window, else the first To recipient's address, domain or Contacts company, else the sender's (per identity), else the general default. New messages get the full design (600px fluid tables, a solid colour under every gradient/picture for Outlook); replies and forwards only the contact line. Branded on Send, before Undo/Send later. The compose window's Branding row uses the core `extensions.compose` hook (domma-mail compose window); older cores brand automatically with no picker. Routes `/api/plugins/email-pro/branding*`.
|
|
2088
2094
|
- Notifications to the mailbox owner only: `email-pro:mailbox` (warning after 5 failed checks in a row; resolved when a check works) and `email-pro:sending` (a scheduled/undo-send message that failed).
|
|
2089
2095
|
- Permission `email` (read = Use: add own mailboxes, read and send) granted to `admin`.
|
|
2090
2096
|
|
|
@@ -2092,7 +2098,7 @@ A full email client in the admin: connect your own IMAP mailboxes, read, write,
|
|
|
2092
2098
|
|
|
2093
2099
|
### Feedback (`feedback`)
|
|
2094
2100
|
|
|
2095
|
-
Tier: free (ships with the engine) · Version: 1.
|
|
2101
|
+
Tier: free (ships with the engine) · Version: 1.4.0 · Requires: a site started by the fleet manager (`MANAGER_URL` + `FLEET_TOKEN`) to send; nothing declared · Uses: Waypoint Pro on the manager (feature-detected) · No MongoDB
|
|
2096
2102
|
|
|
2097
2103
|
Admins of a managed site tell Domma what is broken, missing or good, straight from their admin, and see what became of it - seen, planned, in progress, done or not planned, with Domma's reply. One plugin, two sides: on a site it is "Send feedback" plus that site's reports; on the Manager (dcm) it is the inbox for every site's reports.
|
|
2098
2104
|
|
|
@@ -2105,11 +2111,25 @@ Admins of a managed site tell Domma what is broken, missing or good, straight fr
|
|
|
2105
2111
|
- **The Manager's Super Admin can file feedback (1.1.0)**: on the manager, the level-0 role (whatever it is called) also gets a **My feedback** tab (`#/plugins/feedback/mine`) that files its own reports straight into the inbox as "Manager (this server)", after which they are ordinary reports (status, reply, notes, Waypoint).
|
|
2106
2112
|
- A standalone site (not started by a manager) is told it has nowhere to send to.
|
|
2107
2113
|
- Dates read dd/mm/yyyy (1.1.1).
|
|
2114
|
+
- **Summarise (1.4.0, the Manager only, with AI Assist)**: above the inbox list, groups the reports in view (following the status, type, site and search filters; at least two, up to 1,000 newest first) into themes with counts and a few quotes. Only titles and descriptions are sent - no site names or addresses, people's names, email addresses or files; greetings and sign-offs left out. Asks once per visit; the latest summary stays on the screen until the next one or until a report it read is deleted. Sites see no change. Counts towards the Manager's AI Assist allowance.
|
|
2108
2115
|
- Permission `feedback` with `send` (send and see this site's reports; on the manager, the level-0 role only) and `manage` (the manager's inbox), granted to `admin`.
|
|
2109
2116
|
- Collection `feedback-reports` on the manager only, with all four API verbs off (reports carry admins' names and emails).
|
|
2110
2117
|
|
|
2111
2118
|
**Where:** Admin sidebar "Feedback" (`#/plugins/feedback`). Since: core 0.92.0 (1.0.0), 1.1.0 (the manager's own feedback).
|
|
2112
2119
|
|
|
2120
|
+
### Support (`support`)
|
|
2121
|
+
|
|
2122
|
+
Tier: free (ships with the engine) · Version: 1.3.0 · Requires: a site started by the fleet manager to send (a standalone install gets the contact card only) · No MongoDB
|
|
2123
|
+
|
|
2124
|
+
Help from Domma without leaving the admin. On a site: Domma's contact card (email, phone, hours, how quickly to expect an answer) and requests that are conversations with the Domma team, with the user's name, the site and its CMS version attached, urgent ones first. On the Manager: the inbox for every site's requests.
|
|
2125
|
+
|
|
2126
|
+
**Features**
|
|
2127
|
+
- Ask for help: what it is about, subject, message, Normal or Urgent, optional Where, up to 3 files (2 MB each: PNG, JPEG, GIF, WebP, PDF or text); replies in the same request, with a notice when Domma answers. A request is kept safe if the Manager cannot be reached and sent as soon as it can (20 requests and replies per site in 10 minutes).
|
|
2128
|
+
- A new request or a customer's reply is emailed to the Domma support address (the customer as Reply-To, `[URGENT]` in the subject when urgent); the Support settings cog sets the contact card, that address and the per-site limit.
|
|
2129
|
+
- **AI Assist (1.3.0, the Manager only)**: **Summarise** above an open request's conversation (what the customer needs, where it stands and the open points; kept with the request, and says when the conversation has moved on), **Suggest a reply** beside Send reply (fills the reply box to edit and send yourself; asks before replacing text) and **Summarise** on the Waiting on Domma tab (those requests, not archived ones, grouped into themes). Only the conversation's words are sent - no site names or addresses, people's names, email addresses, phone numbers or files; greetings, sign-offs, quoted emails and signatures left out. Asks once per visit. Sites see no change.
|
|
2130
|
+
|
|
2131
|
+
**Where:** Admin sidebar "Support" (`#/plugins/support`).
|
|
2132
|
+
|
|
2113
2133
|
### Garage (`garage`)
|
|
2114
2134
|
|
|
2115
2135
|
Tier: paid (closed source) · Version: 1.4.3 · Requires: a DVLA Vehicle Enquiry Service API key; no MongoDB (uses the collections service, file or MongoDB); no `minCmsVersion` declared · Uses: none declared
|
|
@@ -2324,7 +2344,7 @@ Everything in Security, plus the protections a busy or high-value site needs: tw
|
|
|
2324
2344
|
|
|
2325
2345
|
### SEO Pro (`seo-pro`)
|
|
2326
2346
|
|
|
2327
|
-
Tier: paid (closed source) · Version: 0.
|
|
2347
|
+
Tier: paid (closed source) · Version: 0.9.0 · Requires: `seo` (the built-in SEO Tool); `minCmsVersion` 1.24.0 · Uses: nothing declared · No MongoDB
|
|
2328
2348
|
|
|
2329
2349
|
An add-on for the SEO Tool built into Domma CMS. It brings Google Search Console into the admin, adds structured data for rich results, finds content problems (links you should add, pages competing for the same search, readability, near duplicates, heavy images), lets you edit every title and description in one grid, moves an old site's addresses across as redirects, logs visitors' dead ends with one-click redirects, and checks every link on a schedule with history and alerts.
|
|
2330
2350
|
|
|
@@ -2340,6 +2360,7 @@ An add-on for the SEO Tool built into Domma CMS. It brings Google Search Console
|
|
|
2340
2360
|
- Pro settings slideover (from the Not found tab): not-found logging, keep days, ignore list, count bots; monitor interval, external checks, external cap, slow threshold; notification thresholds; fleet reporting.
|
|
2341
2361
|
- Notifications (admins): `seo-pro:broken` (newly broken links), `seo-pro:score` (score fell by 10+), `seo-pro:notfound` (a missing page visited 20+ times in a day).
|
|
2342
2362
|
- Fleet: sites report counts (score, pages, broken, orphans, 404s, redirects) every 30 minutes to the manager; Fleet tab on the manager only.
|
|
2363
|
+
- **AI Assist (0.9.0)**: Bulk's **Suggest** writes titles, descriptions and up to three focus keyphrase ideas from the pages' own words, for the ticked rows (up to 10) or the next 10 under Title or description to fix, in one request - they go into the grid as unsaved changes marked "suggested", never over a cell the user typed in, and keyphrase ideas are a click under the focus box. Rich results' **Fill from the page** fills a block's empty fields (and an FAQ's questions or a how-to's steps) from what the page says; not for templates. Content's **Make simpler** on a hard-going Readability row rewrites long and passive sentences, shown before and after with **Apply to the page**, **Copy** or **Drop**: Apply saves the page through the CMS as a new version and replaces only that exact sentence (nothing if it has changed); applies on one page queue one after another; sentences with links, formatting, shortcodes or markup characters, or on the page twice, are Copy only; shortcode and HTML tag contents, code and front matter are never read. Only the visible words of published pages open to everyone (with the title and focus keyphrase) are sent. Routes `/api/plugins/seo-pro/ai`, `/ai/seo`, `/ai/rich`, `/ai/simpler` (`server/ai-routes.js`), needing SEO Manage (Apply also Pages Update). Asks once per visit; the month's use is shown after each.
|
|
2343
2364
|
- Uses core SEO's `seo` permission (read/manage); no permission of its own. A lapsed licence leaves core SEO untouched.
|
|
2344
2365
|
|
|
2345
2366
|
**Where:** Tools > SEO (`#/seo/...`) - the Pro tabs appear in the built-in SEO screen, so they follow the core `seo` permission (level 0 and `admin` by default).
|
|
@@ -2495,7 +2516,7 @@ Targeted surveys on top of the Forms engine. Pick any form, choose an audience f
|
|
|
2495
2516
|
- **Delete a survey (1.18.0)** - Delete... in the menu or Delete survey in the editor (`DELETE /api/plugins/surveys/surveys/:slug`, permission `delete`): its invitation links stop at once; its answers stay with the form's submissions. A survey a Campaigns Pro campaign sends cannot be deleted until that campaign changes.
|
|
2496
2517
|
- **Branching (1.18.0)** - uses the form's own Conditional Logic and triggers from Data > Forms, on the survey page and when a submission is checked; a hidden question is never required.
|
|
2497
2518
|
- **Outreach group (1.18.0)** - Surveys and Campaigns Pro sit together under Outreach in the sidebar.
|
|
2498
|
-
- **Summarise answers (1.19.0)** - with AI Assist (Pro plan), a free-text question with two answers or more gets Summarise answers: Claude groups the answers into themes (title, what people said, how many said it, a few quotes) under a short summary. Follows the current Results filter. Asks once per visit before sending; only the survey's title, the question and the answers' text go to the AI - no names, emails or other parts of the responses. `POST /api/plugins/surveys/surveys/:slug/themes` (permission `update`; 400 under two answers, 422 when Claude declines). The last summary per question is kept on the survey (`summaries`, with when and the filter used), shows whenever Results opens and goes into the printed report; Summarise again replaces it.
|
|
2519
|
+
- **Summarise answers (1.19.0)** - with AI Assist (Pro plan), a free-text question with two answers or more gets Summarise answers: Claude groups the answers into themes (title, what people said, how many said it, a few quotes) under a short summary. Follows the current Results filter. Asks once per visit before sending; only the survey's title, the question and the answers' text go to the AI - no names, emails or other parts of the responses. `POST /api/plugins/surveys/surveys/:slug/themes` (permission `update`; 400 under two answers, 422 when Claude declines). The last summary per question is kept on the survey (`summaries`, with when and the filter used), shows whenever Results opens and goes into the printed report; Summarise again replaces it. Summaries share the site's AI Assist allowance of 500 requests a month with every other Tool (Manager 0.37.69; it had 300 of its own before), with the count shown in Results.
|
|
2499
2520
|
- Opens/Closes are days in the site's time zone (`timeZone` setting, default `Europe/London`): a survey takes answers from the start of its Opens day to the END of its Closes day. The hosted page, submissions, scheduler reminders, Send (409 once closed), the list chip, the badge and the closing notices all use the same rule (1.4.4).
|
|
2500
2521
|
- Shortcode `[survey slug="..." /]` - embeds the survey on any page; Copy embed shortcode copies exactly this, and the page gets the survey script added automatically (1.4.4).
|
|
2501
2522
|
- Results (`#/plugins/surveys/results/:slug`): invited, answered, response rate, per-question aggregates (only this survey's responses, tagged `survey:<slug>`); Export CSV and Export JSON; anonymous flag.
|
|
@@ -2550,7 +2571,7 @@ An issue tracker in the style of Jira: projects with their own workflows, issues
|
|
|
2550
2571
|
|
|
2551
2572
|
### Campaigns Pro (`campaigns-pro`)
|
|
2552
2573
|
|
|
2553
|
-
Tier: paid (closed source) · Version: 1.
|
|
2574
|
+
Tier: paid (closed source) · Version: 1.13.1 · Requires: Domma CMS 1.67.2+ (`minCmsVersion`); the site's email set up for sends; no MongoDB · Uses: `contacts` (import the audience), `analytics-pro` (UTM-tagged landings appear in Sources), `shopping-cart-pro` (linked discount codes), `surveys` (send a survey as a campaign); shares the outreach store (audience, opt-outs) with Surveys
|
|
2554
2575
|
|
|
2555
2576
|
**Campaigns Pro 1.0.0 - one paid Tool (2026-10-13).** The free Campaigns Tool was folded in at Darryl's request; there is no free tier. A campaign is an audience, a message and optionally an offer. Offers close by an end date OR a claim limit, first reached; claims are a locked ledger that can never overshoot. Every email carries a working unsubscribe link feeding the shared opt-out list Surveys also honours. Sends are batched, schedulable (within a quarter of an hour) and resume safely after a restart. Claim page at `/campaign/<slug>` plus a `[campaign-offer]` embed.
|
|
2556
2577
|
|
|
@@ -2564,6 +2585,12 @@ Measurement and automation: a Performance screen per campaign - reached, opened
|
|
|
2564
2585
|
|
|
2565
2586
|
**Blocks and tags in campaign emails (unreleased, 2026-11-13).** Insert block or tag in the campaign editor (body, header, footer) writes a page tag into the message: a site block, or one of the static tags (button, link, card, box, banner, badge, grid, row, spacer, center, text, hero, table, listgroup). At send time, in Preview email and in a test send, each tag is rendered by the engine's own renderer and then turned into email HTML: styles inlined from a small email stylesheet plus the block's own CSS, theme tokens resolved against the site's light theme, grids and flex rows made into tables, icons, scripts and forms removed. Interactive tags (tabs, carousels, forms, collections, embeds, effects) are never rendered - typed by hand they stay as text. Merge fields work inside tags (`[button href="{{link}}" … /]`). The email sanitiser still runs per recipient. Also: right-click or double-click a picture in the message to edit or remove it.
|
|
2566
2587
|
|
|
2588
|
+
**Writing help with AI Assist (1.13.0 and 1.13.1, 2026-11-16).** In the campaign editor's Message section: **Ideas** under the subject suggests five subject lines (also for an A/B test's second subject on Performance), **Write a first draft** turns a sentence or two and a tone (friendly, formal or plain) into a subject and message, asking before it replaces either (1.13.1: a draft uses only `{{name}}`, plus `{{code}}` and `{{link}}` with an offer - never `{{email}}` or a `{{link}}` with nothing behind it), and **Rewrite** makes the message shorter, friendlier, more formal or clearer, keeping `{{link}}` and every other double-brace field exactly (a suggestion that loses one is left out, with a note); **Undo** puts the message back. Only what the author wrote (or the brief) is sent, no recipient's details; nothing is saved or sent until the author saves. `GET /api/plugins/campaigns-pro/ai`, `POST /ai/subjects`, `/ai/draft`, `/ai/rewrite` (permission `update`).
|
|
2589
|
+
|
|
2590
|
+
**Summarise replies (1.13.0).** On Performance, for a campaign sent from the author's own mailbox: Email (0.18.0) finds the replies in that mailbox's inbox, quoted text, signatures, greetings, sign-offs, email addresses and phone numbers are taken out (anything else typed in a reply goes with it), and AI Assist groups the rest into themes with short quotes. The latest summary is kept on the campaign for colleagues; only the mailbox owner can summarise again. `GET`/`POST /api/plugins/campaigns-pro/campaigns/:slug/replies`. Mailbox campaigns now keep each copy's Message-ID (left out of the export) so replies can be traced; the card says why when it cannot help (site's sending, Email off or too old, not sent yet, sent before tracing).
|
|
2591
|
+
|
|
2592
|
+
**A check before sending (1.13.0).** Send now and saving as Scheduled first list anything worth a look: the personal link missing from an offer or survey campaign (or a claim-page link without it, or `{{code}}` without an offer), pictures without a description, more than 10 links, an empty, over-70-character, all-capitals or exclamation-heavy subject, and words spam filters dislike. Warnings only: Send anyway / Schedule anyway.
|
|
2593
|
+
|
|
2567
2594
|
**Where:** Admin sidebar "Campaigns Pro" (`#/plugins/campaigns-pro`); Performance per campaign at `#/plugins/campaigns-pro/performance/:slug`; the audience screen is shared with Surveys.
|
|
2568
2595
|
|
|
2569
2596
|
### Onboard Pro (`onboard-pro`)
|
|
@@ -2955,6 +2982,7 @@ Later changes to these features are in the CHANGELOG (for example 0.92.1: row-le
|
|
|
2955
2982
|
- Quotes and letters from a template with merge fields, filled from Contacts.
|
|
2956
2983
|
- Reviewing a policy with comments: comment on words, reply, resolve.
|
|
2957
2984
|
- Getting a contract reviewed: share as Suggester, then accept or reject their changes.
|
|
2985
|
+
- Putting a summary at the top of a long policy with Summarise this document, then checking and editing it before you share.
|
|
2958
2986
|
|
|
2959
2987
|
### Email (`email-pro`)
|
|
2960
2988
|
|
|
@@ -2962,6 +2990,8 @@ Later changes to these features are in the CHANGELOG (for example 0.92.1: row-le
|
|
|
2962
2990
|
- Inbox zero with rules (test before save), snooze and send later.
|
|
2963
2991
|
- Turning an enquiry email into a CMS page or a collection entry, and saving its attachment to Media.
|
|
2964
2992
|
- Setting an away message and checking it with the preview.
|
|
2993
|
+
- Catching up on a long thread with Summarise, then answering with Suggest a reply and a note of what to say.
|
|
2994
|
+
- Tidying a hurried email with Rewrite (friendlier, clearer), and what AI Assist does and does not send.
|
|
2965
2995
|
|
|
2966
2996
|
### Feedback (`feedback`)
|
|
2967
2997
|
|
|
@@ -3030,6 +3060,8 @@ Later changes to these features are in the CHANGELOG (for example 0.92.1: row-le
|
|
|
3030
3060
|
- Relaunching a site: importing the old sitemap as redirects.
|
|
3031
3061
|
- Adding FAQ and Product rich results and testing them in Google.
|
|
3032
3062
|
- Weekly routine: Not found log, Monitor broken links, Content link suggestions.
|
|
3063
|
+
- Filling missing titles and descriptions ten pages at a time with Bulk's Suggest, checking each before saving.
|
|
3064
|
+
- Making a hard-going page easier to read with Make simpler: Apply, Copy or Drop.
|
|
3033
3065
|
|
|
3034
3066
|
### Booking (`booking`)
|
|
3035
3067
|
|
|
@@ -3065,6 +3097,8 @@ Later changes to these features are in the CHANGELOG (for example 0.92.1: row-le
|
|
|
3065
3097
|
### Campaigns Pro (`campaigns-pro`)
|
|
3066
3098
|
|
|
3067
3099
|
- A first campaign: audience from Contacts, an offer that closes at 50 claims, and reading the results.
|
|
3100
|
+
- Writing a campaign with AI Assist: a first draft from a brief, Rewrite, subject Ideas, and the check before sending.
|
|
3101
|
+
- Reading what people replied: Summarise replies on a campaign sent from your own mailbox.
|
|
3068
3102
|
|
|
3069
3103
|
### Onboard Pro (`onboard-pro`)
|
|
3070
3104
|
|
|
@@ -3080,6 +3114,7 @@ Later changes to these features are in the CHANGELOG (for example 0.92.1: row-le
|
|
|
3080
3114
|
- Running an anonymous staff survey - and what anonymity does and does not guarantee.
|
|
3081
3115
|
- Automating reminders with an external scheduler and the service token.
|
|
3082
3116
|
- Embedding a survey on a page with `[survey]`.
|
|
3117
|
+
- Summarising free-text answers into themes with AI Assist, and reading the answers before acting on them.
|
|
3083
3118
|
|
|
3084
3119
|
### Theme Roller (`theme-roller`)
|
|
3085
3120
|
|
package/package.json
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/body-menu.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/**
|
|
4
4
|
* The reading pane's right-click menu - the pure parts.
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/cms-host.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/** The CMS shell boundary. Standalone never imports this adapter. */
|
|
4
4
|
const version = new URL(import.meta.url).searchParams.get('v') ?? '1';
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/compose-window.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
const MAIL_MODULE_VERSION = new URL(import.meta.url).searchParams.get('v') ?? '1';
|
|
4
4
|
const {createMailHost} = await import(new URL(`./host-context.js?v=${MAIL_MODULE_VERSION}`, import.meta.url).href);
|
|
@@ -270,6 +270,7 @@ export function createComposeWindow(mailHost) {
|
|
|
270
270
|
<label class="form-label">Subject</label>
|
|
271
271
|
<input type="text" class="form-input" data-ref="subject">
|
|
272
272
|
</div>
|
|
273
|
+
<div class="mail-compose-extension" data-ref="extension" hidden></div>
|
|
273
274
|
<div class="mail-compose-body">
|
|
274
275
|
<label class="form-label">Message</label>
|
|
275
276
|
<div class="flex items-center gap-2 mail-template-row" data-bind-hidden="!hasTemplates">
|
|
@@ -336,7 +337,8 @@ export function createComposeWindow(mailHost) {
|
|
|
336
337
|
draft: opened = {}, base, accountId, api, maxAttachmentBytes = 20_000_000,
|
|
337
338
|
onSent = () => {}, onSaved = () => {}, onQueued = () => {}, contacts = [],
|
|
338
339
|
identities = [], mailboxAddress = '', templates = [], undoSeconds = 0,
|
|
339
|
-
mode = 'new', defaults = null, security = null, prefs = {}, capabilities = {}
|
|
340
|
+
mode = 'new', defaults = null, security = null, prefs = {}, capabilities = {},
|
|
341
|
+
composeExtension = null
|
|
340
342
|
}) {
|
|
341
343
|
// How this message was started, decided once. A reopened draft is never
|
|
342
344
|
// treated as new: it already carries the signature it was written with,
|
|
@@ -538,6 +540,7 @@ export function createComposeWindow(mailHost) {
|
|
|
538
540
|
|
|
539
541
|
fromSelect.addEventListener('change', () => {
|
|
540
542
|
currentIdentity = findIdentity(identities, fromSelect.value);
|
|
543
|
+
tellExtension('identityChanged', currentIdentity);
|
|
541
544
|
// The signature in the body belongs to whoever was sending a
|
|
542
545
|
// moment ago. Swapped where it can be found and left alone where
|
|
543
546
|
// it cannot - see `swapSignature`.
|
|
@@ -708,6 +711,69 @@ export function createComposeWindow(mailHost) {
|
|
|
708
711
|
: 'Discard this message? It has not been saved as a draft.';
|
|
709
712
|
}
|
|
710
713
|
|
|
714
|
+
// ---- An edition's compose extension --------------------------------
|
|
715
|
+
//
|
|
716
|
+
// `composeExtension(context)` (createReaderView's `extensions.compose`)
|
|
717
|
+
// may draw into its own slot above the message and answer extra fields
|
|
718
|
+
// for Save and Send. It is told when the sender or the recipients
|
|
719
|
+
// change, and when the window closes. Anything it throws is logged and
|
|
720
|
+
// costs the extension, never the message.
|
|
721
|
+
let extension = null;
|
|
722
|
+
const RESERVED = new Set(['to', 'cc', 'bcc', 'subject', 'body', 'html', 'attachments', 'identityId',
|
|
723
|
+
'inReplyTo', 'references', 'sourceMessage', 'sign', 'encrypt', 'priority', 'readReceipt',
|
|
724
|
+
'deliveryReceipt', 'sendAt', 'replaces']);
|
|
725
|
+
function tellExtension(name, ...args) {
|
|
726
|
+
try { extension?.[name]?.(...args); } catch (err) { console.warn(`[mail] compose extension ${name} failed:`, err); }
|
|
727
|
+
}
|
|
728
|
+
function extensionFields() {
|
|
729
|
+
try {
|
|
730
|
+
const fields = extension?.fields?.();
|
|
731
|
+
if (!fields || typeof fields !== 'object') return {};
|
|
732
|
+
return Object.fromEntries(Object.entries(fields).filter(([key]) => !RESERVED.has(key)));
|
|
733
|
+
} catch (err) {
|
|
734
|
+
console.warn('[mail] compose extension fields failed:', err);
|
|
735
|
+
return {};
|
|
736
|
+
}
|
|
737
|
+
}
|
|
738
|
+
function startExtension() {
|
|
739
|
+
if (typeof composeExtension !== 'function') return;
|
|
740
|
+
const slot = ref('extension');
|
|
741
|
+
let timer = null;
|
|
742
|
+
const recipientsChanged = () => {
|
|
743
|
+
clearTimeout(timer);
|
|
744
|
+
timer = setTimeout(() => tellExtension('recipientsChanged', recipients()), 400);
|
|
745
|
+
};
|
|
746
|
+
const recipients = () => ({
|
|
747
|
+
to: textToAddresses(toInput.value),
|
|
748
|
+
cc: textToAddresses(ccInput.value),
|
|
749
|
+
bcc: textToAddresses(bccInput.value)
|
|
750
|
+
});
|
|
751
|
+
try {
|
|
752
|
+
extension = composeExtension({
|
|
753
|
+
slot,
|
|
754
|
+
accountId,
|
|
755
|
+
api,
|
|
756
|
+
base,
|
|
757
|
+
mode: openedAs,
|
|
758
|
+
isReply: Boolean(draft.inReplyTo) || openedAs === 'forward',
|
|
759
|
+
draft: opened,
|
|
760
|
+
identity: () => currentIdentity,
|
|
761
|
+
recipients,
|
|
762
|
+
show: (on = true) => { slot.hidden = !on; },
|
|
763
|
+
helpPopovers: (root) => helpPopovers?.(root)
|
|
764
|
+
}) ?? null;
|
|
765
|
+
} catch (err) {
|
|
766
|
+
console.warn('[mail] compose extension failed to start:', err);
|
|
767
|
+
extension = null;
|
|
768
|
+
return;
|
|
769
|
+
}
|
|
770
|
+
for (const input of [toInput, ccInput, bccInput]) {
|
|
771
|
+
input.addEventListener('input', recipientsChanged);
|
|
772
|
+
input.addEventListener('change', recipientsChanged);
|
|
773
|
+
}
|
|
774
|
+
closedListeners.push(() => clearTimeout(timer));
|
|
775
|
+
}
|
|
776
|
+
|
|
711
777
|
/**
|
|
712
778
|
* The message as it currently stands.
|
|
713
779
|
*
|
|
@@ -740,7 +806,11 @@ export function createComposeWindow(mailHost) {
|
|
|
740
806
|
references: draft.references ?? [],
|
|
741
807
|
sourceMessage: draft.sourceMessage ?? null,
|
|
742
808
|
attachments: attachments.peek().map(({filename, contentType, content}) =>
|
|
743
|
-
({filename, contentType, content}))
|
|
809
|
+
({filename, contentType, content})),
|
|
810
|
+
// An edition's own fields (Email Pro's branding). Spread last
|
|
811
|
+
// but never over the message itself: a hook that names `to` or
|
|
812
|
+
// `html` is ignored for that key.
|
|
813
|
+
...extensionFields()
|
|
744
814
|
};
|
|
745
815
|
}
|
|
746
816
|
|
|
@@ -1056,6 +1126,7 @@ export function createComposeWindow(mailHost) {
|
|
|
1056
1126
|
// Before the editor: it closes an open menu (left on <body> by a
|
|
1057
1127
|
// Ctrl+Enter send) and drops its dropdowns and window listener.
|
|
1058
1128
|
fontControls?.destroy();
|
|
1129
|
+
tellExtension('close');
|
|
1059
1130
|
editor?.destroy?.();
|
|
1060
1131
|
stopResizing();
|
|
1061
1132
|
for (const suggester of suggesters) suggester.destroy?.();
|
|
@@ -1072,6 +1143,8 @@ export function createComposeWindow(mailHost) {
|
|
|
1072
1143
|
setTimeout(() => { try { slideover.element?.remove(); } catch { /* gone */ } }, 400);
|
|
1073
1144
|
});
|
|
1074
1145
|
|
|
1146
|
+
startExtension();
|
|
1147
|
+
|
|
1075
1148
|
return {
|
|
1076
1149
|
/** Whether closing would lose something the reader wrote. */
|
|
1077
1150
|
dirty: () => !closed && unsaved(),
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/contacts.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/**
|
|
4
4
|
* Recipient suggestions from the host address book.
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/diagnostics-section.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/**
|
|
4
4
|
* The settings section that answers "which build is this, and what went wrong".
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/drag-drop.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/** Drag identities include the mailbox and source folder: UIDs alone are not unique. */
|
|
4
4
|
const PROTECTED_USES = new Set(['\\Inbox', '\\Sent', '\\Drafts', '\\Trash', '\\Junk', '\\Archive', '\\All', '\\Flagged']);
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/folder-tree.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/**
|
|
4
4
|
* Mail folder presentation, shared by the Mail Reader and Email Pro.
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/font-controls.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
const MAIL_MODULE_VERSION = new URL(import.meta.url).searchParams.get('v') ?? '1';
|
|
4
4
|
/**
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/fonts.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/**
|
|
4
4
|
* The fonts and sizes the mail editor offers - pure, so both the compose
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/host-context.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/** Services supplied by the application that hosts the shared mail interface. */
|
|
4
4
|
export function createMailApi({getToken, fetch: request = globalThis.fetch, onUnauthorized = () => {}}) {
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/identity.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/**
|
|
4
4
|
* Who a mailbox sends as, and what it signs off with.
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/image-senders-section.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/**
|
|
4
4
|
* The settings section for senders whose images always load.
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/keyboard.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/**
|
|
4
4
|
* Keyboard navigation for the reader.
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/message-actions.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/**
|
|
4
4
|
* What other Tools add to a message's menu - Booking's "Book Sam...".
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/oauth-panel.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/**
|
|
4
4
|
* "Sign in with Microsoft / Google" for a mailbox - the part of the mailbox
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/panes.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/**
|
|
4
4
|
* Pane sizing for the mail reader, shared by the Mail Reader and Email Pro.
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Source: @domma-mail/core 0.
|
|
1
|
+
// Source: @domma-mail/core 0.31.0, packages/core/src/admin/mail/reader-kit.js.
|
|
2
2
|
// Update with domma-mail/scripts/sync-cms.mjs; edit the shared source.
|
|
3
3
|
/**
|
|
4
4
|
* The reader view's decisions that need no DOM - escaping, the mailbox form's
|