I am having issues with the Marked plugin not rendering line breaks as paragraph tags when content is fetched as a collection. I see the line breaks being added in Chrome dev tools.

I am also having issues with some HTML tags not being rendered, e.g. lists. Some tags (i.e. <i>) appear to render fine.

I've created a collection as so:

services: ->
  @getCollection('html').findAllLive(
      relativeOutDirPath: 'services'
      omitFromCollection: {$ne: true}
      [{weight:1}]
  )

In my Eco template, I am fetching the collection as so:

<% for service in @getCollection("services").findAll().toJSON(): %>

The following code will render some HTML (like <i> tags) but it will not convert \n to <p>:

<%- service.content %>

When it's rendered on its own page, it works perfectly. Am I creating the collection wrong or is this a bug?

I added some hacky JS for the meantime to fix the line breaks, and thankfully I don't need to use lists at this time, but it would be nice if the Marked plugin supported this out-of-the-box for fetching as collections as well.

For others who have the same problem, here's my quick fix for the paragraphs until the Marked plugin converts line breaks to paragraphs:

<p>
<% @serviceContent = service.content.replace(/\n/g, '</p><p>') %>
<%- @serviceContent %>
</p>

Thanks for your help!

After inspecting the code, it seems there is an undocumented feature: markedRenderer. See this gist for more info. It would be nice to add that to README.md so people can know about this shortcut :).

Also, at first it wasn't clear to me that I had to put markedOptions in docpadConfig.plugins.marked. (I tried things like docpadConfig.plugins.markedOptions and docpadConfig.plugins.marked.[marked setting here]. This was probably due to me not interpreting correctly, but some extra clarity never hurts.

I suggest something like this snippet:

You can customise the Marked options by using the `markedOptions` object. Custom marked renderers can be added via `markedRenderer`, like so:
docpadConfig =
    plugins:
        marked:
            markedOptions:
                # customize Marked here... (see https://github.com/chjj/marked#options-1)
            markedRenderer:
                # custom renderer methods here...
                # same as passing a custom renderer instance to `docpadConfig.plugins.marked.markedOptions.renderer` (https://github.com/chjj/marked#renderer)
                # for accepted keys, refer: https://github.com/chjj/marked#block-level-renderer-methods and https://github.com/chjj/marked#inline-level-renderer-methods

I think everything is in the title. I stumbled upon this on npmjs.org.

I'm trying to use the renderer option for marked: https://github.com/chjj/marked#renderer

I expects an instance with some methods, like from new marked.Renderer().

But the plugin errors somewhere in marked, it cannot find methods on the instance I set in the markedOptions.

I investigated and it looks like something is replacing my instance with another object? A model with has/get/set methods?

All options properties get passed but methods get removed.

Hello there, would it be possible instead of using Marked, to use https://github.com/markdown-it/markdown-it which seems to have included many handy improvements, especially Footnotes which is required on my projects.

I've tried to use this plugin with Docpad v6.56.0 but it doesn't work at all.

Could you please take a look @balupton? https://github.com/braziljs/foundation/tree/docpad

Hi dear Bevry team,

Github informed me by email this morning there is a moderate severity security vulnerability detected in marked < 0.3.9, in my website ...
But Docpad in this actual version (v6.79.4) require docpad-plugin-marked in ~2.4.0 ...
Maybe it's time for an update ?

thanks for your work !

Each day on IRC someone is experiencing issues with sanitisation. We should make this off by default, instead of on.

Any arguments against this change @chase ?

Since it’s already supported by Marked, it would be great to be able to override renderers right from Docpad’s config. It’s also partially supported by docpad-plugin-robotskirt. Something like this:

plugins: {
marked: {
  markedRenderer: {
    heading: function (text, level) {
      var escapedText = text.toLowerCase().replace(/[^\w]+/g, '-');
      return '<h' + level + '>' +
        text + ' <a name="' +
        escapedText +
        '" class="anchor" href="#' +
        escapedText +
        '"><span class="header-link"># </span></a></h' + level + '>';
    }
  }
},

Copied from StackOverflow question full of additional details.

There’s even a fork with all needed features applied, so it’s just a matter of checking if everything is correct and filing a pull request.

/cc @vladikoff @varya

How can I enable Syntax highlighting for JavaScript? Thank you