Which way to create content for the terms (wiki)

[henkvancann]

Steven Milstein

3:59 PM
I have a few questions.
I can't find any GitHub API documentation for their Wiki.
I don't see any Terms - like https://github.com/trustoverip/acdc/wiki/agency markdown files in the repo. Am I missing something?
Since this is under KERI & KERI is not under ToIP, shouldn't all the documentation be at https://github.com/weboftrust?\
Would you be open to using hackMD.io as the editor?
a. We would link it to the GitHub repository for version control
b. All the content is in markdown
c. It's accessible via GitHub's REST API and GraphQL
d. It's easier for non-GitHub users to collaborate
e. It's got inline commenting, which is easier than creating Issues & Comments. We could use that later if we need something more formal.
f. We could create a simple hackMD.io Book, so the content is more accessible

[henkvancann]

Henk van Cann
5:23 PM

• 1+2 Wiki is a strange thing under Github. You can clone the .wiki and then you have all the .md files.
• 3. Yes, eventually I will get it there. But I also want cooperation with ToIP.
• 4. I do use it sometimes (agenda + documents). For single term-definitions I get too many files, not practical.
     a. yes, known way to version
     b. same for Github. I use a linter in Vscode
     c-f. let’s discuss how to overcome my main objection “too many files” and I am in for advantages like this.