feed.xml

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>pascal.poizat</title>
    <description>Professor&lt;br/&gt; Université Paris Nanterre&lt;br/&gt; LIP6 (Sorbonne Université, CNRS)
</description>
    <link>http://pascalpoizat.github.io/</link>
    <atom:link href="http://pascalpoizat.github.io/feed.xml" rel="self" type="application/rss+xml" />
    <pubDate>Fri, 30 Jul 2021 11:01:06 +0200</pubDate>
    <lastBuildDate>Fri, 30 Jul 2021 11:01:06 +0200</lastBuildDate>
    <generator>Jekyll v3.6.2</generator>
    
      <item>
        <title>Jekyll and BibTeX</title>
        <description>&lt;p class=&quot;text-justify&quot;&gt;Using &lt;a href=&quot;http://jekyllrb.com&quot;&gt;Jekyll&lt;/a&gt;,
you can &lt;a href=&quot;/blog/posts/2016/01/27/generating-a-page-using-personal-data/&quot;&gt;generate pages based on your data&lt;/a&gt;.&lt;br /&gt;
With the additional help of &lt;a href=&quot;https://github.com/inukshuk/jekyll-scholar&quot;&gt;Jekyll-Scholar&lt;/a&gt;,
this may include your BibTeX bibliographies.&lt;/p&gt;

&lt;h2 id=&quot;installing-jekyll-scholar&quot;&gt;Installing Jekyll-Scholar&lt;/h2&gt;

&lt;p class=&quot;text-justify&quot;&gt;First, if you are using GitHub Pages, you should do without the workflow,
see &lt;a href=&quot;/blog/posts/2016/01/29/github-pages-without-the-workflow/&quot;&gt;this post&lt;/a&gt;,
since Jekyll-Scholar is not part of the authorized plugins.&lt;/p&gt;

&lt;p&gt;Installing Jekyll-Scholar is then performed as follows:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;run &lt;code class=&quot;highlighter-rouge&quot;&gt;gem install jekyll-scholar&lt;/code&gt; and add &lt;code class=&quot;highlighter-rouge&quot;&gt;gems: ['jekyll/scholar']&lt;/code&gt; in your &lt;code class=&quot;highlighter-rouge&quot;&gt;_config.yml&lt;/code&gt; configuration file&lt;/li&gt;
  &lt;li&gt;add &lt;code class=&quot;highlighter-rouge&quot;&gt;gem 'jekyll-scholar'&lt;/code&gt; in your &lt;code class=&quot;highlighter-rouge&quot;&gt;Gemfile&lt;/code&gt; file (if you are using the &lt;a href=&quot;http://bundler.io/&quot;&gt;Bundler&lt;/a&gt; package manager)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;basic-example&quot;&gt;Basic example&lt;/h2&gt;

&lt;p class=&quot;text-justify&quot;&gt;You can use a &lt;code class=&quot;highlighter-rouge&quot;&gt;_bibliography&lt;/code&gt; directory to store your bibliography &lt;code class=&quot;highlighter-rouge&quot;&gt;.bib&lt;/code&gt; files.
The &lt;code class=&quot;highlighter-rouge&quot;&gt;_&lt;/code&gt; in the directory name means that Jekyll will not copy it in the generated site (&lt;code class=&quot;highlighter-rouge&quot;&gt;_site&lt;/code&gt; by default).
If you want that your bibliography file is visible to your site visitors,
then you should take this into account and, e.g., store the file in a &lt;code class=&quot;highlighter-rouge&quot;&gt;bibliography&lt;/code&gt; directory instead.
In the example we will suppose you have a &lt;code class=&quot;highlighter-rouge&quot;&gt;_bibliography/references.bib&lt;/code&gt; file.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;You can configure the way Jekyll-Scholar works using your &lt;code class=&quot;highlighter-rouge&quot;&gt;_config.yml&lt;/code&gt; configuration file.
The default is (see &lt;a href=&quot;https://github.com/inukshuk/jekyll-scholar&quot;&gt;here&lt;/a&gt; for the meaning of the contents):&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-yaml&quot; data-lang=&quot;yaml&quot;&gt;&lt;span class=&quot;na&quot;&gt;scholar&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt;
  &lt;span class=&quot;na&quot;&gt;style&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;apa&lt;/span&gt;
  &lt;span class=&quot;na&quot;&gt;locale&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;en&lt;/span&gt;

  &lt;span class=&quot;na&quot;&gt;sort_by&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;none&lt;/span&gt;
  &lt;span class=&quot;na&quot;&gt;order&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;ascending&lt;/span&gt;

  &lt;span class=&quot;na&quot;&gt;group_by&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;none&lt;/span&gt;
  &lt;span class=&quot;na&quot;&gt;group_order&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;ascending&lt;/span&gt;

  &lt;span class=&quot;na&quot;&gt;source&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;./_bibliography&lt;/span&gt;
  &lt;span class=&quot;na&quot;&gt;bibliography&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;references.bib&lt;/span&gt;
  &lt;span class=&quot;na&quot;&gt;bibliography_template&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s2&quot;&gt;&quot;&lt;/span&gt;&lt;span class=&quot;s&quot;&gt;&quot;&lt;/span&gt;

  &lt;span class=&quot;na&quot;&gt;replace_strings&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;no&quot;&gt;true&lt;/span&gt;
  &lt;span class=&quot;na&quot;&gt;join_strings&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt;    &lt;span class=&quot;no&quot;&gt;true&lt;/span&gt;

  &lt;span class=&quot;na&quot;&gt;use_raw_bibtex_entry&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;no&quot;&gt;false&lt;/span&gt;

  &lt;span class=&quot;na&quot;&gt;details_dir&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt;    &lt;span class=&quot;s&quot;&gt;bibliography&lt;/span&gt;
  &lt;span class=&quot;na&quot;&gt;details_layout&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;bibtex.html&lt;/span&gt;
  &lt;span class=&quot;na&quot;&gt;details_link&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt;   &lt;span class=&quot;s&quot;&gt;Details&lt;/span&gt;

  &lt;span class=&quot;na&quot;&gt;query&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s2&quot;&gt;&quot;&lt;/span&gt;&lt;span class=&quot;s&quot;&gt;@*&quot;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;You may then perform queries in your &lt;code class=&quot;highlighter-rouge&quot;&gt;.html&lt;/code&gt; or &lt;code class=&quot;highlighter-rouge&quot;&gt;.md&lt;/code&gt; pages as follows:&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-liquid&quot; data-lang=&quot;liquid&quot;&gt;---
layout: default
title: publications
---

## Journal Articles

&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;bibliography&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;-q&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;@article&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;

## Book Chapters

&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;bibliography&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;-q&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;@inbook&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;

## Conferences and Workshops

&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;bibliography&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;-q&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;@inproceedings&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;

## Manuscripts

&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;bibliography&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;-q&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;@phdthesis&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;You may find more information about the bibliography queries &lt;a href=&quot;https://github.com/inukshuk/jekyll-scholar&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;h2 id=&quot;tuning-things&quot;&gt;Tuning things&lt;/h2&gt;

&lt;p&gt;We will see how to achieve the following:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;change the way references are ordered&lt;/li&gt;
  &lt;li&gt;have our own citation style&lt;/li&gt;
  &lt;li&gt;have output generated for additional bibliography fields (notes, DOI, HAL, and PDF)
and for the BibTeX reference itself&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;ordering-of-references&quot;&gt;Ordering of references&lt;/h3&gt;

&lt;p class=&quot;text-justify&quot;&gt;Say you want to have ordering by date of publication, in descending order.
Then you have to change your &lt;code class=&quot;highlighter-rouge&quot;&gt;_config.yml&lt;/code&gt; file to include:&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-yaml&quot; data-lang=&quot;yaml&quot;&gt;&lt;span class=&quot;na&quot;&gt;scholar&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt;
  &lt;span class=&quot;s&quot;&gt;...&lt;/span&gt;
  &lt;span class=&quot;s&quot;&gt;sort_by&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;year, month&lt;/span&gt;
  &lt;span class=&quot;na&quot;&gt;order&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;descending&lt;/span&gt;
  &lt;span class=&quot;s&quot;&gt;...&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;h3 id=&quot;citation-styles&quot;&gt;Citation styles&lt;/h3&gt;

&lt;p class=&quot;text-justify&quot;&gt;You can change the citation style by changing the style name for Jekyll-Scholar in &lt;code class=&quot;highlighter-rouge&quot;&gt;_config.yml&lt;/code&gt;.
You can use styles from &lt;a href=&quot;https://github.com/citation-style-language/styles&quot;&gt;the repository for CSL citation styles&lt;/a&gt;.
You can also define you own style and link to it as follows:&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-yaml&quot; data-lang=&quot;yaml&quot;&gt;&lt;span class=&quot;na&quot;&gt;scholar&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt;
  &lt;span class=&quot;s&quot;&gt;...&lt;/span&gt;
  &lt;span class=&quot;s&quot;&gt;style&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;_bibliography/mystyle.csl&lt;/span&gt;
  &lt;span class=&quot;s&quot;&gt;...&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;The definition of a style is quite complex. There is few documentation.
The best I could find is &lt;a href=&quot;http://docs.citationstyles.org/en/stable/&quot;&gt;here&lt;/a&gt;.
The style I use is a modification of
&lt;a href=&quot;http://www.zotero.org/styles/springer-lecture-notes-in-computer-science&quot;&gt;http://www.zotero.org/styles/springer-lecture-notes-in-computer-science&lt;/a&gt;
which you can see &lt;a href=&quot;https://github.com/pascalpoizat/pascalpoizat.github.io/blob/master/src/_bibliography/mystyle.csl&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;h3 id=&quot;tuning-the-generated-output&quot;&gt;Tuning the generated output&lt;/h3&gt;

&lt;p class=&quot;text-justify&quot;&gt;The first thing is to tell Jekyll-Scholar which layout to use for bibliography queries.
We will have the description of it in &lt;code class=&quot;highlighter-rouge&quot;&gt;_layouts/bib.html&lt;/code&gt; so we change &lt;code class=&quot;highlighter-rouge&quot;&gt;config.yml&lt;/code&gt; to have:&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-yaml&quot; data-lang=&quot;yaml&quot;&gt;&lt;span class=&quot;na&quot;&gt;scholar&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt;
  &lt;span class=&quot;s&quot;&gt;...&lt;/span&gt;
  &lt;span class=&quot;s&quot;&gt;bibliography_template&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;bib&lt;/span&gt;
  &lt;span class=&quot;s&quot;&gt;...&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;Then you have to put the &lt;code class=&quot;highlighter-rouge&quot;&gt;bib.html&lt;/code&gt; layout file in &lt;code class=&quot;highlighter-rouge&quot;&gt;_layouts&lt;/code&gt; (the default):&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-html&quot; data-lang=&quot;html&quot;&gt;---
---
&lt;span class=&quot;nt&quot;&gt;&amp;lt;div&lt;/span&gt; &lt;span class=&quot;na&quot;&gt;class=&lt;/span&gt;&lt;span class=&quot;s&quot;&gt;&quot;text-justify&quot;&lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;&amp;gt;&lt;/span&gt;
    {{reference}}
&lt;span class=&quot;nt&quot;&gt;&amp;lt;/div&amp;gt;&lt;/span&gt;

{% if entry.note %}
&lt;span class=&quot;nt&quot;&gt;&amp;lt;div&amp;gt;&lt;/span&gt;
    &lt;span class=&quot;nt&quot;&gt;&amp;lt;em&amp;gt;&lt;/span&gt;{{ entry.note }}&lt;span class=&quot;nt&quot;&gt;&amp;lt;/em&amp;gt;&lt;/span&gt;
&lt;span class=&quot;nt&quot;&gt;&amp;lt;/div&amp;gt;&lt;/span&gt;
{% endif %}

&lt;span class=&quot;nt&quot;&gt;&amp;lt;div&amp;gt;&lt;/span&gt;
    {% if entry.doi %}
    &lt;span class=&quot;nt&quot;&gt;&amp;lt;span&amp;gt;&amp;lt;a&lt;/span&gt; &lt;span class=&quot;na&quot;&gt;href=&lt;/span&gt;&lt;span class=&quot;s&quot;&gt;&quot;{{ entry.doi | prepend: 'http://doi.org/' }}&quot;&lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;&amp;gt;&lt;/span&gt;doi&lt;span class=&quot;nt&quot;&gt;&amp;lt;/a&amp;gt;&amp;lt;/span&amp;gt;&lt;/span&gt;
    {% endif %}
    {% if entry.hal_id %}
    &lt;span class=&quot;nt&quot;&gt;&amp;lt;span&amp;gt;&amp;lt;a&lt;/span&gt; &lt;span class=&quot;na&quot;&gt;href=&lt;/span&gt;&lt;span class=&quot;s&quot;&gt;&quot;{{ entry.hal_id | prepend: 'http://hal.inria.fr/' }}&quot;&lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;&amp;gt;&lt;/span&gt;hal&lt;span class=&quot;nt&quot;&gt;&amp;lt;/a&amp;gt;&amp;lt;/span&amp;gt;&lt;/span&gt;
    {% endif %}
&lt;span class=&quot;nt&quot;&gt;&amp;lt;/div&amp;gt;&lt;/span&gt;
&lt;span class=&quot;nt&quot;&gt;&amp;lt;div&amp;gt;&lt;/span&gt;
    {% if entry.pdf %}
    &lt;span class=&quot;nt&quot;&gt;&amp;lt;span&amp;gt;&amp;lt;a&lt;/span&gt; &lt;span class=&quot;na&quot;&gt;href=&lt;/span&gt;&lt;span class=&quot;s&quot;&gt;&quot;{{ entry.pdf }}&quot;&lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;&amp;gt;&lt;/span&gt;pdf&lt;span class=&quot;nt&quot;&gt;&amp;lt;/a&amp;gt;&amp;lt;/span&amp;gt;&lt;/span&gt;
    {% endif %}
&lt;span class=&quot;nt&quot;&gt;&amp;lt;/div&amp;gt;&lt;/span&gt;

&lt;span class=&quot;nt&quot;&gt;&amp;lt;div&amp;gt;&amp;lt;pre&amp;gt;&lt;/span&gt;{{ entry.bibtex }}&lt;span class=&quot;nt&quot;&gt;&amp;lt;/pre&amp;gt;&amp;lt;/div&amp;gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;The first thing is the layout information used by Jekyll (the two dash lines).
Then you have the &lt;code class=&quot;highlighter-rouge&quot;&gt;{{ reference }}&lt;/code&gt; tag. It is used to include the reference as generated by Jekyll-Scholar.
Here we put it in a &lt;code class=&quot;highlighter-rouge&quot;&gt;&amp;lt;div&amp;gt;...&amp;lt;/div&amp;gt;&lt;/code&gt; tag to have it text-justified.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;Then we want to generate the reference note if there is some.
For this we use a Liquid conditional.
&lt;code class=&quot;highlighter-rouge&quot;&gt;entry&lt;/code&gt; denotes the current reference we are typing out, and
&lt;code class=&quot;highlighter-rouge&quot;&gt;entry.note&lt;/code&gt; denotes the note field of this entry (if it exists).&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;Then we have two &lt;code class=&quot;highlighter-rouge&quot;&gt;&amp;lt;div&amp;gt;&lt;/code&gt;s. One for the links (DOI and the HAL open archive) and one for the PDF of the reference.
This uses respectively the &lt;code class=&quot;highlighter-rouge&quot;&gt;doi&lt;/code&gt; (or &lt;code class=&quot;highlighter-rouge&quot;&gt;DOI&lt;/code&gt;), &lt;code class=&quot;highlighter-rouge&quot;&gt;hal_id&lt;/code&gt; (or &lt;code class=&quot;highlighter-rouge&quot;&gt;HAL_ID&lt;/code&gt;), and &lt;code class=&quot;highlighter-rouge&quot;&gt;pdf&lt;/code&gt; (or &lt;code class=&quot;highlighter-rouge&quot;&gt;PDF&lt;/code&gt;) user-defined fields
in BibTeX reference files. Typically one would have references such as:&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-latex&quot; data-lang=&quot;latex&quot;&gt;@Article&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;PP&lt;span class=&quot;p&quot;&gt;_&lt;/span&gt;MPS12,
    author = &lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;Mateescu, Radu and Poizat, Pascal and Salaün, Gwen&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;,
    year = &lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;2012&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;,
    title = &lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;Adaptation of Service Protocols using Process Algebra and On-the-Fly Reduction Techniques&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt;,
    journal = &lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;IEEE Transactions on Software Engineering&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;,
    pages = &lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;755--777&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;,
    volume = &lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;38&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;,
    number = &lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;4&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;,
    DOI = &lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;10.1109/TSE.2011.62&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;,
    HAL&lt;span class=&quot;p&quot;&gt;_&lt;/span&gt;ID = &lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;hal-00717252&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;,
    PDF = &lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;https://hal.inria.fr/hal-00717252/document&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;,
&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;&lt;strong&gt;Note:&lt;/strong&gt; if you want to use &lt;code class=&quot;highlighter-rouge&quot;&gt;{{ ... }}&lt;/code&gt; in your BibTeX files (to force uppercase titles for example),
then you have to tell Jekyll-Scholar not to interpret this as Liquid templates.
This is achieved by putting in your &lt;code class=&quot;highlighter-rouge&quot;&gt;_config.yml&lt;/code&gt; file:&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-yaml&quot; data-lang=&quot;yaml&quot;&gt;&lt;span class=&quot;na&quot;&gt;scholar&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt;
  &lt;span class=&quot;s&quot;&gt;...&lt;/span&gt;
  &lt;span class=&quot;s&quot;&gt;use_raw_bibtex_entry&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;no&quot;&gt;true&lt;/span&gt;
  &lt;span class=&quot;s&quot;&gt;...&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;Last, but not least, if you want to end each reference with its BibTex source, e.g., to present them in a Boostrap pop-up),
then you can use &lt;code class=&quot;highlighter-rouge&quot;&gt;entry.bibtex&lt;/code&gt;.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;The overall result for the reference above (&lt;strong&gt;at the time of this post&lt;/strong&gt;) is:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/posts_images/2016-02-01-image1.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;As you can see, Jekyll-Scholar is a really interesting plugin.
To learn more, see &lt;a href=&quot;https://github.com/inukshuk/jekyll-scholar&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
</description>
        <pubDate>Mon, 01 Feb 2016 00:00:00 +0100</pubDate>
        <link>http://pascalpoizat.github.io/blog/posts/2016/02/01/jekyll-and-bibtex/</link>
        <guid isPermaLink="true">http://pascalpoizat.github.io/blog/posts/2016/02/01/jekyll-and-bibtex/</guid>
        
        
        <category>jekyll</category>
        
        <category>bibtex</category>
        
        <category>jekyll-scholar</category>
        
      </item>
    
      <item>
        <title>GitHub Pages without the Workflow</title>
        <description>&lt;p class=&quot;text-justify&quot;&gt;Jekyll nicely &lt;a href=&quot;http://jekyllrb.com/docs/github-pages/&quot;&gt;integrates with GitHub Pages&lt;/a&gt;.
However, this comes with rules that forbid using Jekyll plugins but for authorized ones.&lt;br /&gt;
We will see here how to deal with this limit.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;&lt;strong&gt;Note:&lt;/strong&gt; I am discussing here about User pages on GitHub Pages.
For Project pages things are a bit different. For example for User pages, pages are on a &lt;code class=&quot;highlighter-rouge&quot;&gt;master&lt;/code&gt; branch.
For Project pages, pages are on a &lt;code class=&quot;highlighter-rouge&quot;&gt;gh-pages&lt;/code&gt; branch.
See &lt;a href=&quot;https://help.github.com/articles/user-organization-and-project-pages/&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;h2 id=&quot;two-choices&quot;&gt;Two choices&lt;/h2&gt;

&lt;p class=&quot;text-justify&quot;&gt;If you want, e.g., to use the &lt;a href=&quot;https://github.com/inukshuk/jekyll-scholar&quot;&gt;Jekyll-Scholar&lt;/a&gt; plugin
(to generate pages from &lt;code class=&quot;highlighter-rouge&quot;&gt;.bib&lt;/code&gt; BibTeX reference files),
you will have either not to use GitHub Pages
(make a simple &lt;code class=&quot;highlighter-rouge&quot;&gt;my-web-pages&lt;/code&gt; repository and sync your pages with a Web server somewhere else)
or to shortcut the GitHub Pages workflow. This is what we will do here.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;This part is based on &lt;a href=&quot;https://github.com/barais/barais.github.io&quot;&gt;Olivier Barais’s template&lt;/a&gt;,
itself based on &lt;a href=&quot;https://github.com/rudametw/rudametw.github.io&quot;&gt;Walter Rudametkin’s template&lt;/a&gt;.
I chose not to fork their templates here since my site structure is different and I also
wanted to build things from scratch to explain how to integrate elements one by one. Yet, without them,
shortcutting the GitHub Pages workflow would certainly have been much more complicated.
Please consider forking their templates that are much more advanced than mine for the moment.&lt;/p&gt;

&lt;h2 id=&quot;how-things-work-with-the-github-pages-workflow&quot;&gt;How things work with the GitHub Pages workflow&lt;/h2&gt;

&lt;p class=&quot;text-justify&quot;&gt;Jekyll takes its sources, i.e., files and specific directories (ones beginning by &lt;code class=&quot;highlighter-rouge&quot;&gt;_&lt;/code&gt; in short) in the current path
and compute pages in subdirectory &lt;code class=&quot;highlighter-rouge&quot;&gt;_src&lt;/code&gt;. See the Jekyll directory structure &lt;a href=&quot;http://jekyllrb.com/docs/structure/&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;GitHub Pages require that your Jekyll sources are in the root directory of &lt;code class=&quot;highlighter-rouge&quot;&gt;username.github.io&lt;/code&gt;.
Then it runs Jekyll and deploys the resulting pages to &lt;code class=&quot;highlighter-rouge&quot;&gt;http://username.github.io&lt;/code&gt;.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;If you want to write your pages directly (e.g, without templates) you would have to put them
at the root of the &lt;code class=&quot;highlighter-rouge&quot;&gt;username.github.io&lt;/code&gt; repository and add a &lt;code class=&quot;highlighter-rouge&quot;&gt;.nojekyll&lt;/code&gt; empty file to tell GitHub Pages not to
run Jekyll each time you push things. This is very important if you have directories beginning with &lt;code class=&quot;highlighter-rouge&quot;&gt;_&lt;/code&gt; since
they have a special treatment with Jekyll (they are not deployed on the Web site).&lt;/p&gt;

&lt;h2 id=&quot;putting-things-together&quot;&gt;Putting things together&lt;/h2&gt;

&lt;p&gt;The solution that is adopted in &lt;a href=&quot;https://github.com/barais/barais.github.io&quot;&gt;Olivier Barais’s template&lt;/a&gt; and
in &lt;a href=&quot;https://github.com/rudametw/rudametw.github.io&quot;&gt;Walter Rudametkin’s template&lt;/a&gt; is:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;
    &lt;p&gt;define a &lt;code class=&quot;highlighter-rouge&quot;&gt;src&lt;/code&gt; directory at the root (of the repository) containing the Jekyll sources&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;edit files in &lt;code class=&quot;highlighter-rouge&quot;&gt;src&lt;/code&gt; as usual, and commit+push them to GitHub regularly&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;have Jekyll run on these sources and place them in &lt;code class=&quot;highlighter-rouge&quot;&gt;src/_site&lt;/code&gt; (default)&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;“build” the site regularly by copying the pages from &lt;code class=&quot;highlighter-rouge&quot;&gt;src/_site&lt;/code&gt; to the root of the repository,
 and then commit+push the new versions of these to GitHub&lt;/p&gt;
  &lt;/li&gt;
&lt;/ol&gt;

&lt;p class=&quot;text-justify&quot;&gt;For this one has two scripts that automate steps 3. and 4.
Step 3. is achieved by &lt;code class=&quot;highlighter-rouge&quot;&gt;src/run-jekyll.sh&lt;/code&gt;. You can have it run in background while doing steps 1. and 2.
Step 4. is achieved by &lt;code class=&quot;highlighter-rouge&quot;&gt;src/update-site.sh&lt;/code&gt;.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;&lt;strong&gt;Note:&lt;/strong&gt; Jekyll supports the possibility to tell in its configuration file
where are the source and the target directories.
I may use this in the future to simplify things and avoid some file copying.&lt;/p&gt;

</description>
        <pubDate>Fri, 29 Jan 2016 00:00:00 +0100</pubDate>
        <link>http://pascalpoizat.github.io/blog/posts/2016/01/29/github-pages-without-the-workflow/</link>
        <guid isPermaLink="true">http://pascalpoizat.github.io/blog/posts/2016/01/29/github-pages-without-the-workflow/</guid>
        
        
        <category>jekyll</category>
        
        <category>github-pages</category>
        
      </item>
    
      <item>
        <title>Generating a Page using Personal Data</title>
        <description>&lt;p class=&quot;text-justify&quot;&gt;Static page generators such as &lt;a href=&quot;http://jekyllrb.com/&quot;&gt;Jekyll&lt;/a&gt; can
use data stored in files to produce the information contained into HTML pages.&lt;br /&gt;
We will have a look at this using a simple example.&lt;/p&gt;

&lt;h2 id=&quot;the-data-files&quot;&gt;The data files&lt;/h2&gt;

&lt;p class=&quot;text-justify&quot;&gt;The first step is to define the file(s) that will contain the information.
This can be either JSON, YAML, or CSV files.
For &lt;a href=&quot;/duties/&quot;&gt;my list of duties&lt;/a&gt; I chose to use YAML files, but another part of my site,
the list of talks, used to rely on JSON files.
Data files have to be put in the &lt;code class=&quot;highlighter-rouge&quot;&gt;_data&lt;/code&gt; directory of the Jekyll tree structure.
Sub-directories can be used to structure your set of data files. So here I put my data within &lt;code class=&quot;highlighter-rouge&quot;&gt;_data/duties&lt;/code&gt;.
Further, we will have one file for the current duties, &lt;code class=&quot;highlighter-rouge&quot;&gt;currently.yml&lt;/code&gt;,
and another file, &lt;code class=&quot;highlighter-rouge&quot;&gt;before.yml&lt;/code&gt;, for the old ones. Here is the &lt;code class=&quot;highlighter-rouge&quot;&gt;currently.yml&lt;/code&gt; one:&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-yaml&quot; data-lang=&quot;yaml&quot;&gt;&lt;span class=&quot;pi&quot;&gt;-&lt;/span&gt; &lt;span class=&quot;na&quot;&gt;name&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;Pedagogic&lt;/span&gt;
  &lt;span class=&quot;na&quot;&gt;values&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt;

  &lt;span class=&quot;pi&quot;&gt;-&lt;/span&gt; &lt;span class=&quot;na&quot;&gt;period&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;since 2012&lt;/span&gt;
    &lt;span class=&quot;na&quot;&gt;name&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;Director of 1st and 2nd year of Master in CS (Applied cursus, MIAGE)&lt;/span&gt;
    &lt;span class=&quot;na&quot;&gt;at&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;Paris Ouest University&lt;/span&gt;

&lt;span class=&quot;pi&quot;&gt;-&lt;/span&gt; &lt;span class=&quot;na&quot;&gt;name&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;Scientific&lt;/span&gt;
  &lt;span class=&quot;na&quot;&gt;values&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt;

  &lt;span class=&quot;pi&quot;&gt;-&lt;/span&gt; &lt;span class=&quot;na&quot;&gt;period&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;since 2014&lt;/span&gt;
    &lt;span class=&quot;na&quot;&gt;name&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;Member of the Nat. Committee for Scientific Research | CoNRS Sect. 6&lt;/span&gt;
    &lt;span class=&quot;na&quot;&gt;at&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;CNRS&lt;/span&gt;

  &lt;span class=&quot;pi&quot;&gt;-&lt;/span&gt; &lt;span class=&quot;na&quot;&gt;period&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;since 2014&lt;/span&gt;
    &lt;span class=&quot;na&quot;&gt;name&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;Member of the Laboratory Council | Conseil de Laboratoire&lt;/span&gt;
    &lt;span class=&quot;na&quot;&gt;at&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;LIP6 Laboratory&lt;/span&gt;

  &lt;span class=&quot;pi&quot;&gt;-&lt;/span&gt; &lt;span class=&quot;na&quot;&gt;period&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;since 2013&lt;/span&gt;
    &lt;span class=&quot;na&quot;&gt;name&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;Member of the CS Advisory Council | CCD Sect. 27&lt;/span&gt;
    &lt;span class=&quot;na&quot;&gt;at&lt;/span&gt;&lt;span class=&quot;pi&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;s&quot;&gt;Paris Ouest University&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;You have a list of 2 items, each item containing a name (category) and a list of values,
with a value being a period, a name, and the location it took place
(see &lt;a href=&quot;https://fr.wikipedia.org/wiki/YAML&quot;&gt;here&lt;/a&gt; for information about the YAML format).&lt;/p&gt;

&lt;h2 id=&quot;from-data-to-html&quot;&gt;From data to HTML&lt;/h2&gt;

&lt;p class=&quot;text-justify&quot;&gt;To generate HTML information for this, one can create an HTML document, &lt;code class=&quot;highlighter-rouge&quot;&gt;duties.html&lt;/code&gt;,
and use &lt;a href=&quot;http://liquidmarkup.org/&quot;&gt;Liquid templating&lt;/a&gt; to access the data.
To generate a list you simply have to type in &lt;code class=&quot;highlighter-rouge&quot;&gt;duties.html&lt;/code&gt;:&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-liquid&quot; data-lang=&quot;liquid&quot;&gt;---
layout: default
title: duties
---
&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;category&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;in&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;site.data.duties.currently&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;
&amp;lt;h3&amp;gt;&lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;category&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;name&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt;&amp;lt;/h3&amp;gt;
&amp;lt;ul&amp;gt;
    &lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;duty&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;in&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;category.values&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;
    &amp;lt;li&amp;gt;&lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duty&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;period&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt; - &lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duty&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;name&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt;&amp;lt;br/&amp;gt;
    &lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duty&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;at&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt;
    &amp;lt;/li&amp;gt;
    &lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;endfor&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;
&amp;lt;/ul&amp;gt;
&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;endfor&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;As you can see, to access the data in the file &lt;code class=&quot;highlighter-rouge&quot;&gt;_data/duties/currently.yml&lt;/code&gt;, we refer to &lt;code class=&quot;highlighter-rouge&quot;&gt;site.data.duties.currently&lt;/code&gt;.
This can be read as “the &lt;code class=&quot;highlighter-rouge&quot;&gt;currently&lt;/code&gt; file that is in the &lt;code class=&quot;highlighter-rouge&quot;&gt;duties&lt;/code&gt; subdirectory of the site data directory”.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;For loops iterate over a list using some variable &lt;code class=&quot;highlighter-rouge&quot;&gt;v&lt;/code&gt;.&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-liquid&quot; data-lang=&quot;liquid&quot;&gt;&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;v&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;in&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;list&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;...&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;endfor&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;To access to some attribute &lt;code class=&quot;highlighter-rouge&quot;&gt;a&lt;/code&gt; of a variable &lt;code class=&quot;highlighter-rouge&quot;&gt;v&lt;/code&gt;, we use double brackets and indexing.&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-liquid&quot; data-lang=&quot;liquid&quot;&gt;&lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;v&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;a&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;The rest is self-explanatory if you know HTML.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;You can get more information on Liquid templating &lt;a href=&quot;http://jekyllrb.com/docs/datafiles/&quot;&gt;here&lt;/a&gt; and &lt;a href=&quot;http://liquidmarkup.org/&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;h2 id=&quot;factorizing-things&quot;&gt;Factorizing things&lt;/h2&gt;

&lt;p class=&quot;text-justify&quot;&gt;Now if you want to generate also the list of the old duties, you have to copy-paste the piece of code before,
and replace &lt;code class=&quot;highlighter-rouge&quot;&gt;site.data.duties.currently&lt;/code&gt; by &lt;code class=&quot;highlighter-rouge&quot;&gt;site.data.duties.before&lt;/code&gt;. Too bad.
A better way to do things is to define the code in terms of a variable &lt;code class=&quot;highlighter-rouge&quot;&gt;duties&lt;/code&gt; as follows:&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-liquid&quot; data-lang=&quot;liquid&quot;&gt;&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;category&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;in&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;duties&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;
&amp;lt;h3&amp;gt;&lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;category&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;name&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt;&amp;lt;/h3&amp;gt;
&amp;lt;ul&amp;gt;
    &lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;duty&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;in&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;category.values&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;
    &amp;lt;li&amp;gt;&lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duty&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;period&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt; - &lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duty&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;name&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt;&amp;lt;br/&amp;gt;
    &lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duty&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;at&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt;
    &amp;lt;/li&amp;gt;
    &lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;endfor&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;
&amp;lt;/ul&amp;gt;
&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;endfor&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;Then you put this piece of code, say &lt;code class=&quot;highlighter-rouge&quot;&gt;print_duties&lt;/code&gt; within the Jekyll include directory, &lt;code class=&quot;highlighter-rouge&quot;&gt;_includes&lt;/code&gt;.
In order to generate both lists of duties you now simply have to write in &lt;code class=&quot;highlighter-rouge&quot;&gt;duties.html&lt;/code&gt;:&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-liquid&quot; data-lang=&quot;liquid&quot;&gt;---
layout: default
title: duties
---
&amp;lt;h2&amp;gt;Currently&amp;lt;/h2&amp;gt;

&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;assign&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duties&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;site&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duties&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;currently&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;
&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;include&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;na&quot;&gt;print_duties&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;na&quot;&gt;html&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;

&amp;lt;h2&amp;gt;Before&amp;lt;/h2&amp;gt;

&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;assign&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duties&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;site&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duties&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;before&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;
&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;include&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;na&quot;&gt;print_duties&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;na&quot;&gt;html&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;If you prefer to use Markdown, use instead a &lt;code class=&quot;highlighter-rouge&quot;&gt;duties.md&lt;/code&gt; file with:&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-liquid&quot; data-lang=&quot;liquid&quot;&gt;---
layout: default
title: duties
---
## Currently

&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;assign&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duties&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;site&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duties&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;currently&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;
&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;include&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;na&quot;&gt;print_duties&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;na&quot;&gt;html&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;

## Before

&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;assign&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duties&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;site&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duties&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;before&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;
&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;include&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;na&quot;&gt;print_duties&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;na&quot;&gt;html&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;h2 id=&quot;factorizing-things-revisited&quot;&gt;Factorizing things (revisited)&lt;/h2&gt;

&lt;p class=&quot;text-justify&quot;&gt;Indeed file inclusion supports parameters (see &lt;a href=&quot;http://jekyllrb.com/docs/templates/&quot;&gt;here&lt;/a&gt;).
You can add the parameter and its value to the import as follows:&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-liquid&quot; data-lang=&quot;liquid&quot;&gt;---
layout: default
title: duties
---
## Currently

&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;include&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;na&quot;&gt;print_duties&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;na&quot;&gt;html&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;na&quot;&gt;duties&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;site&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duties&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;na&quot;&gt;currently %}

## Before

{% include print_duties&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;na&quot;&gt;html&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;na&quot;&gt;duties&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;site&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;data&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duties&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;before&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

&lt;p class=&quot;text-justify&quot;&gt;In the &lt;code class=&quot;highlighter-rouge&quot;&gt;print_duties.html&lt;/code&gt; template that is in the &lt;code class=&quot;highlighter-rouge&quot;&gt;_includes&lt;/code&gt; directory, you just have to prefix the name of the parameter with &lt;code class=&quot;highlighter-rouge&quot;&gt;include&lt;/code&gt;:&lt;/p&gt;

&lt;figure class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-liquid&quot; data-lang=&quot;liquid&quot;&gt;&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;category&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;in&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;include.duties&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;
&amp;lt;h3&amp;gt;&lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;category&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;name&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt;&amp;lt;/h3&amp;gt;
&amp;lt;ul&amp;gt;
    &lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;for&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;duties&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;in&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;category.values&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;
    &amp;lt;li&amp;gt;&lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duty&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;period&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt; - &lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duty&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;name&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt;&amp;lt;br/&amp;gt;
    &lt;span class=&quot;p&quot;&gt;{{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;duty&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;nv&quot;&gt;at&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}}&lt;/span&gt;
    &amp;lt;/li&amp;gt;
    &lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;endfor&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;
&amp;lt;/ul&amp;gt;
&lt;span class=&quot;p&quot;&gt;{%&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;nt&quot;&gt;endfor&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;%}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;

</description>
        <pubDate>Wed, 27 Jan 2016 00:00:00 +0100</pubDate>
        <link>http://pascalpoizat.github.io/blog/posts/2016/01/27/generating-a-page-using-personal-data/</link>
        <guid isPermaLink="true">http://pascalpoizat.github.io/blog/posts/2016/01/27/generating-a-page-using-personal-data/</guid>
        
        
        <category>jekyll</category>
        
        <category>liquid</category>
        
        <category>templates</category>
        
        <category>yaml</category>
        
      </item>
    
      <item>
        <title>Web Site now using Jekyll</title>
        <description>&lt;p class=&quot;text-justify&quot;&gt;New static Web site, now generated using &lt;a href=&quot;http://jekyllrb.com/&quot;&gt;Jekyll&lt;/a&gt;.&lt;/p&gt;

&lt;h2 id=&quot;static-pages&quot;&gt;Static pages&lt;/h2&gt;

&lt;p class=&quot;text-justify&quot;&gt;There are many reasons to prefer static pages over dynamic ones.
You may find some &lt;a href=&quot;http://nilclass.com/courses/what-is-a-static-website/#1&quot;&gt;here&lt;/a&gt;.
It turns out you just have to write some HTML/CSS files using your editor or IDE of choice and then send these files to a server.
You can do this in a responsive way using &lt;a href=&quot;http://getbootstrap.com/&quot;&gt;BootStrap&lt;/a&gt; and with style using available templates,
see e.g., &lt;a href=&quot;http://html5up.net/&quot;&gt;HTML5UP&lt;/a&gt;.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;There are limits to this approach.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;First, changing the style of your Web site over time soon becomes a burden. A solution is never to change this style.
I am sure you have already seen the nice &lt;em&gt;no-css-no-javascript-HTML-2.0&lt;/em&gt; pages that some people like in academia.
But what you are not one of these?
Further, what if your pages relate to data you gather with time?
Of course, you could try to keep your data and your manually edited Web pages synchronized. Not fun.&lt;/p&gt;

&lt;h2 id=&quot;static-page-generators&quot;&gt;Static page generators&lt;/h2&gt;

&lt;p class=&quot;text-justify&quot;&gt;A solution is to follow a &lt;em&gt;data-and-generators&lt;/em&gt; approach.
Using data, stored in a database or in files, you can generate not only up-to-date Web pages but also resumes, application files, etc.
Nothing really new here.
Indeed, I had used the &lt;a href=&quot;https://github.com/sebastien/tahchee&quot;&gt;TahChee&lt;/a&gt; python-based static Web site generator for some time.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;The choice of a generation framework is vast, &lt;a href=&quot;https://www.staticgen.com/&quot;&gt;see here&lt;/a&gt; for example.&lt;/p&gt;

&lt;h2 id=&quot;jekyll&quot;&gt;Jekyll&lt;/h2&gt;

&lt;p class=&quot;text-justify&quot;&gt;At a first step I would have liked to find one based on the new language I am learning, &lt;a href=&quot;https://kotlinlang.org/&quot;&gt;Kotlin&lt;/a&gt;.
None.
&lt;a href=&quot;http://sysgears.com/grain/&quot;&gt;Grain&lt;/a&gt;, based on Groovy, and with support for the &lt;a href=&quot;http://gradle.org/&quot;&gt;Gradle&lt;/a&gt; build system seems nice too.
But a bit too young.
So let’s go for &lt;a href=&quot;http://jekyllrb.com/&quot;&gt;Jekyll&lt;/a&gt;.&lt;/p&gt;

&lt;p class=&quot;text-justify&quot;&gt;It’s quite simple to have a running Jekyll site:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;if you intend to publish your Web pages using GitHub pages, the good starting point is the very nice &lt;a href=&quot;http://jmcglone.com/guides/github-pages/&quot;&gt;tutorial by Jonathan McGlone&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;if not, you can simply follow the &lt;a href=&quot;http://jekyllrb.com/docs/quickstart/&quot;&gt;Jekyll quick-start guide&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p class=&quot;text-justify&quot;&gt;&lt;strong&gt;Update:&lt;/strong&gt; just found the &lt;a href=&quot;http://jekyll.tips/&quot;&gt;Jekyll Tips&lt;/a&gt; site.
Lots of interesting information here too.&lt;/p&gt;
</description>
        <pubDate>Tue, 26 Jan 2016 00:00:00 +0100</pubDate>
        <link>http://pascalpoizat.github.io/blog/posts/2016/01/26/jekyll-site-launched/</link>
        <guid isPermaLink="true">http://pascalpoizat.github.io/blog/posts/2016/01/26/jekyll-site-launched/</guid>
        
        
        <category>jekyll</category>
        
        <category>github-pages</category>
        
      </item>
    
  </channel>
</rss>