What we learned shipping dark mode

The docs page for this was rewritten alongside it. There is nothing to do on your side; the change is already in front of you.

How it works

We are watching the numbers for a week before turning it on by default. We will fold the remaining cases in once we have seen this one hold. The old behaviour is still reachable for a release, behind a setting.

Step by step

Rollout is complete on every plan, including the free tier. It works the same way on the public site and inside the widget, with no configuration to turn on. It shipped behind a flag first, so a handful of workspaces have been on it for a fortnight.

What changes

Nothing about billing changes, on any plan. Most teams will notice this first on the busiest screen they use.

1. Enable vote weighting.
2. Enable post templates.
3. Enable role-based permissions.
4. Enable changelog email previews.

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

Common pitfalls

This has been the most requested change on the board for a while, and it is now live for every workspace. Thanks to everyone who filed a report with steps; several of them pointed straight at the cause. Existing setups keep working exactly as they did — nothing needs migrating.

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

Next steps

We rewrote this part rather than patching it, because the old approach ran out of room. If you were using the workaround, you can drop it — the built-in path covers the same ground.