You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now both kinto-http.js and kinto.js use doc.esdoc.org to publish their documentation. ESDoc is, unfortunately, not very TypeScript friendly, so I've been planning on switching over to TypeDoc. However, we'll need a place to host the documentation.
Currently, the gh-pages branch contains the demo for the two projects. I propose that we publish the TypeDoc generated documentation to the gh-pages branch using a GitHub Action when we tag a non-pre-release from master. I haven't looked into it yet, but I'm fairly sure we could still host the demo as a part of the generated TypeDoc documentation.
Right now both kinto-http.js and kinto.js use doc.esdoc.org to publish their documentation. ESDoc is, unfortunately, not very TypeScript friendly, so I've been planning on switching over to TypeDoc. However, we'll need a place to host the documentation.
Currently, the gh-pages branch contains the demo for the two projects. I propose that we publish the TypeDoc generated documentation to the gh-pages branch using a GitHub Action when we tag a non-pre-release from master. I haven't looked into it yet, but I'm fairly sure we could still host the demo as a part of the generated TypeDoc documentation.
@leplatrem What do you think?
The text was updated successfully, but these errors were encountered: