We are generally happy with how versioning works for the content itself, however the way the content-types are supposed to be modified creates a major concern for scaling our usage of Prismic. There is no built-in version control (I'm aware of manual copy-paste recommendation), no publishing/scheduling process, no rollbacks, - basically nothing. And since any kind of development basically requires you to constantly modify the content types, the lack of any kind of built-in redundancy for content types is a very obvious point of a very probable failure.
Suppose we have hundreds of pages of a given content type. If a developer makes a mistake and removes/breaks some definitions, and let's say the situation is unnoticed for a week (common for larger teams), and during this time a bunch of pages get updates/republished - the data associated with those removed definitions is silently dropped, - is that correct? Are there any plans to improve this situation?
It basically makes it really hard to maintain even a medium scale, - like having multiple developers working on the implementation (they can easily overwrite each other's changes), or having hundreds of pages.
Why does the content gets silently dropped? Wouldn't it better to block the republish that will cause the loss of content with a warning? Shouldn't there be some some validations during the content type saving as well? Why there's no versioning for content types? No audit logs, no trace of what's changed.
IMO, this is weakest point of the otherwise great product and I hope you'll find these questions valid and we can have a productive discussion here