5 ms·

I love Pelican. It was relatively easy for me to migrate from Octopress (which seems pretty much dead at this point). With pelican it was pretty easy for me to

I love Pelican. It was relatively easy for me to migrate from Octopress (which seems pretty much dead at this point). With pelican it was pretty easy for me to write by own extremely lightweight theme: https://brashear.me/blog/2017/07/30/migration-from-octopress-to-pelican/ https://brashear.me/blog/2017/07/30/migration-from-octopress...

stadeschuldt 8y ago
Coming from Python I like Pelican a lot. It also looks like there is an active development going on: https://github.com/getpelican/pelican https://github.com/getpelican/pelican I am still wondering, why the last release was made over 18 month ago.
- discreditable 8y ago
  My Python is only marginally better than my Ruby (not great). Even so, developing my own theme was easy following their docs. Looking at their blog[1] they seem to do releases very infrequently. 3.5 was released 2014-11-20. 3.6 was released 2015-06-15. 3.7 was released 2016-12-12. It seems like each release is about a year and a half apart. By that cycle we're about due for one. 1. https://blog.getpelican.com/category/news.html https://blog.getpelican.com/category/news.html
- AndyMcConachie 8y ago
  Possibly because stability is a good thing in software. Not saying that's the case with Pelican, but I like things that don't change much. It often means developers know what they're doing.
- IronBacon 8y ago
  Well, I'm still using an ancient version (2.8?) cause the last stable broke the Markdown footnotes' linking (maybe it's a bug in my theme). I'll probably look this week if the bug was fixed, but I'm not in a hurry, last time I updated I didn't realized they eliminated some Jinja2 corner cases that I abused for scoping variables outside code blocs and I think I'm still using the global context in a "creative" way... ^__^;
dunpeal 8y ago
Isn't its license - AGPL v3.0 - a problem? My understanding of the AGPL in this case is that if you publish a blog with Pelican, you have to also publish any trivial fork of Pelican that you create, even if only by a single trivial patch. Seems rather onerous given how likely us devs are to tweak something here or there. I'd gravitate towards any of the many MIT-licensed generators instead.
- smnrchrds 8y ago
  I don't think so. Which provision of AGPL would mandates that?
JoshMnem 8y ago
Pelican is great, especially if you spend a little time configuring the URL structure to remove the `.html` from the end of the URLs. I think something like this will work for most pages (might be incomplete): https://github.com/j127/pelican_blog_project_template/blob/master/pelicanconf.py#L33 https://github.com/j127/pelican_blog_project_template/blob/m...
abdullahkhalids 8y ago
Dead simple. I set it up six years ago, with maybe a full day of work. Never really had to do anything since then, except write my entries in markdown file, and run a script that generates the website and uploads to my nearlyfreespeech hosting server.

stadeschuldt 8y ago

Coming from Python I like Pelican a lot. It also looks like there is an active development going on: https://github.com/getpelican/pelican https://github.com/getpelican/pelican I am still wondering, why the last release was made over 18 month ago.

discreditable 8y ago
My Python is only marginally better than my Ruby (not great). Even so, developing my own theme was easy following their docs. Looking at their blog[1] they seem to do releases very infrequently. 3.5 was released 2014-11-20. 3.6 was released 2015-06-15. 3.7 was released 2016-12-12. It seems like each release is about a year and a half apart. By that cycle we're about due for one. 1. https://blog.getpelican.com/category/news.html https://blog.getpelican.com/category/news.html
AndyMcConachie 8y ago
Possibly because stability is a good thing in software. Not saying that's the case with Pelican, but I like things that don't change much. It often means developers know what they're doing.
IronBacon 8y ago
Well, I'm still using an ancient version (2.8?) cause the last stable broke the Markdown footnotes' linking (maybe it's a bug in my theme). I'll probably look this week if the bug was fixed, but I'm not in a hurry, last time I updated I didn't realized they eliminated some Jinja2 corner cases that I abused for scoping variables outside code blocs and I think I'm still using the global context in a "creative" way... ^__^;

dunpeal 8y ago

Isn't its license - AGPL v3.0 - a problem? My understanding of the AGPL in this case is that if you publish a blog with Pelican, you have to also publish any trivial fork of Pelican that you create, even if only by a single trivial patch. Seems rather onerous given how likely us devs are to tweak something here or there. I'd gravitate towards any of the many MIT-licensed generators instead.

smnrchrds 8y ago
I don't think so. Which provision of AGPL would mandates that?

JoshMnem 8y ago

Pelican is great, especially if you spend a little time configuring the URL structure to remove the `.html` from the end of the URLs. I think something like this will work for most pages (might be incomplete): https://github.com/j127/pelican_blog_project_template/blob/master/pelicanconf.py#L33 https://github.com/j127/pelican_blog_project_template/blob/m...

abdullahkhalids 8y ago

Dead simple. I set it up six years ago, with maybe a full day of work. Never really had to do anything since then, except write my entries in markdown file, and run a script that generates the website and uploads to my nearlyfreespeech hosting server.