Fixed a bug where it would generate an HTML <p> for a singular post that had type markdown. This would cause the purple pound sign to appear below the headline, instead of to the right of the headline, in the rendering.#
For titled posts of type markdown, enclose the generated markdown text in a div not a span, because that's what it is. The type is divMarkdownText. #
Did a few CSS tweaks for Markdown posts, to increase the spacing between headings, and to make the paragraph spacing follow the same rules as non-markdown Old School paragraphs. Checked in the changes. #
New release of Old School, v0.7.16. Checked in the changes.#
Now I just indented, but that's just for me, as it would be if I were editing a Markdown doc for a GitHub readme. I like that I can collapse a section of text. To get it out of the way, but it doesn't generate anything as far as Markdown is concerned.#
I can also start a new paragraph by skipping a line. I leave it empty. That's enough of a clue for Markdown. I don't have to put two spaces at the end of the line.#
I'm thinking of asking some of the power users, people who write great bug reports, and seem to care a lot about the product, to take responsibility for checking a certain area of the product as we go through new versions. I want to speed things up. And I want to give credit to the users who make the biggest difference.#
Fixed a bug where it would generate an HTML <p> for a singular post that had type markdown. This would cause the purple pound sign to appear below the headline, instead of to the right of the headline, in the rendering.#
For titled posts of type markdown, enclose the generated markdown text in a div not a span, because that's what it is. The type is divMarkdownText. #
Did a few CSS tweaks for Markdown posts, to increase the spacing between headings, and to make the paragraph spacing follow the same rules as non-markdown Old School paragraphs. Checked in the changes. #
New release of Old School, v0.7.16. Checked in the changes.#
Now I just indented, but that's just for me, as it would be if I were editing a Markdown doc for a GitHub readme. I like that I can collapse a section of text. To get it out of the way, but it doesn't generate anything as far as Markdown is concerned.#
I can also start a new paragraph by skipping a line. I leave it empty. That's enough of a clue for Markdown. I don't have to put two spaces at the end of the line.#
I'm thinking of asking some of the power users, people who write great bug reports, and seem to care a lot about the product, to take responsibility for checking a certain area of the product as we go through new versions. I want to speed things up. And I want to give credit to the users who make the biggest difference.#
copyright 2021 Dave Winer
Last update: Tuesday November 23, 2021; 4:30 PM EST.