Consider a separate repo for website copy

[simonwiles]

It might make most sense to have a nice clean repository of markdown files with a flat hierarchical structure to make copy editing/updating easier for folks.

[mbingenheimer]

Is that to be created or are you suggesting to have existing repos like this. Do you mean the csv data too is in md?

…

On Tue, Aug 15, 2023 at 10:57 AM Simon Wiles ***@***.***> wrote: It might make most sense to have a nice clean repository of markdown files with a flat hierarchical structure to make copy editing/updating easier for folks. — Reply to this email directly, view it on GitHub <#4>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPUBNXQ3KDOSMY6NGO2ATTXVLQQHANCNFSM6AAAAAA3QQRF4Y> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Dr. Marcus Bingenheimer 馬德偉 Department of Religion, Temple University Visiting @ Chinese Studies Department, National University of Singapore until 2024 https://mbingenheimer.net <https://mbingenheimer.net/publications/publications.html>

[simonwiles]

Right now I've set up a folder in the repo at content/ which contains files for the text-only content of the site. The idea is to make a clean separation, so that anyone who wants/needs to edit the verbiage can do so while engaging with as little code as possible. Since the architecture for the site involves assembling pieces from multiple repositories already, however, I was musing about taking it one step further and just having a repo with nothing but those files in; it might be cleaner and less potentially confusing, and would permit a separation of privileges too, for what that's worth.

(I'm sorry if you got notified for all these "issues", btw -- I was just setting up what is effectively a todo list of sorts using a "project". I often do this just locally when I'm developing alone or with non-GitHub folks, but I figured since we're going to use this platform together from across the globe I'd go all-in 😁.)

[simonwiles]

My next step is to create a 01-temples_inbangkok_mb_data.yaml file which
has the additional data from my spreadsheet. While all projects on
this platform have a GIS aspect for now, this additional data associated
with the points will obviously differ from project to project. Not sure how
to deal with that, but using yaml for it is a first step.

Yeah, I'm not 100% settled on this, but right now I'm leaning towards a folder with the same name/id as the csv file (i.e. 01-temples_inbangkok_mb_data in this case), and in that folder a separate .yaml file for each site, named with the id (e.g. bt-mb-0001.yaml etc.). The contents can then be determined (and iterated on, if necessary) in a very flexible fashion without breaking the site or needing to worry too much about what other datasets are doing.

Do you prefer different files? Aren't sections marked:
---
something
...
equivalent?