mpression-related attack. Turning off compression makes the attack impossible.
ADDED
Note that in this case it appears that you turn off a different compression configuration; whereas CRIME exploits TLS-layer compression, BREACH exploits HTTP-layer compression. 

A:

I just thought of a way to add "Randomizing secrets per request", "Length hiding", and "Rate-limiting requests" to a CSRF mitigation measure.

Consider which forms you wouldn't want an attacker to POST on the user's behalf. These are the forms you'd protect from CSRF.
For each page view, generate a random salt of random length. Send this salt as a hidden input. The random length should help add noise to lengths, even if your front-end load balancer strips comments or otherwise minifies your HTML.
Compute a hash of the salt, the session ID, and a server-side secret, and send this CSRF key as another hidden input.
Optionally log the salt or CSRF key to a table. This allows for rate limiting a particular user account or IP address to a number of hashes per hour and for limiting replays of a particular salt.
When you process the form, compute the hash in the same way as the previous steps, using the salt in the form, and make sure it matches the CSRF key.



Q:

Creating a Manual in InDesign - How do I make it editable while maintaining format for non-ID users?

I am a complete InDesign newbie, and this might be a sort of complex issue, so please bear with me! 
My company produces maintenance manuals for HOAs and homeowners, in both print and electronic formats. We have a base template for each product type, which is then modified to match the project. Up until now, we've been utilizing Microsoft Word, which has been less than ideal; we frequently either add or remove information and/or photos, and making any changes at all usually breaks the formatting, which requires time-consuming corrections. It's also not the most professional looking. So we're exploring other options! 
So far, it seems like InDesign is going to suit our needs; however, I'm the only