Not sure whether this is a lack of imagination on my part, or if it's a bug, or a feature request.
If a skin's skin.properties file includes fullSiteSupport=false, it seems to me that the New Page > Empty page choice should be grayed out. It lets the user add a new page, but one that calls for "include" files that don't exist in the skin at all. The skin will generally ignore it, but why let the user create it in the first place?
If a skin's skin.properties file includes fullSiteSupport=false … The skin will generally ignore it, but why let the user create it in the first place?
If it is disabled then the engine should not attempt to process any existing template pages (produced when using a previous skin) but rather mark them as excluded.
The only usable case I can think of is if the skin allows custom links or iterates over templates, so the page can be referenced, and the end user is an experienced coder. That would seem to be an unlikely combination of things.