{"action":"created","issue":{"url":"https://api.github.com/repos/Mermade/shins/issues/30","repository_url":"https://api.github.com/repos/Mermade/shins","labels_url":"https://api.github.com/repos/Mermade/shins/issues/30/labels{/name}","comments_url":"https://api.github.com/repos/Mermade/shins/issues/30/comments","events_url":"https://api.github.com/repos/Mermade/shins/issues/30/events","html_url":"https://github.com/Mermade/shins/issues/30","id":307585077,"number":30,"title":"Moving some code blocks into centre column","user":{"login":"simondean","id":190464,"avatar_url":"https://avatars0.githubusercontent.com/u/190464?v=4","gravatar_id":"","url":"https://api.github.com/users/simondean","html_url":"https://github.com/simondean","followers_url":"https://api.github.com/users/simondean/followers","following_url":"https://api.github.com/users/simondean/following{/other_user}","gists_url":"https://api.github.com/users/simondean/gists{/gist_id}","starred_url":"https://api.github.com/users/simondean/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/simondean/subscriptions","organizations_url":"https://api.github.com/users/simondean/orgs","repos_url":"https://api.github.com/users/simondean/repos","events_url":"https://api.github.com/users/simondean/events{/privacy}","received_events_url":"https://api.github.com/users/simondean/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-03-22T10:29:17Z","updated_at":"2018-03-22T11:04:01Z","closed_at":null,"author_association":"NONE","body":"I’m using widdershins and shins together to convert an OpenAPI 3 definition into Slate HTML\r\n\r\nI have some markdown in the `info.description` field of the openapi.yaml file that contains JSON and other code blocks. I’m trying to put these code blocks in the centre column of the Slate HTML page, but leave other code blocks in the right column. I’ve managed to do it using Shins `pub/css/screen_overrides.css` file but it’s a bit hacky and brittle\r\n\r\nLooking at other options I noticed the “att list” syntax extension for Markdown. There’s the https://www.npmjs.com/package/markdown-it-attrs package that implements this. With this extension I could add a class to the code blocks I want to hav in the centre column and then target that class from my CSS overrides\r\n\r\nWould it be possible to make shins configurable like widdershins is and to have a config option for specifying a list of markdown extensions to load, eg listed by package name?"},"comment":{"url":"https://api.github.com/repos/Mermade/shins/issues/comments/375265203","html_url":"https://github.com/Mermade/shins/issues/30#issuecomment-375265203","issue_url":"https://api.github.com/repos/Mermade/shins/issues/30","id":375265203,"user":{"login":"simondean","id":190464,"avatar_url":"https://avatars0.githubusercontent.com/u/190464?v=4","gravatar_id":"","url":"https://api.github.com/users/simondean","html_url":"https://github.com/simondean","followers_url":"https://api.github.com/users/simondean/followers","following_url":"https://api.github.com/users/simondean/following{/other_user}","gists_url":"https://api.github.com/users/simondean/gists{/gist_id}","starred_url":"https://api.github.com/users/simondean/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/simondean/subscriptions","organizations_url":"https://api.github.com/users/simondean/orgs","repos_url":"https://api.github.com/users/simondean/repos","events_url":"https://api.github.com/users/simondean/events{/privacy}","received_events_url":"https://api.github.com/users/simondean/received_events","type":"User","site_admin":false},"created_at":"2018-03-22T11:04:01Z","updated_at":"2018-03-22T11:04:01Z","author_association":"NONE","body":"Hi. I tried adding a doc round the description markdown and a lot of the CSS broke. I’m guessing it might be the `A > B` stuff in the existing CSS\r\n\r\nOne of the languages is in the language tabs. It’s `shell`. I did wonder about using `bash` to differentiate but did seem a bit hacky. Might trip people up later on. \r\n\r\nA guard option would good. \r\n\r\nAs an aside, there’s a good discussion on Mardown attributes in the extensions section of the CommonMark site: https://talk.commonmark.org/t/consistent-attribute-syntax/272\r\n"}}
{"actor":{"display_login":"simondean"}}