>>For the Crown Jewel case KISS benefit of SFTP server and protocol still stand from my POV.
>>
>>Gitlab/versioning as replacement for WebDAV is a thought I somtimes mull,
>>coupled with switching from Word plus PDF to MarkDown to view changes in pure text.
>>
,,,,
>>Nextcloud DOES include versioning, although less refined.
>>I might return to the topic AFTER manging the switch to MarkDown
>>
>it was ironic. You know, the problem with the hammer as only tool known and anything looks like a nail.

I was aware of >0 tongues in cheek.

The idea of more KISS documents had surfaced a few times here, esp. as we had a problem 2y ago in Nextcloud, where all documents were triple datestamped to same minute.
We know that MS Office in newer versions allows collaboration + version control, but in practice this still is a bumpy road whenever external stake holders or collaborateurs need to stir the stew - special formating killed, usage of mobile devices, versioning - still a PITA.

With one company we use Word with changes marked, with another Postscript MarkedUP, a third needs new document with page references, last wants Comments in PDF.

Our needs beyond (solved) including graphics are relatively simple:

create/change paper layouts to output to PDF

KISS (GUI?) way to define + apply specific font groups, (CSS or class with property settings)

easy way to include (link?) table data from Excel (or a cursor)

less important: include presentation data (PowerPoint, but less need for specific tool)

uncertain if WYSIWYG should be targeted (pingback from MS Word for DOS usage)

mailmerge probably special case, might make sense to use Excel or Word...

and get version control ease as en passant benefit. But this will lessen DNDRY (dumb non DRY) effort only if there is no repeated import/export to Word, but MD as standard plus PDF as defined "publish" end result.

No wish to add pandoc setting + output check expertise into needed skill set to create and edit texts ;-)

So consolidating on MarkDown would be great, but is *not* greeted with enthusiasm elsewhere (not even everywhere "inhouse"). Reducing the need to create "documents" would be even better, but the bureaucratic gods are strictly against such mindsets.