Quellcode durchsuchen

Publishing

master
David Larlet vor 3 Jahren
Ursprung
Commit
1c688c32fd

+ 2
- 2
david/2021/02/12/index.html Datei anzeigen

@@ -62,7 +62,7 @@
<a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
</svg> Accueil</a>
• <a rel="next" href="/david/2021/02/14/" title="Publication suivante : Bibliothèque">Suivant →</a>
</p>
</nav>
<hr>
@@ -85,7 +85,7 @@
<p class="center">
<a rel="prev" href="/david/2021/02/11/" title="Publication précédente : Nucléaire">← Précédent</a> •
<a href="/david/2021/" title="Liste des publications récentes">↑ En 2021</a>
• <a rel="next" href="/david/2021/02/14/" title="Publication suivante : Bibliothèque">Suivant →</a>
</p>
</nav>
</article>

+ 191
- 0
david/2021/02/14/index.html Datei anzeigen

@@ -0,0 +1,191 @@
<!doctype html><!-- This is a valid HTML5 document. -->
<!-- Screen readers, SEO, extensions and so on. -->
<html lang="fr">
<!-- Has to be within the first 1024 bytes, hence before the <title>
See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
<meta charset="utf-8">
<!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
<!-- The viewport meta is quite crowded and we are responsible for that.
See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
<meta name="viewport" content="width=device-width,initial-scale=1">
<!-- Required to make a valid HTML5 document. -->
<title>Bibliothèque — David Larlet</title>
<meta name="description" content="I know there’s lots of advice out there about considering your audience when you write, but when it comes to my personal site, I’d find that crippling. It would be one more admonishment from the inner critic whispering “no one’s interested in that”, “you have nothing new to add to this topic”, and “you’re not qualified to write about this.” If I’m writing for myself, then it’s easier to have fewer inhibitions. By treating everything as a scrappy note-to-self, I can avoid agonising about quality control …although I still spend far too long trying to come up with titles for posts.">
<!-- That good ol' feed, subscribe :). -->
<link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
<!-- Generated from https://realfavicongenerator.net/ such a mess. -->
<link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
<link rel="manifest" href="/static/david/icons2/site.webmanifest">
<link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
<link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
<meta name="msapplication-TileColor" content="#f0f0ea">
<meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
<meta name="theme-color" content="#f0f0ea">
<!-- Documented, feel free to shoot an email. -->
<link rel="stylesheet" href="/static/david/css/style_2021-01-20.css">
<!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<script>
function toggleTheme(themeName) {
document.documentElement.classList.toggle(
'forced-dark',
themeName === 'dark'
)
document.documentElement.classList.toggle(
'forced-light',
themeName === 'light'
)
}
const selectedTheme = localStorage.getItem('theme')
if (selectedTheme !== 'undefined') {
toggleTheme(selectedTheme)
}
</script>

<body class="remarkdown h1-underline h2-underline h3-underline em-underscore hr-center ul-star pre-tick" data-instant-intensity="viewport-all">


<article>
<header>
<h1>Bibliothèque</h1>
</header>
<nav>
<p class="center">
<a rel="prev" href="/david/2021/02/12/" title="Publication précédente : Beauté">← Précédent</a> •
<a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
</svg> Accueil</a>
</p>
</nav>
<hr>


<blockquote lang="en">
<p>I know there’s lots of advice out there about considering your audience when you write, but when it comes to my personal site, I’d find that crippling. It would be one more admonishment from the inner critic whispering “no one’s interested in that”, “you have nothing new to add to this topic”, and “you’re not qualified to write about this.” If I’m writing for myself, then it’s easier to have fewer inhibitions. By treating everything as a scrappy note-to-self, I can avoid agonising about quality control …although I still spend far too long trying to come up with titles for posts.</p>
<p>[…]</p>
<p>If someone else gets some value from a quick blog post that I dash off here, that’s always a pleasant surprise. It’s a bonus. But it’s not my reason for writing. <mark>My website is primarily a tool and a library for myself.</mark> It just happens to also be public.</p>
<p><cite><em><a href="https://adactio.com/journal/17821">Associative trails</a></em> (<a href="/david/cache/2021/27f60626eb789433d6e2619663bb79f0/">cache</a>)</cite></p>
</blockquote>
<p>J’aime cette notion de bibliothèque d’idées personnelle <em>et</em> publique. Aucun service à ma connaissance ne permet cela avec la garantie de conserver les données et de les indexer sur plusieurs décennies. Privilège de développeur que celui d’<em>être en capacité</em> de le faire grâce aux compétences permettant de transformer — et donc conserver — des données au cours du temps.</p>
<p>Si vous devez un jour faire une recherche sur ce qui a été écrit ici, vous pouvez télécharger <a href="https://git.larlet.fr/davidbgk/larlet-fr-david">l’archive du dépôt</a>, la charger dans n’importe quel éditeur de texte un peu compétent (comme <a href="https://www.sublimetext.com/">SublimeText</a>) et une recherche dans tous les fichiers devrait vous permettre de fouiller. C’est ce que j’utilise personnellement lorsque ma mémoire me fait défaut ou que je veux faire un lien interne.</p>

<blockquote lang="en">
<p>And I’m also reminded of how writers I love and respect maintain their own reservoirs of knowledge, complete with migratory paths down from the mountains.</p>
<p>[…]</p>
<p>And it’s interesting, right, this accretive note-taking and the process of taking core samples through the deep time of your own ideas. I’ve built something similar, not as consistently, but for about two decades too, and <mark>I keep all my notes in plain text</mark>, and all in the same searchable database.</p>
<p><cite><em><a href="http://interconnected.org/home/2021/02/10/reservoirs">Memexes, mountain lakes, and the serendipity of old ideas</a></em> (<a href="/david/cache/2021/9b2e831c217bc1179c0f74c4fc363c11/">cache</a>)</cite></p>
</blockquote>

<nav>
<p class="center">
<a rel="prev" href="/david/2021/02/12/" title="Publication précédente : Beauté">← Précédent</a> •
<a href="/david/2021/" title="Liste des publications récentes">↑ En 2021</a>
</p>
</nav>
</article>


<hr>

<footer>
<p>
<a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
</svg> Accueil</a> •
<a href="/david/log/" title="Accès au flux RSS"><svg class="icon icon-rss2">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-rss2"></use>
</svg> RSS</a> •
<a href="http://larlet.com" title="Go to my English profile" data-instant><svg class="icon icon-user-tie">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-user-tie"></use>
</svg> Pro</a> •
<a href="mailto:david%40larlet.fr" title="Envoyer un courriel"><svg class="icon icon-mail">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-mail"></use>
</svg> Email</a> •
<abbr class="nowrap" title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340"><svg class="icon icon-hammer2">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-hammer2"></use>
</svg> Légal</abbr>
</p>
<template id="theme-selector">
<form>
<fieldset>
<legend><svg class="icon icon-brightness-contrast">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-brightness-contrast"></use>
</svg> Thème</legend>
<label>
<input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
</label>
<label>
<input type="radio" value="dark" name="chosen-color-scheme"> Foncé
</label>
<label>
<input type="radio" value="light" name="chosen-color-scheme"> Clair
</label>
</fieldset>
</form>
</template>
</footer>
<script src="/static/david/js/instantpage-5.1.0.min.js" type="module"></script>
<script>
function loadThemeForm(templateName) {
const themeSelectorTemplate = document.querySelector(templateName)
const form = themeSelectorTemplate.content.firstElementChild
themeSelectorTemplate.replaceWith(form)

form.addEventListener('change', (e) => {
const chosenColorScheme = e.target.value
localStorage.setItem('theme', chosenColorScheme)
toggleTheme(chosenColorScheme)
})

const selectedTheme = localStorage.getItem('theme')
if (selectedTheme && selectedTheme !== 'undefined') {
form.querySelector(`[value="${selectedTheme}"]`).checked = true
}
}

const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
window.addEventListener('load', () => {
let hasDarkRules = false
for (const styleSheet of Array.from(document.styleSheets)) {
let mediaRules = []
for (const cssRule of styleSheet.cssRules) {
if (cssRule.type !== CSSRule.MEDIA_RULE) {
continue
}
// WARNING: Safari does not have/supports `conditionText`.
if (cssRule.conditionText) {
if (cssRule.conditionText !== prefersColorSchemeDark) {
continue
}
} else {
if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
continue
}
}
mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
}

// WARNING: do not try to insert a Rule to a styleSheet you are
// currently iterating on, otherwise the browser will be stuck
// in a infinite loop…
for (const mediaRule of mediaRules) {
styleSheet.insertRule(mediaRule.cssText)
hasDarkRules = true
}
}
if (hasDarkRules) {
loadThemeForm('#theme-selector')
}
})
</script>
</body>
</html>

+ 2
- 0
david/2021/index.html Datei anzeigen

@@ -148,6 +148,8 @@
<h2><a href="/david/2021/02/12/">Beauté</a> (2021-02-12)</h2>
<h2><a href="/david/2021/02/14/">Bibliothèque</a> (2021-02-14)</h2>
</main>



+ 23
- 0
david/2021/sources/2021-02-14 - Bibliothèque.md Datei anzeigen

@@ -0,0 +1,23 @@
# Bibliothèque

> [en] I know there’s lots of advice out there about considering your audience when you write, but when it comes to my personal site, I’d find that crippling. It would be one more admonishment from the inner critic whispering “no one’s interested in that”, “you have nothing new to add to this topic”, and “you’re not qualified to write about this.” If I’m writing for myself, then it’s easier to have fewer inhibitions. By treating everything as a scrappy note-to-self, I can avoid agonising about quality control …although I still spend far too long trying to come up with titles for posts.
>
> […]
>
> If someone else gets some value from a quick blog post that I dash off here, that’s always a pleasant surprise. It’s a bonus. But it’s not my reason for writing. ==My website is primarily a tool and a library for myself.== It just happens to also be public.
>
> <cite>*[Associative trails](https://adactio.com/journal/17821)* ([cache](/david/cache/2021/27f60626eb789433d6e2619663bb79f0/))</cite>

J’aime cette notion de bibliothèque d’idées personnelle *et* publique. Aucun service à ma connaissance ne permet cela avec la garantie de conserver les données et de les indexer sur plusieurs décennies. Privilège de développeur que celui d’*être en capacité* de le faire grâce aux compétences permettant de transformer — et donc conserver — des données au cours du temps.

Si vous devez un jour faire une recherche sur ce qui a été écrit ici, vous pouvez télécharger [l’archive du dépôt](https://git.larlet.fr/davidbgk/larlet-fr-david), la charger dans n’importe quel éditeur de texte un peu compétent (comme [SublimeText](https://www.sublimetext.com/)) et une recherche dans tous les fichiers devrait vous permettre de fouiller. C’est ce que j’utilise personnellement lorsque ma mémoire me fait défaut ou que je veux faire un lien interne.

> [en] And I’m also reminded of how writers I love and respect maintain their own reservoirs of knowledge, complete with migratory paths down from the mountains.
>
> […]
>
> And it’s interesting, right, this accretive note-taking and the process of taking core samples through the deep time of your own ideas. I’ve built something similar, not as consistently, but for about two decades too, and ==I keep all my notes in plain text==, and all in the same searchable database.
>
> <cite>*[Memexes, mountain lakes, and the serendipity of old ideas](http://interconnected.org/home/2021/02/10/reservoirs)* ([cache](/david/cache/2021/9b2e831c217bc1179c0f74c4fc363c11/))</cite>



+ 2
- 0
david/index.html Datei anzeigen

@@ -74,6 +74,8 @@
<nav>
<ul>
<li><a href="/david/2021/02/14/">Bibliothèque</a> (2021-02-14)</li>
<li><a href="/david/2021/02/12/">Beauté</a> (2021-02-12)</li>
<li><a href="/david/2021/02/11/">Nucléaire</a> (2021-02-11)</li>

+ 26
- 1
david/log/index.xml Datei anzeigen

@@ -5,13 +5,38 @@
<link href="https://larlet.fr/david/" rel="alternate" type="text/html" />
<link href="https://larlet.fr/david/log/" rel="self" />
<id>https://larlet.fr/david/</id>
<updated>2021-02-19T12:00:00+01:00</updated>
<updated>2021-02-21T12:00:00+01:00</updated>
<author>
<name>David Larlet</name>
<uri>https://larlet.fr/david/</uri>
</author>
<rights>Copyright (c) 2004-2021, David Larlet</rights>
<entry xml:lang="fr">
<title>Bibliothèque</title>
<link href="https://larlet.fr/david/2021/02/14/" rel="alternate" type="text/html" />
<updated>2021-02-14T12:00:00+01:00</updated>
<id>https://larlet.fr/david/2021/02/14/</id>
<summary type="html">

&lt;blockquote lang=&quot;en&quot;&gt;
&lt;p&gt;I know there’s lots of advice out there about considering your audience when you write, but when it comes to my personal site, I’d find that crippling. It would be one more admonishment from the inner critic whispering “no one’s interested in that”, “you have nothing new to add to this topic”, and “you’re not qualified to write about this.” If I’m writing for myself, then it’s easier to have fewer inhibitions. By treating everything as a scrappy note-to-self, I can avoid agonising about quality control …although I still spend far too long trying to come up with titles for posts.&lt;/p&gt;
&lt;p&gt;[…]&lt;/p&gt;
&lt;p&gt;If someone else gets some value from a quick blog post that I dash off here, that’s always a pleasant surprise. It’s a bonus. But it’s not my reason for writing. &lt;mark&gt;My website is primarily a tool and a library for myself.&lt;/mark&gt; It just happens to also be public.&lt;/p&gt;
&lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;https://adactio.com/journal/17821&quot;&gt;Associative trails&lt;/a&gt;&lt;/em&gt; (&lt;a href=&quot;https://larlet.fr/david/cache/2021/27f60626eb789433d6e2619663bb79f0/&quot;&gt;cache&lt;/a&gt;)&lt;/cite&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;J’aime cette notion de bibliothèque d’idées personnelle &lt;em&gt;et&lt;/em&gt; publique. Aucun service à ma connaissance ne permet cela avec la garantie de conserver les données et de les indexer sur plusieurs décennies. Privilège de développeur que celui d’&lt;em&gt;être en capacité&lt;/em&gt; de le faire grâce aux compétences permettant de transformer — et donc conserver — des données au cours du temps.&lt;/p&gt;
&lt;p&gt;Si vous devez un jour faire une recherche sur ce qui a été écrit ici, vous pouvez télécharger &lt;a href=&quot;https://git.larlet.fr/davidbgk/larlet-fr-david&quot;&gt;l’archive du dépôt&lt;/a&gt;, la charger dans n’importe quel éditeur de texte un peu compétent (comme &lt;a href=&quot;https://www.sublimetext.com/&quot;&gt;SublimeText&lt;/a&gt;) et une recherche dans tous les fichiers devrait vous permettre de fouiller. C’est ce que j’utilise personnellement lorsque ma mémoire me fait défaut ou que je veux faire un lien interne.&lt;/p&gt;

&lt;blockquote lang=&quot;en&quot;&gt;
&lt;p&gt;And I’m also reminded of how writers I love and respect maintain their own reservoirs of knowledge, complete with migratory paths down from the mountains.&lt;/p&gt;
&lt;p&gt;[…]&lt;/p&gt;
&lt;p&gt;And it’s interesting, right, this accretive note-taking and the process of taking core samples through the deep time of your own ideas. I’ve built something similar, not as consistently, but for about two decades too, and &lt;mark&gt;I keep all my notes in plain text&lt;/mark&gt;, and all in the same searchable database.&lt;/p&gt;
&lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;http://interconnected.org/home/2021/02/10/reservoirs&quot;&gt;Memexes, mountain lakes, and the serendipity of old ideas&lt;/a&gt;&lt;/em&gt; (&lt;a href=&quot;https://larlet.fr/david/cache/2021/9b2e831c217bc1179c0f74c4fc363c11/&quot;&gt;cache&lt;/a&gt;)&lt;/cite&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr/&gt;&lt;p&gt;&lt;a href=&quot;mailto:david@larlet.fr&quot;&gt;Réagir ?&lt;/a&gt;&lt;/p&gt;</summary>
</entry>
<entry xml:lang="fr">
<title>Beauté</title>
<link href="https://larlet.fr/david/2021/02/12/" rel="alternate" type="text/html" />

+ 1
- 0
requirements.txt Datei anzeigen

@@ -3,3 +3,4 @@ minicli==0.4.4
mistune==2.0.0a5
Pillow==7.1.2
python-slugify==4.0.0
regex==2020.11.13

Laden…
Abbrechen
Speichern