Digital Garden

Digital gardens are places where information grows. It is a collection of notes and ideas that are organised in a way that allows for exploration and discovery. It is meant to be a living, growing repository of knowledge and ideas, rather than a static document. This site itself is a digital garden following principles of brutalist web design.

Challenges

A digital garden presents a few challenges.

• Chronological is the wrong metaphor, but how to capture time and sequence?. A digital garden can contain a large amount of information, and it can be difficult to decide how to organise and structure it in a way that is intuitive and easy for others to navigate.

• Finding the right tools: There are many different tools and platforms that can be used to create a digital garden, and it can be challenging to find the one that best fits your needs and workflow. Some popular choices include static site generators like Hugo, note-taking tools like Emacs with Org mode, or modern platforms like Quarto.

• Keeping the garden up to date: A digital garden is meant to be a living, growing repository of knowledge and ideas, which means that it requires ongoing maintenance and updates. It can be time-consuming to keep the garden up to date and to ensure that the information it contains is accurate and current. Using version control systems like Git can help track changes and maintain history.

• Balancing depth and breadth: A digital garden can contain a wide range of topics and ideas, and it can be challenging to find the right balance between providing enough detail to be useful and not overwhelming the reader with too much information. This is where proper organisation and typography become essential.

• Promoting and sharing the garden: A digital garden is only valuable if it is used and appreciated by others. It can be challenging to promote and share a digital garden and to get others to engage with and contribute to it. Having an RSS feed and following good HTML practices can help with discoverability.

Chronological is the wrong metaphor, but how to capture time and sequence?

In a digital garden, the organisation of information is not necessarily tied to a specific timeline or sequence. Instead, the focus is on creating connections and relationships between ideas, rather than presenting them in a linear fashion.

One way to capture the sense of time and sequence in a digital garden is to use tags or labels to indicate when a particular note or idea was created or updated. This allows for some level of temporal organisation, while still allowing for flexibility and the ability to create connections between ideas that may not necessarily be related to a specific point in time.

Another option is to use a visual representation of time, such as a timeline or a calendar, to show the evolution of ideas or concepts over a specific period of time. This can help to give context and provide a sense of progression, while still allowing for the non-linear organisation of information that is characteristic of a digital garden.

As an example, have a Git commit hash as well as a recent changes history. Each page already displays a commit hash to give it a context as well as a recently updated section in the index.

However, using commit hashes to capture the sequence of events might not be the most intuitive or user-friendly approach. Git commit hashes are typically long strings of letters and numbers, and they are not necessarily easy for people to remember or understand.

The RSS11 RSS 2.0 file. also provides a temporal source of truth.

Networking

Digital gardens nurture the creation of complex networks from simple concept associations. Quoting Tim Berners-Lee’s22 https://en.wikipedia.org/wiki/Tim_Berners-Lee “Weaving the Web” (Berners-Lee 1999) (2000):

One of the beautiful things about physics is its ongoing quest to find simple rules that describe the behaviour of very small, simple objects. Once found, these rules can often be scaled up to describe the behaviour of monumental systems in the real world. […]

If the rules governing hypertext links between servers and browsers stayed simple, then our web of a few documents could grow to a global web. The art was to define the few basic, common rules of “protocol” that would allow one computer to talk to another, in such a way that when all computers everywhere did it, the system would thrive, not break down. ****