...
- Expand the number of skin variables and possibly include images or other elements to allow the skin to be more heavily configured.
- Allow the administrator to 'preview' the skin changes in a way that only the administrator sees the affects of the changes until the skin changes are persisted.
- Enhance the security infrastructure to limit the users who can configure a skin so a delegated administrator can affect only their skin and not other tenant's skins.
- Expand to a database-driven strategy where the skin is stored in the database and not necessarily on the file system.
Opportunities for consideration
- Move skin compilation into an asynchronous task on a non-render thread, getting the details right so that uPortal rendering does not block on in-process skin (re-)compilation and users do not get half-baked in-process skin artifacts during skin (re-)compilation.