I would like to compliment the operating system developed by the Solus team, which I think has been excellent. However, I note that much documentation is lacking on many parts. The little they have is greatly simplified. Wouldn't it be a case of giving the community a way to collaborate on documentation to make the Wiki quite complete, such as Arch Linux?

    emersoncavalcanti1972 Wouldn't it be a case of giving the community a way to collaborate on documentation to make the Wiki quite complete, such as Arch Linux?

    I don't want a wiki on the same level as Arch Linux, I would much rather people contribute to documentation for the respective project they're looking for. People can already contribute to the Help Center documentation via GitHub, however it is currently undergoing a rewrite (the Help Center itself is undergoing a redesign, feel free to look at our latest blog post where I talk about that) to facilitate improved documentation writing and discovery.

        At risk of being nasty (I risk that), yet another place that people won't look for information (sadly). True, some few would use it, but the vast majority seem to think that even searching the forum is too much trouble.

        emersoncavalcanti1972 but some programs need a little more than the store to install.

        Then why would we have documentation for it. We don't need documentation on how to use our Software Center and we already have docs on our package manager. Seems completely unnecessary.

          What I am commenting on is complementing what is already done on the Wiki itself. Installing PHP has some peculiarities, for example, and if it is documented, simplifies the work of those starting out with the distribution. Yes, you can access the forum, but if you already have the documentation, avoid questions in the forum. I'm talking about supplementing the documentation, just as it is already on the site itself. See HTTPD. This is already documented and is enough for those just starting out to be able to install. The rest can be found in the manufacturer's documentation. Following my example, Apache is one of the possible servers. We have NGINX which is available in repositories and for which we have no documentation.

            emersoncavalcanti1972 See HTTPD. This is already documented and is enough for those just starting out to be able to install.

            We have specific documentation for httpd on the Help Center because it is stateless and doesn't come with configuration for PHP support OOTB, because that doesn't really make sense for a desktop development environment where people may not even be using httpd with PHP. For nginx, it already comes with the configuration necessary and is not fully stateless, all documentation online provided by nginx, for nginx, basically holds your hand, so it isn't necessary to document it.

            Just because we have something in the repo doesn't mean it needs to be documented.

            emersoncavalcanti1972 Yes, you can access the forum, but if you already have the documentation, avoid questions in the forum.

            Yea no, people still ask questions on the forums regardless of how much documentation we provide.

                4 months later

                I think a wiki is a good solution because the help documents will grow and it will be difficult to navigate.
                There is also the habit of searching on a search engine, the wiki is easier for searching.
                example: "solus installer wine"

                  choub24 Not really something we are interested in supporting. Wikis require a lot more effort to moderate and our goal isn't really for the Help Center to be a kitchen sink. It's only meant to contain documentation that is specific to Solus and not general information about how to use Linux or certain applications.

                    a year later