Internal notes on posts
The limit is generous enough that most teams will never meet it. Keyboard access and screen-reader labels were part of the work, not a follow-up.
Before you start
Existing setups keep working exactly as they did — nothing needs migrating. We are watching the numbers for a week before turning it on by default.
How it works
It works the same way on the public site and inside the widget, with no configuration to turn on. There is nothing to do on your side; the change is already in front of you. Two long-standing reports close with this, and both are linked below.
What changes
The setting lives under Settings, and defaults to the behaviour you already had. Anything already in flight when this went out finishes under the old path. It is slower on the first load and faster on every one after.
- Enable CSV export.
- Enable a Chrome extension.
curl -sS https://api.example.test/v2/items \
-H "Authorization: Bearer $BULLETIN_API_KEY"