We can send newsletters manually, but it's not intuitive. The command is yarn newsletter:send-test (which defaults to the Hello World newsletter unless another one is specified). This isn't actually a test, as it really will send the newsletter. (Although there are guards against this going to the real production mailing lists when called this in non-production environments.)
It should be easier (and documented) to send a newsletter out of band.
While this task itself is pretty easy, we should really tackle #77 to complete it, since right now newsletters will just include "the past 24 hours of claims", and the use case for sending newsletters out of band is usually like "it didn't send this morning at 8am, so we're catching up at 10am, and really want the past 26 hours' worth, but tomorrow we'll just want the previous 22 hours' worth".
We can send newsletters manually, but it's not intuitive. The command is
yarn newsletter:send-test(which defaults to the Hello World newsletter unless another one is specified). This isn't actually a test, as it really will send the newsletter. (Although there are guards against this going to the real production mailing lists when called this in non-production environments.)It should be easier (and documented) to send a newsletter out of band.
While this task itself is pretty easy, we should really tackle #77 to complete it, since right now newsletters will just include "the past 24 hours of claims", and the use case for sending newsletters out of band is usually like "it didn't send this morning at 8am, so we're catching up at 10am, and really want the past 26 hours' worth, but tomorrow we'll just want the previous 22 hours' worth".