4 ms·

> Eleventy is "Jekyll but in JavaScript" and way closer to what I want, but its flavor of Liquid is just slightly different from Jekyll's to the point where I w

> Eleventy is "Jekyll but in JavaScript" and way closer to what I want, but its flavor of Liquid is just slightly different from Jekyll's to the point where I would have to update a bunch of posts, plus there's no incremental build yet. So much for > bamboleo 3 days ago [–] https://news.ycombinator.com/item?id=25561177 https://news.ycombinator.com/item?id=25561177 > You can’t be serious. Jekyll blogs are pure text files you can download and view in a thousand ways. Good luck extracting sensible data from WordPress’ database without losing metadata. Unless SSG get a common metadata and/or post format I don't think migration is as smooth as some say it is. In the XML days we had ATOM. I don't know if we have any JSON/MD things like that ?

ratww 6y ago
The posts on those are just Markdown, and most of them use the same metadata format. For Atom/RSS you can use a plugin in Jekyll or 11ty. It's really not that complicated...
- johnchristopher 6y ago
  I believe you are missing my point. I am not talking about syndication, I am talking about a reliable standard post/content format that would guarantee interoperability and plug and playability between static CMS. Without tweaking.
  - ratww 6y ago
    I did understand, maybe you misunderstood me. I answered your question by saying that the current format (Markdown+Metadata) is the one used by lots of popular Static CMSs. I wrote one to migrate away from Jekyll and it was just a matter of copying the files. There's absolutely nothing more to it, it's just files. I answered about ATOM/RSS because it might be useful if you want to migrate to something that supports importing using ATOM. Of course, there's also templates, Wordpress also has zero compatibility or ability to export templates or reuse them somewhere, so I don't think it applies.
dceddia 6y ago
Heh, they are indeed pure text files, but then again so is XML :D My Jekyll posts are mostly Markdown with some YAML frontmatter, but some have a few "include" statements here and there that use Liquid. The frontmatter stuff is easy enough to transform with some `sed` commands or whatever. The bigger problem is the surrounding stuff that relies more on Liquid, like email signup forms, the list of posts, the list of tags, etc. All the little things that would need a small bit of work to reformat to work with another tool, it all adds up. And there were some oddities with how the two parsers handled newlines around Liquid, so sometimes Eleventy's output would be jumbled together when Jekyll's looks fine.
- johnchristopher 6y ago
  There's a quote about reinventing xml ^^. 15 years ago I wrote a very rudimentary static blog using only ATOM documents and some XSL. Maybe it's time to revisit the idea. > The bigger problem is the surrounding stuff that relies more on Liquid, like email signup forms, the list of posts, the list of tags, etc. All the little things that would need a small bit of work to reformat to work with another tool, it all adds up. Yeah, but then it's not really content (posts) so I think it's okay. This doesn't need to be as portable.

ratww 6y ago

The posts on those are just Markdown, and most of them use the same metadata format. For Atom/RSS you can use a plugin in Jekyll or 11ty. It's really not that complicated...

johnchristopher 6y ago
I believe you are missing my point. I am not talking about syndication, I am talking about a reliable standard post/content format that would guarantee interoperability and plug and playability between static CMS. Without tweaking.
- ratww 6y ago
  I did understand, maybe you misunderstood me. I answered your question by saying that the current format (Markdown+Metadata) is the one used by lots of popular Static CMSs. I wrote one to migrate away from Jekyll and it was just a matter of copying the files. There's absolutely nothing more to it, it's just files. I answered about ATOM/RSS because it might be useful if you want to migrate to something that supports importing using ATOM. Of course, there's also templates, Wordpress also has zero compatibility or ability to export templates or reuse them somewhere, so I don't think it applies.

dceddia 6y ago

Heh, they are indeed pure text files, but then again so is XML :D My Jekyll posts are mostly Markdown with some YAML frontmatter, but some have a few "include" statements here and there that use Liquid. The frontmatter stuff is easy enough to transform with some `sed` commands or whatever. The bigger problem is the surrounding stuff that relies more on Liquid, like email signup forms, the list of posts, the list of tags, etc. All the little things that would need a small bit of work to reformat to work with another tool, it all adds up. And there were some oddities with how the two parsers handled newlines around Liquid, so sometimes Eleventy's output would be jumbled together when Jekyll's looks fine.

johnchristopher 6y ago
There's a quote about reinventing xml ^^. 15 years ago I wrote a very rudimentary static blog using only ATOM documents and some XSL. Maybe it's time to revisit the idea. > The bigger problem is the surrounding stuff that relies more on Liquid, like email signup forms, the list of posts, the list of tags, etc. All the little things that would need a small bit of work to reformat to work with another tool, it all adds up. Yeah, but then it's not really content (posts) so I think it's okay. This doesn't need to be as portable.