Hi John,
Interesting approach if you only need to load one different skin per portal. However, I have a default portal with various skin layouts. That is one with right, content, top and left pane and another the same, but without the right pane, or no left pane either. Let's call this approach I). So on different tabid's you might need to load a different skin. Maybe this can be tackled in the same way with portal resource files. I.e.
Default skins: skin.ascx as default, skin_norightpane.ascx
Alias for portalalias10: and skin.alias-10.ascx and skin_norightpane.alias-10.ascx
Alias for portalalias 13: skin.portal-13.ascx. etc.
However, I understood only some colors need to be different. What about linking different css in similar way?
Default> skin.css
Alias 10: skin.css + skin.alias10.css (with changes that override on skin.css)
Alias 13: skin.css + skin.alias13.css etc.
Will this kind of linking work? I will call it approach II.
And I also can across someting like theming? Could this be approach III?
J.