[wip] migrate site from jekyll to nanoc

still miss:
* pagination
* deploy via FTP
* travis CI
* checks

.gitignore

@@ -1 +1,5 @@
-/_site
+# nanoc life
+/tmp/*
+/crash.log
+/output/*
+

.travis.yml

@@ -1,9 +1,10 @@
-before_script:
-    - gem install jekyll
-    - gem install rdiscount
+# TODO nanoc build + deploy FTP
+# before_script:
+#     - gem install jekyll
+#     - gem install rdiscount
 
-script:
-    - jekyll --safe
+# script:
+#     - jekyll --safe
 
-notifications:
-    - email: false
+# notifications:
+#     - email: false

Gemfile

@@ -0,0 +1,30 @@
+source 'https://rubygems.org'
+
+# nanoc itself
+gem 'nanoc', '~>3.6', '>=3.6.6'
+
+# nanoc view
+gem 'adsf'
+gem 'rack'
+
+# nanoc validate:css and validate:html Rake tasks
+gem 'w3c_validators'
+
+# nanoc filters
+gem 'kramdown' # markdown
+
+# css
+gem 'rainpress'
+
+# relativize paths
+gem 'nokogiri'
+
+# javascript
+gem 'uglifier'
+
+# html
+gem 'html_compressor'
+
+# syntax highlighting
+gem 'htmlentities'
+gem 'systemu'

Gemfile.lock

@@ -0,0 +1,49 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    POpen4 (0.1.4)
+      Platform (>= 0.4.0)
+      open4
+    Platform (0.4.0)
+    adsf (1.2.0)
+      rack (>= 1.0.0)
+    colored (1.2)
+    cri (2.5.0)
+      colored (~> 1.2)
+    execjs (2.0.2)
+    html_compressor (0.0.3)
+      POpen4 (>= 0.1.4)
+    htmlentities (4.3.1)
+    json (1.8.1)
+    kramdown (1.3.3)
+    mini_portile (0.5.3)
+    nanoc (3.6.8)
+      cri (~> 2.3)
+    nokogiri (1.6.1)
+      mini_portile (~> 0.5.0)
+    open4 (1.3.3)
+    rack (1.5.2)
+    rainpress (1.0)
+    systemu (2.6.4)
+    uglifier (2.5.0)
+      execjs (>= 0.3.0)
+      json (>= 1.8.0)
+    w3c_validators (1.2)
+      json
+      nokogiri
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  adsf
+  html_compressor
+  htmlentities
+  kramdown
+  nanoc (~> 3.6, >= 3.6.6)
+  nokogiri
+  rack
+  rainpress
+  systemu
+  uglifier
+  w3c_validators

README.md

@@ -1,6 +1,5 @@
 # Olivier Patry
 
-Personal home page source control based on [GitHub Pages](http://pages.github.com/) based on [Jekyll](https://github.com/mojombo/jekyll).
-The content is, most of the time, written using [Markdown](http://daringfireball.net/projects/markdown/).
+The content is, most of the time, written using [Markdown](http://daringfireball.net/projects/markdown/) and served by `[nanoc](http://nanoc.ws/)`.
 
-The opatry's user GitHub Page is redirected to http://opatry.net. 
+The opatry's user GitHub Page is deployed on http://opatry.net. 

Rules

@@ -0,0 +1,51 @@
+#!/usr/bin/env ruby
+
+compile '/assets/*' do
+  # don’t filter or layout
+end
+
+compile '*' do
+  if item.binary?
+    # don’t filter binary items
+  else
+    filter :fenced_code_block
+    filter :erb
+    filter :kramdown
+    filter :colorize_syntax, :default_colorizer => :pygmentize  # syntax highlighting
+    unless item[:layout] == 'none'
+      layout item[:layout] || 'default'
+    end
+    #filter :html_compressor, :type => item[:extension]
+  end
+end
+
+route '/posts/*' do
+  y,m,d,slug = /([0-9]+)\-([0-9]+)\-([0-9]+)\-([^\/]+)/.match(item.identifier).captures
+
+  "/#{y}/#{m}/#{d}/#{slug}/index.html"
+end
+
+route '/assets/*' do
+  # /assets/foo.html/ -> /foo.html
+  item.identifier[7..-2]
+end
+
+route '/rss/' do
+  '/rss.xml'
+end
+
+route '/sitemap/' do
+  '/sitemap.xml'
+end
+
+route '*' do
+  if item.binary?
+    # Write item with identifier /foo/ to /foo.ext
+    item.identifier.chop + '.' + item[:extension]
+  else
+    # Write item with identifier /foo/ to /foo/index.html
+    item.identifier + 'index.html'
+  end
+end
+
+layout '*', :erb

_posts/2013-03-18-bash-prompt-git.md → content/posts/2013-03-18-bash-prompt-git.md

@@ -8,9 +8,9 @@ Using `git branch` we can retrieve the current git branch if any.
 
 You can use the following `PS1` definition (by editing your `~/.bashrc` file for instance):
 
-{% highlight bash %}
+``` bash
 export PS1='\n\[\033[0;36m\w/\033[m \033[0;33m`git branch 2> /dev/null | grep -e ^* | sed -E  s/^\\\\\*\ \(.+\)$/\(\\\\\1\)\ /`\033[m\]\n\033[0;35m⌘\033[m  '
-{% endhighlight %}
+```
 
 Displays something like that:
 
@@ -26,7 +26,7 @@ Another [demonstration which add an extra `*`](http://nathanhoad.net/git-bash-ta
 
 Here is my current one:
 
-{% highlight bash %}
+``` bash
 function parse_git_dirty {
   [[ $(git status 2> /dev/null | tail -n1) != "nothing to commit (working directory clean)" ]] && echo "*"
 }
@@ -36,7 +36,7 @@ function parse_git_branch {
 }
 
 export PS1='\n\[\033[0;36m\w/\033[m \033[0;33m$(parse_git_branch)\033[m\]\n\033[0;35m\$\033[m '
-{% endhighlight %}
+```
 
 <div style="font-family: monospace;">
 <pre><code>	

_posts/2013-03-19-git-memo.md → content/posts/2013-03-19-git-memo.md

@@ -8,25 +8,25 @@ comments: false
 
 Add to `~/.bashrc` (`~/.profile` or whatever you deem appropriate).
 
-{% highlight bash %}
+``` bash
 if [ -f ~/.git-completion.bash ]; then
 	. ~/.git-completion.bash
 fi
-{% endhighlight %}
+```
 
 [via](http://www.vogella.com/blog/2013/03/19/git-auto-completion-for-the-bash-shell/)
 
 # Git Prompt Colors
 
-{% highlight bash %}
-$ git config --global color.ui true
-{% endhighlight %}
+  ``` bash
+  $ git config --global color.ui true
+  ```
 
 [via](http://git-scm.com/book/en/Customizing-Git-Git-Configuration#Colors-in-Git)
 
 Custom colorization parameters can be done (see doc). As an example:
 
-{% highlight ini %}
+``` ini
 [color]
   ui = auto
 [color "branch"]
@@ -42,6 +42,6 @@ Custom colorization parameters can be done (see doc). As an example:
   added = yellow
   changed = green
   untracked = cyan
-{% endhighlight %}
+```
 
 [via](http://nathanhoad.net/how-to-colours-in-git)