{"action":"created","issue":{"url":"https://api.github.com/repos/CTPUG/wafer/issues/127","labels_url":"https://api.github.com/repos/CTPUG/wafer/issues/127/labels{/name}","comments_url":"https://api.github.com/repos/CTPUG/wafer/issues/127/comments","events_url":"https://api.github.com/repos/CTPUG/wafer/issues/127/events","html_url":"https://github.com/CTPUG/wafer/issues/127","id":108841852,"number":127,"title":"Include talk type in the schedule","user":{"login":"drnlm","id":642056,"avatar_url":"https://avatars.githubusercontent.com/u/642056?v=3","gravatar_id":"","url":"https://api.github.com/users/drnlm","html_url":"https://github.com/drnlm","followers_url":"https://api.github.com/users/drnlm/followers","following_url":"https://api.github.com/users/drnlm/following{/other_user}","gists_url":"https://api.github.com/users/drnlm/gists{/gist_id}","starred_url":"https://api.github.com/users/drnlm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/drnlm/subscriptions","organizations_url":"https://api.github.com/users/drnlm/orgs","repos_url":"https://api.github.com/users/drnlm/repos","events_url":"https://api.github.com/users/drnlm/events{/privacy}","received_events_url":"https://api.github.com/users/drnlm/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-09-29T10:34:45Z","updated_at":"2015-12-01T01:01:09Z","closed_at":null,"body":"From IRC\r\n\r\n**Hodgestar**: drnlm: How do you feel about adding having the talk type on the schedule page somehow? Perhaps as an additional class on the appropriate td>\r\n**tumbleweed**: sounds useful\r\n\r\nObvious implementation questions:\r\n * Should we restrict the Talk Types to things that can easily be turned into attribute values? Or just rely on good stanitization?\r\n * Do we need a type for pages in the schedule? "},"comment":{"url":"https://api.github.com/repos/CTPUG/wafer/issues/comments/160813012","html_url":"https://github.com/CTPUG/wafer/issues/127#issuecomment-160813012","issue_url":"https://api.github.com/repos/CTPUG/wafer/issues/127","id":160813012,"user":{"login":"madduck","id":195073,"avatar_url":"https://avatars.githubusercontent.com/u/195073?v=3","gravatar_id":"","url":"https://api.github.com/users/madduck","html_url":"https://github.com/madduck","followers_url":"https://api.github.com/users/madduck/followers","following_url":"https://api.github.com/users/madduck/following{/other_user}","gists_url":"https://api.github.com/users/madduck/gists{/gist_id}","starred_url":"https://api.github.com/users/madduck/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/madduck/subscriptions","organizations_url":"https://api.github.com/users/madduck/orgs","repos_url":"https://api.github.com/users/madduck/repos","events_url":"https://api.github.com/users/madduck/events{/privacy}","received_events_url":"https://api.github.com/users/madduck/received_events","type":"User","site_admin":false},"created_at":"2015-12-01T01:01:09Z","updated_at":"2015-12-01T01:01:09Z","body":"Indeed, so either we need a TalkType → CSS class mapping, or a function (\"slugify\"?), or we add the CSS class to the event type (Summit does this, and also allows an icon for each TalkType)."}}