Quinten Steenhuis
Example of option 2 for a custom addendum:  In the generic addendum, we would replace the `A_Plaintiff_Confidential_Information0011_attachment` with `x` in each location it appears now.
Pause this because we may want to generate **everything** in the background instead of just this
I'm now not sure when we'll get to generating everything in the background, so I'm okay starting with just this for now. It's a relatively small and safe change that...
Another Jonathan example: this one uses a background task to assemble the document, and displays either a waiting screen or the assembled document, whichever is ready: ``` attachment: variable name:...
@BryceStevenWilley we should return to this issue--noticing some significant slow downs with multi-weaver feature that feel addressable
I think that's the only really good way to handle an arbitrarily long list of forms...Jonathan had some helpful ideas
Could we do two-stage processing of the template - is it worth caching the "preview" version of the template with mostly rendered contents--or is it going to take the same...
This relates to #713 - it's essentially the other side of the fix there.
Should check words.yml for these--some might be custom validation messages specific to ILAO/NH Legal Aid
Couple things to point out: * Maybe we want to use "pick" instead of "select" * Use digits instead of spelled out numbers? * Maybe avoid the word "please"? Debatable...