Ticket #1700 (closed task: moved)

Opened 7 years ago

Last modified 6 years ago

Unify ImageJ web sites

Reported by: curtis Owned by: curtis
Priority: critical Milestone: imagej-2.0.0
Component: Community Version:
Severity: non-issue Keywords:
Cc: Blocked By:
Blocking: #1720

Description (last modified by curtis) (diff)

There are multiple overlapping subdomains right now: mirror.imagej.net, developer.imagej.net, wiki.imagej.net. The goal is to unify them to all serve the same content from imagej.net with smart delegation: legacy URLs go to the mirror content, wiki pages load from the wiki, etc.

The front page of imagej.net will become a splash page, with links to ImageJ2, ImageJ1 and Fiji. (The current ImageJ1 front will still get its own URL, imagej1.html or similar).

One challenge is to unify the Drupal and MediaWiki portions somehow. Perhaps the MediaWiki Drupal Integration plugin would work well for that? See ticket #1782 for more on that work.

Change History

comment:1 Changed 7 years ago by bdezonia

  • Blocking 1720 added

comment:2 Changed 7 years ago by curtis

Dscho & I discussed briefly about the pros and cons of Drupal vs. MediaWiki. The main idea is that MediaWiki is better for collaboration, easier to use, etc. But Drupal has some killer plugins, particularly Views and Panels which make it very easy to structure, aggregate and present content in a more flexible way than MediaWiki can. (MediaWiki has templates for fake structure, but it is much harder to e.g. create a table where each row is a page and each column is a template element.)

We didn't conclude much except that more research is needed to come up with the best solution/combination/compromise between the two systems, to make truly open contributions possible while retaining the strengths of both systems however possible.

comment:3 Changed 7 years ago by curtis

  • Description modified (diff)

Drupal vs. MediaWiki research has been split to a separate ticket: #1782.

comment:4 Changed 6 years ago by curtis

  • Status changed from new to closed
  • Resolution set to moved
Note: See TracTickets for help on using tickets.