- Finally realized the point of standard.site. I’m now publishing standard.site documents. These link back the Quartz generated website.
- Its purpose is a little bit like RSS for a comparison.
- 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.
- Sequoia seemed promising but it had issues.
draftfield override was ignored.titleis required, otherwise it’ll default to “undefined.”.- Frontmatter is required. If missing, it would emit errors.
- Sequoia seemed promising but it had issues.
- It took me a long while to understand this. While
site.standard.documentrecords can store an editable copy of its documents. This isn’t required and itscontentfield does not have a concrete standard. It’s intended for editor/viewing platforms like Leaflet.- 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.
- Though, I am just putting raw markdown for the
textContentfield. It could be possible to restore some data and file hierarchy with thepathfield. It’s not something I would rely on, but they’re here just in case the Git repositories explode, somehow.
- Though, I am just putting raw markdown for the
- 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.
- Quartz generates cover images. I should use those.