I suspect that either my understanding of how to create a page template in 5.x is lacking or I have a problem with my DNN configuration. On the "Current Page" tab of the ribbon bar one of the available selections is "Export". Selecting this appears to indicate that whatever it is that is being exported is targeted initially to the Templates folder. There is a checkbox to include page content. I "assume" that this is going to create a page template based off of the page being exported. When I then try to add a page by using the add button from the ribbon bar and selecting the "template" created from the export feature what I get is a new page with the containers and content that were exported, but the page skin is incorrect. It appears to be set to the portal default skin. I then have to edit the page and select the original skin for the containers to be placed in the correct positions. If however I do an "Import" then a page will be created with with everything correct. Is there a reason why the add page on the ribbon bar works differently? I have been asked by my management why they can't add the page through the add feature and have to go through the import process.

Well I'm guessing the core team have set it up this way so that you have the choice of whether or not to have the skin applied. In some instances you would want the default skin to be used rather than the template skin.

So you're saying that the ribbon bar add page does not necessarily use the skin defind in the template even though you specifically selected a template other than the default? That pretty much defeats the purpose of selecting a template from the list since the list starts out with the default template selected. There may be containers in a custom template that do not exist in the default template.