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

[priyadarshan]

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.