|Anonymous | Login | Signup for a new account||2013-12-11 22:15 EST|
|Main | My View | View Issues | Change Log | Roadmap | Docs|
|Viewing Issue Simple Details|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0001967||[Slicer4] Core: Documentation & Wiki||minor||have not tried||2012-05-01 18:42||2013-08-01 12:51|
|Summary||0001967: Improve "slicer.org" page - Easier access to build / download / contribute|
Following Slicer4 Tcon of May 1st, we agreed that the current page "slicer.org" is hard to decode for a new comer.
There gray link on the tob, small link on the side ... and the image in the middle doesn't a lot of information.
Instead, link/icon to: Download / Documentation / Build / Contribute / tutorial etc .. could be added in the middle.
The aesthetic of the page could also be reviewed to look more like what have been done for download.slicer.org.
Since the download.slicer.org already contain information about developer/user etc .. may it could make sens to have "slicer.org" to "download.slicer.org"
The idea is to come up with a action plan / strategy to consolidate and unify the documentation so that finding "documentation / download / build instruction etc " is obvious.
|Tags||No tags attached.|
for an example.
The top page advertises key features of the package in order to entice people to look further. In my opinion the top page should primarily target end users. The downloads page is for people that have already decided to try. That is step 2. Having said that, I am open for changing the appearance and organization of the top page. As step one, we should have a list of the things that should be present on the top page. Step two would be to arrange them properly.
|Does it sounds reasonable to address that issue for the AHM ?|
From Steve - March 21, 2013:
Hi Jie -
I believe you can get what you need from .
@Mike, Jc: should we hightlight this link on download.slicer.org?
 http://slicer.kitware.com/midas3/slicerpackages/view [^]
During the past few years, possible improvements that would help minimizing user confusion related to either Slicer documentation or Slicer wiki have been entered in the Slicer bug tracker.
Looking retrospectively, it seems not to be the most efficient way of keeping track of these tasks. These ones have been re-targeted from one release to an other (particularly the one related to Mediawiki)
To avoid cluttering the bug tracker and artificially increase the amount of issues left to complete the coming 4.3 release (or the coming ones), I just marked these issues as closed and created a wiki page to better document what could be improved.
See http://www.slicer.org/slicerWiki/index.php/Documentation/Labs/DocumentationImprovments [^]
If you think, tracking these issue with mantis still makes sense, feel free to re-open the issue.
Do not hesitate to improve the wiki page. For the first draft, I simply referenced the closes issue.
Let me know what you think,
|2012-05-01 18:42||jcfr||New Issue|
|2012-05-01 18:42||jcfr||Status||new => assigned|
|2012-05-01 18:42||jcfr||Assigned To||=> jcfr|
|2012-05-01 18:42||jcfr||Assigned To||jcfr => pieper|
|2012-05-02 20:18||kikinis||Issue Monitored: kikinis|
|2012-05-02 20:25||kikinis||Note Added: 0004128|
|2012-05-15 18:56||jcfr||Category||Slicer Wiki => Documentation & Wiki|
|2012-05-18 10:24||pieper||Assigned To||pieper => mhalle|
|2012-05-18 11:41||jcfr||Note Added: 0004491|
|2012-06-28 10:38||jcfr||Relationship added||related to 0002272|
|2012-08-20 12:21||nicole||Target Version||=> Slicer 4.2.0 - Feature freeze Sept 1st 2012|
|2012-08-20 14:05||jcfr||Target Version||Slicer 4.2.0 - Feature freeze Sept 1st 2012 => Slicer 4.2.5|
|2012-08-21 13:39||jcfr||Target Version||Slicer 4.2.5 => Slicer 4.3.0|
|2013-03-21 10:15||jcfr||Note Added: 0008187|
|2013-08-01 12:50||jcfr||Status||assigned => resolved|
|2013-08-01 12:50||jcfr||Resolution||open => won't fix|
|2013-08-01 12:51||jcfr||Note Added: 0009343|
|2013-08-01 12:51||jcfr||Status||resolved => closed|
|Mantis 1.1.4[^] Copyright © 2000 - 2008 Mantis Group|