![]() ![]() As a result, around 90% of Audacity users were using web search engines such as Google to get help with Audacity, where more user-focused content from third parties massively out-performed our manual (the average manual page gets about 180 clicks per month). ![]() Thirdly, it was written to serve a dual-purpose: being both a developer reference as well as a user manual, which made it quite complicated – a problem exacerbated by not having a search function. Apart from being an unnecessary release blocker, this also meant that any corrections or optimisations to the manual could only be published whenever a new version of Audacity was released. Secondly, the manual was being packaged with the installer, which meant that it needed to be completely up-to-date prior to a release. Consequently, it has also not been translated in quite a long time, which we feel is a big disadvantage. As a result, the number of active editors has been very small (around 3 or 4 people). The existing system is built on MediaWiki, which unfortunately comes with a lot of trouble attached that limits its overall usefulness: For example, due to spam problems, it has not been open to contributions from the public for a long time. In this post, I want to introduce our plans to create a new online manual, which we intend to replace the current one found here.įirst, it is worth explaining why we want to replace the existing manual, which has been meticulously kept up-to-date by a handful of dedicated contributors. ![]()
0 Comments
Leave a Reply. |