moritzps

Keybase proof

I hereby claim:

• I am moritzps on github.
• I am moritzscholz (https://keybase.io/moritzscholz) on keybase.
• I have a public key ASDdyx27IukZ-q4U-iWKlYk1wM2wBDIeLfC07l8SfcEzRgo

To claim this, I am signing this object:

moritzps

Disclaimer

• I am a product manager @magic_labs and not a developer and my understanding of Ruby/Rails/Programming is very basic, I have an even more limited idea of how papertrail works, so maybe everything I wrote just does not work.
• Neither do I have any idea of database optimization, both in speed and storage. So maybe the ideas would work, but they are very inefficient.

General

Thoughts on versioning

• We get this feature request a lot: People want to make sure their work is saved, even if they mess up. Since we have a lot of Alchemy customers ourselves we have to handle customer service requests and often it is about getting deleted or edited elements back. If we talk to langer companies most of the time the feature is requested since some content editors don’t know how to use technology in general and delete or modify content they were not supposed to or didn’t mean to. There is no undo feature yet and versioning would allow several features (like undo and else) that protects the users work.