1 year ago · 1cdbb30b80
--- a/cache/2023/65169d7164c8bf5790a224d45a95adb7/index.html
+++ b/cache/2023/65169d7164c8bf5790a224d45a95adb7/index.html
@@ -0,0 +1,180 @@
 <!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` element
  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>The Content Management System of my Dreams (part 1) - A little bit of history (archive) — David Larlet</title>
 <meta name="description" content="Publication mise en cache pour en conserver une trace.">
 <!-- 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="#f7f7f7">
 <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
 <meta name="theme-color" content="#f7f7f7" media="(prefers-color-scheme: light)">
 <meta name="theme-color" content="#272727" media="(prefers-color-scheme: dark)">
 <!-- 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>

  <meta name="robots" content="noindex, nofollow">
  <meta content="origin-when-cross-origin" name="referrer">
  <!-- Canonical URL for SEO purposes -->
  <link rel="canonical" href="https://www.padawan.info/en/2023/02/the-content-management-system-of-my-dreams-part-1-a-little-bit-of-history.html">

 <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>The Content Management System of my Dreams (part 1) - A little bit of history</h1>
  </header>
  <nav>
    <p class="center">
      <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-home"></use>
      </svg> Accueil</a> •
      <a href="https://www.padawan.info/en/2023/02/the-content-management-system-of-my-dreams-part-1-a-little-bit-of-history.html" title="Lien vers le contenu original">Source originale</a>
    </p>
  </nav>
  <hr>
  <p><strong>The world needs more static sites but does not need yet another <abbr title="Static Site Generator">SSG</abbr> munching Markdown files.</strong></p>
 <p>Each and every time I encounter a new <abbr title="Content Management System">CMS</abbr> I cry and want to design a new one. No wonder why there is a flurry of half-baked “off-the-shelf” CMS and even more custom ones out there.</p>
 <p>Most tech people do not understand the sweet spot between designing and editing a web site, its content management, static <i>vs</i> dynamic publishing, and all their users real needs. Or even who are the <em>real</em> users of the end product.</p>
 <h3>A little history about a forgotten jewel</h3>
 <p>In 2001 — that's 22 years ago, about a bazillion years in web time — a tiny two-people company named Six Apart, announced and published <a href="https://en.wikipedia.org/wiki/Movable_Type">Movable Type</a>. It was a blog engine that, from the start, allowed one to publish any number of blogs, related or not down to their domain names, with a 100% web <abbr title="User Interface">UI</abbr> that allowed designers, contributors, editors and site visitors to do what they each wanted to do.</p>
 <p>Designers could create and manage all templates using a browser. The template markup (<abbr title="Movable Type Markup Language">MTML</abbr>) would prevent, by design, obvious security issues by simply not allowing anything outside what it was designed to do: display content — whatever it is, it did not care if it is HTML, PDF, PHP and whatnot — in the site style.<br>It did not prevent one to extend the application logic, using either a scripting language of their choosing, or developing plugins that would expose new MTML tags.<br>It introduced a very powerful concept: the ability to publish anything as files, with a template logic allowing to generate index pages (like the home page), listings (e.g. a page listing blog entries, lists generated through custom rules such as tags, categories, date-based archives etc.), and custom shared templates you could use directly in other templates and computed in-place or just once and included either via an internal cache or via Apache and PHP includes.<br>Cherry on the cake, it included a very smart internal cache system that would allow the designer to tell <abbr title="Movable Type">MT</abbr> exactly when and where to refresh files. This particular ability, which about no CMS gets right 22 years later, would allow MT to publish a blog in 100% static HTML files with visitors comments added on the fly by republishing <em>only the strict minimum of pages</em> (obviously the commented blog post, along with any page impacted by it, like a page displaying the latest comments or their number).</p>
 <p>Yes, 22 years ago we had a CMS that would allow dynamic content on a static site. And even if it needed a database for content <em>management</em>, it would not for <em>serving content</em>. You could shut down your database server, the site would continue to work just fine if no new content needed to be published. If you had to face a spam attack throught comments, you could just disable one file and your site would still work, just without new comments while waiting for the wave to pass.</p>
 <p></p>
 <p>You know what? <a href="http://www.movabletype.com">Movable Type</a> is still alive and kicking today. Albeit in Japanese and developed by a company that used to care about editors outside Japan.<br>I have been using it from day one of this blog (né Year II before <abbr title="Loïc Le Meur, coucou Loïc , long time no see!">LLM</abbr>). I have tried a few times to play with a new CMS only to go back to MT.<br>I have built several sites, <a href="https://www.lefigaro.fr/blogs">one of them</a> growing over a million PV per day on a single small web server that did not need any upgrade for years, <a href="https://www.paris-web.fr">another one</a> that has quite a complex set of content and sustained years of attempts by WordPress lovers to replace it, only for them to come to love MT at the end, each and every time.</p>
 </article>


 <hr>

 <footer>
  <p>
    <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.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-2021-12.svg#icon-rss2"></use>
      </svg> Suivre</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-2021-12.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-2021-12.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-2021-12.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-2021-12.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>
--- a/cache/2023/65169d7164c8bf5790a224d45a95adb7/index.md
+++ b/cache/2023/65169d7164c8bf5790a224d45a95adb7/index.md
@@ -0,0 +1,13 @@
 title: The Content Management System of my Dreams (part 1) - A little bit of history
 url: https://www.padawan.info/en/2023/02/the-content-management-system-of-my-dreams-part-1-a-little-bit-of-history.html
 hash_url: 65169d7164c8bf5790a224d45a95adb7

 <p><strong>The world needs more static sites but does not need yet another <abbr title="Static Site Generator">SSG</abbr> munching Markdown files.</strong></p>
 <p>Each and every time I encounter a new <abbr title="Content Management System">CMS</abbr> I cry and want to design a new one. No wonder why there is a flurry of half-baked “off-the-shelf” CMS and even more custom ones out there.</p>
 <p>Most tech people do not understand the sweet spot between designing and editing a web site, its content management, static <i>vs</i> dynamic publishing, and all their users real needs. Or even who are the <em>real</em> users of the end product.</p>
 <h3>A little history about a forgotten jewel</h3>
 <p>In 2001 — that's 22 years ago, about a bazillion years in web time — a tiny two-people company named Six Apart, announced and published <a href="https://en.wikipedia.org/wiki/Movable_Type">Movable Type</a>. It was a blog engine that, from the start, allowed one to publish any number of blogs, related or not down to their domain names, with a 100% web <abbr title="User Interface">UI</abbr> that allowed designers, contributors, editors and site visitors to do what they each wanted to do.</p>
 <p>Designers could create and manage all templates using a browser. The template markup (<abbr title="Movable Type Markup Language">MTML</abbr>) would prevent, by design, obvious security issues by simply not allowing anything outside what it was designed to do: display content — whatever it is, it did not care if it is HTML, PDF, PHP and whatnot — in the site style.<br>It did not prevent one to extend the application logic, using either a scripting language of their choosing, or developing plugins that would expose new MTML tags.<br>It introduced a very powerful concept: the ability to publish anything as files, with a template logic allowing to generate index pages (like the home page), listings (e.g. a page listing blog entries, lists generated through custom rules such as tags, categories, date-based archives etc.), and custom shared templates you could use directly in other templates and computed in-place or just once and included either via an internal cache or via Apache and PHP includes.<br>Cherry on the cake, it included a very smart internal cache system that would allow the designer to tell <abbr title="Movable Type">MT</abbr> exactly when and where to refresh files. This particular ability, which about no CMS gets right 22 years later, would allow MT to publish a blog in 100% static HTML files with visitors comments added on the fly by republishing <em>only the strict minimum of pages</em> (obviously the commented blog post, along with any page impacted by it, like a page displaying the latest comments or their number).</p>
 <p>Yes, 22 years ago we had a CMS that would allow dynamic content on a static site. And even if it needed a database for content <em>management</em>, it would not for <em>serving content</em>. You could shut down your database server, the site would continue to work just fine if no new content needed to be published. If you had to face a spam attack throught comments, you could just disable one file and your site would still work, just without new comments while waiting for the wave to pass.</p>
 <p></p>
 <p>You know what? <a href="http://www.movabletype.com">Movable Type</a> is still alive and kicking today. Albeit in Japanese and developed by a company that used to care about editors outside Japan.<br>I have been using it from day one of this blog (né Year II before <abbr title="Loïc Le Meur, coucou Loïc , long time no see!">LLM</abbr>). I have tried a few times to play with a new CMS only to go back to MT.<br>I have built several sites, <a href="https://www.lefigaro.fr/blogs">one of them</a> growing over a million PV per day on a single small web server that did not need any upgrade for years, <a href="https://www.paris-web.fr">another one</a> that has quite a complex set of content and sustained years of attempts by WordPress lovers to replace it, only for them to come to love MT at the end, each and every time.</p>
--- a/cache/2023/f8b7c3246cf1d4e06c735ee163be32a0/index.html
+++ b/cache/2023/f8b7c3246cf1d4e06c735ee163be32a0/index.html
@@ -0,0 +1,188 @@
 <!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` element
  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>The Content Management System of my Dreams (part 2) - The trouble with dynamic publishing (archive) — David Larlet</title>
 <meta name="description" content="Publication mise en cache pour en conserver une trace.">
 <!-- 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="#f7f7f7">
 <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
 <meta name="theme-color" content="#f7f7f7" media="(prefers-color-scheme: light)">
 <meta name="theme-color" content="#272727" media="(prefers-color-scheme: dark)">
 <!-- 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>

  <meta name="robots" content="noindex, nofollow">
  <meta content="origin-when-cross-origin" name="referrer">
  <!-- Canonical URL for SEO purposes -->
  <link rel="canonical" href="https://www.padawan.info/en/2023/02/the-content-management-system-of-my-dreams-part-2-the-trouble-with-dynamic-publishing.html">

 <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>The Content Management System of my Dreams (part 2) - The trouble with dynamic publishing</h1>
  </header>
  <nav>
    <p class="center">
      <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-home"></use>
      </svg> Accueil</a> •
      <a href="https://www.padawan.info/en/2023/02/the-content-management-system-of-my-dreams-part-2-the-trouble-with-dynamic-publishing.html" title="Lien vers le contenu original">Source originale</a>
    </p>
  </nav>
  <hr>
  <h3>The trouble with dynamic publishing</h3>
 <p>PHP, Personal Home Page, popularized dynamic publishing. It gave way to blog engines, such as b2, b2evolution, <a href="https://dotclear.org">Dotclear</a>. Speaking of history, Movable Type was <em>the</em> number one blog engine loved by geeks and non geeks alike, and the few developers that would not burst in flames in front of Perl like sun-bathing vampires. When Six Apart made a brusque U-turn in killing the Open Source version of MT to pursue questionnable commercial ventures (because it was already well known that it is easier to make money out of other people's content rather than selling a CMS), a certain Matt Mullenweg saw the uproar of the community, took an opportunity by forking <a href="https://en.wikipedia.org/wiki/B2evolution">b2/cafelog</a> and rebranded it as WordPress. The crowd of bloggers took the bait and followed in droves. In one fell swoop Movable Type faded in history and WordPress took over the world.</p>
 <p>Web developers got so enamored with instantaneous “dynamic publishing” that the thought of having to click one more button and wait more than a few seconds to see a code change became unbearable. It would waste their time and by some twisted reasoning they decided that static publishing was old school and dynamic publishing was <em>soooo</em> in.<br>If it's good for them, it must be good for everyone else, right?</p>
 <p>This is why most “dynamic sites” will make a hundred calls to a database just to display <em>one</em> page to <em>one</em> visitor, even if its content never changes. Think about it this way: for each page view you are assembling the whole following scene along with summoning actors, the sea and some clouds for style, instead of just showing a print:</p>
 <p><img srcset="https://upload.wikimedia.org/wikipedia/commons/thumb/c/c2/Theodore_Gericault_Raft_of_the_Medusa-1.jpg/640px-Theodore_Gericault_Raft_of_the_Medusa-1.jpg 640w" sizes="640px" src="https://upload.wikimedia.org/wikipedia/commons/thumb/c/c2/Theodore_Gericault_Raft_of_the_Medusa-1.jpg/266px-Theodore_Gericault_Raft_of_the_Medusa-1.jpg" alt="File:Theodore Gericault Raft of the Medusa-1.jpg" class="sdms-quick-view__thumbnail sdms-quick-view__thumbnail--loaded"></p>
 <p><em>“Ah! But you are doing it wrong! Just put a cache in front of it. Problem solved!”</em></p>
 <p>And there you have <em>two</em> problems. If you need an external cache in front of your CMS, <em>you</em> are doing it wrong.<br>Cache is one of the most difficult problems in IT. Its invalidation certainly is. If the cache is added in front of the CMS, rather than being managed by the CMS itself (like MT does), you now have two different systems that need more development and maintenance work to handle changes. Your site just became more costly and more difficult to manage.</p>
 <p>I have a concrete example of this point. A site is generating its home page dynamically. Because of performance issues (it can take more than 10 seconds to generate the page) an external cache has been added in front of the site. Now the site has a cache invalidation issue that prevents a small promotion block to update when a new item is added in the CMS. The adopted solution consists of throwing an ugly truck of javascript at the visitor's browser and have it make a call to an API to fetch the last two promotions. Yes, this is a “dynamic” site that requires a double request and three computations from two servers and the browser, for each view (at least for the latter when the web server cache works, I won't even talk about caching the API server response). I reckon that this site is wasting at least 10 times the energy and money that is reasonable. And of course absolutely nothing can be done on it, beyond content edition, without a highly specialized developer and a complex deployment process.</p>
 <p>Another obvious auto-inflicted problem are performance issues, which are almost always offset by throwing more horsepower in front of the slow carriage. On the Internet, nobody knows we are entertaining a whole menagerie to serve you this page.</p>
 <p>At a time where we all must seriously think about our ecological impact and energy use, it is not ok to not take a step back and question every architectural decision that needlessly multiply servers and computing cycles when we should know, and do, better. Lazyness is half-jokingly said to be good in development. This is not funny when it turns into self-centered decisions like switching to a dynamic system because a developer or a content editor does not care to wait while rebuilding a page. <strong>A few seconds saved for one person turn into a fantastic waste of time, money and energy for everyone else</strong>.</p>
 <p>I am serious about these aspects. There are concerning reports, most of them totally out of whack, pointing fingers at the Internet sector for its ecological waste. Let alone suicidal (literally), it would be absolutely hypocritical to dismiss them by cherry-picking where those reports are wrong (that's easy) while we are conveniently forgetting about the ecological impact of some of our decisions. We are responsible, and at some point in the near future, <strong><em>we will be held responsible for our footprint in the climate disaster</em></strong>.</p>
 <p>“But I <em>need</em> a dynamic site!”</p>
 <p>Do you, really?</p>
 <p>Think very hard about that word. What exactly is <em>dynamic</em> on your home page? Are you speaking about that Top News thingy? How often do they change? Are you doing this to satisfy yourself (some content editors have the same proclivity than developers to throw a tantrum because their new content does not appear instantaneously on the site)? Is this a business requirement or a real need of your users?</p>
 <p>Of course you might need dynamic pages, for example on backoffice sites, profile pages, pages that are unique to one user. But an outstanding majority of pages floating in the cloud do not need to be recalculated for each view. Even if they contain information that changes sometimes, especially if those information are not unique to any visitor.<br>And if you do need some dynamic pages, nothing prevents you to publish the rest as static files, especially for the most visited pages of your site.</p>
 <p>Here is an easy check point: <strong>if your pages show the same content to all visitors then <em>you do not need a dynamic site</em></strong>, regardless of the frequency of its changes.</p>
 <p>There is an ironic turn at this point in history. Stay tuned…</p>
 </article>


 <hr>

 <footer>
  <p>
    <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.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-2021-12.svg#icon-rss2"></use>
      </svg> Suivre</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-2021-12.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-2021-12.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-2021-12.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-2021-12.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>
--- a/cache/2023/f8b7c3246cf1d4e06c735ee163be32a0/index.md
+++ b/cache/2023/f8b7c3246cf1d4e06c735ee163be32a0/index.md
@@ -0,0 +1,21 @@
 title: The Content Management System of my Dreams (part 2) - The trouble with dynamic publishing
 url: https://www.padawan.info/en/2023/02/the-content-management-system-of-my-dreams-part-2-the-trouble-with-dynamic-publishing.html
 hash_url: f8b7c3246cf1d4e06c735ee163be32a0

 <h3>The trouble with dynamic publishing</h3>
 <p>PHP, Personal Home Page, popularized dynamic publishing. It gave way to blog engines, such as b2, b2evolution, <a href="https://dotclear.org">Dotclear</a>. Speaking of history, Movable Type was <em>the</em> number one blog engine loved by geeks and non geeks alike, and the few developers that would not burst in flames in front of Perl like sun-bathing vampires. When Six Apart made a brusque U-turn in killing the Open Source version of MT to pursue questionnable commercial ventures (because it was already well known that it is easier to make money out of other people's content rather than selling a CMS), a certain Matt Mullenweg saw the uproar of the community, took an opportunity by forking <a href="https://en.wikipedia.org/wiki/B2evolution">b2/cafelog</a> and rebranded it as WordPress. The crowd of bloggers took the bait and followed in droves. In one fell swoop Movable Type faded in history and WordPress took over the world.</p>
 <p>Web developers got so enamored with instantaneous “dynamic publishing” that the thought of having to click one more button and wait more than a few seconds to see a code change became unbearable. It would waste their time and by some twisted reasoning they decided that static publishing was old school and dynamic publishing was <em>soooo</em> in.<br>If it's good for them, it must be good for everyone else, right?</p>
 <p>This is why most “dynamic sites” will make a hundred calls to a database just to display <em>one</em> page to <em>one</em> visitor, even if its content never changes. Think about it this way: for each page view you are assembling the whole following scene along with summoning actors, the sea and some clouds for style, instead of just showing a print:</p>
 <p><img srcset="https://upload.wikimedia.org/wikipedia/commons/thumb/c/c2/Theodore_Gericault_Raft_of_the_Medusa-1.jpg/640px-Theodore_Gericault_Raft_of_the_Medusa-1.jpg 640w" sizes="640px" src="https://upload.wikimedia.org/wikipedia/commons/thumb/c/c2/Theodore_Gericault_Raft_of_the_Medusa-1.jpg/266px-Theodore_Gericault_Raft_of_the_Medusa-1.jpg" alt="File:Theodore Gericault Raft of the Medusa-1.jpg" class="sdms-quick-view__thumbnail sdms-quick-view__thumbnail--loaded"></p>
 <p><em>“Ah! But you are doing it wrong! Just put a cache in front of it. Problem solved!”</em></p>
 <p>And there you have <em>two</em> problems. If you need an external cache in front of your CMS, <em>you</em> are doing it wrong.<br>Cache is one of the most difficult problems in IT. Its invalidation certainly is. If the cache is added in front of the CMS, rather than being managed by the CMS itself (like MT does), you now have two different systems that need more development and maintenance work to handle changes. Your site just became more costly and more difficult to manage.</p>
 <p>I have a concrete example of this point. A site is generating its home page dynamically. Because of performance issues (it can take more than 10 seconds to generate the page) an external cache has been added in front of the site. Now the site has a cache invalidation issue that prevents a small promotion block to update when a new item is added in the CMS. The adopted solution consists of throwing an ugly truck of javascript at the visitor's browser and have it make a call to an API to fetch the last two promotions. Yes, this is a “dynamic” site that requires a double request and three computations from two servers and the browser, for each view (at least for the latter when the web server cache works, I won't even talk about caching the API server response). I reckon that this site is wasting at least 10 times the energy and money that is reasonable. And of course absolutely nothing can be done on it, beyond content edition, without a highly specialized developer and a complex deployment process.</p>
 <p>Another obvious auto-inflicted problem are performance issues, which are almost always offset by throwing more horsepower in front of the slow carriage. On the Internet, nobody knows we are entertaining a whole menagerie to serve you this page.</p>
 <p>At a time where we all must seriously think about our ecological impact and energy use, it is not ok to not take a step back and question every architectural decision that needlessly multiply servers and computing cycles when we should know, and do, better. Lazyness is half-jokingly said to be good in development. This is not funny when it turns into self-centered decisions like switching to a dynamic system because a developer or a content editor does not care to wait while rebuilding a page. <strong>A few seconds saved for one person turn into a fantastic waste of time, money and energy for everyone else</strong>.</p>
 <p>I am serious about these aspects. There are concerning reports, most of them totally out of whack, pointing fingers at the Internet sector for its ecological waste. Let alone suicidal (literally), it would be absolutely hypocritical to dismiss them by cherry-picking where those reports are wrong (that's easy) while we are conveniently forgetting about the ecological impact of some of our decisions. We are responsible, and at some point in the near future, <strong><em>we will be held responsible for our footprint in the climate disaster</em></strong>.</p>
 <p>“But I <em>need</em> a dynamic site!”</p>
 <p>Do you, really?</p>
 <p>Think very hard about that word. What exactly is <em>dynamic</em> on your home page? Are you speaking about that Top News thingy? How often do they change? Are you doing this to satisfy yourself (some content editors have the same proclivity than developers to throw a tantrum because their new content does not appear instantaneously on the site)? Is this a business requirement or a real need of your users?</p>
 <p>Of course you might need dynamic pages, for example on backoffice sites, profile pages, pages that are unique to one user. But an outstanding majority of pages floating in the cloud do not need to be recalculated for each view. Even if they contain information that changes sometimes, especially if those information are not unique to any visitor.<br>And if you do need some dynamic pages, nothing prevents you to publish the rest as static files, especially for the most visited pages of your site.</p>
 <p>Here is an easy check point: <strong>if your pages show the same content to all visitors then <em>you do not need a dynamic site</em></strong>, regardless of the frequency of its changes.</p>
 <p>There is an ironic turn at this point in history. Stay tuned…</p>
--- a/cache/2023/f9e282fb545b5c1f50dfa1c0d98c50e3/index.html
+++ b/cache/2023/f9e282fb545b5c1f50dfa1c0d98c50e3/index.html
@@ -0,0 +1,501 @@
 <!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` element
  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>South Pole Topography (archive) — David Larlet</title>
 <meta name="description" content="Publication mise en cache pour en conserver une trace.">
 <!-- 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="#f7f7f7">
 <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
 <meta name="theme-color" content="#f7f7f7" media="(prefers-color-scheme: light)">
 <meta name="theme-color" content="#272727" media="(prefers-color-scheme: dark)">
 <!-- 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>

  <meta name="robots" content="noindex, nofollow">
  <meta content="origin-when-cross-origin" name="referrer">
  <!-- Canonical URL for SEO purposes -->
  <link rel="canonical" href="https://brr.fyi/posts/south-pole-topography">

 <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>South Pole Topography</h1>
  </header>
  <nav>
    <p class="center">
      <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-home"></use>
      </svg> Accueil</a> •
      <a href="https://brr.fyi/posts/south-pole-topography" title="Lien vers le contenu original">Source originale</a>
    </p>
  </nav>
  <hr>
  <p>South Pole Station sits on the polar plateau, a mostly-featureless expanse of snow and ice,
  several miles thick, extending as far as the eye can see in all directions. Onto this stark, barren landscape,
  we’ve established a series of stations throughout the decades.</p>
 <p>They’ve varied in size, style, complexity, comfort, and prestige. From Old Pole, to the Dome, to the modern
  Elevated Station, the United States has maintained some type of presence at the South Pole continuously for
  a long time.</p>
 <p>One thing all these stations have in common? Nature is constantly trying to bury them! And it’s succeeding.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/extended-ventilation-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/extended-ventilation-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/extended-ventilation-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/extended-ventilation-01-small.jpg" alt="Extended Ventilation 01">
    </picture>
    <em>That's not a shack on the surface -- that's an extended ventilation shaft, connecting
      to *an entire building* which is now buried under the snow.</em>
  </a>
 </p>
 <p>I’ll include the obligatory preface here. I am an IT worker. My skills and knowledge are in computers, not snowdrift
  modeling. I have suddenly found myself in a strange, unfamiliar place, beyond my comprehension. This place is full
  of wonderful new infrastructure and infrastructure-adjacent features.</p>
 <p>I have also, to my surprise, stumbled my way into running a somewhat popular Antarctica blog.</p>
 <p>Everything I say here is based on me just walking around, photographing things, and making some (hopefully!) safe
  inferences about how this place works. There are professionals, both here and elsewhere, who devote their <strong>entire
    careers</strong> to modeling and compensating for snowdrift! Listen to them, not me, if you want to learn more about this
  stuff. I am far outside my element here.</p>
 <p>Now without further ado – here’s some observations on the topography of South Pole Station.</p>
 <p>Since every direction is technically “North” from here, we use a grid overlay, to bring some semblance of order
  to our surroundings. The prevailing winds here come from “Grid North”. They first encounter the “front” of the
  Elevated Station, then pass around / under it into the Operations Sector (“backyard”), where we have most of our
  logistics (storage, outbuildings, etc).</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/station-front-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/station-front-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/station-front-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/station-front-01-small.jpg" alt="Station Front 01">
    </picture>
    <em>The "front" of the Elevated Station. Winds blow from this direction, toward the station.</em>
  </a>
 </p>
 <p>Windblown snow is carried toward the station. Some is deposited on the front side, some passes under or around.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/transition-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/transition-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/transition-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/transition-01-small.jpg" alt="Transition 01">
    </picture>
    <em>Around the side of the station, showing the transition in snow elevation from front to back.</em>
  </a>
 </p>
 <p>The Elevated Station itself acts as a bit of a snow barrier – it’s designed to avoid any major drifting/accumulation,
  but there’s still a stark difference in elevation between the front and back.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/ground-level-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/ground-level-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/ground-level-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/ground-level-01-small.jpg" alt="Ground Level 01">
    </picture>
    <em>View from what was once "ground level", now situated below several feet of snow.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/elevated-station-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-station-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-station-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/elevated-station-01-small.jpg" alt="Elevated Station 01">
    </picture>
    <em>View from under the station, showing the extent of the current snow elevation difference.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/elevated-station-02.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-station-02-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-station-02-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/elevated-station-02-small.jpg" alt="Elevated Station 02">
    </picture>
    <em>Another view from under the station.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/elevated-station-03.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-station-03-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-station-03-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/elevated-station-03-small.jpg" alt="Elevated Station 03">
    </picture>
    <em>One last view from under the station, looking toward the operations sector / backyard.</em>
  </a>
 </p>
 <p>The station was once significantly <em>more</em> elevated than it currently is. The snow is creeping up! This is apparent
  when you look at the stairwells down to “ground” level. The bottom of the stairwells are completely buried.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/buried-stairs-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-stairs-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-stairs-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/buried-stairs-01-small.jpg" alt="Buried Stairs 01">
    </picture>
    <em>A set of buried stairs, on the backside of the A1 berthing pod of the Elevated Station.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/buried-stairs-02.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-stairs-02-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-stairs-02-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/buried-stairs-02-small.jpg" alt="Buried Stairs 02">
    </picture>
    <em>Buried stairs at Destination Alpha, the main entrance to the Elevated Station.</em>
  </a>
 </p>
 <p>Part of the elevation difference between the front and the back is just the result of wind-blown snow
  interacting with the building.</p>
 <p>However, in addition, a great deal of work is done to keep the backyard relatively flat / level.
  This prolongs its life at a given elevation, before we have to do all the hard work of lifting things up.
  We move <strong>tons</strong> of snow! It’s nearly a full-time job.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/snow-hauler-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/snow-hauler-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/snow-hauler-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/snow-hauler-01-small.jpg" alt="Snow Hauler 01">
    </picture>
    <em>A snow hauler, for moving huge quantities of snow in order to keep the backyard flat.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/end-of-the-world-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/end-of-the-world-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/end-of-the-world-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/end-of-the-world-01-small.jpg" alt="End of the World 01">
    </picture>
    <em>The "End of the World", far out beyond all our storage and outbuildings in the backyard,
      where we pile up snow removed from the backyard/operations area.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/groomed-road-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/groomed-road-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/groomed-road-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/groomed-road-01-small.jpg" alt="Groomed Road 01">
    </picture>
    <em>A mostly-flat, groomed road in the operations sector, with some snow piles visible in the distance.</em>
  </a>
 </p>
 <p>However, even in the operations sector, it’s still apparent that we’ve had significant snow accumulation
  over the decades.</p>
 <p>Most notable is the Arches. The Arches are a series of metal semi-circle storage/work facilities, built decades ago,
  well before the current modern Elevated Station. These are still in active use today! They house our power plant,
  water plant, primary cold/warm storage, fuel storage, carpenter shop, and vehicle maintenance facility.</p>
 <p>They are also <strong>completely buried</strong> under decades of accumulated snow! We can walk right over them, and if it weren’t
  for the ventilation shafts and miscellaneous other utilities, we’d be none the wiser.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/arches-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/arches-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/arches-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/arches-01-small.jpg" alt="Arches 01">
    </picture>
    <em>Entrance to the arches, showing snow completely covering them.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/arches-02.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/arches-02-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/arches-02-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/arches-02-small.jpg" alt="Arches 02">
    </picture>
    <em>Another view of the entrance to the arches. This shows the graceful ramp we had to build so vehicles can
      still get in and out, considering the entrance is now far below "ground" level.</em>
  </a>
 </p>
 <p>The power plant has also been here for decades. It’s been refurbished and overhauled over the years, but the building
  has been here for quite a long time. It’s now completely buried! All that is visible are the exhaust vents.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/power-plant-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/power-plant-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/power-plant-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/power-plant-01-small.jpg" alt="Power Plant 01">
    </picture>
    <em>Exhaust vents from the now-buried power plant.</em>
  </a>
 </p>
 <p>Getting down from the Elevated Station to the Arches means descending about 50ft. We’ve built a vertical
  tower with an enclosed staircase for this purpose. Only about half of it is visible here! The rest is underground.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/vertical-tower-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/vertical-tower-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/vertical-tower-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/vertical-tower-01-small.jpg" alt="Vertical Tower 01">
    </picture>
    <em>Vertical tower connecting the Elevated Station to the now-buried Arches.</em>
  </a>
 </p>
 <p>Less stark but still telling, there are a number of buried infrastructure elements in the backyard.</p>
 <p>Here’s the access hatch to a buried infrastructure vault. Significant work goes into “digging out” things that have
  become buried, so they are still accessible. At some point, however, the snowcover becomes too much, and the hatch
  needs to be extended up to the current ground level.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/buried-infrastructure-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-infrastructure-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-infrastructure-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/buried-infrastructure-01-small.jpg" alt="Buried Infrastructure 01">
    </picture>
    <em>Entrance to a deeply-buried infrastructure vault.</em>
  </a>
 </p>
 <p>There are examples all over station of extended hatches and
  ladders, to reach infrastructure that keeps getting buried deeper below ground level.</p>
 <p>Here’s a work in progress at a location a bit farther out from station. A team has dug out a buried access hatch,
  and soon an extension will be added so that it sits at the new ground level. The infrastructure underground doesn’t
  change, but the access hatch requires constant maintenance.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/buried-access-hatch-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-access-hatch-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-access-hatch-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/buried-access-hatch-01-small.jpg" alt="Buried Access Hatch 01">
    </picture>
    <em>An access hatch to an underground infrastructure vault, soon to be extended up to ground level.</em>
  </a>
 </p>
 <p>In the backyard, there are a number of strategies to deal with the accumulation of snow.</p>
 <p>Some buildings are built right at ground level. These will get slowly buried, unless work is done to engineer the
  snow around them. You can engineer away several feet of snow accumulation, and still make a building seem at “ground”
  level, just by introducing a gentle downward slope toward a building from the prevailing ground level.</p>
 <p>Here’s a few buildings that are not elevated. Yes, they collect snowdrifts. And yes, they’ll eventually have to be
  moved! But for now, the herculean effort to grade and engineer the topography of the backyard means they are still
  accessible at “ground” level.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/outbuildings-02.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/outbuildings-02-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/outbuildings-02-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/outbuildings-02-small.jpg" alt="Outbuildings 02">
    </picture>
    <em>A ground-level outbuilding, still accessible due to careful management of the surrounding topography.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/outbuildings-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/outbuildings-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/outbuildings-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/outbuildings-01-small.jpg" alt="Outbuildings 01">
    </picture>
    <em>Another ground-level outbuilding. Note the snowdrifts!</em>
  </a>
 </p>
 <p>Speaking of snowdrifts, they are relentless! They will pile up against anything facing the wind. Here’s one
  ground-level outbuilding with some drifts up against it:</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/outbuilding-snow-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/outbuilding-snow-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/outbuilding-snow-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/outbuilding-snow-01-small.jpg" alt="Outbuilding Snow 01">
    </picture>
    <em>An outbuilding with fresh, un-shoveled snowdrifts against it.</em>
  </a>
 </p>
 <p>There is also a lot of ground-level storage. Here’s a typical storage aisle:</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/storage-aisle-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/storage-aisle-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/storage-aisle-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/storage-aisle-01-small.jpg" alt="Storage Aisle 01">
    </picture>
    <em>Storage aisle. Note the relentless drifting snow! Also visible is a temporary pile of snow, plowed out of the
      way so this storage can be accessed.</em>
  </a>
 </p>
 <p>Other buildings are designed to be resilient to some amount of snow accumulation. Just like the main Elevated Station,
  here’s a building that is elevated above ground, so it can more gracefully tolerate a shift in
  ground level.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/elevated-outbuilding-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-outbuilding-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-outbuilding-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/elevated-outbuilding-01-small.jpg" alt="Elevated Outbuilding 01">
    </picture>
    <em>An outbuilding in our RF sector, housing information technology equipment. Elevated above ground,
      so we can tolerate shifts in snow cover without compromising access to the building.</em>
  </a>
 </p>
 <p>We also make use of elevated storage! Here’s a series of elevated storage platforms. This is more complex and
  more expensive than just putting stuff on the ground, but it means we’ll be able to access it for years to come
  without having to dig it out.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/elevated-storage-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-storage-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-storage-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/elevated-storage-01-small.jpg" alt="Elevated Storage 01">
    </picture>
    <em>Elevated storage. This is a common tactic for long-term storage, to avoid stuff getting buried.</em>
  </a>
 </p>
 <p>On a lighter note, one benefit of our massive snow hauling operation is that we can occasionally indulge in a bit of
  fun. Here’s the South Pole Sledding Hill, lovingly maintained by station staff. There’s plenty of snow to go around!</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/sledding-hill-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/sledding-hill-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/sledding-hill-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/sledding-hill-01-small.jpg" alt="Sledding Hill 01">
    </picture>
  </a>
 </p>
 <p>It’s neat to see the layered history of the South Pole. You can
  roughly gauge the age of infrastructure by how deeply buried it is!</p>
 <p>Walking from the Elevated Station down to the
  Arches is a fun journey into the past.</p>
 <p>Climbing down an access hatch, extended multiple times to keep up with
  the relentless snow, is a good day-to-day reminder of the forces of nature at work here.</p>
 <p>I hope others find this as interesting as I do.</p>
 <p>Until next time!</p>
 </article>


 <hr>

 <footer>
  <p>
    <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.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-2021-12.svg#icon-rss2"></use>
      </svg> Suivre</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-2021-12.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-2021-12.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-2021-12.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-2021-12.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>
--- a/cache/2023/f9e282fb545b5c1f50dfa1c0d98c50e3/index.md
+++ b/cache/2023/f9e282fb545b5c1f50dfa1c0d98c50e3/index.md
@@ -0,0 +1,334 @@
 title: South Pole Topography
 url: https://brr.fyi/posts/south-pole-topography
 hash_url: f9e282fb545b5c1f50dfa1c0d98c50e3

 <p>South Pole Station sits on the polar plateau, a mostly-featureless expanse of snow and ice,
  several miles thick, extending as far as the eye can see in all directions. Onto this stark, barren landscape,
  we’ve established a series of stations throughout the decades.</p>
 <p>They’ve varied in size, style, complexity, comfort, and prestige. From Old Pole, to the Dome, to the modern
  Elevated Station, the United States has maintained some type of presence at the South Pole continuously for
  a long time.</p>
 <p>One thing all these stations have in common? Nature is constantly trying to bury them! And it’s succeeding.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/extended-ventilation-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/extended-ventilation-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/extended-ventilation-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/extended-ventilation-01-small.jpg" alt="Extended Ventilation 01">
    </picture>
    <em>That's not a shack on the surface -- that's an extended ventilation shaft, connecting
      to *an entire building* which is now buried under the snow.</em>
  </a>
 </p>
 <p>I’ll include the obligatory preface here. I am an IT worker. My skills and knowledge are in computers, not snowdrift
  modeling. I have suddenly found myself in a strange, unfamiliar place, beyond my comprehension. This place is full
  of wonderful new infrastructure and infrastructure-adjacent features.</p>
 <p>I have also, to my surprise, stumbled my way into running a somewhat popular Antarctica blog.</p>
 <p>Everything I say here is based on me just walking around, photographing things, and making some (hopefully!) safe
  inferences about how this place works. There are professionals, both here and elsewhere, who devote their <strong>entire
    careers</strong> to modeling and compensating for snowdrift! Listen to them, not me, if you want to learn more about this
  stuff. I am far outside my element here.</p>
 <p>Now without further ado – here’s some observations on the topography of South Pole Station.</p>
 <p>Since every direction is technically “North” from here, we use a grid overlay, to bring some semblance of order
  to our surroundings. The prevailing winds here come from “Grid North”. They first encounter the “front” of the
  Elevated Station, then pass around / under it into the Operations Sector (“backyard”), where we have most of our
  logistics (storage, outbuildings, etc).</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/station-front-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/station-front-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/station-front-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/station-front-01-small.jpg" alt="Station Front 01">
    </picture>
    <em>The "front" of the Elevated Station. Winds blow from this direction, toward the station.</em>
  </a>
 </p>
 <p>Windblown snow is carried toward the station. Some is deposited on the front side, some passes under or around.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/transition-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/transition-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/transition-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/transition-01-small.jpg" alt="Transition 01">
    </picture>
    <em>Around the side of the station, showing the transition in snow elevation from front to back.</em>
  </a>
 </p>
 <p>The Elevated Station itself acts as a bit of a snow barrier – it’s designed to avoid any major drifting/accumulation,
  but there’s still a stark difference in elevation between the front and back.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/ground-level-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/ground-level-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/ground-level-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/ground-level-01-small.jpg" alt="Ground Level 01">
    </picture>
    <em>View from what was once "ground level", now situated below several feet of snow.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/elevated-station-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-station-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-station-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/elevated-station-01-small.jpg" alt="Elevated Station 01">
    </picture>
    <em>View from under the station, showing the extent of the current snow elevation difference.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/elevated-station-02.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-station-02-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-station-02-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/elevated-station-02-small.jpg" alt="Elevated Station 02">
    </picture>
    <em>Another view from under the station.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/elevated-station-03.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-station-03-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-station-03-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/elevated-station-03-small.jpg" alt="Elevated Station 03">
    </picture>
    <em>One last view from under the station, looking toward the operations sector / backyard.</em>
  </a>
 </p>
 <p>The station was once significantly <em>more</em> elevated than it currently is. The snow is creeping up! This is apparent
  when you look at the stairwells down to “ground” level. The bottom of the stairwells are completely buried.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/buried-stairs-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-stairs-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-stairs-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/buried-stairs-01-small.jpg" alt="Buried Stairs 01">
    </picture>
    <em>A set of buried stairs, on the backside of the A1 berthing pod of the Elevated Station.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/buried-stairs-02.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-stairs-02-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-stairs-02-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/buried-stairs-02-small.jpg" alt="Buried Stairs 02">
    </picture>
    <em>Buried stairs at Destination Alpha, the main entrance to the Elevated Station.</em>
  </a>
 </p>
 <p>Part of the elevation difference between the front and the back is just the result of wind-blown snow
  interacting with the building.</p>
 <p>However, in addition, a great deal of work is done to keep the backyard relatively flat / level.
  This prolongs its life at a given elevation, before we have to do all the hard work of lifting things up.
  We move <strong>tons</strong> of snow! It’s nearly a full-time job.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/snow-hauler-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/snow-hauler-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/snow-hauler-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/snow-hauler-01-small.jpg" alt="Snow Hauler 01">
    </picture>
    <em>A snow hauler, for moving huge quantities of snow in order to keep the backyard flat.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/end-of-the-world-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/end-of-the-world-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/end-of-the-world-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/end-of-the-world-01-small.jpg" alt="End of the World 01">
    </picture>
    <em>The "End of the World", far out beyond all our storage and outbuildings in the backyard,
      where we pile up snow removed from the backyard/operations area.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/groomed-road-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/groomed-road-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/groomed-road-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/groomed-road-01-small.jpg" alt="Groomed Road 01">
    </picture>
    <em>A mostly-flat, groomed road in the operations sector, with some snow piles visible in the distance.</em>
  </a>
 </p>
 <p>However, even in the operations sector, it’s still apparent that we’ve had significant snow accumulation
  over the decades.</p>
 <p>Most notable is the Arches. The Arches are a series of metal semi-circle storage/work facilities, built decades ago,
  well before the current modern Elevated Station. These are still in active use today! They house our power plant,
  water plant, primary cold/warm storage, fuel storage, carpenter shop, and vehicle maintenance facility.</p>
 <p>They are also <strong>completely buried</strong> under decades of accumulated snow! We can walk right over them, and if it weren’t
  for the ventilation shafts and miscellaneous other utilities, we’d be none the wiser.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/arches-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/arches-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/arches-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/arches-01-small.jpg" alt="Arches 01">
    </picture>
    <em>Entrance to the arches, showing snow completely covering them.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/arches-02.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/arches-02-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/arches-02-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/arches-02-small.jpg" alt="Arches 02">
    </picture>
    <em>Another view of the entrance to the arches. This shows the graceful ramp we had to build so vehicles can
      still get in and out, considering the entrance is now far below "ground" level.</em>
  </a>
 </p>
 <p>The power plant has also been here for decades. It’s been refurbished and overhauled over the years, but the building
  has been here for quite a long time. It’s now completely buried! All that is visible are the exhaust vents.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/power-plant-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/power-plant-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/power-plant-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/power-plant-01-small.jpg" alt="Power Plant 01">
    </picture>
    <em>Exhaust vents from the now-buried power plant.</em>
  </a>
 </p>
 <p>Getting down from the Elevated Station to the Arches means descending about 50ft. We’ve built a vertical
  tower with an enclosed staircase for this purpose. Only about half of it is visible here! The rest is underground.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/vertical-tower-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/vertical-tower-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/vertical-tower-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/vertical-tower-01-small.jpg" alt="Vertical Tower 01">
    </picture>
    <em>Vertical tower connecting the Elevated Station to the now-buried Arches.</em>
  </a>
 </p>
 <p>Less stark but still telling, there are a number of buried infrastructure elements in the backyard.</p>
 <p>Here’s the access hatch to a buried infrastructure vault. Significant work goes into “digging out” things that have
  become buried, so they are still accessible. At some point, however, the snowcover becomes too much, and the hatch
  needs to be extended up to the current ground level.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/buried-infrastructure-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-infrastructure-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-infrastructure-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/buried-infrastructure-01-small.jpg" alt="Buried Infrastructure 01">
    </picture>
    <em>Entrance to a deeply-buried infrastructure vault.</em>
  </a>
 </p>
 <p>There are examples all over station of extended hatches and
  ladders, to reach infrastructure that keeps getting buried deeper below ground level.</p>
 <p>Here’s a work in progress at a location a bit farther out from station. A team has dug out a buried access hatch,
  and soon an extension will be added so that it sits at the new ground level. The infrastructure underground doesn’t
  change, but the access hatch requires constant maintenance.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/buried-access-hatch-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-access-hatch-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/buried-access-hatch-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/buried-access-hatch-01-small.jpg" alt="Buried Access Hatch 01">
    </picture>
    <em>An access hatch to an underground infrastructure vault, soon to be extended up to ground level.</em>
  </a>
 </p>
 <p>In the backyard, there are a number of strategies to deal with the accumulation of snow.</p>
 <p>Some buildings are built right at ground level. These will get slowly buried, unless work is done to engineer the
  snow around them. You can engineer away several feet of snow accumulation, and still make a building seem at “ground”
  level, just by introducing a gentle downward slope toward a building from the prevailing ground level.</p>
 <p>Here’s a few buildings that are not elevated. Yes, they collect snowdrifts. And yes, they’ll eventually have to be
  moved! But for now, the herculean effort to grade and engineer the topography of the backyard means they are still
  accessible at “ground” level.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/outbuildings-02.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/outbuildings-02-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/outbuildings-02-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/outbuildings-02-small.jpg" alt="Outbuildings 02">
    </picture>
    <em>A ground-level outbuilding, still accessible due to careful management of the surrounding topography.</em>
  </a>
 </p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/outbuildings-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/outbuildings-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/outbuildings-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/outbuildings-01-small.jpg" alt="Outbuildings 01">
    </picture>
    <em>Another ground-level outbuilding. Note the snowdrifts!</em>
  </a>
 </p>
 <p>Speaking of snowdrifts, they are relentless! They will pile up against anything facing the wind. Here’s one
  ground-level outbuilding with some drifts up against it:</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/outbuilding-snow-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/outbuilding-snow-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/outbuilding-snow-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/outbuilding-snow-01-small.jpg" alt="Outbuilding Snow 01">
    </picture>
    <em>An outbuilding with fresh, un-shoveled snowdrifts against it.</em>
  </a>
 </p>
 <p>There is also a lot of ground-level storage. Here’s a typical storage aisle:</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/storage-aisle-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/storage-aisle-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/storage-aisle-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/storage-aisle-01-small.jpg" alt="Storage Aisle 01">
    </picture>
    <em>Storage aisle. Note the relentless drifting snow! Also visible is a temporary pile of snow, plowed out of the
      way so this storage can be accessed.</em>
  </a>
 </p>
 <p>Other buildings are designed to be resilient to some amount of snow accumulation. Just like the main Elevated Station,
  here’s a building that is elevated above ground, so it can more gracefully tolerate a shift in
  ground level.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/elevated-outbuilding-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-outbuilding-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-outbuilding-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/elevated-outbuilding-01-small.jpg" alt="Elevated Outbuilding 01">
    </picture>
    <em>An outbuilding in our RF sector, housing information technology equipment. Elevated above ground,
      so we can tolerate shifts in snow cover without compromising access to the building.</em>
  </a>
 </p>
 <p>We also make use of elevated storage! Here’s a series of elevated storage platforms. This is more complex and
  more expensive than just putting stuff on the ground, but it means we’ll be able to access it for years to come
  without having to dig it out.</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/elevated-storage-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-storage-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/elevated-storage-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/elevated-storage-01-small.jpg" alt="Elevated Storage 01">
    </picture>
    <em>Elevated storage. This is a common tactic for long-term storage, to avoid stuff getting buried.</em>
  </a>
 </p>
 <p>On a lighter note, one benefit of our massive snow hauling operation is that we can occasionally indulge in a bit of
  fun. Here’s the South Pole Sledding Hill, lovingly maintained by station staff. There’s plenty of snow to go around!</p>
 <p>
  <a href="https://brr.fyi/media/south-pole-topography/sledding-hill-01.jpg">
    <picture>
      <source srcset="https://brr.fyi/media/south-pole-topography/sledding-hill-01-small.webp" type="image/webp"></source>
      <source srcset="https://brr.fyi/media/south-pole-topography/sledding-hill-01-small.jpg" type="image/jpg"></source>
      <img src="https://brr.fyi/media/south-pole-topography/sledding-hill-01-small.jpg" alt="Sledding Hill 01">
    </picture>
  </a>
 </p>
 <p>It’s neat to see the layered history of the South Pole. You can
  roughly gauge the age of infrastructure by how deeply buried it is!</p>
 <p>Walking from the Elevated Station down to the
  Arches is a fun journey into the past.</p>
 <p>Climbing down an access hatch, extended multiple times to keep up with
  the relentless snow, is a good day-to-day reminder of the forces of nature at work here.</p>
 <p>I hope others find this as interesting as I do.</p>
 <p>Until next time!</p>
--- a/cache/2023/index.html
+++ b/cache/2023/index.html
@@ -77,12 +77,16 @@
      
        <li><a href="/david/cache/2022/a889fa6d4e07bdc390d44461ed6dce21/" title="Accès à l’article dans le cache local : Getting Takahē to run on Piku">Getting Takahē to run on Piku</a> (<a href="https://taoofmac.com/space/blog/2022/12/21/0900" title="Accès à l’article original distant : Getting Takahē to run on Piku">original</a>)</li>
      
        <li><a href="/david/cache/2022/f8b7c3246cf1d4e06c735ee163be32a0/" title="Accès à l’article dans le cache local : The Content Management System of my Dreams (part 2) - The trouble with dynamic publishing">The Content Management System of my Dreams (part 2) - The trouble with dynamic publishing</a> (<a href="https://www.padawan.info/en/2023/02/the-content-management-system-of-my-dreams-part-2-the-trouble-with-dynamic-publishing.html" title="Accès à l’article original distant : The Content Management System of my Dreams (part 2) - The trouble with dynamic publishing">original</a>)</li>
      
        <li><a href="/david/cache/2022/c45d25b1d1062fcf10fbf7caaf9e21b1/" title="Accès à l’article dans le cache local : Exercices (de feuille) de styles">Exercices (de feuille) de styles</a> (<a href="https://blog.professeurjoachim.com/billet/2023-01-05-exercices-de-feuille-de-styles" title="Accès à l’article original distant : Exercices (de feuille) de styles">original</a>)</li>
      
        <li><a href="/david/cache/2022/1ae1896e5eb2ccc03f2295f38090048e/" title="Accès à l’article dans le cache local : Être jeune et vivre une pandémie">Être jeune et vivre une pandémie</a> (<a href="https://cremis.ca/publications/articles-et-medias/etre-jeune-et-vivre-une-pandemie/" title="Accès à l’article original distant : Être jeune et vivre une pandémie">original</a>)</li>
      
        <li><a href="/david/cache/2022/9caf3cf36d339cfffad8582583493204/" title="Accès à l’article dans le cache local : How Blogging Changes The Way You Think">How Blogging Changes The Way You Think</a> (<a href="https://clivethompson.medium.com/how-blogging-changes-the-way-you-think-526734dc86d1" title="Accès à l’article original distant : How Blogging Changes The Way You Think">original</a>)</li>
      
        <li><a href="/david/cache/2022/65169d7164c8bf5790a224d45a95adb7/" title="Accès à l’article dans le cache local : The Content Management System of my Dreams (part 1) - A little bit of history">The Content Management System of my Dreams (part 1) - A little bit of history</a> (<a href="https://www.padawan.info/en/2023/02/the-content-management-system-of-my-dreams-part-1-a-little-bit-of-history.html" title="Accès à l’article original distant : The Content Management System of my Dreams (part 1) - A little bit of history">original</a>)</li>
      
        <li><a href="/david/cache/2022/1676902071b6e1e7e0d3395bc47956b5/" title="Accès à l’article dans le cache local : Adding ActivityPub to your static site">Adding ActivityPub to your static site</a> (<a href="https://paul.kinlan.me/adding-activity-pub-to-your-static-site/" title="Accès à l’article original distant : Adding ActivityPub to your static site">original</a>)</li>
      
        <li><a href="/david/cache/2022/ee7eb9c245d1b2c4b91b8dda4cd7d318/" title="Accès à l’article dans le cache local : Benjamin Hennot : Interview">Benjamin Hennot : Interview</a> (<a href="https://www.rayonvertcinema.org/benjamin-hennot-interview/" title="Accès à l’article original distant : Benjamin Hennot : Interview">original</a>)</li>
@@ -181,6 +185,8 @@
      
        <li><a href="/david/cache/2022/3cffe9d9946878273e050e9d35d9bf9e/" title="Accès à l’article dans le cache local : Exploratrices, un prototype de jeu vidéo">Exploratrices, un prototype de jeu vidéo</a> (<a href="https://marienfressinaud.fr/exploratrices.html" title="Accès à l’article original distant : Exploratrices, un prototype de jeu vidéo">original</a>)</li>
      
        <li><a href="/david/cache/2022/f9e282fb545b5c1f50dfa1c0d98c50e3/" title="Accès à l’article dans le cache local : South Pole Topography">South Pole Topography</a> (<a href="https://brr.fyi/posts/south-pole-topography" title="Accès à l’article original distant : South Pole Topography">original</a>)</li>
      
        <li><a href="/david/cache/2022/a0ccec7acb932e4155960c1c88d65eff/" title="Accès à l’article dans le cache local : La mission de Deuxfleurs">La mission de Deuxfleurs</a> (<a href="https://plume.deuxfleurs.fr/~/Deuxfleurs/La%20mission%20de%20Deuxfleurs" title="Accès à l’article original distant : La mission de Deuxfleurs">original</a>)</li>
      
        <li><a href="/david/cache/2022/ae079737f65e55da1d7a672b3a685b46/" title="Accès à l’article dans le cache local : Tolerance for boredom">Tolerance for boredom</a> (<a href="https://aworkinglibrary.com/writing/tolerance-for-boredom" title="Accès à l’article original distant : Tolerance for boredom">original</a>)</li>