I would suggest this to be considered very seriously, because nowadays how easy it is to rebrand or change the default look of a website is one of the top features of all web-related frameworks. At least from the point of view of a beginning deployer.
> Is there a strong technical reason that the root CSS class name for a > skin contains the skin name? Can we find an alternate solution that > doesn't require as much work for the deployer to create a new skin? -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
