Supposedly Jekyll has the advantage that is supported by GitHub Pages.
This actually bit me moving to Netlify the other day. All my builds would fail because I didn't require the github-pages gem. I didn't think I needed it since I wasn't using Github Pages anymore, but apparently, that gem includes jekyll and the fluff needed for github pages, so Netlify's documentation says to require it so they can use it to build.
Supposedly Jekyll has the advantage that is supported by GitHub Pages.
It means you only need to modify the content and make git push. :-)
And the disadvantage is that is not made in Python. ;-)
Why is that a disadvantage?
It was a joke. Because I like Python more than Ruby.
Just a matter of taste.
I have never made a real comparison before, feature by feature.
I did just use Pelican and it was very nice. If you need extensions then it is better to choose one from the programming language that you use.
This actually bit me moving to Netlify the other day. All my builds would fail because I didn't require the github-pages gem. I didn't think I needed it since I wasn't using Github Pages anymore, but apparently, that gem includes jekyll and the fluff needed for github pages, so Netlify's documentation says to require it so they can use it to build.
The Python-Based version of Jekyll is Hyde. github.com/hyde/hyde
I guess the templates are 100% compatible, right ?
I wasn't aware. Thank you.
Then I would use Hyde to process the content locally and publish the templates in github pages.