jekyll-org-mode-converter 0.1.6 → 0.1.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 507492c094ee73eee0923aa4a3c26d801d146929
-  data.tar.gz: 2a61d495b21d1dc056c1b876f4f4a73f59150f44
+  metadata.gz: 431fa2402a74aae26f855c2d82965d491c249a8f
+  data.tar.gz: 807c465d160a7cda5e1a547d45c55cc049215e0b
 SHA512:
-  metadata.gz: 00786f59c4769486f15fd87c9254649adfc705143e4ee8085a838f35767ba7e7ebb7020a667bc6e0b8fec4780de8f51856d7e0080108a4f05ef465a5befab5be
-  data.tar.gz: 5bd9cdb4553aa3d14254aa272049db430a07e32ef07098d18d17851cf9047169b2f18f4afe87007bad04500ae635d140e7bdd5e2a22f2eb7c0242a6a86aea6cf
+  metadata.gz: be670e2a50fef33acb41865dfcfcfd64b963d5efc37662af6b389eaf8fd7b99a7fb0ad6cc65463e1c11d41792078ed405b37ca6cfa5c546b49f942b7acf88aad
+  data.tar.gz: c4c3e5ad23b14fb72ca856953f13f5026bdcff5ac365257b096ed3b0f0e709859c71912f4b778946473e9537a82c052de4fcc1236f5494e31cab413f2a36463f

data/README.org

@@ -20,8 +20,8 @@ While this seems like a great project, it has some problems:
 
 To convert your documents you need to run a separate make file that runs some elisp to convert your org files to html, and then run Jekyll in a sub directory on the converted html to build the resulting website. 
 
-While I understand that hacking Elisp seems like the appropriate course of action for the experienced Emacs user in any scenario, 
-I don't believe *every problem* is best solved by hacking Elisp.
+While I understand that hacking Elisp always seems like the appropriate course of action for many experienced Emacs users, 
+I don't believe *every problem* is best solved inside Emacs.
 
 ** My approach
 I decided to approach the problem from a Jekyll point of view. I wanted to use the standard Jekyll workflow, only with Org mode files instead of Markdown files.  
@@ -79,10 +79,10 @@ bundle exec jekyll serve
 ** Deploying to Github
 One of the cool features of Jekyll is that you can deploy Jekyll websites to Github by simply pushing the Jekyll code
 to your GitHub remote. Unfortunately for us, Github does not allow you to run custom plugins for [[http://jekyllrb.com/docs/plugins/][security reasons]].
-This implies that to use [[https://help.github.com/articles/using-jekyll-with-pages/][Jekyll with GitHub Pages]] you ideally need to write posts in Markdown. But I love Org mode and I don't want to learn yet another markup language. 
+This implies that to use [[https://help.github.com/articles/using-jekyll-with-pages/][Jekyll with GitHub Pages]] you ideally need to write posts in Markdown. But we love Org mode and we don't want to learn yet another markup language. 
 
-Luckily all is not lost, but one will need to build your site locally and push your static pages to GitHub.
-To keep everything tidy I organize my git repository in the following way:
+Luckily, all is not lost. We will need to build our site locally and push the static pages to GitHub.
+My approach is to keep both the Jekyll code and the static HTML in a single repository, which I organize in the following way:
 
 #+begin_src
 .
@@ -91,13 +91,13 @@ To keep everything tidy I organize my git repository in the following way:
 |
 |-- www          (resulting site goes here)
 |
-|-- .nojekyll    (prevents GitHub from processing our jekyll code)
+|-- .nojekyll    (prevents GitHub from building our Jekyll code)
 |
-|-- index.html   (redirects users to www/index.html)
+|-- index.html   (redirects users to www/)
 #+end_src
 
 
-You will need to configure the destination directory by adding the following line in your ~_config.yml~
+You need to configure the destination directory by adding the following line in your ~_config.yml~
 #+begin_src ruby
 destination: ../www
 #+end_src
@@ -107,21 +107,21 @@ For relative links to work properly you will also need to set the ~baseurl~ prop
 baseurl: /www
 #+end_src
 
-Also, you will need to create a file called ~.nojekyll~ to prevent GitHub from trying to serve the Jekyll pages in the src directory.
+Also, you should create a file called ~.nojekyll~ to prevent GitHub from trying to build the Jekyll pages in the src directory.
 
-Create ~index.html~ with the following content
+Create ~index.html~ to redirect to the ~wwww~ directory
 #+begin_src html
 <html>
 <meta http-equiv="refresh" content="0; url=www" />
 </html>
 #+end_src
 
-Run ~jekyll build~ on the ~src~ directory and push the results to GitHub.
+Localy you should run ~jekyll build~ on the ~src~ directory and push the results to GitHub.
 
 
 
 ** Example
-To see an example of the Github deployment method in action, have a look at [[http://tjaartvdwalt.github.io][my personal website]]. You can see the source code [[http://tjaartvdwalt.github.io/][here]].
+To see an example of the Github deployment method in action, have a look at [[http://tjaartvdwalt.github.io][my personal website]]. You can see the source code [[https://github.com/tjaartvdwalt/tjaartvdwalt.github.io][here]].
 
 ** Contributing to jekyll-org-mode-converter
  

data/VERSION

@@ -1 +1 @@
-0.1.6
+0.1.7

data/jekyll-org-mode-converter.gemspec

@@ -2,11 +2,11 @@
 # DO NOT EDIT THIS FILE DIRECTLY
 # Instead, edit Jeweler::Tasks in Rakefile, and run 'rake gemspec'
 # -*- encoding: utf-8 -*-
-# stub: jekyll-org-mode-converter 0.1.6 ruby lib
+# stub: jekyll-org-mode-converter 0.1.7 ruby lib
 
 Gem::Specification.new do |s|
   s.name = "jekyll-org-mode-converter"
-  s.version = "0.1.6"
+  s.version = "0.1.7"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.require_paths = ["lib"]

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: jekyll-org-mode-converter
 version: !ruby/object:Gem::Version
-  version: 0.1.6
+  version: 0.1.7
 platform: ruby
 authors:
 - Tjaart van der Walt