Wildcard Indexes currently do not support compounding in any fashion. Given the way they are implemented, it seems logical that no additional compound field should follow the wildcard part. However, a preceding compound field should not violate the premises of wildcard indexing and would support additional use cases.
Consider a collection containing polymorphic documents that share a common "type" field but may otherwise contain varying content fields...
In such cases, many queries will want to match documents based on a content field, but only within a given target type. Hence it would be preferable to create the following index:
Which is currently not permitted and will be answered with a generic "wildcard indexes do not allow compounding" error message.
MongoDB currently scales better with few large collections and few indexes than it does with many small collections and many indexes (WT-5479). Given that one of the major advantages of MongoDB is that it is schema-free, building polymorphic collections seems like the natural way to go. More flexible wildcard indexes could provide key support in this regard.