{
  "$type": "site.standard.document",
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreihgyjlt4szf4vjy4aswx2jaopaunwhtx2ie76hwh2wotpj6eoxpnm"
    },
    "mimeType": "image/webp",
    "size": 14784
  },
  "description": "Finally realized the point of standard.site. I’m now publishing standard.site documents. These link back the Quartz generated website.\n\nIts purpose is a little bit like RSS for a comparison.\n\nI tried existing tools, but they didn’t work well for the rather unique [[Quartz]] setup I have. I built my own tooling for it.\n\nSequoia seemed promising bu...",
  "path": "/Journal/2026-06-11",
  "publishedAt": "2026-06-11T21:13:03.809Z",
  "site": "at://did:plc:rfescy2ghdk6ma2wwwhr3bu2/site.standard.publication/3mktkmfk37k2g",
  "textContent": "\n- Finally realized the point of *[standard.site](https://standard.site/)*. I’m now publishing *standard.site* documents. These link back the *Quartz* generated website.\n  - Its purpose is a little bit like *[RSS](https://en.wikipedia.org/wiki/RSS)* for a comparison.\n  - I tried existing tools, but they didn’t work well for the rather unique *[[Quartz]]* setup I have. I built my own tooling for it.\n    - [*Sequoia*](https://sequoia.pub/) seemed promising but it had issues.\n      - `draft` field override was ignored.\n      - `title` is required, otherwise it’ll default to “undefined.”.\n      - Frontmatter is required. If missing, it would emit errors.\n  - It took me a long while to understand this. While `site.standard.document` records can store an editable copy of its documents. This isn’t required and its `content` field does not have a concrete standard. It’s intended for editor/viewing platforms like [*Leaflet*](https://leaflet.pub/reader).\n    - This means that I’m not using *standard.site* as a means of synchronization. I already have too many forms of synchronization for the *spacious nexus*.\n      - Though, I am just putting raw markdown for the `textContent` field. It could be possible to restore some data and file hierarchy with the `path` field. It’s not something I would rely on, but they're here just in case the *Git* repositories explode, somehow.\n- [x] ~~*Quartz* generates cover images. I should use those.~~ Done.\n- I’m getting the idea that I should try out *Quartz 5*.\n  - Supposedly, it’s more extensible. Should refer back to [[Journal/2026-05-26]].",
  "title": "2026-06-11"
}