08/11/2020

The archive contains older posts which may no longer reflect my current views.

# Remembering the fallen.

# Over the past couple of weeks I have been thinking about how to move forward with the blog or, rather, with writing in general after the Great Notes Catastrophy.

The way the blog operates has changed over time but there's more that can be done to make it more individual, more personal. With that in mind I've been reading about digital gardens again.

If you've been reading for a while you may remember that I tried this before, using a wiki plugin but it didn't work out at the time.

I've said so many times about being a fast writer but feel that I'm finally ready to slow down. Updating my notes over a period of time (even if it was just to convince myself I was still interested) showed me that I could return, adding new thoughts without the pressure of having to finish or hit publish.

I didn't want to do something as intense as a wiki (I installed Obsidian on my MacBook a while back but just haven't touched it) but wanted to do something more permanent than a blog post whilst still being just as casual.

I don't think a notes app on my phone is really the ideal place for this so wondered about something on the blog; it would have to be simple enough to manage in a mobile browser. What if I took the inline editing from the blog and applied it to pages?

Over the past couple of days I've, therefore, come up with a rudimentary solution which includes the following features:

  • new page templates for the "garden"
  • the ability to create and delete pages programatically
  • the same inline editing as with posts
  • wiki style links between pages using "[[ ]]" delimiters that are automatically translated to working HTML tags on display.
  • a parent/child system (so far only one layer deep) to group pages correctly

Home/Index:

Garden index page

Page:

Garden item page

As with the Post functionality, all controls are hidden if you don't have permission to use them. I plan to increase the number of child layers once I work out the logic for multiple nested queries but this will do for a start.

I'm really happy with how it's come together in such a short space of time and hope that I'll make use of this more as it's a "roll your own" solution. I imagine it being the staging area for thoughts that could become posts as well as a resource to link to from elsewhere.

3 comments: click to read or leave your own Comments

# I'll work out how I'm going to link to the "garden" once I've got some content in there.

# Some tweaks to the layout and handling child items. Also, rewritten the link replacement to better cater for multiple links.