{"action":"opened","issue":{"url":"https://api.github.com/repos/nostalgic-css/NES.css/issues/218","repository_url":"https://api.github.com/repos/nostalgic-css/NES.css","labels_url":"https://api.github.com/repos/nostalgic-css/NES.css/issues/218/labels{/name}","comments_url":"https://api.github.com/repos/nostalgic-css/NES.css/issues/218/comments","events_url":"https://api.github.com/repos/nostalgic-css/NES.css/issues/218/events","html_url":"https://github.com/nostalgic-css/NES.css/issues/218","id":393207780,"node_id":"MDU6SXNzdWUzOTMyMDc3ODA=","number":218,"title":"Document pixelize mixin","user":{"login":"jjspace","id":8007967,"node_id":"MDQ6VXNlcjgwMDc5Njc=","avatar_url":"https://avatars1.githubusercontent.com/u/8007967?v=4","gravatar_id":"","url":"https://api.github.com/users/jjspace","html_url":"https://github.com/jjspace","followers_url":"https://api.github.com/users/jjspace/followers","following_url":"https://api.github.com/users/jjspace/following{/other_user}","gists_url":"https://api.github.com/users/jjspace/gists{/gist_id}","starred_url":"https://api.github.com/users/jjspace/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jjspace/subscriptions","organizations_url":"https://api.github.com/users/jjspace/orgs","repos_url":"https://api.github.com/users/jjspace/repos","events_url":"https://api.github.com/users/jjspace/events{/privacy}","received_events_url":"https://api.github.com/users/jjspace/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-20T20:53:59Z","updated_at":"2018-12-20T20:53:59Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"<!-- Please fill your information below. -->\r\n<!-- You can delete these lines enclosed by `<` and `>` before posting, too. -->\r\n\r\n**Is your feature request related to a problem? Please describe.**\r\n<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->\r\nIn reviewing #217 and other recent PRs I've noticed it's not always clear how to use the `pixelize` mixin especially given all the recent changes to it. This extends to how we handle `box-shadows` throughout most of the project and when we can use a \"default color\" (see #60, #143).\r\n\r\n**Describe the solution you'd like**\r\n<!-- A clear and concise description of what you want to happen. -->\r\nCreate some documentation on how `pixelize` works and how and where it should be used. This will include an explanation on what values must be passed in as well as what properties it will generate so the user knows which properties they should avoid setting themselves unless specifically intending to override.\r\n\r\nAs a parallel also create some guidelines on how to use `box-shadows` so we are all on the same page. This is important since a lot of the style of this framework is based on this property.\r\n\r\n**Describe alternatives you've considered**\r\n<!-- A clear and concise description of any alternative solutions or features you've considered. -->\r\nThe alternative is having no documentation and relying on the members and contributors to have a complete understanding of this topic across all of us and correct new contributors as they make mistakes in PRs.\r\n\r\n**Additional context**\r\n<!-- Add any other context or screenshots about the feature request here. -->\r\nAs of right now I think I have the best understanding of how we're using `pixelize` and `box-shadows` across the entire framework as I have done a lot of work regarding these recently so I feel I would be best to write up at least the first draft. This can also kickstart a sort of \"style guide\" and discussion on our own best practices within the framework."}}
{"actor":{"display_login":"jjspace"}}