6 ms·
So there are engineers building component CMSs for Markdown to help engineers edit product docs, and there are product people building component CMSs for DITA X
by starkparker 28d ago
So there are engineers building component CMSs for Markdown to help engineers edit product docs, and there are product people building component CMSs for DITA XML to help product people edit customer docs, and never the twain shall meet because an engineer would rather jump into a burning building than share a repo with DITA XML. Even when there's an interface layer on top of it with features that are fully indistinguishable from this product.
The future is batshit. I hate DITA and I still think this is deeply funny, in the same way as falling into my own grave and realizing they're throwing dirt on me would be funny.
- deleted 28d ago[deleted]
- deleted 28d ago[deleted]
- anetrebskii 28d ago[dead]
- anetrebskii 28d agoTotally agree. The fight is still on. It's my only attempt to bring these two worlds together, taking into account the AI era where people generate MD files. My approach is to get the product team to use a Git repository by providing them with a tool that allows them to work with MD files as they would with Google Docs: sharing a link for easy opening (like Zoom), comments, and a nice editor, and completely hiding Git. I personally use Spec Kit for writing specifications for future AI coding, and many people (not only engineers) are doing the same and generating different documents in MD using AI. However, the biggest issue is that people are trying to find an editor to work with generated MD files or push them to another storage via SCP/CLI, which doesn't work as well as local MD files. I would be happy if it helps some teams as it did for me.