Add more docs for FE, Link to BE docs

[chubetho]

Notes: Backend docs is now linked but not reliable

Run npm run docs to see result

[chubetho]

Because tsdoc to markdown package is currently not support TS > 5.0

[twynb]

this same error is also thrown when running npm install on the repo atm - i don't think making users always use npm install --force is a good idea (or good practice)

[twynb]

attempting to run npm run docs crashes for me, with the error no such file or directory, open {path\to\repo}\AudioStreamSplitting\docs\frontend\composables\useConvertSecToMin.md. I'm assuming this is a config issue where no docs for composables/other components are generated, but looking at the vitepress config it seems to try to load those docs.

[chubetho]

attempting to run npm run docs crashes for me, with the error no such file or directory, open {path\to\repo}\AudioStreamSplitting\docs\frontend\composables\useConvertSecToMin.md. I'm assuming this is a config issue where no docs for composables/other components are generated, but looking at the vitepress config it seems to try to load those docs.

Remove tsdoc2markdown now because it does not support ts>5.0 at the moment.
I will find another alternative package or write one later.

[twynb]

The backend docs issue i think should be fixed in a separate ticket (hence me paging alex).

Please fix the composables issue before merging.

[twynb]

this links to the index, but links from the index onwards don't seem to work. i tried renaming one of the backend markdown files so the file name doesn't contain any "."s, which fixed the issue - @4lex0017 is it possible for sphinx to have a different separating character rather than "." for module namespacing? (like "backend-modules-api_service.md" rather than "backend.modules.api-service.md")

[4lex0017]

Nope it is not possible

[4lex0017]

Unless we wirite a script to do it