@dev1 , something is disappointing here:
> Parts of this documentation were created with the assistance of AI tool, all AI-generated content has undergone review, but it may still contain inaccuracies, omissions, or outdated information.
(quote from https://github.com/ich777/mos-docs/blob/master/README.md )
Thanks for the feedback. We’re overhauling the docs right now. Sorry for the inconvenience.
@ich777 , actually do you need any help with documentation?
I’m always open for help since we are a small team, basically me for the System/Backend/API and another person for the Frontend. The docs are currently maintained by another user who is currently exploring other, maybe more eye pleasing possibilities.
Here is the staging from the new docs: Github: https://github.com/J000K3R/mos-docs-staging Preview site: https://j000k3r.github.io/mos-docs-staging (but do keep in mind that they are possibly a bit outdated)
@ich777 , because there is no “issues” module in https://github.com/J000K3R/mos-docs-staging, let me ask here: could you please add a license information to the repository https://github.com/J000K3R/mos-docs-staging 🙂
Sure, we can add that but please keep in mind this is just a temporary repo where J000K3R tries things and that’s why there is no LICENSE yet, but he already added it while I write this here. When the repo is migrated over to https://github.com/ich777/mos-docs the LICENSE will be updated.
deleted by creator
