1. 29

  2. 7

    I really like this, except that it requires JavaScript, of course. Perhaps this in the form of an Apache extension or something similar would be a good idea?

    Edit: just realized that markdeep provides a non-js fallback. Really great work!

    Edit 2: please don’t convert both -- and --- to an em dash! Many languages use en dashes and not em dashes.

    1. 3

      I think it’s not different enough from Markdown to be interesting. Sure it has text diagrams, but you can put text diagrams in Markdown too. You can also add some JavaScript to your Markdown files to have them render automatically in a browser (although I’m not sure I see a point to this, as opposed to just rendering the file to HTML before publishing it).

      It basically feels like a proprietary variant of Markdown, tied to a specific JS lib, so once you start using it it makes it hard to move your data. As opposed to regular Markdown (based for instance on CommonMark), which will work pretty much everywhere.

      1. 4

        While I agree with your sentiment I should point out that the link says that markdeep is an open-source hobby project, not proprietary. (I know you wrote feels like but I thought this note was still worth pointing out.)

        1. 3

          I use it in my blog, and Markdeep is amazing.

          I’m using the diagram feature, and for me it’s basically the decision of either using Markdeep, or not providing diagrams at all, because Markdeep just works.

          1. 1

            Do you do diagrams by hand? I always get annoyed tweaking the whitespace.

            1. 1

              Well there’s always things like artist-mode in emacs, or DrawIt in vim. More convoluted than dia or visio, but they do have the advantage of being inline in a readme.

          2. 1

            I think adding graphs is valuable however I think it maybe should be done as a contribution to markdown.

            1. 7

              There’s no contributing to Markdown, which is the genesis story of CommonMark.

          3. 3

            The source code is unfortunately not version-controlled and for a while, only the minified version was available.

            1. 2

              The site talks about looking good in any web browser, but the text was too small to read comfortably and when I used the reader mode in Safari it broke and lost most of the page.