Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Subject: Re: The brick and mortar
From: "mieum" <mieum@namu.blue>
To: "Arav K." <nothien@uber.space>, "Callum Brown" <callum@calcuode.com>,
 <~mieum/booksin.space@lists.sr.ht>
Date: Mon, 02 Nov 2020 21:55:45 +0900
Message-Id: <C6SSLF9F0X0D.3JILVV5D9W7X3@maclibre>
In-Reply-To: <C6SNUFB650FV.33Q9XOEYIFX53@gux>

Arav, thanks for all your effort and input :) Your sketch helps
visualize how to start building this thing. I have a few questions and
comments in response:

1. Should the source files for the capsule builder be included in the
   repo, or should that be put into its own project repo elsewhere? I'm
   not really sure how the sourcehut builds system works or how to plan
   around it :)=20
  =20
   But as far as update intervals goes, I don't know that
   something such as this would require being updated frequently. I
   wonder about how many more resources this would require (not just the
   server, but also on sourcehut's end). Alternatively, couldn't the
   server pull the changes in response to a webhook, and then have a
   rebuild triggered if changes are merged?

2. For texts with multiple authors, there should be a way to ensure that
   a mutli-authored text is included in the indexes of each of those
   individual authors also. It seems like this would be trivial to
   implement when building from the metadata.

3. Will this require a database, or would it suffice to just source the
   data and metadata directly through the source directory structure at
   build time?

4. This one kind of relates to #1, but shouldn't the git repo include
   some sort of yaml template that includes all the necessary and
   accepted fields? Perhaps there should at least be a msc/ or meta/
   folder containing stuff like that...?

It seemed like there was more I wanted to ask about, but I'm too groggy
to remember. Anyway, thanks again, Arav. I'm hoping that this week I
will have a chance to start getting some code together (by the weekend
at the latest).=20

~mieum