<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  
  <title>lafe&#39;s blog</title>
  <subtitle>This is a longer description about your blog.</subtitle>
  <link href="https://www.lafes.net/blog/feed.xml" rel="self" />
  <link href="https://www.lafes.net/blog/" />
  <updated>2026-05-09T17:55:00Z</updated>
  <id>https://www.lafes.net/blog/</id>
  <author>
    <name>lafe</name>
  </author>
  <entry>
    <title>Designing a digital garden</title>
    <link href="https://www.lafes.net/blog/20260509-Designing-a-digital-garden/" />
    <updated>2026-05-09T17:55:00Z</updated>
    <id>https://www.lafes.net/blog/20260509-Designing-a-digital-garden/</id>
    <content type="html">&lt;p&gt;
	How do you design something that is not really meant to have a lot of structure?
	Digital gardens come in a lot of shapes. Some are like crazy warrens of pages
	and topics that have no overt organization, but flow organically. Some are very
	hierarchical, categorized, tagged, searchable, and usable.
&lt;/p&gt;
&lt;p&gt;
	It seems like a lot of folks equate a digital garden with a personal wiki or
	&quot;personal knowledge system&quot;. That&#39;s definitely not what I&#39;m going for here.
	Or not exactly.
&lt;/p&gt;
&lt;p&gt;
	Fortunately for me, none of these concepts are exactly new. And lots of pixels
	have been shaped into words by people seeking to solve some of the same problems
	that I&#39;m thinking about now. For all that it was written in 1998, these
	&lt;a href=&quot;https://www.eastgate.com/garden/Enter.html&quot;&gt;writings about hypertext
	gardens&lt;/a&gt; are still pretty relevant today.
&lt;/p&gt;
&lt;p&gt;
	For now, I think that I am looking for some very basic categorization and
	hierarchy, but only in the broadest of senses. To address the idea of dark,
	undiscoverable corners of the garden (assuming I ever write such a thing)
	a basic (automatically generated?) site map may serve. Perhaps some pages will
	serve as &quot;hubs&quot; for discoverability of pages around similar topics. And
	maybe if I get really fancy I&#39;ll link to related topics.
&lt;/p&gt;
&lt;p&gt;
	I&#39;m a fan of trying things, and seeing if they work. If they don&#39;t, I&#39;ll try
	something else. Maintaining inter-linking and back-linking, by hand may end
	up being fun, or it might be a pain. Fortunately, I can always add a bit more
	technology if necessary. Or abandon the idea completely.
&lt;/p&gt;
&lt;p&gt;
	A digital gardener does seem to have the same basic job description as a
	&lt;a href=&quot;https://wiki.c2.com/?WikiGardener&quot;&gt;Wiki Gardener&lt;/a&gt;. But this garden
	isn&#39;t (yet?) so collaborative.
&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Added atom feed</title>
    <link href="https://www.lafes.net/blog/20260508-Added-atom-feed/" />
    <updated>2026-05-08T23:37:00Z</updated>
    <id>https://www.lafes.net/blog/20260508-Added-atom-feed/</id>
    <content type="html">&lt;p&gt;
	I was finally able to get the &lt;a href=&quot;https://www.lafes.net/blog/feed.xml&quot;&gt;atom feed&lt;/a&gt; up and going.
	The plan is to use that for blogging, and probably (mostly!) for site updates,
	page additions, and whatnot. If you use a news/rss reader or aggregator service,
	AND you care to follow what I&#39;m up to on this site, then you may wish to subscribe.
&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Hello world</title>
    <link href="https://www.lafes.net/blog/20260501-Hello-world/" />
    <updated>2026-05-01T22:04:00Z</updated>
    <id>https://www.lafes.net/blog/20260501-Hello-world/</id>
    <content type="html">&lt;p&gt;
	I&#39;ve been working on getting &lt;a href=&quot;https://www.11ty.dev&quot;&gt;11ty&lt;/a&gt; set up to
	work its magic for a simple blog setup for me. I want to be able to add simple
	little html files for each new entry, without a lot of work to update boiler-plate.
	This seemed to be well within 11ty&#39;s capabilities... I just had to learn how.
&lt;/p&gt;
</content>
  </entry>
</feed>