Up until now, I had a directory
blog which was full of directories, such
20220112-content-structure, where the first six digits represented the date. In that directory I then had an
index.org file with the content of my post.
Now I have moved to a hierarchical date structure, where the content for that post is now in
blog/2022/01/12/content-structure/index.org. I wrote a quick and dirty shell script to move all the posts.
Evgeny, yes, I thought that would be the problem. I have been using permalinks like that ever since I started using Hugo back in 2016. It's messier than it might first appear, because as you can see from this 'snip' of my
config.toml only some content is laid out that way.
[permalinks] blog = "/blog/:year/:month/:day/:slug/" notes = "/notes/:year/:month:/:day/:slug/" mentions = "/mentions/:year/:month:/:day/:slug/" resources = "/resources/:slug/" pages = "/pages/:slug/"
I suppose, it would be easy enough for me,
sed to move to a directory structure like yours (fixing up any relref on the way). Then, the structure 'on-disk' of all my content would be consistent across all the sections (blog, notes, mentions, etc.) with how it is presented on the web.
Oh joy. I got a response from Evgeny. Now I need to sort out my workflow for responding to responses.
To answer your questions, my directory structure is using
page bundeles with each section (blog, notes, pages, etc) having all my posts, like this:
petersmith.org archetypes config.toml content blog ... ... 20041208-anzam-strategising-activity-and-practice index.org 20041208-professional-doctorates index.org 20041209-comments-on-supervision index.org 20041210-teaching-excellence-award index.org 20110227-yale-on-writing index.org 20110303-boots-and-all index.org 20110305-how-to-write-an-article index.org 20110305-the-paragraph index.org 20220104-responsive-grids index.org 20220106-second-second-steps-in-indieweb index.org 20220110-third-steps-to-indieweb index.org mentions notes pages resources data mentions.json i18n layouts public resources static themes
My new theme, is working well enough that I have now republished my website using it. It also means that I have webmentions working as well. I have some rough edges to sort out but its definitely a MVP (minimum viable product).
It feels as if a cast of thousands have been involved in the this new theme. I have so many people to thank.
First there is Aaron Parecki. I had been watching his videos to help me get into doing my video production (for the BusDev@Auckland seminar series) but then I stumbled into his website, and was introduced to the world of IndieWeb and webmentions. Aaron's site webmention.io also provided the glue to get webmentions working here.
Soon after my first foray into webmentions, I got a mention by Robbi Nespu. That was important not just because of the excellent advice Robbi gave me, but it also gave me the impetus to charge ahead with trying to fully implement webmentions. Looking at Robbi's site, I still need to do more work to get things like 'bookmarks', 'rsvps', and other IndieWeb things working here.
That all prompted me to start (re)theme-ing this site to better accommodate webmentions. As I say, it works, but there is still more to be done.Full entry …
At the same time, I have made the 'mobile' version of the site, a little less clunky. So, far so very good.Full entry …
Whilst out walking around Newmarket we went past Gordon Harris, and popped in to have a look. I had been looking elsewhere at the Staedtler Resina fountain pen, and noticed that here it was in a clearance sale. That was too much to resist. The colour choices were limited (hence the black), but they did have the pen with a fine nib (anything broader would have been a too much for me). So, $107 later I have this pen.Full entry …
As I continue to develop my new template I tackled the issue of responsive design; that is, displaying nicely regardless of the device viewing the site. In my previous themes I made no attempt at making them responsive. They were built to be displayed on a computer screen, and that was about it.
This time, however, I done a little work to make it 'somewhat' responsive.
The modern doctrine around site/web design is that one should do mobile first, and then do whatever magic is needed to make the theme work on other screen sizes. Not so for me. My initial design was for a full-size computer screen, which I then modified to work on a mobile screen.
In 'laying out' the page to be displayed, I have used a variety of techniques. When I first started designing web pages I used tables; that tells you how long ago that was. Then, with the advent of stylesheets (and CSS). CSS saw me starting to use 'floats' to position things on the page. That soon got messy so I started to use other people's framework, and for a sometime I used Foundation.
However, such frameworks (be it Foundation or Bootstrap) seemed to be something of an over kill, and pretty heavyweight. That together with the steep learning curve saw me abandoning other people's frameworks and using my own based on
But things have moved on since flexboxes became popular, and now we have
CSS grids. So, I've bitten the bullet and have spent some time learning how to use them.
The first phase creating a new theme is complete. The site renders "ok", and I am pretty pleased with how it looks. It feels clean and elegant.
Full entry …
My current theme, NewPapyrus, looks rather like a page printed on paper; i.e., like this:
When I first saw a site that looked like this, I quite liked it. However, whilst it does the job, it isn't elegant. It's functional, but I have come to think that, aesthetically, it is lacking. After all, what is the point in replicating paper on a screen?
Looking at typographic sites such as The Ministry of Type, I am inspired to do something different to what I have (and maybe more like them).Full entry …