To celebrate 10 YEARS (!) of beautiful markdown documents with Markdeep, I made a new website!

https://casual-effects.com/markdeep/

Same attention to hand-crafted code, 100% data privacy, client-side processing, and text-based obsession.

New fancy CSS styles, support for more editors and markdown features, and new browser compatibility tricks for a seamless document experience.

This kicks off a month of new Markdeep feature releases to ring in the new year and the next decade of Markdeep.

#markdown

@morgan3d 10 years? Whoa.
@aras I know, right? It makes me realize maybe time is passing on us. Some of the origin dates on files I use regularly are getting old enough to drive a car and drink beer now...
@morgan3d looks wonky on mobile
@morgan3d Hey, not sure if you're aware, but the site is barely usable on mobile (Firefox on a Pixel 7). It's extremely laggy, and doesn't adjust well to the narrow viewport
@das_robin Thanks, it must be the gradient animation. I'll update that to disable on mobile.

Hello @morgan3d ,

I recently found your posting and I'm absolutely amazed of Markdeep!
I like the idea of Markdown and your implementation is IMO just the right way to use it.

Two questions:
1. I tried to include it in a Moodle courses textarea. Sadly Markdeep formats the whole moodle course instead of just the single textarea, I want to be formated. Is there a way to tell Markdeep some limits? (e.g. a specific html-tag ID, a CSS class or some special Markdeep-codemarks?)

2. I found https://casual-effects.com/gamejam/babybat/index.html, and under "4. Mechanics" there is a bullet list. What happens in the point "Controls" under "One tap = one flap"? The list is broken, it is is displayed in the first hierarchy, instead of the second, and "Energy" is kicked out, it has a "-" (hierarchy 0?) instead of a bullet. Is it a bug?

@chbmeyer @morgan3d It reminds me of StrapDown.js ๐Ÿ™‚

But yeah, disappointing in mobile ๐Ÿ˜“

@chbmeyer @morgan3d Can you try to indent your list with two spaces instead of one? Probably that's the reason why the parser gets confused.

@KeyJ @morgan3d

After I thought a while my best guess is the additional linebreak.
Line 142 should not exist, it should be added to line 141.

@chbmeyer You can run Markdeep in different modes. For working with a LMS I recommend using "HTML" mode. In that mode Markdeep will only process within <markdeep> tags.

You can also run in "script" mode and explicitly invoke the markdown renderer from JavaScript to have full control.