Integrate fetched contents (Editionsmodell, Transkribus-Dokumentation)?

[pdaengeli]

I set up an action that fetches the two hackmd notes four times a day. Primarily this serves as a backup, but we can also consider to integrate the results in the Vitepress docs.

• decision: (at what point) does this make sense?
• structure: currently content is pushed to hackmd-backup/_fetched; likely this should be moved to some place under src
  • there was the plan to put Transkribus-related material in block A and the edition model in block B (see parent issue Documentation: workflow #2)
• improve styling: GH md rendering doesn't do a great job with hackmd rendering; we'd need to see how it looks in Vitepress (perhaps need to enable some extensions)
• communicate character of the documents: we should flag these documents as externally-sourced to make clear that they may lag behind by some hours and to prevent manual editing

[cforney]

I suggest this structure:

.
├─ src
│  ├─ _fetched
│  ├─ index.md
│  └─ ...
└─ hackmd-backup
   └─ process-hackmd.xsl

That is:

• hackmd-backup/_fetched goes to src/_fetched
• process-hackmd.xsl remains in hackmd-backup

[cforney]

Moved content generated by hackmd-backup to src/_fetched and updated the worfklow accordingly.

Note that hackmd-backup/_fetched is still used in the action as a scratchpad.

Further, I quickly added these contents to the app. The markdown rendering looks already good, even if some details need to be adjusted.