resources: keridoc-how-we-did
This data as json
| id | type | name | url | maintainer | status | last_checked | date | year | level | evidence | access | abstract | authors | series | chair | minutes | recording | media | decisions | version | language | license | release | pushed | depends | since | via | summary | note | has_abstract | has_summary | kind | sector | country | products |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| keridoc-how-we-did | site | KERIDoc: How we did (how the sites were built) | https://weboftrust.github.io/keridoc/docs/how-we-did/intro | Henk van Cann, WebOfTrust | quiet | 2026-11-02 | practitioner | informative | public | The section of KERIDoc on how its maintainers built the sites: installing the repository, the Docusaurus process and file system, writing a page, loading the glossary, the Terms WOT manage sheet, GitHub Actions, the Kerific extension and Discord bot, building the KERISSE search index with Typesense, and the IP rights of scraped sources. | kerisse | 1 | 0 |