Thank you for your efforts in documenting FTV. I’m open to accepting help with this.
But: Providing a wiki page that that isn’t clearly identified as a draft requires regularly updating the page. Since FTV has many options, keeping the documentation of those options up to date and complete will require a lot of work. People may become confused if the wiki page is not up to date in case the development is faster than updating the wiki page. Also, a finished-looking wiki page may suggest that the addon is finished and stable. However, it is definitely not finished yet. Any update may cause it to become (more) unstable, as there are currently no Pull Requests with reviews in order to publish new features early for testing of new beta versions.
Some things can be documented now because they won’t change much. However, there will be some things that will change in the future. It doesn’t make much sense to write detailed and comprehensive documentation yet, but if you are motivated you can write the documentation somewhere else (e.g. on a Users page or in a file on your computer). Once no more major changes are planned, your prepared draft documentation can be copied over to the main page, which will then also be linked in the addon. If you create a Users page on the wiki, make sure to add a warning that your version is a draft.
From my point of view, what is actually doable right now is adding a section to the wiki page that lists solutions to problems, answering questions like “Which configurations do I need to change to achieve …?” This is somewhat the opposite to the usual way of documenting configurations, which answer questions like “What happens when I change this configuration?”. I think it’s much more efficient in terms of the effort required to document (and update) it and the value for the user. As long as the main wiki page clearly states that the addon and the wiki page are works in progress, this would be okay in my opinion.