Hi @William_Bell ! Great stuff, hope you enjoy my doc!
I hear you on a native encryption feature in Coda! It’d be quite simple to develop a pack to transform plaintext to/from ciphertext, but the bigger issue is getting around Coda’s Doc History. If I type something into a text column, then click a button to “encrypt” it, nothing’s stopping another Coda user from hopping into the doc’s Doc History and rolling the action back to see my original text.
Also, if the encryption key is just part of the [Encrypt] button’s setup, then it’d be visible to other users in the doc, allowing them to use it to freely decrypt the ciphertext.
These are all issues I explore in the “Can you keep a secret doc” above, and that I (hopefully) solve in the follow up The Encryption Template I posted a few weeks after. The template uses published forms to handle the encryption process. This prevents Coda from ever storing the plaintext or encryption key anywhere, and keeps this information private and secure.
I made that template free to copy, so you’re welcome to give it a try if you’re interested. There’s a bit of setup required initially, but once your doc is up and running it should save you some time and effort as you’ll no longer have to manually copy-paste from that cryptotools.net site.
Shout if you’ve got any questions 