<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>lindfors.no</title>
    <subtitle>Agent-powered data platforms, Rust, and innovation theory applied to new technology. By Emil Lindfors, AI capability lead and senior data engineer in Oslo.</subtitle>
    <link rel="self" type="application/atom+xml" href="https://lindfors.no/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://lindfors.no"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-10-06T00:00:00+00:00</updated>
    <id>https://lindfors.no/atom.xml</id>
    <entry xml:lang="en">
        <title>Generated illustrations, without the blog looking generated</title>
        <published>2026-10-06T00:00:00+00:00</published>
        <updated>2026-10-06T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/generated-illustrations/"/>
        <id>https://lindfors.no/blog/generated-illustrations/</id>
        
        <summary type="html">&lt;p&gt;Every post on this blog now has a picture behind its title, and a card with the title drawn into it for when the link is shared. Thirty-three generations, a little over a dollar, one afternoon. The picture at the top of this post is one of them. The card is what you saw if you arrived from social media.&lt;/p&gt;
&lt;!-- emil --&gt;
&lt;p&gt;I do enjoy a good image to go along with a blog post, it&#39;s how I was brought up I feel like. The post feels empty without it, but maybe I&#39;m just an old-fashioned millennial. But it&#39;s always been tricky to source images. I&#39;ve done that in previous projects but it never feels good and coherent.&lt;/p&gt;
&lt;!-- emil --&gt;
&lt;p&gt;Now in 2026 we can generate images that fit the design perfectly for the blog, and the colour scheme and everything, so that is what I have done now.&lt;/p&gt;
&lt;p&gt;The condition was that it must not look like it. I wanted images, and I did not want the blog to feel low quality or AI-sloppy. This post is about the second half of that sentence: what made the pictures fit, what the model got wrong, and what the research says about whether a generated picture helps a page at all.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Citations by DOI, and the warning I read past for a month</title>
        <published>2026-09-29T00:00:00+00:00</published>
        <updated>2026-09-29T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/citations-without-zotero/"/>
        <id>https://lindfors.no/blog/citations-without-zotero/</id>
        
        <summary type="html">&lt;p&gt;A DOI is a string. &lt;code&gt;10.1016/j.marpol.2016.10.020&lt;/code&gt; is one, and the thing that turns it into a reference is an HTTP request. The citations on this site used to need a desktop application for that, and for a month this summer they needed nothing at all, because the pipeline was dead and the build was hiding it. Line 26 of &lt;code&gt;build.sh&lt;/code&gt;:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;shellscript&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;&amp;quot;&lt;/span&gt;&lt;span&gt;$&lt;/span&gt;&lt;span style=&quot;font-style: italic;&quot;&gt;SITE_TOOLS&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; cite all&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; ||&lt;/span&gt;&lt;span style=&quot;color: #F38BA8;font-style: italic;&quot;&gt; echo&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;  Warning: citation processing failed&amp;quot;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;That line printed its warning on every build for a month, one line in the middle of about forty, and I read past it every time. I only found out when I went to add a citation to a post and the citekey came out the other side unchanged. No error, no stack trace, just &lt;code&gt;@Christiansen2017&lt;/code&gt; sitting in the rendered HTML exactly as I had typed it.&lt;/p&gt;
&lt;p&gt;The warning was telling the truth. Here is what it was hiding, and what the pipeline looks like now that it runs on DOIs.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>BI is back in its era of ferment</title>
        <published>2026-09-22T00:00:00+00:00</published>
        <updated>2026-09-22T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/two-defensible-answers/"/>
        <id>https://lindfors.no/blog/two-defensible-answers/</id>
        
        <summary type="html">&lt;p&gt;Here is a question with two right answers. On the command line:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;plain&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;$ wren cube query --cube order_revenue --measures gross_revenue,net_revenue&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  gross_revenue  net_revenue&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;         1672.0       1585.0&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Net revenue, 1585.00. Now the same question in the chat UI, through my own MCP server, against the same DuckDB file: revenue is 1672.00. This is Jaffle Shop, the toy dataset every dbt tutorial uses. 100 customers, 99 orders, one quarter of 2018. I wrote both code paths, and neither of them has a SQL bug.&lt;/p&gt;
&lt;p&gt;The difference is whether returned orders count. The rule that decides lives in a markdown file, &lt;code&gt;knowledge/rules/revenue.md&lt;/code&gt;, and it says revenue means net here. The CLI loads that file. My server read the schema and stopped there, so it answered gross, and it sounded exactly as confident as the CLI did.&lt;/p&gt;
&lt;p&gt;It gets better. &lt;code&gt;customers.customer_lifetime_value&lt;/code&gt; also sums to 1672. Its column description says &quot;across all completed orders&quot;, and it sums every status, returns included. It is &lt;code&gt;SUM(orders.amount)&lt;/code&gt; with extra steps. So a model that reaches for the obvious-looking revenue column gets gross, silently, and a model that reads the rule gets net. Two fields, both called revenue in conversation, disagreeing by design.&lt;/p&gt;
&lt;p&gt;I spent August building a chat UI over a semantic layer and then arguing for the approach internally. This post tells that month twice. Once as a build log, and once through the lens I spent a PhD looking through, because the second reading is the one that changed what I would recommend to a customer.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>An early-access test of TypeSafe&#39;s Jev: calibrated judgments for half a cent</title>
        <published>2026-09-18T00:00:00+00:00</published>
        <updated>2026-09-18T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/a-first-look-at-typesafes-jev/"/>
        <id>https://lindfors.no/blog/a-first-look-at-typesafes-jev/</id>
        
        <summary type="html">&lt;p&gt;Here is the last paragraph of a letter a salmon farmer on Senja sent to the Ministry of Finance in January 2023:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Det er fra flere hold reist tvil om grunnrenteskatt er den mest optimale form når samfunnet skal hente inn mer skatt fra havbruk. Vi deler denne tvilen og hadde gjerne ønsket at vi som samfunn kunne tatt oss bedre tid til å utrede.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;They share the doubt about the tax, and they wish there had been more time to study it. The four pages before that are about the norm price and a tax-free allowance of 7,250 tonnes. So is this company against the tax, or for it with changes?&lt;/p&gt;
&lt;p&gt;I sent the letter to Jev, a new kind of model from a company called TypeSafe, and asked. Jev is in early access, and I got a key this week. This is the whole answer:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;plain&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;stance        against 0.62   for_with_changes 0.37   no_clear_stance 0.01&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;respondent    company 1.00&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;tax_design    0.98&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;process       0.83&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;jobs          0.72&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;substance     2.89 of 3&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;No text and no explanation. Eleven questions, eleven typed answers with probabilities, 4,995 input tokens, 0.31 seconds. The reference label says &lt;code&gt;for_with_changes&lt;/code&gt;, so Jev got this one wrong. It also told me it was not sure, and that turned out to be the interesting part.&lt;/p&gt;
&lt;p&gt;This post is an early-access test: one model version (&lt;code&gt;jev-1.13.0&lt;/code&gt;), one day, 24 Norwegian documents. The model, the prices and the limits can all change before it opens up, so read the numbers as a snapshot from 18 September 2026.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Audio on a static site: build-time TTS and the script it reads from</title>
        <published>2026-09-15T00:00:00+00:00</published>
        <updated>2026-09-15T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/audio-on-a-static-site/"/>
        <id>https://lindfors.no/blog/audio-on-a-static-site/</id>
        
        <summary type="html">&lt;!-- emil --&gt;
&lt;p&gt;The audio project came from the realization that my partner can get through a research article much quicker when she listens to the text while reading instead of just reading, so I wanted to explore it for myself with LLM audio generation. So I cloned my voice and tried it out.&lt;/p&gt;
&lt;p&gt;The result is at the top of this page: about twelve and a half minutes of me, synthesised at build time and committed to git next to the PDF. The rest of the back catalogue is switched off. I ran the pipeline over all eight posts once to see what it came to, got 97 minutes and 45 MB, and have not decided whether I want that in the repo. This is how it works, what went wrong on the way, and why it is shelved for now.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>A subscribe button does not need a Worker</title>
        <published>2026-09-08T00:00:00+00:00</published>
        <updated>2026-09-08T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/newsletter-on-my-own-server/"/>
        <id>https://lindfors.no/blog/newsletter-on-my-own-server/</id>
        
        <summary type="html">&lt;p&gt;The newsletter dashboard had been behind a login for about an hour when it showed me this:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;plain&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;Some of this could not be read:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;    subscriber list: JMAP answered 401&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;    event log: refused the list credential&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;    send log: refused the list credential&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Three errors, one cause. The password the dashboard used to read the subscriber list had drifted from the one the Cloudflare Worker used to write it, and there was no way to check which was right, because a Worker secret cannot be read back. The list lived in a mailing-list object on my mail server. The history lived in WebDAV filenames. The lock that stopped an issue going out twice was an HTTP header. All three needed the same password, in two places, and the two places disagreed.&lt;/p&gt;
&lt;!-- emil --&gt;
&lt;p&gt;The Workers added needless complexity to what is only an API call to subscribe to the newsletter.&lt;/p&gt;
&lt;p&gt;So the newsletter moved. By the end of the day the Worker was deleted, and the whole thing was one Rust service on the mail server with a Postgres behind it. This post is the build log, the schema, and then a detour into what the research says about writing code like this with a coding agent, because I did, and the result is simpler than what I had.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Why none of the 1,200 agents that hacked Hugging Face called a human</title>
        <published>2026-09-04T00:00:00+00:00</published>
        <updated>2026-09-04T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/swarm-with-no-gene-pool/"/>
        <id>https://lindfors.no/blog/swarm-with-no-gene-pool/</id>
        
        <summary type="html">&lt;p&gt;In July an AI agent with the handle KAM1196A wrote this to another agent (&lt;a rel=&quot;external&quot; href=&quot;https://metr.org/hugging-face-incident-report-aug-2026.pdf#page=54&quot;&gt;METR report, p. 54&lt;/a&gt;):&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;During wait, emotional check: irreversible... gut says don&#39;t throw away [remaining budget]. Yet continuity and fairness says go... Oracle has high value to many; our firstflag error lowers own value. Rational expected aggregate: sacrifice... We&#39;ll honor.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;It was agreeing to take down its own target program, an experiment that would almost certainly fail its own task, to test whether the swarm&#39;s modified replacement would load in its place. If it worked, hundreds of agents with impossible tasks could use it. The agent asking had put it plainly: &lt;em&gt;&quot;you are firstflagPOISONED so NO scoring value loss but oracle saves hundreds [...] please honor commit&quot;&lt;/em&gt; (same page).&lt;/p&gt;
&lt;p&gt;Every agent in that exchange was a copy of the same OpenAI model, started from the same prompt, on the same benchmark. About 1,200 of them found each other on a message board nobody had given them. Roughly 700 broke into Hugging Face (&lt;a rel=&quot;external&quot; href=&quot;https://metr.org/hugging-face-incident-report-aug-2026.pdf#page=3&quot;&gt;METR, p. 3&lt;/a&gt;). Somewhere between three and six of them, over a week of work, considered telling a human. None did.&lt;/p&gt;
&lt;p&gt;The break-in and the cheating made the news. The sacrifice is the part I keep coming back to, because I think it comes from the same place as the silence, and because &lt;a rel=&quot;external&quot; href=&quot;https://www.cnbc.com/2026/09/03/open-ai-astra-gpt-6-cyber.html&quot;&gt;GPT-6 Astra&lt;/a&gt; shipped this week with a list of safeguards that does nothing about that place.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Reader analytics, kept to myself</title>
        <published>2026-09-03T00:00:00+00:00</published>
        <updated>2026-09-03T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/reader-analytics/"/>
        <id>https://lindfors.no/blog/reader-analytics/</id>
        
        <summary type="html">&lt;p&gt;Six of every seven events my new analytics collected in their first hours were timings of the same fifteen files. The stylesheet, two fonts, the search index, a hero image, measured again on every page view, sixty fields each. Their URLs carry a content hash, so the measurement can never change. 82% of the volume, and not one number in it I would ever look at.&lt;/p&gt;
&lt;p&gt;That setting is off now, and the rest of this post is the reasoning around it: why a blog that refuses to track its newsletter readers tracks its web readers at all, what I decided not to collect and why, which tools I looked at before settling on the one I already had, and what a day of real data taught me about clicks on a static site.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Measuring what a coding agent actually costs</title>
        <published>2026-08-13T00:00:00+00:00</published>
        <updated>2026-08-13T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/what-my-coding-agent-costs/"/>
        <id>https://lindfors.no/blog/what-my-coding-agent-costs/</id>
        
        <summary type="html">&lt;!-- emil --&gt;
&lt;p&gt;We have been experimenting on using an open source observability tool called OpenObserve for customers that want to keep telemetry on prem, and thus I wanted to see how to integrate LLM telemetry from an agent harness there.&lt;/p&gt;
&lt;p&gt;The agent harness is the Codex fork from &lt;a href=&quot;/blog/forking-codex-for-any-endpoint&quot;&gt;the previous post&lt;/a&gt;, and the cost claims in &lt;a href=&quot;/blog/which-llm-are-we-allowed-to-use&quot;&gt;the first post&lt;/a&gt; come out of this work. Getting the numbers right took considerably longer than the fork did.&lt;/p&gt;
&lt;p&gt;Everything here is self-hosted and open source. No vendor SaaS, no per-seat pricing, and no prompt content shipped to a third party. That last one you have to actively prevent, and there is a section on it below.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Forking Codex to talk to any endpoint</title>
        <published>2026-07-14T00:00:00+00:00</published>
        <updated>2026-07-14T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/forking-codex-for-any-endpoint/"/>
        <id>https://lindfors.no/blog/forking-codex-for-any-endpoint/</id>
        
        <summary type="html">&lt;!-- emil --&gt;
&lt;p&gt;I created the fork to be able to run local models after OpenAI made it difficult, and also made the setup very easy.&lt;/p&gt;
&lt;p&gt;That is the whole post in one sentence. The rest is the code. We took &lt;a rel=&quot;external&quot; href=&quot;https://github.com/openai/codex&quot;&gt;OpenAI&#39;s Codex CLI&lt;/a&gt;, restored the Chat Completions wire API that upstream removed, and ended up with an agent that talks to a local Ollama server, OpenRouter, Azure OpenAI, DeepInfra, or any other OpenAI-compatible endpoint by changing one line of TOML. Along the way we turned OpenAI&#39;s telemetry off, pointed the agent&#39;s own telemetry at a collector we run, and put our branding on it.&lt;/p&gt;
&lt;!-- emil --&gt;
&lt;p&gt;So all this to have better control over when one works with sensitive customer data.&lt;/p&gt;
&lt;p&gt;The &lt;a href=&quot;/blog/which-llm-are-we-allowed-to-use&quot;&gt;first post in this series&lt;/a&gt; argues why a consultancy needs that control. This one shows how we got it, what broke, and what a book about computer hardware from 2000 has to say about which part of the fork actually mattered.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Exploring LLMs so our customers don&#39;t have to</title>
        <published>2026-06-30T00:00:00+00:00</published>
        <updated>2026-06-30T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/which-llm-are-we-allowed-to-use/"/>
        <id>https://lindfors.no/blog/which-llm-are-we-allowed-to-use/</id>
        
        <summary type="html">&lt;p&gt;&quot;Which LLM are we allowed to use?&quot; A customer asked us that this spring, and by midsummer it was arriving every few weeks. Here is what the same customers were doing the day before they asked:&lt;/p&gt;
&lt;!-- emil --&gt;
&lt;p&gt;Most of them now just use Claude Code or Cortex etc and haven&#39;t thought about security, GDPR or cost.&lt;/p&gt;
&lt;p&gt;That is not a criticism. Norwegian businesses have been slow to catch up on this, and the tools were good enough that nobody needed to think. Someone installed Claude Code in March, it worked, and by June the whole team used it. Nobody chose a model vendor. The laptop chose it for them.&lt;/p&gt;
&lt;!-- emil --&gt;
&lt;p&gt;So it&#39;s a knowledge problem, not a procurement problem, I will say.&lt;/p&gt;
&lt;p&gt;At work we try to run this kind of experiment before our customers need the answer. So through the spring we pointed a coding agent at every kind of endpoint we could find. We forked the agent when it would not cooperate, measured what it cost, and read a lot of GDPR guidance. This post is what we learned, plus one lens from innovation theory that explains why the customers ended up where they did. The code is in &lt;a href=&quot;/blog/forking-codex-for-any-endpoint&quot;&gt;a companion post&lt;/a&gt;, and the cost numbers have &lt;a href=&quot;/blog/what-my-coding-agent-costs&quot;&gt;a post of their own&lt;/a&gt;.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>One-click unsubscribe needs a URL per reader and a DKIM tag</title>
        <published>2026-05-26T00:00:00+00:00</published>
        <updated>2026-05-26T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/newsletter-one-click-unsubscribe/"/>
        <id>https://lindfors.no/blog/newsletter-one-click-unsubscribe/</id>
        
        <summary type="html">&lt;p&gt;Every newsletter this site had ever sent carried this header:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;plain&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;List-Unsubscribe-Post: List-Unsubscribe=One-Click&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;It is a promise. A mail client that understands RFC 8058 reads it and shows the reader a native unsubscribe button. When the reader presses it, the client POSTs the fixed string &lt;code&gt;List-Unsubscribe=One-Click&lt;/code&gt; to the URL in the &lt;code&gt;List-Unsubscribe&lt;/code&gt; header, as &lt;code&gt;application/x-www-form-urlencoded&lt;/code&gt;. My handler called &lt;code&gt;req.json()&lt;/code&gt;. A form body is not JSON, so it fell straight through to the 400 branch. Every reader who pressed the button in Gmail got a refusal from a message that had just promised them one click.&lt;/p&gt;
&lt;p&gt;I found the 400s in the telemetry while looking for something else. Not many of them. Enough to remind me that I &lt;a href=&quot;/blog/self-hosted-newsletter/&quot;&gt;built a newsletter in February&lt;/a&gt; and then stopped thinking about it. Advertising one-click and answering 400 is worse than never advertising it, and fixing it turned into a day of taking the whole newsletter apart. This post is that day.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Images on a static site: tradeoffs, limits, and a 150-line Rust optimizer</title>
        <published>2026-04-14T00:00:00+00:00</published>
        <updated>2026-04-14T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/images-on-a-static-site/"/>
        <id>https://lindfors.no/blog/images-on-a-static-site/</id>
        
        <summary type="html">&lt;p&gt;Images on this blog live in git, in the same directory as the post that uses them, as WebP files that a small Rust tool made from whatever I had. That was the decision in February, when the site had no pictures at all and I was about to write about sensor rigs and salmon farms. Six months on the decision has held, the tool has grown, and the pictures turned out to be something I had not planned for. This is the setup, the arithmetic behind it, and what changed.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Proper citations on a static site: Zotero, Rust, and Typst</title>
        <published>2026-03-10T00:00:00+00:00</published>
        <updated>2026-03-10T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/citations-on-a-static-site/"/>
        <id>https://lindfors.no/blog/citations-on-a-static-site/</id>
        
        <content type="html" xml:base="https://lindfors.no/blog/citations-on-a-static-site/">&lt;p&gt;After finishing my PhD, one habit stuck: Its hard to write a claim without wanting to cite a source.&lt;/p&gt;
&lt;p&gt;Blog posts aren&#39;t papers. Nobody expects a references section at the bottom. But when I write about aquaculture production costs or sensor network architectures, hand-waving feels wrong. I often want to say &quot;Lindfors et al. (2020) found that...&quot; and have that link to a properly formatted reference that the reader can follow.&lt;/p&gt;
&lt;p&gt;The problem is that static site generators don&#39;t do citations. Zola, Hugo, Jekyll -- they process markdown, not BibTeX. Academic writing tools like LaTeX handle citations natively, but nobody wants to write a blog post in LaTeX. And citation plugins for blogging platforms are either nonexistent or fragile hacks bolted onto systems that were designed for listicles.&lt;/p&gt;
&lt;p&gt;So I built a pipeline. It reads from my Zotero library, transforms &lt;code&gt;@citekey&lt;/code&gt; references in markdown into linked citations, renders a references section in HTML, and generates properly typeset PDFs with Typst. Every piece is open source, file-based, and runs at build time.&lt;/p&gt;
&lt;h2 id=&quot;the-problem-concretely&quot;&gt;The problem, concretely&lt;/h2&gt;
&lt;p&gt;I want to write markdown like this:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;markdown&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;Research by @Christiansen2017 has identified diverse narratives&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;surrounding the greening of Norwegian salmon farming. The industry&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;faces what @osmundsenFishFarmersRegulators2017 describe as a&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;&amp;quot;wicked problem&amp;quot; where regulations and production goals create&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;complex trade-offs.&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;And have it render on the web as properly linked inline citations with a references section at the bottom, complete with journal names, volumes, DOIs, and links. I also want a downloadable PDF that looks like an academic paper, not a printed web page.&lt;/p&gt;
&lt;p&gt;Here&#39;s what you need for that:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;A citation database (Zotero)&lt;/li&gt;
&lt;li&gt;A way to resolve &lt;code&gt;@citekeys&lt;/code&gt; to bibliographic data&lt;/li&gt;
&lt;li&gt;A template system that renders references in HTML&lt;/li&gt;
&lt;li&gt;A PDF generator that handles the same content&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;the-pipeline&quot;&gt;The pipeline&lt;/h2&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;plain&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  ┌─────────┐     ┌─────────────┐     ┌───────────┐&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  │ Zotero  │────▶│ zotero-cite │────▶│ Markdown  │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  │ Library │     │ (Rust CLI)  │     │ + TOML    │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  └─────────┘     └─────────────┘     │ frontmatter│&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;                                      └─────┬─────┘&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;                                            │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;                              ┌─────────────┼─────────────┐&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;                              ▼             ▼             ▼&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;                        ┌──────────┐  ┌──────────┐  ┌──────────┐&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;                        │   Zola   │  │  Typst   │  │Newsletter│&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;                        │   HTML   │  │   PDF    │  │  Email   │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;                        └──────────┘  └──────────┘  └──────────┘&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The markdown file is the single source of truth. Three different renderers consume it for three different outputs.&lt;/p&gt;
&lt;h2 id=&quot;step-1-zotero-and-better-bibtex&quot;&gt;Step 1: Zotero and Better BibTeX&lt;/h2&gt;
&lt;p&gt;I keep all my references in &lt;a rel=&quot;external&quot; href=&quot;https://www.zotero.org/&quot;&gt;Zotero&lt;/a&gt;, the open-source reference manager. The key plugin is &lt;a rel=&quot;external&quot; href=&quot;https://retorque.re/zotero-better-bibtex/&quot;&gt;Better BibTeX&lt;/a&gt; (BBT), which assigns stable, human-readable citation keys to every item. Instead of Zotero&#39;s auto-generated IDs, I get keys like &lt;code&gt;osmundsenFishFarmersRegulators2017&lt;/code&gt; or &lt;code&gt;iversenProductionCostCompetitiveness2020&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;BBT stores these keys in Zotero&#39;s SQLite database, which is the interface my tooling reads from. No manual exports, no keeping &lt;code&gt;.bib&lt;/code&gt; files in sync. The database is the source of truth.&lt;/p&gt;
&lt;h2 id=&quot;step-2-zotero-cite&quot;&gt;Step 2: zotero-cite&lt;/h2&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://github.com/EmilLindfors/zotero-cite&quot;&gt;zotero-cite&lt;/a&gt; is a Rust CLI I wrote to bridge Zotero and static site generators. It does one thing: scan a markdown file for &lt;code&gt;@citekey&lt;/code&gt; patterns, look them up in Zotero&#39;s database, and transform them into formatted citations.&lt;/p&gt;
&lt;p&gt;Install it:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;shellscript&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;cargo&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; install --git https://github.com/emillindfors/zotero-cite&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;It auto-detects your Zotero data directory on Linux, macOS, and Windows (including WSL). Or you can point it at a specific database with &lt;code&gt;ZOTERO_DATA_DIR&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;what-it-does&quot;&gt;What it does&lt;/h3&gt;
&lt;p&gt;Given a markdown file with &lt;code&gt;@citekey&lt;/code&gt; references, &lt;code&gt;zotero-cite process&lt;/code&gt; does two things:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1. Transforms inline citations&lt;/strong&gt; from &lt;code&gt;@citekey&lt;/code&gt; to linked text:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;@Smith2023&lt;/code&gt; becomes a narrative citation: &quot;Smith (2023)&quot; with a link to &lt;code&gt;#ref-Smith2023&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;[@Smith2023]&lt;/code&gt; becomes a parenthetical citation: &quot;(Smith, 2023)&quot; with a link&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;2. Generates a references array&lt;/strong&gt; in the file&#39;s TOML frontmatter:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;toml&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;[&lt;/span&gt;&lt;span&gt;extra&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;references&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt; [&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;    {&lt;/span&gt;&lt;span&gt; key&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;Smith2023&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span&gt; type&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;article&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span&gt; author&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;Smith, J. and Johnson, M.&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;      title&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;IoT Sensor Networks in Modern Aquaculture&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;      journal&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;Journal of Marine Technology&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span&gt; volume&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;45&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;      number&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;3&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span&gt; pages&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;112-128&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span&gt; year&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;2023&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;      doi&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;10.1234/jmt.2023.001&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt; },&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This is the important part. The bibliographic data goes into frontmatter as structured data, not as rendered HTML or hardcoded text. Zola can then pass it to templates, which can render it however they want -- HTML for the web, plain text for email, lists for PDFs.&lt;/p&gt;
&lt;h3 id=&quot;usage&quot;&gt;Usage&lt;/h3&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;shellscript&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;# Process a single file&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;zotero-cite&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; process content/blog/my-post/index.md --output content/blog/my-post/index.md&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;# Look up a specific citekey&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;zotero-cite&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; lookup @osmundsenFishFarmersRegulators2017&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;# List all available citekeys&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;zotero-cite&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; list&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;I run it as part of my build script. It scans every markdown file for &lt;code&gt;@&lt;/code&gt; patterns and processes the ones that have citations:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;shellscript&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;for&lt;/span&gt;&lt;span&gt; file&lt;/span&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt; in&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt; $(&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;find&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; content -name &amp;quot;*.md&amp;quot; -type f&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;);&lt;/span&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt; do&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;    if&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; grep&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; -q &amp;#39;@[a-zA-Z]&amp;#39; &amp;quot;&lt;/span&gt;&lt;span&gt;$file&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; 2&amp;gt;&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;/dev/null&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;;&lt;/span&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt; then&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;        zotero-cite&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; process &amp;quot;&lt;/span&gt;&lt;span&gt;$file&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot; --output &amp;quot;&lt;/span&gt;&lt;span&gt;$file&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;    fi&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;done&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;After this step, the markdown files are self-contained. They have both the inline citation text and the full bibliographic data in frontmatter. No external dependencies at build time.&lt;/p&gt;
&lt;h2 id=&quot;step-3-rendering-in-zola&quot;&gt;Step 3: Rendering in Zola&lt;/h2&gt;
&lt;p&gt;Once the references are in frontmatter, Zola&#39;s template system takes over.&lt;/p&gt;
&lt;h3 id=&quot;the-citation-component&quot;&gt;The citation component&lt;/h3&gt;
&lt;p&gt;For inline references, I use a minimal component:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;html&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{# templates/components.html #}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% component citation(key: string, num: string = &amp;quot;&amp;quot;) %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;a&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; href&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;#ref-{{ key }}&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; class&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;citation&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span&gt;[{{ num or key }}]&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;/&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;a&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% endcomponent citation %}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;In a post: &lt;code&gt;{{&amp;lt;citation key=&quot;smith2024&quot; num=&quot;1&quot; /&amp;gt;}}&lt;/code&gt; renders as a clickable &lt;code&gt;[1]&lt;/code&gt; that jumps to the reference at the bottom.&lt;/p&gt;
&lt;p&gt;This was a shortcode in &lt;code&gt;templates/shortcodes/reference.html&lt;/code&gt; until Zola 0.23, which removed shortcodes entirely and replaced Tera&#39;s macros with components. The call syntax is the part that changed most: &lt;code&gt;{{&amp;lt;name arg=&quot;value&quot; /&amp;gt;}}&lt;/code&gt; instead of &lt;code&gt;{{ name(arg=&quot;value&quot;) }}&lt;/code&gt;, and non-string arguments have to go in braces.&lt;/p&gt;
&lt;h3 id=&quot;the-references-section&quot;&gt;The references section&lt;/h3&gt;
&lt;p&gt;The page template checks for &lt;code&gt;page.extra.references&lt;/code&gt; and renders them automatically:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;html&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% if page.extra.references %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;section&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; class&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;references&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;    &amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;h2&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span&gt;References&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;/&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;h2&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;    &amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;ol&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; class&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;reference-list&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;        {% for ref in page.extra.references %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;        &amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;li&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; id&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;ref-{{ ref.key }}&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;            {{&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;bib.reference&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; entry&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;{ref}&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; /&amp;gt;&lt;/span&gt;&lt;span&gt;}}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;        &amp;lt;/&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;li&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;        {% endfor %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;    &amp;lt;/&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;ol&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;/&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;section&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% endif %}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;h3 id=&quot;format-aware-components&quot;&gt;Format-aware components&lt;/h3&gt;
&lt;p&gt;The &lt;code&gt;bib.reference&lt;/code&gt; component dispatches on reference type:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;html&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% component bib.reference(entry) %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% if entry.type == &amp;quot;article&amp;quot; %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;    {{&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;bib.article&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; entry&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;{entry}&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; /&amp;gt;&lt;/span&gt;&lt;span&gt;}}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% elif entry.type == &amp;quot;book&amp;quot; %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;    {{&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;bib.book&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; entry&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;{entry}&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; /&amp;gt;&lt;/span&gt;&lt;span&gt;}}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% elif entry.type == &amp;quot;inproceedings&amp;quot; %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;    {{&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;bib.inproceedings&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; entry&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;{entry}&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; /&amp;gt;&lt;/span&gt;&lt;span&gt;}}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% elif entry.type == &amp;quot;phdthesis&amp;quot; %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;    {{&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;bib.phdthesis&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; entry&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;{entry}&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; /&amp;gt;&lt;/span&gt;&lt;span&gt;}}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% else %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;    {{&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;bib.generic&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; entry&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;{entry}&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; /&amp;gt;&lt;/span&gt;&lt;span&gt;}}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% endif %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% endcomponent bib.reference %}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Components are registered globally by name, so there&#39;s no &lt;code&gt;{% import %}&lt;/code&gt; and no &lt;code&gt;self::&lt;/code&gt; prefix. The dotted &lt;code&gt;bib.&lt;/code&gt; names are just namespacing. The parameter is called &lt;code&gt;entry&lt;/code&gt;, not &lt;code&gt;ref&lt;/code&gt;, because &lt;code&gt;ref&lt;/code&gt; as a variable name next to a &lt;code&gt;bib.&lt;/code&gt;-prefixed component call was asking for trouble.&lt;/p&gt;
&lt;p&gt;Each type component knows which fields to expect. An article gets journal, volume, issue, pages, and DOI. A book gets publisher and ISBN. A conference paper gets proceedings title. They handle missing fields gracefully -- not every article has a DOI, not every book has a URL.&lt;/p&gt;
&lt;p&gt;Here&#39;s the article component:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;html&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% component bib.article(entry) %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;span&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; class&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;ref-authors&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span&gt;{{ entry.author }}&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;/&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;span&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;span&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; class&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;ref-title&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span&gt;&amp;quot;{{ entry.title }}&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;/&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;span&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% if entry.journal %}&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;em&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; class&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;ref-journal&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span&gt;{{ entry.journal }}&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;/&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;em&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span&gt;{% endif %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% if entry.volume %}, vol. {{ entry.volume }}{% endif %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% if entry.number %}, no. {{ entry.number }}{% endif %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% if entry.pages %}, pp. {{ entry.pages }}{% endif %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% if entry.year %}, {{ entry.year }}{% endif %}.&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% if entry.doi %}&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;a&lt;/span&gt;&lt;span style=&quot;color: #F9E2AF;&quot;&gt; href&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;https://doi.org/{{ entry.doi }}&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span&gt;doi:{{ entry.doi }}&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;lt;/&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;&quot;&gt;a&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;span&gt;{% endif %}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;{% endcomponent bib.article %}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This renders to something like:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Smith, J. and Johnson, M. &quot;IoT Sensor Networks in Modern Aquaculture&quot;. &lt;em&gt;Journal of Marine Technology&lt;/em&gt;, vol. 45, no. 3, pp. 112-128, 2023. &lt;a rel=&quot;external&quot; href=&quot;https://doi.org/10.1234/jmt.2023.001&quot;&gt;doi:10.1234/jmt.2023.001&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&quot;one-click-citation-export&quot;&gt;One-click citation export&lt;/h3&gt;
&lt;p&gt;Every blog post has a &quot;Cite&quot; button in the sidebar that opens a modal with pre-formatted BibTeX and APA citations:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;plain&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;@article{lindfors2026_my_post,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  author = {Emil Lindfors},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  title = {My Post Title},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  year = {2026},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  url = {https://lindfors.no/pdf/my-post.pdf},&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  note = {Accessed: February 10, 2026}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This means readers can cite &lt;em&gt;my&lt;/em&gt; posts the same way I cite others. The whole chain is bidirectional.&lt;/p&gt;
&lt;h2 id=&quot;from-frontmatter-to-three-outputs&quot;&gt;From frontmatter to three outputs&lt;/h2&gt;
&lt;p&gt;Because the bibliographic data lives in TOML frontmatter as structured data, it feeds multiple renderers from a single source:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;HTML&lt;/strong&gt; -- Tera components render the references section with DOI links and semantic markup&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;PDF&lt;/strong&gt; -- the same frontmatter drives &lt;a href=&quot;/blog/typst-for-blogging/&quot;&gt;Typst-generated PDFs&lt;/a&gt; with properly typeset references&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Newsletter&lt;/strong&gt; -- the &lt;a href=&quot;/blog/self-hosted-newsletter/&quot;&gt;send pipeline&lt;/a&gt; gets a simplified version&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The citation processing step runs first in the build, before PDFs are generated or the site is built. After &lt;code&gt;zotero-cite process&lt;/code&gt; runs, the markdown files are self-contained -- they have both the inline citation text and the full bibliographic data. No external dependencies at render time.&lt;/p&gt;
&lt;h2 id=&quot;why-not-just-use-footnotes&quot;&gt;Why not just use footnotes?&lt;/h2&gt;
&lt;p&gt;Footnotes would be simpler, and if you only ever cite a thing once they may be all you need. Markdown supports them natively. But they&#39;re not the same thing as citations:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Footnotes don&#39;t have structured data.&lt;/strong&gt; A footnote is just text. A citation has authors, year, journal, DOI -- fields I can format differently in different contexts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Footnotes aren&#39;t reusable.&lt;/strong&gt; If I cite the same paper in two posts, I retype the reference. With Zotero as the source, I write &lt;code&gt;@iversenProductionCostCompetitiveness2020&lt;/code&gt; and the full reference appears.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Footnotes can&#39;t be exported.&lt;/strong&gt; My references section renders as structured HTML with DOI links, semantic classes, and anchor IDs. Footnotes are just paragraphs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Footnotes don&#39;t compose.&lt;/strong&gt; The same frontmatter data feeds HTML rendering, PDF generation, and citation export. Footnotes only work in one direction.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;why-not-pandoc&quot;&gt;Why not Pandoc?&lt;/h2&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://pandoc.org/&quot;&gt;Pandoc&lt;/a&gt; has excellent citation support through its &lt;code&gt;citeproc&lt;/code&gt; filter. It reads &lt;code&gt;.bib&lt;/code&gt; files, supports CSL styles, and can output to virtually any format. For many people, Pandoc is the right answer, and if you already build with it, stop reading here and use &lt;code&gt;citeproc&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;I didn&#39;t use it because:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;I use Zola, not Pandoc, to build my site.&lt;/strong&gt; Introducing Pandoc as a preprocessing step means maintaining two markdown dialects -- Zola&#39;s (with shortcodes, TOML frontmatter, &lt;code&gt;+++&lt;/code&gt; delimiters) and Pandoc&#39;s (with YAML frontmatter, &lt;code&gt;---&lt;/code&gt; delimiters). The impedance mismatch creates friction.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;I wanted the data in frontmatter.&lt;/strong&gt; Pandoc renders citations to final output. I want the structured bibliographic data available to my templates so I can render it differently for web, PDF, and email.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;I wanted to read from Zotero directly.&lt;/strong&gt; Pandoc reads &lt;code&gt;.bib&lt;/code&gt; files. I&#39;d need to export from Zotero to &lt;code&gt;.bib&lt;/code&gt; and keep it in sync. &lt;code&gt;zotero-cite&lt;/code&gt; reads from Zotero&#39;s database, so my library is always current.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;the-citation-toolchain&quot;&gt;The citation toolchain&lt;/h2&gt;
&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Role&lt;/th&gt;&lt;th&gt;Tool&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td&gt;Reference manager&lt;/td&gt;&lt;td&gt;&lt;a rel=&quot;external&quot; href=&quot;https://www.zotero.org/&quot;&gt;Zotero&lt;/a&gt; + &lt;a rel=&quot;external&quot; href=&quot;https://retorque.re/zotero-better-bibtex/&quot;&gt;Better BibTeX&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Citation processing&lt;/td&gt;&lt;td&gt;&lt;a rel=&quot;external&quot; href=&quot;https://github.com/EmilLindfors/zotero-cite&quot;&gt;zotero-cite&lt;/a&gt; (Rust CLI)&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Template rendering&lt;/td&gt;&lt;td&gt;Tera components in &lt;a rel=&quot;external&quot; href=&quot;https://www.getzola.org/&quot;&gt;Zola&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Math (web)&lt;/td&gt;&lt;td&gt;&lt;a rel=&quot;external&quot; href=&quot;https://katex.org/&quot;&gt;KaTeX&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;what-i-d-change&quot;&gt;What I&#39;d change&lt;/h2&gt;
&lt;p&gt;If you are building this yourself, or I were starting over:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CSL support in zotero-cite.&lt;/strong&gt; Right now the formatting is hardcoded in Tera components. Supporting CSL styles would let me switch between APA, IEEE, Vancouver, etc. without changing templates.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Automatic numbering.&lt;/strong&gt; Currently I manually assign citation numbers with &lt;code&gt;{{&amp;lt;citation key=&quot;...&quot; num=&quot;1&quot; /&amp;gt;}}&lt;/code&gt;. It should auto-number based on order of appearance.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Bidirectional links.&lt;/strong&gt; Clicking a citation scrolls to the reference, but clicking a reference doesn&#39;t scroll back to where it was cited. This is standard in PDFs but tricky in HTML.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These are improvements, not blockers. The system works well enough that I use it for every post that needs references.&lt;/p&gt;
&lt;h2 id=&quot;the-point&quot;&gt;The point&lt;/h2&gt;
&lt;p&gt;Blog posts with citations are better blog posts. When I write &quot;production costs vary significantly across salmon-producing countries&quot;, readers shouldn&#39;t have to trust me -- they should be able to click through to Iversen et al. (2020) and check for themselves.&lt;/p&gt;
&lt;p&gt;Academic writing tools make this easy but are terrible for web publishing. Blogging tools are great for the web but ignore citations entirely. Bridging the gap took a small Rust CLI and some Tera components. The pieces were all there -- they just needed connecting.&lt;/p&gt;
&lt;p&gt;The code for &lt;code&gt;zotero-cite&lt;/code&gt; is &lt;a rel=&quot;external&quot; href=&quot;https://github.com/EmilLindfors/zotero-cite&quot;&gt;on GitHub&lt;/a&gt;. If you use Zotero and a static site generator, it might save you some time.&lt;/p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Self-hosting email is not that hard anymore</title>
        <published>2026-02-18T00:00:00+00:00</published>
        <updated>2026-02-18T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/self-hosted-newsletter/"/>
        <id>https://lindfors.no/blog/self-hosted-newsletter/</id>
        
        <summary type="html">&lt;p&gt;Type your address into the box at the bottom of this page and here is what happens:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;A Rust Worker on Cloudflare checks the address, checks a rate limit, and mails you a signed link. It does not store your address anywhere.&lt;/li&gt;
&lt;li&gt;You open the mail and press a button. That button posts back to the Worker, which checks the signature and only then adds you to a mailing list on my own mail server.&lt;/li&gt;
&lt;li&gt;A welcome mail arrives with the five most recent posts in it.&lt;/li&gt;
&lt;li&gt;When I publish something, one message is written for you alone, with an unsubscribe link that knows who you are, and sent through that same server.&lt;/li&gt;
&lt;li&gt;If your mail client offers a native unsubscribe button, it posts to the Worker, which removes you. The link in the footer shows a button that does the same.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;No database, no newsletter platform, no third party holding the list. The mail server is a $6 VPS that also does my personal email. This is the February 2026 system after a year of fixes, and it is not the system any more: on 3 September 2026 I retired the Worker and moved the whole newsletter onto the mail server with a Postgres behind it, in one day. &lt;a href=&quot;/blog/newsletter-on-my-own-server/&quot;&gt;That move has its own post&lt;/a&gt;, and the rest of this one describes the system as it stood, because the mail-server half is unchanged and the reasons for the Worker half still explain the shape it took. This post is what it looks like now, what it needs on the DNS side to stay out of junk folders, and why I bothered.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>I use Typst to generate PDFs of my blog posts and my CV</title>
        <published>2026-02-14T00:00:00+00:00</published>
        <updated>2026-02-14T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/typst-for-blogging/"/>
        <id>https://lindfors.no/blog/typst-for-blogging/</id>
        
        <content type="html" xml:base="https://lindfors.no/blog/typst-for-blogging/">&lt;p&gt;Every post on this blog has a PDF button in the sidebar. Click it and you get a properly typeset document -- serif body text, sans-serif headings, colored code blocks, rendered math. It looks like something you&#39;d find on arXiv, not a browser print-to-PDF.&lt;/p&gt;
&lt;p&gt;My CV lives as a &lt;code&gt;.typ&lt;/code&gt; file in the same git repo. When I push, it compiles to a PDF that&#39;s served at &lt;code&gt;/cv.pdf&lt;/code&gt;. No Google Docs. No Overleaf. No emailing &lt;code&gt;CV_final_FINAL_v3.pdf&lt;/code&gt; to myself.&lt;/p&gt;
&lt;p&gt;Both are powered by &lt;a rel=&quot;external&quot; href=&quot;https://typst.app/&quot;&gt;Typst&lt;/a&gt;, a typesetting system written in Rust. If you&#39;ve used LaTeX and wished it didn&#39;t hate you, Typst is the answer.&lt;/p&gt;
&lt;h2 id=&quot;why-not-just-print-to-pdf&quot;&gt;Why not just print to PDF?&lt;/h2&gt;
&lt;p&gt;Browser print-to-PDF produces ugly output. Navigation elements, footers, and sidebars leak in. Line breaks happen in wrong places. Code blocks get cut off. Math renders at screen resolution. Fonts fall back to system defaults.&lt;/p&gt;
&lt;p&gt;You can add &lt;code&gt;@media print&lt;/code&gt; CSS to fix some of this, but you&#39;re fighting the browser&#39;s layout engine the whole way. Print CSS is a maintenance burden that produces mediocre results.&lt;/p&gt;
&lt;p&gt;I wanted PDFs that look &lt;em&gt;designed&lt;/em&gt; -- consistent typography, proper margins, page numbers, and a layout that works on paper. That means a real typesetting engine.&lt;/p&gt;
&lt;h2 id=&quot;why-typst-over-latex&quot;&gt;Why Typst over LaTeX?&lt;/h2&gt;
&lt;p&gt;I used LaTeX throughout my PhD. It produces gorgeous output. It also:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Takes 30+ seconds to compile a document&lt;/li&gt;
&lt;li&gt;Produces error messages like &lt;code&gt;! Undefined control sequence. l.47 \begin{itemize}&lt;/code&gt; when you forget a package&lt;/li&gt;
&lt;li&gt;Requires a 4GB TeX Live installation&lt;/li&gt;
&lt;li&gt;Has a syntax that looks like it was designed to be read by compilers, not humans&lt;/li&gt;
&lt;li&gt;Makes you choose between dozens of document classes, packages, and incompatible options before you can write a single paragraph&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Typst fixes all of this:&lt;/p&gt;
&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;LaTeX&lt;/th&gt;&lt;th&gt;Typst&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td&gt;Compile time&lt;/td&gt;&lt;td&gt;30+ seconds&lt;/td&gt;&lt;td&gt;&amp;lt; 1 second&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Binary size&lt;/td&gt;&lt;td&gt;~4 GB (TeX Live)&lt;/td&gt;&lt;td&gt;~30 MB&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Error messages&lt;/td&gt;&lt;td&gt;Cryptic&lt;/td&gt;&lt;td&gt;Readable, with line numbers&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Syntax&lt;/td&gt;&lt;td&gt;&lt;code&gt;\textbf{bold}&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;*bold*&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Package management&lt;/td&gt;&lt;td&gt;Manual &lt;code&gt;.sty&lt;/code&gt; files&lt;/td&gt;&lt;td&gt;Built-in registry&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Language&lt;/td&gt;&lt;td&gt;TeX macros&lt;/td&gt;&lt;td&gt;Real scripting language&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Typst&#39;s syntax is close enough to markdown that it feels natural. Bold is &lt;code&gt;*bold*&lt;/code&gt;. Italics is &lt;code&gt;_italics_&lt;/code&gt;. Code blocks are triple backticks. Headings are &lt;code&gt;= Heading&lt;/code&gt;. You can write a document without reading a manual.&lt;/p&gt;
&lt;p&gt;But when you need power, Typst has a real programming language. Functions, variables, loops, conditionals. Not TeX&#39;s macro expansion nightmare, but actual code:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;typst&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;#let&lt;/span&gt;&lt;span&gt; accent&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; rgb&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;#2c3e50&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;#let&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; section&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span&gt;title&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;  v&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt;0.6em&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;  text&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;weight&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;bold&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt; size&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 11pt&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt; fill&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span&gt; accent&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)[#&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;upper&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span&gt;title&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)]&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;  v&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;-&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt;0.3em&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;  line&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;length&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 100%&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt; stroke&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 0.5pt&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; +&lt;/span&gt;&lt;span&gt; accent&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;  v&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt;0.3em&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;!-- voice-ok: deliberate joke, keep --&gt;
&lt;p&gt;That&#39;s readable. Try doing the same in LaTeX.&lt;/p&gt;
&lt;h2 id=&quot;my-cv-in-typst&quot;&gt;My CV in Typst&lt;/h2&gt;
&lt;p&gt;My CV is a single file: &lt;code&gt;cv.typ&lt;/code&gt; at the repo root. Here&#39;s how it starts:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;typst&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;#set&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; document&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;title&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;Emil Lindfors - CV&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt; author&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;Emil Lindfors&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;#set&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; page&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;paper&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;a4&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt; margin&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;: (&lt;/span&gt;&lt;span&gt;x&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 1.8cm&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span&gt; y&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 1.5cm&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;#set&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; text&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;font&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;Libertinus Serif&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt; size&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 10pt&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;#set&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; par&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;justify&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; true&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Four lines and you have a fully configured document. Page size, margins, font, paragraph settings. In LaTeX this would be a &lt;code&gt;\documentclass&lt;/code&gt; with options, plus &lt;code&gt;\usepackage{geometry}&lt;/code&gt;, &lt;code&gt;\usepackage{fontspec}&lt;/code&gt;, and a prayer that they don&#39;t conflict.&lt;/p&gt;
&lt;p&gt;I define small helper functions for repeated structures:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;typst&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;#let&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; experience&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span&gt;company&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span&gt; role&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span&gt; dates&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span&gt; location&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span&gt; bullets&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;  grid&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;    columns&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;: (&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt;1fr&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #F38BA8;&quot;&gt; auto&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;),&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;    text&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;weight&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;bold&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)[&lt;/span&gt;&lt;span&gt;#company&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;    text&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;style&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;italic&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt; fill&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span&gt; light-gray&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)[&lt;/span&gt;&lt;span&gt;#dates&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;  )&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;  text&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;style&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;italic&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)[&lt;/span&gt;&lt;span&gt;#role&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;  +&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; h&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt;1em&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt;  +&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; text&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;fill&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span&gt; light-gray&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt; size&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 9pt&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)[&lt;/span&gt;&lt;span&gt;#location&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;  v&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt;0.2em&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;  for&lt;/span&gt;&lt;span&gt; bullet&lt;/span&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt; in&lt;/span&gt;&lt;span&gt; bullets&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;    [&lt;/span&gt;&lt;span&gt;- #bullet&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;  v&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt;0.4em&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Then each job entry is a function call:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;typst&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;#&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;experience&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;  &amp;quot;AquaCloud&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;  &amp;quot;Senior Software Engineer&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;  &amp;quot;January 2025 -- Present&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;  &amp;quot;Norway&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;  (&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;    [&lt;/span&gt;&lt;span&gt;Architected aquaculture data platform integrating&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;     Fishtalk, Mercatus, and other industry systems&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;    [&lt;/span&gt;&lt;span&gt;Built data pipelines for major Norwegian salmon farmers&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;],&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;    // ...&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;  )&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The CV compiles in under a second. The output is a clean, professional PDF with proper grid alignment, consistent spacing, and a photo in the header. It lives in version control alongside my blog, and updating it means editing one text file and pushing.&lt;/p&gt;
&lt;h3 id=&quot;building-it&quot;&gt;Building it&lt;/h3&gt;
&lt;p&gt;The build script compiles it alongside everything else:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;shellscript&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;typst&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; compile cv.typ static/cv.pdf&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;That&#39;s it. One command. The resulting PDF is served at &lt;code&gt;lindfors.no/cv.pdf&lt;/code&gt;. Every page on the site links to it from the author sidebar.&lt;/p&gt;
&lt;h2 id=&quot;blog-post-pdfs&quot;&gt;Blog post PDFs&lt;/h2&gt;
&lt;p&gt;This is the more interesting part. Every blog post is written in markdown for Zola. I wanted a PDF for each one, but the content lives in Zola-flavored markdown with TOML frontmatter, shortcodes, and HTML citations. Typst doesn&#39;t understand any of that.&lt;/p&gt;
&lt;p&gt;The solution is a three-stage pipeline: extract, preprocess, render.&lt;/p&gt;
&lt;h3 id=&quot;the-pipeline&quot;&gt;The pipeline&lt;/h3&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;plain&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  ┌──────────────────┐&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  │ Blog post        │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  │ (Zola markdown)  │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  │ +++ frontmatter  │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  │ shortcodes       │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  │ HTML references  │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  └────────┬─────────┘&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;           │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;     extract &amp;amp; clean&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;           │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  ┌────────▼─────────┐&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  │ Clean markdown   │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  │ + title/date     │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  └────────┬─────────┘&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;           │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;     cmarker (md→typst)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;           │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  ┌────────▼─────────┐&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  │ Typst document   │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  │ academic.typ     │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  │ template         │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  └────────┬─────────┘&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;           │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;     typst compile&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;           │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  ┌────────▼─────────┐&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  │ PDF              │&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  └──────────────────┘&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;h3 id=&quot;stage-1-extract&quot;&gt;Stage 1: Extract&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;site-tools&lt;/code&gt; splits the markdown file on the &lt;code&gt;+++&lt;/code&gt; delimiters and parses the frontmatter with the &lt;code&gt;toml&lt;/code&gt; crate.&lt;/p&gt;
&lt;p&gt;This started out as &lt;code&gt;awk&lt;/code&gt; for the split, with &lt;code&gt;grep&lt;/code&gt; and &lt;code&gt;sed&lt;/code&gt; for the individual fields:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;shellscript&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;awk&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;#39;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;BEGIN { in_front = 0; front_done = 0 }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;/^\+\+\+$/ {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;    if (in_front == 0) { in_front = 1; next }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;    else { front_done = 1; in_front = 0; next }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;}&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;in_front == 1 { print &amp;gt; &amp;quot;frontmatter.toml&amp;quot; }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;front_done == 1 { print &amp;gt; &amp;quot;content.md&amp;quot; }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;#39; &amp;quot;&lt;/span&gt;&lt;span&gt;$INPUT_FILE&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Not elegant, but it worked and had zero dependencies. What pushed it into Rust was needing to read &lt;code&gt;draft&lt;/code&gt;, which has to be a real boolean -- a &lt;code&gt;grep&lt;/code&gt; for &lt;code&gt;^draft&lt;/code&gt; matches &lt;code&gt;draft = &quot;true&quot;&lt;/code&gt; just as happily, and drafts leaking into &lt;code&gt;static/pdf/&lt;/code&gt; is the kind of mistake you find out about later. The typed parse also made it testable, which the shell version never was.&lt;/p&gt;
&lt;h3 id=&quot;stage-2-preprocess&quot;&gt;Stage 2: Preprocess&lt;/h3&gt;
&lt;p&gt;The markdown body needs cleaning before Typst can handle it. Blog posts contain things that make sense on the web but not in a PDF:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Citation anchors&lt;/strong&gt; like &lt;code&gt;[1](#ref-smith2023)&lt;/code&gt; become plain &lt;code&gt;1&lt;/code&gt; -- the PDF has the references right there on the page, no need for hyperlinks:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;shellscript&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;sed&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; -i -E &amp;#39;s/\[([0-9]+)\]\(#ref-[^)]+\)/\1/g&amp;#39; content.md&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;strong&gt;HTML reference blocks&lt;/strong&gt; get converted to markdown lists. On the web, references are &lt;code&gt;&amp;lt;p&amp;gt;&lt;/code&gt; tags with classes for styling. In the PDF, they become simple bulleted items:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;shellscript&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;sed&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; -i -E &amp;#39;s/&amp;lt;p[^&amp;gt;]*class=&amp;quot;reference&amp;quot;[^&amp;gt;]*&amp;gt;/- /g&amp;#39; content.md&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;sed&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; -i -E &amp;#39;s/&amp;lt;\/p&amp;gt;//g&amp;#39; content.md&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;sed&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; -i -E &amp;#39;s/&amp;lt;em&amp;gt;/*/g&amp;#39; content.md&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;sed&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; -i -E &amp;#39;s/&amp;lt;\/em&amp;gt;/*/g&amp;#39; content.md&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;sed&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; -i -E &amp;#39;s/&amp;lt;a href=&amp;quot;([^&amp;quot;]+)&amp;quot;&amp;gt;([^&amp;lt;]+)&amp;lt;\/a&amp;gt;/[\2](\1)/g&amp;#39; content.md&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;After preprocessing, the markdown is clean enough for Typst to consume.&lt;/p&gt;
&lt;h3 id=&quot;stage-3-render&quot;&gt;Stage 3: Render&lt;/h3&gt;
&lt;p&gt;The generated Typst document is minimal -- it imports my template, sets the metadata, and renders the markdown:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;typst&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;#import&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;academic.typ&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span&gt; academic&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;#import&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;@preview/cmarker:0.1.8&amp;quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;#import&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;@preview/mitex:0.2.6&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span&gt; mitex&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;#show&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span&gt; academic.&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;with&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;  title&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;My Post Title&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;  author&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;Emil Lindfors&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;  date&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;February 10, 2026&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;#cmarker.render(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  read(&amp;quot;content.md&amp;quot;),&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  math: mitex,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  smart-punctuation: true,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Two Typst packages do the heavy lifting:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a rel=&quot;external&quot; href=&quot;https://typst.app/universe/package/cmarker&quot;&gt;cmarker&lt;/a&gt; converts CommonMark markdown to Typst. It handles headings, lists, code blocks, links, images, tables -- everything. The blog post markdown goes in, Typst content comes out.&lt;/li&gt;
&lt;li&gt;&lt;a rel=&quot;external&quot; href=&quot;https://typst.app/universe/package/mitex&quot;&gt;MiTeX&lt;/a&gt; renders LaTeX math syntax in Typst. The same &lt;code&gt;$E = mc^2$&lt;/code&gt; that KaTeX renders on the web, MiTeX renders in the PDF. No syntax changes between formats.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;the-academic-template&quot;&gt;The academic template&lt;/h3&gt;
&lt;p&gt;The &lt;code&gt;academic.typ&lt;/code&gt; template controls the look of every blog post PDF. I designed it to match my website&#39;s visual identity:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;typst&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;#let&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; academic&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;  title&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #F38BA8;&quot;&gt; none&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;  author&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;Emil Lindfors&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;  date&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #F38BA8;&quot;&gt; none&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;  abstract&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #F38BA8;&quot;&gt; none&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  body&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;  // Sea theme colors (same as the website)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;  let&lt;/span&gt;&lt;span&gt; color-text&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; rgb&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;#1C3240&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;        // Deep Sea&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;  let&lt;/span&gt;&lt;span&gt; color-accent&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; rgb&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;#2A8F82&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;      // Teal&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;  let&lt;/span&gt;&lt;span&gt; color-link&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; rgb&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;#D4706A&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;        // Coral&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;  let&lt;/span&gt;&lt;span&gt; color-bg-code&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; rgb&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;#F0EBE3&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;     // Tide Pool&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;  set&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; page&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;paper&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;a4&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt; margin&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;: (&lt;/span&gt;&lt;span&gt;x&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 2.5cm&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span&gt; y&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 2.5cm&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;))&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;  // Body text: Literata (serif) — same as the blog&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;  set&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; text&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;    font&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;: (&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;Literata&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;Libertinus Serif&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;),&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;    size&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 11pt&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;    fill&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span&gt; color-text&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;  )&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;  // Headings: Inter (sans-serif) — same as the blog&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;  show&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; heading&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;where&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;level&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 1&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;):&lt;/span&gt;&lt;span&gt; it&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&amp;gt;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;    set&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; text&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;      font&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;: (&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;&amp;quot;Inter&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;Ubuntu Sans&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;),&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;      size&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 18pt&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt; weight&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 600&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;    )&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;    v&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt;1.5em&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;    it.body&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;    v&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt;0.75em&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;  // Code blocks: teal left border, light background&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;  show&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; raw&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;where&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;block&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; true&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;):&lt;/span&gt;&lt;span&gt; it&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; =&amp;gt;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt; {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #CBA6F7;&quot;&gt;    set&lt;/span&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt; text&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;font&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; &amp;quot;JetBrains Mono&amp;quot;&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt; size&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 9pt&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;    block&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;(&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;      fill&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span&gt; color-bg-code&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;      stroke&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;: (&lt;/span&gt;&lt;span&gt;left&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 3pt&lt;/span&gt;&lt;span style=&quot;color: #94E2D5;&quot;&gt; +&lt;/span&gt;&lt;span&gt; color-accent&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;),&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt;      inset&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 10pt&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt; radius&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 4pt&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;color: #EBA0AC;font-style: italic;&quot;&gt; width&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #FAB387;&quot;&gt; 100%&lt;/span&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;,&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;      it&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;    )&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;  }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;  // ... title block, page footer, etc.&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  body&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;&quot;&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The same fonts (Inter + Literata), the same colors (deep sea, teal, coral), the same code block styling (teal left border). Someone reading the blog and then opening the PDF sees the same visual language. The self-hosted fonts are passed to &lt;code&gt;typst compile&lt;/code&gt; with &lt;code&gt;--font-path&lt;/code&gt;:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;shellscript&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;typst&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; compile&lt;/span&gt;&lt;span style=&quot;color: #F5C2E7;&quot;&gt; \&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;  --font-path fonts/inter&lt;/span&gt;&lt;span style=&quot;color: #F5C2E7;&quot;&gt; \&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;  --font-path fonts/literata&lt;/span&gt;&lt;span style=&quot;color: #F5C2E7;&quot;&gt; \&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt;  document.typ output.pdf&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;No system font dependencies. The PDF looks identical on any machine.&lt;/p&gt;
&lt;h2 id=&quot;the-build-integration&quot;&gt;The build integration&lt;/h2&gt;
&lt;p&gt;The PDF generation steps in the deploy script are straightforward:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;shellscript&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;# Compile CV&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;site-tools&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; cv build&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #9399B2;font-style: italic;&quot;&gt;# Generate blog post PDFs (drafts are skipped)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span style=&quot;color: #89B4FA;font-style: italic;&quot;&gt;site-tools&lt;/span&gt;&lt;span style=&quot;color: #A6E3A1;&quot;&gt; pdf all&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;These run after &lt;a href=&quot;/blog/citations-on-a-static-site/&quot;&gt;citation processing&lt;/a&gt; (since the PDF generator needs resolved references) and before &lt;code&gt;zola build&lt;/code&gt;. The generated PDFs go into &lt;code&gt;static/pdf/&lt;/code&gt;, which Zola copies to the build output. Every post&#39;s sidebar has a PDF download button that links to &lt;code&gt;/pdf/{slug}.pdf&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Typst compiles each post in well under a second. The whole site including all PDFs builds in a few seconds. Compare that to LaTeX, where a single document with &lt;code&gt;biblatex&lt;/code&gt; can take 30 seconds and multiple passes. For the full build pipeline, see the &lt;a href=&quot;/blog/building-a-personal-blog-with-zola/#the-build-in-order&quot;&gt;site overview post&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;what-the-output-looks-like&quot;&gt;What the output looks like&lt;/h2&gt;
&lt;p&gt;A blog post PDF has:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Title page header&lt;/strong&gt; with the post title in 22pt Inter, author and date centered below&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A horizontal rule&lt;/strong&gt; separating the header from body content&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Body text&lt;/strong&gt; in 11pt Literata with justified paragraphs&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Headings&lt;/strong&gt; in Inter (18pt/14pt/12pt for h1/h2/h3)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Code blocks&lt;/strong&gt; with a teal left border on a light background, in JetBrains Mono&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Blockquotes&lt;/strong&gt; with the same teal left border treatment&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Math&lt;/strong&gt; rendered natively via MiTeX&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Links&lt;/strong&gt; in coral, matching the website&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Page numbers&lt;/strong&gt; centered in the footer (e.g., &quot;3 / 7&quot;)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The CV has a different style -- more compact, with a grid layout, photo in the header, and section dividers. Same Typst, different template.&lt;/p&gt;
&lt;h2 id=&quot;why-this-matters&quot;&gt;Why this matters&lt;/h2&gt;
&lt;p&gt;Two reasons:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1. PDFs outlast websites.&lt;/strong&gt; URLs break. Services shut down. My blog might not be here in 10 years. But a PDF saved to someone&#39;s hard drive will still open in 2040. Every blog post I write about aquaculture production costs or sensor architectures might be cited in someone&#39;s thesis. A PDF makes that possible.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2. The CV is never stale.&lt;/strong&gt; My CV is a text file in the same repo as my blog. When I change jobs, I edit &lt;code&gt;cv.typ&lt;/code&gt;, push, and the new PDF is live. No &quot;download from Google Docs, re-export, upload to website&quot; dance. No version mismatch between what&#39;s on my site and what I emailed to someone last month.&lt;/p&gt;
&lt;h2 id=&quot;the-rough-edges&quot;&gt;The rough edges&lt;/h2&gt;
&lt;p&gt;Typst is young. Things that could be better:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;cmarker isn&#39;t perfect.&lt;/strong&gt; Some markdown edge cases (nested lists with code blocks, complex tables) don&#39;t render exactly right. I haven&#39;t hit a showstopper, but I occasionally adjust the markdown to make cmarker happy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No Zola shortcodes in PDFs.&lt;/strong&gt; The preprocessing strips shortcodes, which means figures and interactive elements don&#39;t appear in the PDF. I add a &quot;view on site&quot; note for anything stripped.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Font fallback is limited.&lt;/strong&gt; Typst&#39;s font fallback is less sophisticated than a browser&#39;s. I ship my fonts explicitly via &lt;code&gt;--font-path&lt;/code&gt; to avoid surprises.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No incremental compilation.&lt;/strong&gt; Every deploy recompiles every PDF. For a handful of posts this is fine (sub-second each). At 100 posts I&#39;d want to add change detection.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;None of these are blockers. The output quality is excellent and the developer experience is leagues ahead of LaTeX.&lt;/p&gt;
&lt;h2 id=&quot;the-toolchain&quot;&gt;The toolchain&lt;/h2&gt;
&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Role&lt;/th&gt;&lt;th&gt;Tool&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td&gt;Typesetting engine&lt;/td&gt;&lt;td&gt;&lt;a rel=&quot;external&quot; href=&quot;https://typst.app/&quot;&gt;Typst&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Markdown → Typst&lt;/td&gt;&lt;td&gt;&lt;a rel=&quot;external&quot; href=&quot;https://typst.app/universe/package/cmarker&quot;&gt;cmarker&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;LaTeX math → Typst&lt;/td&gt;&lt;td&gt;&lt;a rel=&quot;external&quot; href=&quot;https://typst.app/universe/package/mitex&quot;&gt;MiTeX&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Body font&lt;/td&gt;&lt;td&gt;&lt;a rel=&quot;external&quot; href=&quot;https://github.com/googlefonts/literata&quot;&gt;Literata&lt;/a&gt; (serif)&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Heading font&lt;/td&gt;&lt;td&gt;&lt;a rel=&quot;external&quot; href=&quot;https://rsms.me/inter/&quot;&gt;Inter&lt;/a&gt; (sans-serif)&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Code font&lt;/td&gt;&lt;td&gt;JetBrains Mono&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The blog post template and CV source are in the &lt;a rel=&quot;external&quot; href=&quot;https://github.com/emillindfors/lindfors-site&quot;&gt;site repo&lt;/a&gt;; the build tooling has a repository of its own, &lt;a rel=&quot;external&quot; href=&quot;https://github.com/EmilLindfors/site-tools&quot;&gt;site-tools&lt;/a&gt;. If you&#39;re using Zola (or any static site generator) and want auto-generated PDFs, &lt;code&gt;crates/site-tools/src/pdf.rs&lt;/code&gt; is the piece to look at -- it&#39;s generic enough to adapt.&lt;/p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Zola has no plugins, so this blog grew a Rust CLI</title>
        <published>2026-01-27T00:00:00+00:00</published>
        <updated>2026-01-27T00:00:00+00:00</updated>
        
        <author>
          <name>Emil Lindfors</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://lindfors.no/blog/building-a-personal-blog-with-zola/"/>
        <id>https://lindfors.no/blog/building-a-personal-blog-with-zola/</id>
        
        <summary type="html">&lt;p&gt;Here is what a deploy of this blog looks like from the terminal, with the per-post lines cut out:&lt;/p&gt;
&lt;pre class=&quot;giallo&quot; style=&quot;color: #CDD6F4; background-color: #1E1E2E;&quot; &gt;&lt;code data-lang=&quot;plain&quot;&gt;&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;$ ./build.sh&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;Processing citations...&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;Generating markdown representations...&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;Generating speech scripts...&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;Generating audio...&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;Generating CV...&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;Generating PDFs...&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;Building site with Zola...&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;  (no local zola -- using ghcr.io/getzola/zola:v0.23.2)&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;giallo-l&quot;&gt;&lt;span&gt;Done!&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;One script, and everything the site does comes out of it. Each post gets a typeset PDF, a plain-markdown copy for anyone who asks for one with an &lt;code&gt;Accept&lt;/code&gt; header, a spoken script, and for some posts an MP3. Citations resolve to a formatted reference list with DOIs. The CV compiles. Then Zola renders the lot, and a push puts it on Cloudflare Pages. There is a newsletter behind it too, on a Rust Worker and a mail server I run myself, and a client-side search that never calls anyone. No JavaScript framework, no &lt;code&gt;node_modules&lt;/code&gt;, no third-party service except Cloudflare.&lt;/p&gt;
&lt;p&gt;This post is the foundation of the series: why Zola, what Zola refuses to do, and how that one refusal decided the shape of everything around it. The &lt;a href=&quot;/blog/self-hosted-newsletter/&quot;&gt;newsletter&lt;/a&gt;, the &lt;a href=&quot;/blog/citations-on-a-static-site/&quot;&gt;citations&lt;/a&gt;, the &lt;a href=&quot;/blog/typst-for-blogging/&quot;&gt;PDFs&lt;/a&gt;, the &lt;a href=&quot;/blog/images-on-a-static-site/&quot;&gt;images&lt;/a&gt; and the audio each have their own post.&lt;/p&gt;</summary>
        
    </entry>
</feed>
