
Ubuntu Studio’s web presence has been spread across several Canonical-hosted systems for a long time: the main website on an old Canonical web server, the Ubuntu Community Help Wiki at help.ubuntu.com/community/UbuntuStudio, and the Ubuntu Developer Wiki at wiki.ubuntu.com/UbuntuStudio. Those platforms served their purpose, but each had become a poor fit for how the project actually works today.
What’s Moving
The main Ubuntu Studio website has already moved away from Canonical hosting and onto its current home. That move was driven by necessity: Canonical shut down the old web server that had hosted the site, so Ubuntu Studio needed a new home for its primary web presence. This has been a mostly transparent process and most users would never have noticed a difference.

The Community Help Wiki — the place where users have always gone to find answers about audio configuration, hardware support, the Audio Handbook, and getting started with Ubuntu Studio — is being mirrored and maintained directly on ubuntustudio.org at /help/. Every page you’re used to is coming with us: the Pro Audio Intro, the Ubuntu Studio Audio Handbook and all its chapters, the FAQ, hardware support information, terminal basics, troubleshooting guides, and community information. Most of this is outdated now, and we need help to bring it up to modernization.

The Developer Wiki — home to the team’s internal processes, release planning, testing documentation, artwork resources, and packaging and development notes — is moving to ubuntustudio.org at /wiki/. The full section structure is preserved: Testing, PR & Support, Artwork, Packaging/Development, Documentation, and Organization are all there. This information is also outdated.
Why Now
The website move and the wiki move do not have exactly the same origin.
For the main website, the trigger was straightforward: Canonical shut down the old web server that hosted it. Ubuntu Studio had to move the site in order to keep a public home on the web.
For the help and developer wikis, the issue was the editing experience and maintenance burden. The old MoinMoin-based wiki workflow is cumbersome, slow, and awkward to work with. Its markup is not standard Markdown, which makes editing, reviewing, and migrating content more difficult than it should be. Over time, that friction made it harder to keep pages current, fix outdated instructions, and encourage casual contributors to improve documentation.
Meanwhile, ubuntustudio.org has been running on WordPress for some time, and the team has been using GitHub for development work. By routing our documentation through a GitHub repository — using the Git it Write plugin to publish markdown directly to WordPress — we get something we’ve never really had before: a documentation workflow that fits naturally alongside our other development work. Pull requests, issue tracking, version history, and a low barrier to entry for new contributors all come with it.
What This Means for Contributors
If you’ve ever wanted to fix something on the old wiki and been put off by the process, this is your opening. The content lives in a public GitHub repository. Find the file, fix the text, open a pull request. That’s it.
The content is organized into buckets that map to the old wiki structure:
help/content/support/— support pages (FAQ, hardware, audio configuration, etc.)help/content/handbook/— the Audio Handbook and Pro Audio Introhelp/content/community/— IRC, mailing lists, joining the teamhelp/content/reference/— resources, links, wiki guidewiki/content/ubuntu-studio/— developer wiki pages
If you’re editing a page that has outdated information, and there’s plenty of it, particularly around the old PulseAudio/JACK workflow that predates PipeWire — this is the place to update it.
What Isn’t Changing
The old wiki pages at help.ubuntu.com and wiki.ubuntu.com aren’t going anywhere immediately. Canonical maintains those as part of Ubuntu infrastructure, and they’ll continue to exist. Our goal isn’t to break any existing bookmarks or search results, it’s to have a home where we can keep things current.
We’re also not rewriting the documentation wholesale. The content of the mirrored pages is as faithful to the originals as it can be, with updates where the old guidance referred to software or workflows that no longer apply to current Ubuntu Studio releases.
Where to Find Everything
- Help pages: ubuntustudio.org/help/
- Developer wiki: ubuntustudio.org/wiki/
- GitHub repository: github.com/UbuntuStudio-Official/ubuntustudio-website
If you find something wrong, missing, or out of date — open a pull request, or file an issue and let the team know.


















