koenbok
commented
10 years ago This looks really good. I'll check it further out tomorrow.
On Wednesday, July 9, 2014, Craig Zheng notifications@github.com wrote:
Updates the blog plugin to be more configurable and work with pure(ish) Markdown files.
I discussed this via email with Koen a few months ago, but I haven't heard back in a while. Figured I'd go ahead and submit it and see what happens. I don't necessarily expect this to get merged right now, just want to put it
out there for discussion and improvement. Here's my last email to Koen:
You can see I had to make a couple of tiny changes to page.py. There are other ways around that problem but that was the least intrusive I could think of. If you'd rather solve it in a different way, let me know and I can adapt the blog plugin accordingly.
Here's a writeup of how it works right now: [ https://gist.github.com/cz/5f8e58e76dfa9d0f8e3e]. Could be the basis for user docs later on.
Feel free to comment inline on the commit if there are changes you'd like to see. Or if this looks good enough for a pull request just let me know and I'll submit it.
Finally, was curious to know what your vision is for the plugin system in general. Is it as extensive as you'd like it to be? Do you imagine any sort of ecosystem of externally-maintained plugins? I'm inclined to continue tinkering with this (exploring stuff like tags and excerpts) to see if we
can arrive at a proper Jekyll/Pelican alternative.
You can merge this Pull Request by running
git pull https://github.com/cz/Cactus v3
Or view, comment on, or merge it at:
https://github.com/koenbok/Cactus/pull/96 Commit Summary
- First pass at markdown-only blog posts
- Merge branch 'v3' of github.com:koenbok/Cactus into v3
File Changes
- M cactus/page.py https://github.com/koenbok/Cactus/pull/96/files#diff-0 (5)
- M cactus/skeleton/plugins/blog.disabled.py https://github.com/koenbok/Cactus/pull/96/files#diff-1 (197)
Patch Links:
— Reply to this email directly or view it on GitHub https://github.com/koenbok/Cactus/pull/96.
cz
guaka
chaudum
anvol
Updates the blog plugin to be more configurable and work with pure(ish) Markdown files. See also #15.
I discussed this via email with Koen a few months ago, but I haven't heard back in a while. Figured I'd go ahead and submit it and see what happens. I don't necessarily expect this to get merged right now, just want to put it out there for discussion and improvement. Here's my last email to Koen:
You can see I had to make a couple of tiny changes to page.py. There are other ways around that problem but that was the least intrusive I could think of. If you'd rather solve it in a different way, let me know and I can adapt the blog plugin accordingly.
Here's a writeup of how it works right now: [https://gist.github.com/cz/5f8e58e76dfa9d0f8e3e]. Could be the basis for user docs later on.
Feel free to comment inline on the commit if there are changes you'd like to see. Or if this looks good enough for a pull request just let me know and I'll submit it.
Finally, was curious to know what your vision is for the plugin system in general. Is it as extensive as you'd like it to be? Do you imagine any sort of ecosystem of externally-maintained plugins? I'm inclined to continue tinkering with this (exploring stuff like tags and excerpts) to see if we can arrive at a proper Jekyll/Pelican alternative.