Add automated API docs #27
Labels
No labels
bug
config
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
orinoco/shacl-vue#27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Look into JSdoc; https://github.com/psychoinformatics-de/shacl-vue/pull/26/commits/863e84c825cf1ff8c858c9255b382ebfa6f2879e already has a single example of a jsdoc-based docstring for a module.
For an html theme, investigate:
JSDoc can be used for api documentation.
For general user and developer documentation, I have decided to go with Vitepress, since it's compatible with vuejs 3 and powered by vite tooling which is already used for the build process of this package.
With
f432d21b86todf848e252cwe now have a setup for docs that are deployed together with the demo shacl-vue application (at/docs) via github pages.The only step left to figure out is how to use jdoc for api doc generation and then make the resulting pages part of the docs generated by vitepress
Could aim to get a script that runs through vue components, generates markdown from their jsdoc-style comments and docstrings, and then adds those markdown files to the sources for vitepress to build the docs site from.
Look into:
Most recently maintained theme for jsdoc that I could find is https://github.com/ankitskvmdam/clean-jsdoc-theme. The default jsdoc theme looks really bad.
Docs are currently built on PR/merge and deployed to github pages. The missing piece remains autogenerating Javascript API docs from docstrings. Also, with the refactoring and separation of
shacl-tulip, the idea is to include its docs (mainly API) into a subsection ofshacl-vue