<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>cengen.no</title>
  <subtitle>Notes, projects and recipes by Christian Engen</subtitle>
  <link href="https://cengen.no/feed.xml" rel="self" />
  <link href="https://cengen.no/" />
  <updated>2026-07-30T00:00:00Z</updated>
  <id>https://cengen.no/</id>
  <author>
    <name>Christian Engen</name>
  </author>
  <entry>
    <title>A site of my own</title>
    <link href="https://cengen.no/posts/hello/" />
    <updated>2026-07-30T00:00:00Z</updated>
    <id>https://cengen.no/posts/hello/</id>
    <content type="html">&lt;p&gt;I&#39;ve kept notes in Obsidian for years. It works well for thinking and badly for
sharing — every recipe I actually cook is buried in a vault only I can open, in
whatever shape it was in when I pasted it there.&lt;/p&gt;
&lt;p&gt;So: a site. Three things I want from it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Recipes that survive contact with a kitchen.&lt;/strong&gt; Structured ingredients, real
steps, readable on a phone with flour on my hands. Committing them to a page
forces me to clean them up, which is the actual point.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;A place to link projects.&lt;/strong&gt; Side projects currently exist as GitHub repos with
no context. A short page each is enough.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Somewhere to write.&lt;/strong&gt; Not often. Just somewhere that isn&#39;t a work document.&lt;/p&gt;
&lt;p&gt;Built with &lt;a href=&quot;https://www.11ty.dev/&quot;&gt;Eleventy&lt;/a&gt;, hosted on Cloudflare Pages,
deployed on &lt;code&gt;git push&lt;/code&gt;. The whole thing is a folder of markdown files, which is
the only publishing pipeline I&#39;ve ever managed to stick with.&lt;/p&gt;
</content>
  </entry>
</feed>