Plans to support JSON Feed?

[reefdog]

JSON Feed was just announced. Assuming it has any legs—Manton and Brent are no lightweights—it might stick around. Is it reasonable to expect jekyll-feed to one day support it alongside Atom, or should a new plugin be developed?

Either way, I'm keen to help develop support. Just wondering if it belongs in a new plugin or as a configurable option for this one.

[pathawks]

I can't speak for @benbalter, but I have no plans at this point.

If there were a compelling advantage, we could take another look. I am very excited about the technology, but I think we need to be conservative about what we add.

From the JSON Feed spec:

Any publisher already publishing RSS and/or Atom should continue to do so. In fact, if you’re trying to decide which format (of RSS, Atom, and JSON Feed) to use, and you can do only one, pick RSS — it’s time-tested, popular, and good.

[benbalter]

I'm with @pathawks on this one. If we add it now, we have to support it in perpetuity, even if consumers don't adopt it.

That said, we may be able to move some of the template logic to a drop like we did for SEO tag (creating shared field values), and allow another plugin to consume those calculated fields.

[reefdog]

Sensible position. Thanks, both! (Feel free to close this or leave it open as a signpost, as you see fit.)

[pathawks]

If we did support JSON Feed, we would want to build the feed in Ruby rather than Liquid (like what SEO Tag now does for JSON-LD).

Closing for now, but if there were a compelling use case I really would love to add support. Will keep an eye on this.

[pathawks]

That said, we may be able to move some of the template logic to a drop like we did for SEO tag (creating shared field values), and allow another plugin to consume those calculated fields.

@benbalter I wonder how much shared logic there is between jekyll-feed and jekyll-seo. I wonder if it would make any sense at all to abstract some of that logic into a separate gem?

[parkr]

I'm really jazzed about this project and would love to see JSON Feed supported. Could we reconsider this? Would it make more sense to ship as a separate plugin, e.g. jekyll-feed-json?

[pathawks]

Maybe we 🎄 and if a site specifies a path in site.feed.json_path we can enable JSON Feed output?

There is enough shared logic that it would be a shame to duplicate everything in a second gem.

FWIW, Gruber is making me more excited for JSON Feed as well.

[parkr]

Maybe we 🎄 and if a site specifies a path in site.feed.json_path we can enable JSON Feed output?

I think defaulting this to false would be a good way to go about doing this for the first iteration or two. If, in a few months, this thing hasn't gone away, then we can default it to true and give everyone Better Feeds™️.

[mattr-]

Based on https://ndarville.com/blog/2017/05/19/json-feed-for-jekyll/ I think we're better off leaving out support for JSON feed for now.

[parkr]

The layout is imperfect at best. I plopped it into my site and i had to fix all sorts of things because quotes & HTML borked it up. There is no Liquid replacement for JSON.generate.

[mattr-]

There is no Liquid replacement for JSON.generate.

No doubt. But it seems good enough for now, which gives us the ability to see how JSON feed adaption progresses and how the "standard" develops. I see no reason for us to add support that we have to maintain in near perpetuity for a 2 day old spec.

[mryellow]

If there were a compelling advantage

Pulling post lists with Javascript into SPA.

Parsing XML is old-hat.