3 ms·
You made your non-tech staff write Markdown files? How did that go? Also, about contracts — .doc/.docx is lingua franca. How did you deal with collaborating wit
by gcv 13y ago
You made your non-tech staff write Markdown files? How did that go? Also, about contracts — .doc/.docx is lingua franca. How did you deal with collaborating with the rest of the world?
- hunvreus 13y ago1. We wrote a WYSIWYG for Markdown (https://github.com/Wiredcraft/Moleskin https://github.com/Wiredcraft/Moleskin). Also, everybody learns Markdown at Wiredcraft. 2. Actually, the standard would be PDF for legal documents (never understood why people send you a contract in a format that is easily editable). The tool we're currently building allows you to use our WYSIWYG to collaboratively edit documents online while keeping Markdown in the backend.
- icebraining 13y agonever understood why people send you a contract in a format that is easily editable All formats are easily editable; contracts should be digitally signed to prevent shenanigans.
- gcv 13y agoThe final version of a contract is certainly PDF, but during negotiations, people must be able to make and track edits. Git has these features covered, but I just can't imagine sending a Markdown contract draft file marked "FOR DISCUSSION ONLY, NOT INTENDED AS A BINDING CONTRACT" to a typical counterparty. I guess that your WYSIWYG editor might do the trick — it depends on the extent to which your counterparties rely on MS Office tools.