org-octopress icon indicating copy to clipboard operation
org-octopress copied to clipboard

Separate org-octopress organization from org-jekyll

Open justin808 opened this issue 11 years ago • 2 comments

@yoshinari-nomura How about if we break out ox-jekyll into it's own project?

And then have org-octopress depend on it?

I've come the conclusion that it's simpler and more accurate to skip any conversion to markdown and to use the HTML formatting.

I just sent you the code to make source blocks work.

Basically, my workflow is: (see my article: http://railsonmaui.com/blog/2013/04/27/octopress-setup-with-github-and-org-mode/)

  1. Use rake task to generate blank blog post file or blank page file. This places the yaml front matter (which ox-jekyll is doing right now)
  2. I've got my publishing setup for various page and blog entries for octopress.
  3. I then run a emacs command to publish the project (rather than the single file).

Let me know what you think.

I think I should create a separate github project for org-ox-jekyll, and then we can change org-octopress to depend on it.

justin808 avatar Nov 25 '13 11:11 justin808

Hi, Justin

I've come the conclusion that it's simpler and more accurate to skip any conversion to markdown and to use the HTML formatting.

Yes, I recommend you to so.

From #11, I have understood you are planning to make the most of octopress plugins suchlike {% codeblock %}. I think it should be configurable whether to use the original src-block expansion or your one.

About your workflow, I have a comment. It is very clever way but I don't want to insert YAML front matter using #+BEGIN_HTML because YAML front matter is not an HTML at all. This is somewhat an abuse of #+BEGIN_HTML. That's why I added #+JEKYLL_* options that compliant with the org-mode manner.

So, how about modify the first step like:

  1. Use rake task to generate blank blog post file or blank page file as an org file. This rake task places the #+JEKYLL_* headers instead of YAML front matter. That is, it does the same as org-octopress-new-post.

I could not understand why you want to split org-octopress project into two. Even now, you can use only the exporter if you don't want to use Emacs UI suchlike org-octopress-new-post.

I sometimes invoke Emacs in batch-mode from Makefile or Rakefile. It would be match your taste if you like Rakefile and command line interface.

yoshinari-nomura avatar Nov 25 '13 15:11 yoshinari-nomura

Ok, that works. We just put the front matter in the org file when we create it and I can modify my rake task to call this function.

Let's figure out how the publishing configuration can handle static pages.

Justin Gordon | 808-877-6461 | m: 808-281-7272 www.railsonmaui.com | twitter: @railsonmauihttps://twitter.com/railsonmaui | sugarranchmaui.com http://www.sugarranchmaui.com/ | Sugar Ranch Bloghttps://www.facebook.com/SugarRanch

justin808 avatar Nov 25 '13 18:11 justin808