If you really want to stop using Markdown to write with, then the best solution will be to use a proper conversion tool to turn these into word processing documents, such as DOCX or ODT, and then import that into Scrivener. I don't think (without plugins anyway) that Obsidian has any way of making this easier, but a good general purpose tool for this is Pandoc. Source: over 2 years ago

Properly written code, there are documentation tool like this for Angular and others. Https://compodoc.app/. Source: over 1 year ago

Compodoc is a good tool for generating docs for an angular project. The documents generated also includes visual maps of dependencies. Source: over 1 year ago

App documentation, here is compodoc (https://compodoc.app/) It is generated when the dev does a git commit and build in the pipeline. Source: over 1 year ago

✅ Angular 14 ✅ Angular Material ✅ Unit Testing with Jest ✅ End-to-End Testing with TestCafé ✅ Internationalization with Transloco ✅ Auto documentation with Compodoc ✅ Analyse your project with source-map-explorer ✅ Docker ✅ ESLint ✅ Prettier ✅ Commit Linting. - Source: dev.to / over 1 year ago

Finally, we have come to a point where we want our JSDoc comment documentations to turn into a full scale documentation website, which we can share with new developers instead of providing lengthy Word documents, or which can be used by the team to search for explanations and direction during development. Thankfully, there are amazing tools that help us build such sites easily, with just a console command. Today... - Source: dev.to / almost 2 years ago