So, I've not tried this in depth yet (it's on my list of things to do); there is a
bit column in the
CMS_Class table named
ClassIsContentOnly. Also, for each node in
CMS_Tree, there is another
bit field named
By toggling these values in SQL, I can change the behaviour of the CMS pages application.
As far as I can see, the field in the tree determines how the document is displayed in the pages app, and the field in class definition determines the default value for instances of that class when created. I'm fairly sure that there is more to it that this, but this would be the place I would start. If you're using content pages, you're going to need to think about how you might want to deal with and widget content etc.
As I say, I've not looked in to this in any detail yet, so there may be some other issues that you need to deal with too.