3 ms·
Some of the options I’m considering: 1) Moving everything to git, and having MKDocs as the source of all documentation for the project. I’m not convinced this
by chrismcv 8y ago
Some of the options I’m considering:
1) Moving everything to git, and having MKDocs as the source of all documentation for the project. I’m not convinced this will work well on the Requirements phase. Versioning would be done with git tags. And I suspect it will requirement techie effort to get up the point of being useful, while alienating our less technical (or more entrenched in MS solutions) staff members.
2) JIRA + Confluence - seems to integrate the Requirements + Design more tightly, though not sure about delivery of versioned documents to client.
3) Stick with Word + Sharepoint - which I loath.