I already posed this question almost 2 years ago, see issue: What to do with the wiki · Issue #8 · TYPO3-Documentation/T3DocTeam · GitHub
Since then some things have happened but not enough to sufficiently make headway.
What has happened:
- I (and a few others) have been doing some cleaning up: Determine pages where the content has already moved elsewhere (mostly docs.typo3.org), remove these pages and request redirects. More than 50 pages were removed this way.
- created lists for migrating content, see Wiki migration, maintenance and decisions · GitHub
- a Slack channel was set up: #typo3-wiki
- several people got together and decided to create a Wiki2docs initiative. This never really took off.
- it was communicated that it was decided to make the Wiki readonly. I don’t really know who decided this and why.
To help the workflow, I used the already existing tags and categories to mark the content, e.g. {{delete}} is candidate for removal, see TYPO3 Documentation — Homepage of docs.typo3.org main documentation
I think, in order to proceed, this topic needs a decision. And then people executing it.
The decision
Possible choices are:
- Take down entire Wiki. This has the difficulty that it is not just used for docs. It is also used for exceptions and some team communication, see TYPO3 Documentation — Homepage of docs.typo3.org main documentation
- Merge, remove and redirect on a 1 page at a time basis: Remove pages that are outdated or where content is already moved elsewhere. For the rest, possibly move content to docs.typo3.org. Remove the page and create a redirect.
- Make Wiki readonly. This was suggested but I don’t really see the merit. Maybe someone else can explain.
You may think choice 2 is unrealistic but it is actually doable with a few more people pitching in. As a whole, we have about 1000 pages. 50 were already removed, 283 are exceptions, 147 are already candidate for deletion. Probably, these just need redirects and get removed. see TYPO3 Documentation — Homepage of docs.typo3.org main documentation. A number of pages can just be removed with little effort. For others it requires more work.
My recommendation
This is a combination of 1 and 2 above in a multi-phase process.
- Have someone in charge of the process to coordinate this
- Continue with the migrating / deleting / redirecting on page-by-page basis
- Communicate ASAP that entire Wiki will be taken down in 1 1/2 years - Oct 8, 2021. Communicate how everyone can help and what needs to be done.
- Start looking for alternatives for exceptions and communication (e.g. t3board, various groups)
Sub-suggestion: communicate decision
In any case, I think it would be a good idea to communicate this decision on a broad basis, e.g. Wiki will be taken down in 1 1/2 years - Oct 8, 2021. Until then, we strongly urge everyone to pitch in, move content, remove content and create redirects.
Sub-suggestion: Archive Wiki, make available for download
I would propose to archive currrent Wiki right now and create a downloadable tarball. Ideally create a backup of current system and a “static copy” (e.g. with wget) for local viewing.
The reason: It is far more easy to remove things if there is at least a backup of the content somewhere. IMHO, some of the content is still useful. But still, it needs a more rigorous cleanup (than is currently being done). Otherwise we will be revisiting this topic again in 2 years. I don’t think it is a good idea to keep postponing this.
I have not tested the viability of the “static copy” for wiki.typo3.org but I have done this for other systems (often it needs a little tweaking). It is important to create an archive with relative links and paths to assets so you can view this locally, just using a browser.
Example:
# -k: convert links
# -m: mirror
# -nc: no clobber (do not overrwrite files with same name)
# -p: download necessary assets
# -E: append .html to HTML file if doesn't end in html
wget -E -p -nc -m -k https://wiki.typo3.org