{"action":"created","issue":{"url":"https://api.github.com/repos/yahoo/pure/issues/88","labels_url":"https://api.github.com/repos/yahoo/pure/issues/88/labels{/name}","comments_url":"https://api.github.com/repos/yahoo/pure/issues/88/comments","events_url":"https://api.github.com/repos/yahoo/pure/issues/88/events","html_url":"https://github.com/yahoo/pure/issues/88","id":15425257,"number":88,"title":"Break out skin-specific properties into *-skin.css modules","user":{"login":"msweeney","id":39166,"avatar_url":"https://avatars.githubusercontent.com/u/39166?v=3","gravatar_id":"","url":"https://api.github.com/users/msweeney","html_url":"https://github.com/msweeney","followers_url":"https://api.github.com/users/msweeney/followers","following_url":"https://api.github.com/users/msweeney/following{/other_user}","gists_url":"https://api.github.com/users/msweeney/gists{/gist_id}","starred_url":"https://api.github.com/users/msweeney/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/msweeney/subscriptions","organizations_url":"https://api.github.com/users/msweeney/orgs","repos_url":"https://api.github.com/users/msweeney/repos","events_url":"https://api.github.com/users/msweeney/events{/privacy}","received_events_url":"https://api.github.com/users/msweeney/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/yahoo/pure/labels/discussion","name":"discussion","color":"fbca04"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2013-06-11T22:08:42Z","updated_at":"2015-02-03T00:34:54Z","closed_at":"2015-02-03T00:34:54Z","body":"As @jshirley alludes to in his comment on the preprocessor thread (https://github.com/yui/pure/issues/68#issuecomment-19141600), in order to make customization easier (and following our modular approach) it would be nice to have all of the styling that we consider \"skinnable\" broken out into separate files.  I propose that we move \"skin\" specific styling into separate src/build files.\r\n\r\nThis would provide consumers with a template file for customizing skins and the option to include their skin as an alternative to the default `*-skin.css` module(s). "},"comment":{"url":"https://api.github.com/repos/yahoo/pure/issues/comments/72569248","html_url":"https://github.com/yahoo/pure/issues/88#issuecomment-72569248","issue_url":"https://api.github.com/repos/yahoo/pure/issues/88","id":72569248,"user":{"login":"jamesalley","id":824331,"avatar_url":"https://avatars.githubusercontent.com/u/824331?v=3","gravatar_id":"","url":"https://api.github.com/users/jamesalley","html_url":"https://github.com/jamesalley","followers_url":"https://api.github.com/users/jamesalley/followers","following_url":"https://api.github.com/users/jamesalley/following{/other_user}","gists_url":"https://api.github.com/users/jamesalley/gists{/gist_id}","starred_url":"https://api.github.com/users/jamesalley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jamesalley/subscriptions","organizations_url":"https://api.github.com/users/jamesalley/orgs","repos_url":"https://api.github.com/users/jamesalley/repos","events_url":"https://api.github.com/users/jamesalley/events{/privacy}","received_events_url":"https://api.github.com/users/jamesalley/received_events","type":"User","site_admin":false},"created_at":"2015-02-03T00:34:53Z","updated_at":"2015-02-03T00:34:53Z","body":"Despite my last comment, in the case of Menu, when I refactored it recently, I ended up doing just what Matt proposed. I still bundle the skin by default, but if you do your own rollups you'll more easily be able to omit the skin properties.\r\n\r\nThis is something I plan on doing going forward. I'm not going to break out all skinnable properties all at once, but as I refactor any given module I will be keeping this in mind."}}