{"action":"created","issue":{"url":"https://api.github.com/repos/buddypress/next-template-packs/issues/17","repository_url":"https://api.github.com/repos/buddypress/next-template-packs","labels_url":"https://api.github.com/repos/buddypress/next-template-packs/issues/17/labels{/name}","comments_url":"https://api.github.com/repos/buddypress/next-template-packs/issues/17/comments","events_url":"https://api.github.com/repos/buddypress/next-template-packs/issues/17/events","html_url":"https://github.com/buddypress/next-template-packs/issues/17","id":159007230,"number":17,"title":"Styles as reduced shared modular blocks","user":{"login":"hnla","id":499419,"avatar_url":"https://avatars.githubusercontent.com/u/499419?v=3","gravatar_id":"","url":"https://api.github.com/users/hnla","html_url":"https://github.com/hnla","followers_url":"https://api.github.com/users/hnla/followers","following_url":"https://api.github.com/users/hnla/following{/other_user}","gists_url":"https://api.github.com/users/hnla/gists{/gist_id}","starred_url":"https://api.github.com/users/hnla/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hnla/subscriptions","organizations_url":"https://api.github.com/users/hnla/orgs","repos_url":"https://api.github.com/users/hnla/repos","events_url":"https://api.github.com/users/hnla/events{/privacy}","received_events_url":"https://api.github.com/users/hnla/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-06-07T19:41:30Z","updated_at":"2016-06-10T09:03:14Z","closed_at":null,"body":"Toying with the idea of running smaller scss modules for components e.g `_activity_entry` or more generic `_bp_lists`\r\n\r\nThese are run this way so as to be re-used as 'lib' elements for all or any future packs.\r\n\r\nOur directory `/bp-templates/` has a directory `/bp-templates/shared/styles/` in here we keep out partials.\r\n\r\nOur .scsss sheet in a template location `/bp-templates/bp-nouveau/scss/buddypress.scss` includes these partials and gains modular shared styles that suit a basic layout.\r\n\r\nIf that template set doesn't want it simply removes the `@import '../../shared/styles/_bp_lists';`\r\n\r\nI'm sure there are many issues in this kind of idea and a plugin like BP, this is to establish the idea for discussion and see what issues there would be... it works on my local but that isn't seeing issues such as style ruleset structuring yet.\r\n"},"comment":{"url":"https://api.github.com/repos/buddypress/next-template-packs/issues/comments/225129699","html_url":"https://github.com/buddypress/next-template-packs/issues/17#issuecomment-225129699","issue_url":"https://api.github.com/repos/buddypress/next-template-packs/issues/17","id":225129699,"user":{"login":"imath","id":1834524,"avatar_url":"https://avatars.githubusercontent.com/u/1834524?v=3","gravatar_id":"","url":"https://api.github.com/users/imath","html_url":"https://github.com/imath","followers_url":"https://api.github.com/users/imath/followers","following_url":"https://api.github.com/users/imath/following{/other_user}","gists_url":"https://api.github.com/users/imath/gists{/gist_id}","starred_url":"https://api.github.com/users/imath/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/imath/subscriptions","organizations_url":"https://api.github.com/users/imath/orgs","repos_url":"https://api.github.com/users/imath/repos","events_url":"https://api.github.com/users/imath/events{/privacy}","received_events_url":"https://api.github.com/users/imath/received_events","type":"User","site_admin":false},"created_at":"2016-06-10T09:03:14Z","updated_at":"2016-06-10T09:03:14Z","body":"First i'm not against using scss processor to build css files. I'm also in favor of using modular blocks as you're suggesting. I just think we need to provide a modular approach that is more user friendly, meaning splitting the buddypress.css file into smaller ones.\r\n\r\nIt could be buddypress-colors.css, buddypress-activity.css etc... that your scss modules would build.\r\n\r\nThen we could have a more granular approach when enqueueing styles by registering overridable path and enqueueing the needed styles when required.\r\n\r\neg:\r\n\r\n```php\r\nwp_register_style( 'bp-nouveau-main', 'path/to/buddypress.css', array(), $version );\r\nwp_register_style( 'bp-nouveau-colors', 'path/to/buddypress-colors.css', array( 'bp-nouveau-main' ), $version );\r\nwp_register_style( 'bp-nouveau-activity', 'path/to/buddypress-activity.css', array( 'bp-nouveau-colors' ), $version );\r\n\r\n// Then a bit later in the loading process, when we need to style activities\r\nwp_enqueue_style( 'bp-nouveau-activity' );\r\n```\r\n"}}
{"actor":{"display_login":"imath"}}