Improve "Helm" and "Rancher" sections of the documentation about website

[Ornias1993]

Documentation is a "feel free to fix it yourself" section of the project.

On topic:

• As stated in the news articles there is not official Rancher support at this time.
• Helm support is "like normal", we're not likely to offer much step-by-step advice on it, as we need to assume the users knows how to use helm.
• The currently given info on the common chart, combined with the values.yaml files, should give more than enough information on deployment options for users with experience with using Helm
• It's not true that only SCALE is supported, Helm is a fully supported platform within the project.

[robotcorner]

So is there a rough timeline on rancher?

I get the strategy is fix it yourself with some of these things. However, the effective rate a maintainer could enhance the documentation is way way quicker. I just thought the sections needed a little love is all and the idea that the general user is going to write the documentation doesn't make a lot of sense if you think about it.

Also now that we can't suggest these thinks in github to track then (idk what the point of a feature request on it is) and we can't suggest new apps on github anymore how do these types of request get properly tracked and supported eventually. Just because I'm the first one to voice something doesn't mean I'm the only person thinking it and if there was at least a place for the community to track these kind of nice to have request and app feature suggestions then that would be nice because the one platform we used to track these things in (github) you don't want requests in. Discord is a messaging system and is not sufficient for tracking such work through inception to completion (at least for app work and requests), we need a tacking sheet or something if were not using github for that kind of stuff.

[Ornias1993]

Let me clear some things up:

1. Rancher is not a supported platform
2. Maintainers are not payed and often have more important things to than write docs for platforms that dont have docs yet.
3. we dont track requests because: they do not get made. There is no reason to track them, zero. 99/100 times a chart is build is because someone needs it or right when the request comes in. The tracker did not actually get used at all.
4. Having a tracker for docs makes no sense, it would end up with 9999 issues no one is going to bother with.
5. The community is perfectly able to write docs, they do so all the time. But if you want something fixed, you’ll also have to yourself

Also: its not faster for maintainers most of the time.

[Ornias1993]

Simply put: chart request where just a garbage dump that never got any maintainer attention, because we never intended for it to get any.

there where flooding the github with issues that only existed to give people a place to dump them into.

[Ornias1993]

Im leaving this issue, but considering how much this is derailling ill lock it.