I've seen the documentation for creating content mappings and it looks potentially useful, but it would be even more useful and easier to set up if the SDK supported it.
Currently the only way to define mappings is point-and-click via the UI, or raw API calls using the REST API, but definitions of content type bindings should really live together with the content types themselves. A definition for mapping a FooContentType to a BarContentType should also then be able to type-check itself to make sure the binding is actually valid.
I've seen the documentation for creating content mappings and it looks potentially useful, but it would be even more useful and easier to set up if the SDK supported it.
Currently the only way to define mappings is point-and-click via the UI, or raw API calls using the REST API, but definitions of content type bindings should really live together with the content types themselves. A definition for mapping a
FooContentTypeto aBarContentTypeshould also then be able to type-check itself to make sure the binding is actually valid.