We’re nearly there! As the finishing line came into view, we’ve hit our second wind and are thundering towards the end of the cycle. In Robert’s last update he announced that we’ve finally moved to the documentation.ubuntu.com domain, which has unblocked us on setting up page redirects from the wiki (so I’ve spent some time doing that). But what else has been going on?
Are you wondering what all this is about? Check out our entire article series:
Ubuntu Project docs
- Bringing together 20 years of documentation
- Ubuntu Project docs: MIR, ACLs, and more
- Ubuntu Project docs update: making sense of the contributor story
- Ubuntu Project docs: welcoming our first contributions!
- Ubuntu Project docs: Will it blend?
- Ubuntu Project docs: Sorting things out
- Ubuntu Project docs: Piloting ‘article series’
- Ubuntu Project docs: Another day at the office…
- Ubuntu Project docs: post pit-stop push
- Ubuntu Project docs: Going (semi)official!
In the last two weeks…
A lot of unblocking happened at once, so there’s been a correspondingly huge amount of work done!
We finalized the Developer Membership Board docs migration (including setting up wiki redirects), and the DMB took the opportunity to submit several rounds of improvements and updates to their docs – as have the MIR team, who have been steadily working on improving their docs throughout the cycle. Thanks to both teams for their continued hard work and engagement with the docs 
Following the successful release of Ubuntu 25.10 Questing Quokka (congratulations to everyone involved! 
), thanks to @uralt from the Release Team who updated the list of releases, which was their first direct update to their new documentation! Thanks also to @ravi-sharma for cleaning up the bug triage page and bringing it up to date!
@rkratky has done a bunch more behind the scenes fixups. One notable quality-of-life improvement he implemented for the bug responses page, in response to a community request, makes it possible for us to selectively soft-wrap inside code blocks. Now that the behaviour matches the old wiki, we no longer need to choose between hard wrapping and endless scrolling!
In addition to all of that, he also implemented a GitHub action to check Launchpad group membership, which means that he has been able to kickstart the migration of the SRU documentation. Not only that, but he also did the initial move of the git-ubuntu documentation. Thanks to the maintainers of both projects for their support in this endeavour!
For myself, (as I mentioned above) I’ve been tracking down and updating as many migrated wiki links as I can find. Some important pages have slipped through the cracks as they were not in the initial list, but also, were not linked to by any of the other pages we’ve moved so far. One such is the bug tags page - thank you @rbasak for bringing that page to my attention!
I’ve also been working closely with the Community Team to migrate their documentation. @aaronprisk and @ilvipero (and friends!) had, over the past couple of years, already done a great job of updating what was previously on the wiki and creating well-structured and usable documentation from that via Discourse. Thanks to their tireless efforts, the docs are already in Markdown and in good condition! 
We look forward to landing these additions over the next two weeks.
What’s next?
Apart from the aforementioned Community, git-ubuntu and SRU docs, Robert and I will be doing a “final sweep” to tidy up loose ends and get us on a solid footing to know what needs to be done next cycle. This means cleaning up remaining references to old wiki links, redirecting pages that haven’t yet been redirected to the new docs, and creating issues on GitHub to point out what still needs to be done. This is where you come in!
How to contribute/get involved
Over the next two weeks, it would be really helpful if you could post issues for:
- Pages you think are useful and should be migrated (but have not yet been)
- Documentation you would have found helpful but wasn’t there
- Pages where something isn’t working as you expected
- General suggestions for improvements
- Ideas for things you think would be “great to have”
If you have the time and inclination, please also feel welcome to submit proposed changes as a pull request! Thanks in advance for all your help 