Technical documentation tasks specific to tools. May include documentation tasks for specific tools, tool documentation hackathon sessions, Toolhub content quality improvements, and other projects focused on improving the technical information about -- and the findability of -- tools.
Details
Fri, Dec 5
Thank you for tagging this task with good first task for Wikimedia newcomers!
Sep 29 2025
Revisiting this. Will transfer work done to wiki page.
Jul 17 2025
I updated or created the following resources that will be useful to newcomers who want to work on tech docs:
https://www.mediawiki.org/wiki/Documentation/Contribute
https://www.mediawiki.org/wiki/Documentation/Toolkit#Improve_individual_docs (the review checklists linked there)
https://www.mediawiki.org/wiki/Documentation/Tutorials
Apr 26 2025
Hey @CBID2, I actually already replied to your question on the talk page. :) I'm the author of Adiutor (the gadget too), and I have not quit maintaining it. I believe you were misinformed. I stepped away from maintaining the extension, not the gadget. Since we are all volunteers and the gadget needs some care, I added the "unmaintained" template because it needs to be ported to ES6 and updated to follow Wikimedia ESLint rules.
Hey @TBurmeister! :) I noticed that the tool's documentation mentioned that Adiutor is no longer maintained. I posted a question about in their discussion forum, and I was told by folks in the IRC chat that the maintainer "rage-quit", so I'm kind of lost on where to go from here.
Apr 14 2025
One other thing I should've mentioned: If you'd prefer to work in Markdown, that is also a welcome form of documentation contribution. You would need to learn / know how to use git-based workflows, and create a draft in a text editor or code editor. You could also try using the built-in tools that services like Github and GitLab offer for editing files in a browser. I can't provide step-by-step guidance for learning to do that, but there are lots of resources on the web that can teach you how to do it.
Hi @CBID2, thanks for wanting to work on this task! It's great that you created a User page and a subpage for your draft. Here are some pointers for next steps:
- In your draft page, it looks like you may have copied the Markdown version of the template, instead of the wikitext? If you are using VisualEditor, this may not be apparent, but if you switch to editing the wikitext source of the page you can see the markup. In your draft, the section headings are marked with ###, which is what is used in Markdown. Instead, to properly render as headings on the page, they should use wikitext format instead, which uses == for headings.
- Here is a guide about switching between VisualEditor and source (wikitext) editing: https://en.wikipedia.org/wiki/Help:VisualEditor#Opening_VisualEditor
- Here is a guide about wikitext formatting: https://en.wikipedia.org/wiki/Help:Wikitext
Apr 13 2025
@apaskulin, can you help me with this?
Apr 11 2025
Hi @TBurmeister! :) This is how I setup the documentation so far: progress. Am I on the right track? This is the very first time I'm contributing to Wikimedia's documentation, so I need all the mentoring I can get :)
Apr 10 2025
Thank you for tagging this task with good first task for Wikimedia newcomers!
Apr 4 2025
Apr 3 2025
Apr 2 2025
Though it was stated not actively maintained, but what can be done to
revitalize the tool and make it functional. Team 12 love this tool.
Unfortunately this tool is out of date. It is showing translations from the versions of English Wiktionary pages that existed more than a year ago. I haven't updated the database since then.
Summary of activities:
Mar 30 2025
Great job during the Hackathon, everyone! If you want to keep learning and keep contributing to technical documentation, here are instructions: https://www.mediawiki.org/wiki/Documentation/Contribute.
If you want to reach out to the maintainers of the tool you documented, to talk to them about where to add what you wrote in "official" documentation for the Book Linker tool, I suggest you should start a discussion on their User page: https://en.wikipedia.org/wiki/User_talk:GreenC, or reach out via Github https://github.com/greencardamom.
Great job during the Hackathon, everyone! If you want to keep learning and keep contributing to technical documentation, here are instructions: https://www.mediawiki.org/wiki/Documentation/Contribute.
If you want to reach out to the maintainers of the tool you documented, to talk to them about where to add what you wrote in "official" documentation for the https://enwikt-translations.toolforge.org/ tool, I suggest you should start a discussion on their User page: https://en.wikipedia.org/wiki/User:Erutuon
Great job during the Hackathon, everyone! If you want to keep learning and keep contributing to technical documentation, here are instructions: https://www.mediawiki.org/wiki/Documentation/Contribute.
If you want to reach out to the maintainers of the tool you documented, to talk to them about where to add what you wrote in "official" documentation for the Page Collection Report tool, I suggest you should:
Bravo à tous pour ce Hackathon ! Si vous souhaitez continuer à apprendre et à contribuer à la documentation technique, voici les instructions : https://www.mediawiki.org/wiki/Documentation/Contribute.
Great job during the Hackathon, everyone! If you want to keep learning and keep contributing to technical documentation, here are instructions: https://www.mediawiki.org/wiki/Documentation/Contribute.
If you want to reach out to the maintainers of the tool you documented, to talk to them about where to add what you wrote in "official" documentation for the WikiBooster tool, I suggest you should:
This is impressive, kudos to the team!
The WikiSpeed tool was not a good candidate for Hackathon documentation, so this team worked on https://phabricator.wikimedia.org/T390387 instead.
Great job during the Hackathon, everyone! If you want to keep learning and keep contributing to technical documentation, here are instructions: https://www.mediawiki.org/wiki/Documentation/Contribute.
J'espère que c'est pour le français
Done
