Design notes on email digests

Keyboard access and screen-reader labels were part of the work, not a follow-up. We are watching the numbers for a week before turning it on by default. The change is backwards compatible, so integrations built against the old shape carry on unchanged.

Step by step

We rewrote this part rather than patching it, because the old approach ran out of room. Anything already in flight when this went out finishes under the old path. There is nothing to do on your side; the change is already in front of you.

1. Enable an offline mode.
2. Enable Zapier triggers.
3. Enable a Linear two-way sync.
4. Enable role-based permissions.

Limits

Two long-standing reports close with this, and both are linked below. It works the same way on the public site and inside the widget, with no configuration to turn on. Large workspaces should see the biggest difference, since the old query grew with the number of items.

1. Enable dark mode.
2. Enable webhook retries.
3. Enable vote weighting.
4. Enable Slack notifications.

Common pitfalls

It shipped behind a flag first, so a handful of workspaces have been on it for a fortnight. It is slower on the first load and faster on every one after.

Next steps

Thanks to everyone who filed a report with steps; several of them pointed straight at the cause. We will fold the remaining cases in once we have seen this one hold.

1. Enable role-based permissions.
2. Enable granular email preferences.

curl -sS https://api.example.test/v2/posts \
  -H "Authorization: Bearer $BULLETIN_API_KEY"