Thanks! 🙂 I actually considered that approach at first, but ...

Raw JSON

{
  "kind": 1,
  "id": "0a68054e01070516014adea11100271178d3e09470d6560a4b6a659bd3a439f3",
  "pubkey": "9c73236f565eb90bd4681c29ebb2d9c1b80e4e184cdbf84d6da742e990670cb6",
  "created_at": 1775691049,
  "tags": [
    [
      "e",
      "be5cbd0fb068fd58eef567d8fc62bfb8752bb7a831453bb77ba5334540304e32",
      "",
      "root"
    ],
    [
      "e",
      "bbef2d3205d99ed7531854eecc9ff303a007db4f9dac1a0c53d57023681fdb76",
      "",
      "reply",
      "fd2ee25fd0ef442aa1b7404a9354b12e554ec0dead81a6c8bdb8cda2ff09373f"
    ],
    [
      "p",
      "78aa9a1b854547293006a8af7996f3181ad0e05fc5c157458f74f558bf8789ee"
    ],
    [
      "p",
      "9c73236f565eb90bd4681c29ebb2d9c1b80e4e184cdbf84d6da742e990670cb6"
    ],
    [
      "p",
      "fd2ee25fd0ef442aa1b7404a9354b12e554ec0dead81a6c8bdb8cda2ff09373f",
      ""
    ],
    [
      "client",
      "nostria"
    ]
  ],
  "content": "Thanks! 🙂 I actually considered that approach at first, but decided to do it the “hard way” and learn everything from scratch 🎸\n\nOnce I realized how many small pieces of the album feed need updating for every release, I took it a step further and built my own offline album feed generator. It auto-fills the parts that never change (in the backend), pre-populates form fields for track durations and defaults for things that rarely change, and leaves clean fields for what needs updating each time. When everything’s filled out, it displays the full code and generates a correctly named XML file for download.\n\nI also wanted the XML to be as clean and human-readable as possible (and sneak in a bit of personal branding), which added some extra complexity. But now it’s (hopefully) working exactly how I envisioned.",
  "sig": "5ffffb2f63361a53b6e87f0703750aefbef1abed924c00195f5729354047fc70db44ac645b0917f34ab94b7d66d971c6de389c3e7e988e11642fe23409d3bb81"
}