juanre/org-jekyll

Export jekyll posts from org-mode

org-jekyll's Issues

Please specify the license for this package

Could you please specify the license used for this package?

Assuming that you want to release under "the GPL v3 or any later version", the best way to do that would be to add this permission statement to the library header:

;; This file is free software; you can redistribute it and/or modify
;; it under the terms of the GNU General Public License as published by
;; the Free Software Foundation; either version 3, or (at your option)
;; any later version.

;; This file is distributed in the hope that it will be useful,
;; but WITHOUT ANY WARRANTY; without even the implied warranty of
;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
;; GNU General Public License for more details.

;; You should have received a copy of the GNU General Public License
;; along with this program.  If not, see <http://www.gnu.org/licenses/>.

Also consider adding a LICENSE file containing the text of the GPL-3. You could add just that file without also adding the above persmission statement, but if you do that, then the "or (at your option) any later version" bit won't be known. So I recommend that you add both the actual license and the permission statement.

If you find the permission statement to be too noisy, then you could instead add one of these following lines to the header. If you do that, then it becomes more important to also add the LICENSE file - a judge might decide that such a line by itself is not sufficient. Still, adding just such a line is better than not specifing the license at all.

;; License: GNU General Public License version 3, or (at your option) any later version
;; License: GNU General Public License version 3, or any later version
;; License: GNU GPL version 3, or (at your option) any later version
;; License: GPL version 3, or (at your option) any later version
;; License: GPL version 3, or any later version
;; License: GPL v3, or (at your option) any later version
;; License: GPL v3, or any later version
;; License: GPL-3+

tags property

The property "tags" does not seem to be translated into YAML from the properties drawer in org. It seems to be because it is a "special property" in org. http://orgmode.org/manual/Special-properties.html#Special-properties

But how does one go about setting the tags for posts then?

Ignore children in subtree

Hello

I am attracted by the idea of exporting subtree in a org file, which is presented in your package. However, I found that it only export the content of the entry and the title of the sub-entries. The contents of the sub-entries are totally ignored. However, when I export entry using org-jekyll-export-current-entry, the contents are correctly exported.

I have solved this problem by modifying the line

(org-map-entries (lambda () (org-jekyll-export-entry project))
                 "blog|BLOG"))))

to

(org-map-entries (lambda () (org-show-subtree) (org-jekyll-export-entry project))
                 "blog|BLOG"))))

It seems the command (org-content) only return the table of content (folding the content) and the (org-map-entires) would not automatically expand the entry to the function.

With kind regards

[feature request] publish all subtrees except the ones with :private: property

Hi,

Would you consider adding the feature to publish all subtrees by default (even without the :on: property), except the subtrees with a :private: property?

org-jekyll is a veritable boon for us. Thank you so much for your work!

Org-Jekyll small sample .org; working with images, math, and pages (as opposed to posts)

Thank you for writing Org-Jekyll.

I have tried a few Org-Jekyll (or Org-Octopress) solutions in the past few weeks but none of them seem to work with the drastically-changed Org 8. I was wondering if you could add to your repository a small sample .org file which could be used for testing as well as serve as a template. (This would especially help the user to see how the tags :blog: and :on: must be applied, since the export methodology used by your Org-Jekyll is tag based, and not file based.)

Also I am particularly curious whether your Org-Jekyll handles correctly the following:

• images (via native Org [[file:rel_path/to/image.png][Image]]
• math (since only the body is exported by Org, the path to MathJax.js, say, the official secure MathJax CDN must be added by Jekyll. (How) Is this done?)
• pages (as opposed to posts. I know handling these is done by Jekyll but does it work correctly when combined with Org?)

Merge with org-mode

Would you consider merging or mirroring org-jekyll in the org-mode repo? There's a contrib/ directory for that, I think.

[feature request] manage most or all of a source folder

Hi,

I find org-jekyll very useful already, because of its focus on managing a blog via a single org-mode file using jekyll's powerful features.

Basically, org-jekyll greatly helps manage the _posts part of a jekyll setup.

It is very useful to keep the blog section of a site as one org-file, and very empowering to be able to use jeckyll to publish it, since that offers for free:

• jekyll's templating, which is one of org-publish's weak spots. That means, for example, being able to expose org-mode's properties to jekyll (very nice!);
• jekyll's plugins;
• jekyll's themes (another weak spot in org-publish);
• also, one can use org-jekyll with octopress, with even more benefits.

It would be extremely useful, I am sure not only for me, to be able to use org-jekyll to manage a whole site as well (i.e. most or all of the source folder, not just the _posts subfolder).

One possible way that could be done would be by calling org-publish specifying a different publishing-function instead of org-publish-org-to-html. Having the same recursive traversal of the source folder, applying something like org-jekyll-export-entry instead.

One of org-jekyll's strongest points (at least according to me) is to manage a given folder with one monolithic org file.

The new feature could expand on that. Each org file's subtree could be published as a set of jekyll (yaml+html) files inside the corresponding subfolder in source.

Also, since (usually, at least for pages), the default behavior is to be published (versus keeping as drafts). It would be nice to publish all subtrees by default.

Since it is in any case a must to be able to specify certain subtrees as drafts, perhaps a :private: property could be considered.

It would be also nice if the properties could be inherited, or defined globally at the beginning of an org file.

Perhaps, the distinction between blog and page could be moved to a property, too, instead of specifying a tag like it is now. In this way tags could be left exclusively to the user.

Thank you so much for considering this.

org-jekyll-export-blog exports quote blocks as "nil" (8.0 branch)

Using the org-mode-8.0 branch, I found that entries exported using org-jekyll-export-blog would export quote blocks in subtrees as <p>nil</p>.

Example block:

#+BEGIN_QUOTE
"By placing tools in the middle of the conversation, 
everyone is pairing all of the time." -- Jesse Newland
#+END_QUOTE

When exporting the subtree with org-jekyll-export-current-entry all is okay.

Renaming files

Thanks a lot for making this - it is just what I am looking for.
I've been monkeying for a few hours on renaming the files by prepending the right date to the file name. Your website seems to say this will happen, but I can't make it go for love or money.
http://juanreyero.com/open/org-jekyll/

Is there an option I should be triggering? Thanks for any help.