Automated docs#71
Conversation
✅ Deploy Preview for biongff-vizarr ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
can I suggest having a typedoc.json at root level like {
"entryPointStrategy": "packages",
"entryPoints": ["./*"], // or ["viewer"]
"packageOptions": {
"entryPoints": ["src/index.tsx"]
}
}and the typedoc.json in viewer like {
"projectDocuments": ["introduction.md"]
}so that we can have a command in the root package json to build the docs |
| @@ -28,6 +28,8 @@ | |||
| "@vitejs/plugin-react": "^4.3.4", | |||
There was a problem hiding this comment.
Could we add a docs:build script to package.js to standard how the docs are built?
There was a problem hiding this comment.
Also, could you add instructions to the contributing guide about how to build and check the automated docs after changes are made?
| @@ -0,0 +1,33 @@ | |||
| --- | |||
There was a problem hiding this comment.
I think we can expect there to be several static content pages for the documentation website. Instead of putting these in the viewer root (which might get cluttered), could we perhaps move these into docs, and move the build directory to docs/build, which can be excluded in .gitignore?
✅ Deploy Preview for biongff-vizarr ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Description
cd viewer
npx typedoc --plugin typedoc-github-theme
Fixes # (issue)
Related to # (if applicable)
Type of change
Checklist
npm test)pre-commit run --all-files)