Fix broken images links

cache/2020/ff864f1890f6eb967b3f9645554708e0/index.html

@@ -76,7 +76,7 @@
 
 <p>The most popular static site generator, Jekyll, may have the best documentation pages of the lot. And yet, it still puts a bunch of technical language front-and-center, on the project’s home page:</p>
 
-<figure class="border"><img src="jekyll-quick-start.png" alt="A series of 4 terminal commands, starting with: gem install bundler jekyll…"/><figcaption>Jekyll’s core message, “Get up and running in seconds”</figcaption></figure>
+<figure class="border"><img src="https://fvsch.com/static-site-generators/jekyll-quick-start.png" alt="A series of 4 terminal commands, starting with: gem install bundler jekyll…"/><figcaption>Jekyll’s core message, “Get up and running in seconds”</figcaption></figure>
 
 <p>This is developer-talk, <em>because static site generators are tools made by developers for themselves and their peers</em>.</p>
 
@@ -122,7 +122,7 @@
 
 <p>This site is made of a handful of long “chapter” pages, with a top-level table of contents which lists all chapters and their sections:</p>
 
-<figure class="border"><img alt="Screenshot showing a full table of contents with 3 levels of titles" src="style-guide.png" srcset="style-guide.png 1x, style-guide@2x.png 2x"/></figure>
+<figure class="border"><img alt="Screenshot showing a full table of contents with 3 levels of titles" src="https://fvsch.com/static-site-generators/style-guide.png" srcset="https://fvsch.com/static-site-generators/style-guide.png 1x, https://fvsch.com/static-site-generators/style-guide@2x.png 2x"/></figure>
 
 <p>For easier <em>content management</em> and reordering of sections, I had broken each chapter into different section files, so that the index page is generated from three levels of content. Looking at the “General Rules” branch only, the content hierarchy looks like:</p>
 

cache/2020/ff864f1890f6eb967b3f9645554708e0/index.md

@@ -31,7 +31,7 @@ hash_url: ff864f1890f6eb967b3f9645554708e0
 <pre><code class="language-md">![My cat at 4 months]({{&lt; imgproc sniffles-4months.jpg Resize "600x" /&gt;}})</code></pre>
 <p>At this point we must recognize that static site generators are tools made by developers <em>for developers</em>. They require a ton of previous knowledge: HTML, Markdown, command line interfaces, FTP or some other way to publish HTML files online, and of course you would need some kind of web hosting to put those files. Users will also need to dive into technical documentation for their tool of choice when they want to customize their site’s pages, work in “templates”, learn a templating language, and probably write some CSS.</p>
 <p>The most popular static site generator, Jekyll, may have the best documentation pages of the lot. And yet, it still puts a bunch of technical language front-and-center, on the project’s home page:</p>
-<figure class="border"><img src="jekyll-quick-start.png" alt="A series of 4 terminal commands, starting with: gem install bundler jekyll…"/><figcaption>Jekyll’s core message, “Get up and running in seconds”</figcaption></figure>
+<figure class="border"><img src="https://fvsch.com/static-site-generators/jekyll-quick-start.png" alt="A series of 4 terminal commands, starting with: gem install bundler jekyll…"/><figcaption>Jekyll’s core message, “Get up and running in seconds”</figcaption></figure>
 <p>This is developer-talk, <em>because static site generators are tools made by developers for themselves and their peers</em>.</p>
 <p>On the other hand, “content management” software such as WordPress, Drupal or <a href="https://getkirby.com/">my personal favorite, Kirby</a>, target a dual audience: content editors (who write and manage content), and developers (who set up the CMS and implement the site’s design and features).</p>
 <p>I’m making this point because, if we own up to who our software’s audience is, then we can consider what we can do for that audience and hopefully design less terrible software.</p>
@@ -58,7 +58,7 @@ hash_url: ff864f1890f6eb967b3f9645554708e0
 <p>When I’ve used static site generators in the past ten years, there were a few pain points like lacking documentation and strange and incompatible conventions. But the nail in the coffin was always that it’s either impossible or way too hard to <strong>build a single page from several pieces of content</strong>.</p>
 <p>Recently, I’ve looked at static site generators again, because I wanted to convert Kaliop’s <a href="https://kaliop.github.io/frontend-style-guide/2.0/">Frontend Style Guide</a>, originally built with Kirby CMS, to something that could be built to static HTML in fewer steps <em>by developers</em> (e.g. <code>npm install &amp;&amp; npm run build</code>).</p>
 <p>This site is made of a handful of long “chapter” pages, with a top-level table of contents which lists all chapters and their sections:</p>
-<figure class="border"><img alt="Screenshot showing a full table of contents with 3 levels of titles" src="style-guide.png" srcset="style-guide.png 1x, style-guide@2x.png 2x"/></figure>
+<figure class="border"><img alt="Screenshot showing a full table of contents with 3 levels of titles" src="https://fvsch.com/static-site-generators/style-guide.png" srcset="https://fvsch.com/static-site-generators/style-guide.png 1x, https://fvsch.com/static-site-generators/style-guide@2x.png 2x"/></figure>
 <p>For easier <em>content management</em> and reordering of sections, I had broken each chapter into different section files, so that the index page is generated from three levels of content. Looking at the “General Rules” branch only, the content hierarchy looks like:</p>
 <pre><code class="language-txt">2.0
 └─ general

cache/ff864f1890f6eb967b3f9645554708e0/index.html

@@ -507,7 +507,7 @@ footer {
 
 <p>The most popular static site generator, Jekyll, may have the best documentation pages of the lot. And yet, it still puts a bunch of technical language front-and-center, on the project’s home page:</p>
 
-<figure class="border"><img src="jekyll-quick-start.png" alt="A series of 4 terminal commands, starting with: gem install bundler jekyll…"/><figcaption>Jekyll’s core message, “Get up and running in seconds”</figcaption></figure>
+<figure class="border"><img src="https://fvsch.com/static-site-generators/jekyll-quick-start.png" alt="A series of 4 terminal commands, starting with: gem install bundler jekyll…"/><figcaption>Jekyll’s core message, “Get up and running in seconds”</figcaption></figure>
 
 <p>This is developer-talk, <em>because static site generators are tools made by developers for themselves and their peers</em>.</p>
 
@@ -553,7 +553,7 @@ footer {
 
 <p>This site is made of a handful of long “chapter” pages, with a top-level table of contents which lists all chapters and their sections:</p>
 
-<figure class="border"><img alt="Screenshot showing a full table of contents with 3 levels of titles" src="style-guide.png" srcset="style-guide.png 1x, style-guide@2x.png 2x"/></figure>
+<figure class="border"><img alt="Screenshot showing a full table of contents with 3 levels of titles" src="https://fvsch.com/static-site-generators/style-guide.png" srcset="https://fvsch.com/static-site-generators/style-guide.png 1x, https://fvsch.com/static-site-generators/style-guide@2x.png 2x"/></figure>
 
 <p>For easier <em>content management</em> and reordering of sections, I had broken each chapter into different section files, so that the index page is generated from three levels of content. Looking at the “General Rules” branch only, the content hierarchy looks like:</p>
 
@@ -719,7 +719,7 @@ References: …</code></pre>
     <p>
       Je m’intéresse à la place que je peux avoir dans ce monde. En tant qu’humain, en tant que membre d’une famille et en tant qu’associé d’une coopérative. De temps en temps, je fais aussi des <a href="https://github.com/davidbgk" title="Principalement sur Github mais aussi ailleurs">trucs techniques</a>. Et encore plus rarement, <a href="/david/talks/" title="En ce moment je laisse plutôt la place aux autres">j’en parle</a>.
     </p>
-    
+
     <p>
       Voici quelques articles choisis :
       <a href="/david/blog/2019/faire-equipe/" title="Accéder à l’article complet">Faire équipe</a>,

cache/ff864f1890f6eb967b3f9645554708e0/index.md

@@ -31,7 +31,7 @@ hash_url: ff864f1890f6eb967b3f9645554708e0
 <pre><code class="language-md">![My cat at 4 months]({{&lt; imgproc sniffles-4months.jpg Resize "600x" /&gt;}})</code></pre>
 <p>At this point we must recognize that static site generators are tools made by developers <em>for developers</em>. They require a ton of previous knowledge: HTML, Markdown, command line interfaces, FTP or some other way to publish HTML files online, and of course you would need some kind of web hosting to put those files. Users will also need to dive into technical documentation for their tool of choice when they want to customize their site’s pages, work in “templates”, learn a templating language, and probably write some CSS.</p>
 <p>The most popular static site generator, Jekyll, may have the best documentation pages of the lot. And yet, it still puts a bunch of technical language front-and-center, on the project’s home page:</p>
-<figure class="border"><img src="jekyll-quick-start.png" alt="A series of 4 terminal commands, starting with: gem install bundler jekyll…"/><figcaption>Jekyll’s core message, “Get up and running in seconds”</figcaption></figure>
+<figure class="border"><img src="https://fvsch.com/static-site-generators/jekyll-quick-start.png" alt="A series of 4 terminal commands, starting with: gem install bundler jekyll…"/><figcaption>Jekyll’s core message, “Get up and running in seconds”</figcaption></figure>
 <p>This is developer-talk, <em>because static site generators are tools made by developers for themselves and their peers</em>.</p>
 <p>On the other hand, “content management” software such as WordPress, Drupal or <a href="https://getkirby.com/">my personal favorite, Kirby</a>, target a dual audience: content editors (who write and manage content), and developers (who set up the CMS and implement the site’s design and features).</p>
 <p>I’m making this point because, if we own up to who our software’s audience is, then we can consider what we can do for that audience and hopefully design less terrible software.</p>
@@ -58,7 +58,7 @@ hash_url: ff864f1890f6eb967b3f9645554708e0
 <p>When I’ve used static site generators in the past ten years, there were a few pain points like lacking documentation and strange and incompatible conventions. But the nail in the coffin was always that it’s either impossible or way too hard to <strong>build a single page from several pieces of content</strong>.</p>
 <p>Recently, I’ve looked at static site generators again, because I wanted to convert Kaliop’s <a href="https://kaliop.github.io/frontend-style-guide/2.0/">Frontend Style Guide</a>, originally built with Kirby CMS, to something that could be built to static HTML in fewer steps <em>by developers</em> (e.g. <code>npm install &amp;&amp; npm run build</code>).</p>
 <p>This site is made of a handful of long “chapter” pages, with a top-level table of contents which lists all chapters and their sections:</p>
-<figure class="border"><img alt="Screenshot showing a full table of contents with 3 levels of titles" src="style-guide.png" srcset="style-guide.png 1x, style-guide@2x.png 2x"/></figure>
+<figure class="border"><img alt="Screenshot showing a full table of contents with 3 levels of titles" src="https://fvsch.com/static-site-generators/style-guide.png" srcset="https://fvsch.com/static-site-generators/style-guide.png 1x, https://fvsch.com/static-site-generators/style-guide@2x.png 2x"/></figure>
 <p>For easier <em>content management</em> and reordering of sections, I had broken each chapter into different section files, so that the index page is generated from three levels of content. Looking at the “General Rules” branch only, the content hierarchy looks like:</p>
 <pre><code class="language-txt">2.0
 └─ general