Closed kinsidar closed 6 years ago
@kinsidar, Move the documentation to a permanent branch on VSTS. Work out what is needed. Document it.
@peterennis
I think the problem with that is that since we are using github pages to host the documentation page, if we move it to VSTS branch we would not be able to do that.
Would it be feasible to create a repository just for SVIPDB documentation page?
@kinsidar Look at this: https://marketplace.visualstudio.com/items?itemName=hoyt-tian.gitbook-kit
See if it works well with VS code.
@kinsidar, You are invited to SVIPDOC as a collaborator. Put the documentation there.
Thanks! Will move the documentation there.
Currently we host the SVIPDB documentation on this repository, resulting in many commits that are not related to Association-Contacts.
Should we move the documentation to a fork of SVIPDB on github?
@peterennis