Dave is testing support for Markdown in Drummer. However, I didn't realize it was already available. Here's me trying a post with Markdown. What about blockquote? Here's a try, I'm curious how will this be rendered.
The idea is that if a node has that type, when rendering it in Old School, we convert the text from Markdown to HTML.
It is better to mark a whole post with title as Markdown. Here's the list of benefits I see now.
This gives me an editor that I am most used to. Most of my posts are written in Markdown. So, it is welcome to get the same behaviour in Drummer too.
Unlike my initial comment to Dave, I understand the benefit of marking a node as Markdown. I can very well choose not to make all nodes as Markdown, but then selectively mark a post, one like this, as Markdown.
This will be really useful for longer posts as basic styling like italics, bold and links are already well handled. For anything that's not handled like strikethrough or inline code, this would be really useful.
The whole post is rendered as a single post, each paragraph is not considered as separate node. So, each paragraph does not get its individual link. I like that, though I am not certain if that is intentional.
The Markdown node cannot handle multiple paragraphs (basically, multiple basic child nodes, which are neither quotes, lists etc). Only way I could make it work is to include <br/> at the end. I am certain this is a miss on Dave's part, and he will fix it.
I can use HTML in Markdown node, refer the last line of this post. Nice!
I realized, of course, I will have to pull in the latest style.css and other template files. For example, otherwise the list is not rendered correctly -- elements need the style rules. And I believe Dave hasn't checked in the changes yet. I made the changes to my custom stylesheet -- I will have to undo this once Dave checks in.
In short, I like this. I know where I am going to make sure of it. Here are the two instances I can think of now.
If there's any time when I feel I can use the Markdown elements, I will convert that node to Markdown.
If I want to write a long post with lists and links involved, or even code snippets, I will convert the title node to Markdown.
Beyond these two instances, the basic outline works well. I do not want to unnecessarily hamper the simplicity of posting with Drummer. That lack of complexity is this system's USP.
Dave is testing support for Markdown in Drummer. However, I didn't realize it was already available. Here's me trying a post with Markdown. What about blockquote? Here's a try, I'm curious how will this be rendered.
The idea is that if a node has that type, when rendering it in Old School, we convert the text from Markdown to HTML.
It is better to mark a whole post with title as Markdown. Here's the list of benefits I see now.
This gives me an editor that I am most used to. Most of my posts are written in Markdown. So, it is welcome to get the same behaviour in Drummer too.
Unlike my initial comment to Dave, I understand the benefit of marking a node as Markdown. I can very well choose not to make all nodes as Markdown, but then selectively mark a post, one like this, as Markdown.
This will be really useful for longer posts as basic styling like italics, bold and links are already well handled. For anything that's not handled like strikethrough or inline code, this would be really useful.
The whole post is rendered as a single post, each paragraph is not considered as separate node. So, each paragraph does not get its individual link. I like that, though I am not certain if that is intentional.
The Markdown node cannot handle multiple paragraphs (basically, multiple basic child nodes, which are neither quotes, lists etc). Only way I could make it work is to include <br/> at the end. I am certain this is a miss on Dave's part, and he will fix it.
I can use HTML in Markdown node, refer the last line of this post. Nice!
I realized, of course, I will have to pull in the latest style.css and other template files. For example, otherwise the list is not rendered correctly -- elements need the style rules. And I believe Dave hasn't checked in the changes yet. I made the changes to my custom stylesheet -- I will have to undo this once Dave checks in.
In short, I like this. I know where I am going to make sure of it. Here are the two instances I can think of now.
If there's any time when I feel I can use the Markdown elements, I will convert that node to Markdown.
If I want to write a long post with lists and links involved, or even code snippets, I will convert the title node to Markdown.
Beyond these two instances, the basic outline works well. I do not want to unnecessarily hamper the simplicity of posting with Drummer. That lack of complexity is this system's USP.