Hi @braden,
There is little experience with using subdocuments as they were just released in October.
Could you explain more about your concept of separation of metadata? Maybe you could share some sample-JSON code.
I imagine that you want to allow users to load the editor as fast as possible. But when they only look at metadata (the name of the document, …) they shouldn’t load the editor-content at all. In this case, you should definitely load the editor-content as a subdocument.
Aside from the asynchronous nature of subdocuments (they load asynchronously and - depending on the provider - require a separate network request), I don’t see any disadvantages of using them. In some cases you want to apply atomic transformations (e.g. you want to change two related properties at the same time) that should be executed as one transaction. In this case, you probably don’t want to use subdocuments either.