mwlarkin1 wrote: A big caveat so far is richtext fields, which are difficult to manage with JSON
Is it because richtext content is in its pristine form? Did you consider encoding it?
I had used encoding to cache json-like data to database: json --> gzip --> bin2hex. Very effective, continuous, json-compatible. May add an md4 hash as a control sum, saved and sent alongside data. Coding-decoding is fast and will allow passing crazy richtext content back and forth. In case of richtext it would be richtext --> gzip --> bin2hex --> json.