We've started developing custom modules for our internal use of common libraries and controls, according to the guide https://docs.kentico.com/display/K8/Creating+custom+modules and we're also creating nuget installation packages as per https://docs.kentico.com/display/K82/Creating+installation+packages+for+modules and we think it's great for distribution.
I am aware that including other object types like objects that inherit from CMS.Document is not supported, see note on https://docs.kentico.com/display/K82/Creating+custom+binding+classes
But wouldn't it be possible that we could create the page type as usual and in the module detail page reference it to be included in the in the .zip file that is created for you to use with https://docs.kentico.com/display/K82/Installing+modules+from+installation+packages ?
Similar to how Additional libraries work, a proposed suggestion is:
This is what I manually do each type we create a package, I create a separate export that I manually include into the nuget package for the user to import after the module.
Couldn't the above suggestion also be extended to other objects that are not directly supported by the modules, like Page Templates, Containers, etc?
Please disregard this post if this has been improved on the upcoming v9, however I'd be very much interested in contributing with this suggestion if possible.
I think page types are part of the modularisation enhancements in Kentico 9.
Please, sign in to be able to submit a new answer.