ImageJ developers have been working hard for quite a few weeks to design a new website for the imagej.net wiki. We are retaining all content while migrating away from the current MediaWiki infrastructure, replacing it with Jekyll site hosted on GitHub Pages. Our goal is for the new site to remain editable and extensible by the community in an easy manner, while avoiding the security concerns of a self-hosted LAMP stack.
@elevans has been developing the new design, including features analogous to what we need from the MediaWiki infrastructure. Meanwhile @frauzufall has been mass migrating all the existing content. We have now completed the initial design and content migration iterations, and are close to entering the next phase of the migration.
Here is the migration timeline, with what’s needed to move on to each next phase:
PRE-ALPHA - where we are now - completing the initial design and content migration.
ALPHA - in ~3-7 days - 1st version of new read-only site available for community review. Static read-only version of old wiki remains available at imagej.net.
- Community - compare pages of interest from new imagej.github.io site with old imagej.net wiki. Report problems discovered here on this thread.
- @elevans - write initial contribution docs on how to edit pages, add pages, and add images.
- All of us - as time permits, iterate fixing rough edges of migrated content, particularly issues noticed and reported by the community.
BETA - in ~2-3 weeks - site opens for community editing. Static read-only version of imagej.net continues to remain available.
- Community - Begin editing the site using GitHub workflows. For new/unknown folks that means PRs at first; for frequent editors that means direct commit access so edits go live instantly, same as the old wiki. Spam no longer an issue.
- Dev team - Continue addressing issues encountered by the community.
PRODUCTION - in ~4-6 weeks - imagej.net domain begins serving new content, replacing the old wiki.
- All of us - continue to work on content, report & fix issues, and improve the site!
Side note for existing imagej.net content with critical errors
While the current imagej.net is read-only, if you feel there are corrections that must be made to particular pages, it is possible: you can file a PR against the imagej/imagej-net-static repository. You would need to edit the rendered HTML directly, but we will merge such PRs until the new site reaches PRODUCTION phase. However, any changes made to
imagej-net-static will not automatically be reflected in the new site contents; we recommend you also make the same changes in the new
imagej.github.io repository once we reach the BETA phase of development and edits there become supported.