A decent help manual would be good. If you want to know how to use something the present help page is useless. For example, in the view options, how do use use the additional colours? Should be simple but cannot find what purpose they serve. Not a geek or techy unfortunately. The Help page is hopeless.
I agree, but it takes a lot of time and effort to update.
Will be done as time permits. We do have real jobs as well.
Users have problems with MMEX undocumented features - example here. We really need good doc writer!
I noticed that there was a request for documentation help in this thread, and I wanted to offer my help. While my coding skills are extremely basic and I could not contribute code, I would be happy to work on documenting any features that are undocumented or need work.
I would probably need a little help pointing me in the right direction (i.e. features needing work) and probably need to interface with the developers to ensure content accuracy to get started. Please let me know if you are still in need of help!
@forger125 the best interface is to use git and pull requests. Change or add some information into help page then make pull request. All others will see changes and accept or refuse it.
Other option is to create small wiki pages. Something like how to, for example, currency update, find transaction etc. Then we can rewrite help pages using this info.
@vomikan Thank you for the helpful info. I'll try to work directly on the pages found in the docs folder and submit pull requests to those. Are there any particular features or additions that are especially in need of documentation (the forum link earlier in the thread times out for me)? Otherwise, I will begin looking through the documentation and pull requests/changelog for a place to start. Thank you again!
As I have been looking through the documentation, I had a thought that I was hoping to run by some contributors (e.g. @slodki or @vomikan). Since the docs are essentially local HTML files, would a more featureful approach to documentation be using a static site generator such as Hugo with a documentation theme (e.g. Hugo Learn)?
Some pros to this approach would be:
As for cons, this would make the documentation toolchain more complex by adding another software element into the mix, and could potentially make resolving documentation issues more challenging if static site generator debugging was involved. Also, this would require maintainers to have some knowledge of Hugo. Just wanted to offer it as a suggestion, and in the meantime I will continue working on the documentation as is :smile:
Hi
I've involved a lot of contributers into translation https://crowdin.com/project/moneymanagerex
And commit bulk changes regarding this
Related case https://github.com/moneymanagerex/moneymanagerex/issues/1933
I am afreid it may be conflict, bur please be patient. I any cases your updated will be included.
I cannot see duplicate issue related to features to be described in user manual...