Re: [tor-bugs] #3590 [Website]: torproject.org/download is very confusing

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#3590: torproject.org/download is very confusing
-------------------------+--------------------------------------------------
 Reporter:  cypherpunks  |          Owner:  phobos  
     Type:  defect       |         Status:  accepted
 Priority:  normal       |      Milestone:          
Component:  Website      |        Version:          
 Keywords:               |         Parent:          
   Points:               |   Actualpoints:          
-------------------------+--------------------------------------------------

Comment(by cypherpunks):

 From velope:

 Replying to [comment:31 phobos]:

 An omnibus package is a fine idea that deserves its own enhancement
 ticket, but it does nothing to move the website forward in any realistic
 timeframe.

 It's good to hear additional rationale and support for the download-easy
 page.

 The fundamental cause of confusion with earlier full-download pages was
 simply that there were too many links in total (platform X language X
 signature) for any organizing approach to completely succeed. What's
 different now is that javascript pulldowns can visually collapse the
 matrix so that the eye doesn't get so lost. We suppose that non-javascript
 users will be in a small minority, but sub-tables by package are needed to
 support them. Good design has a chance of minimizing their confusion.

 By the way, in case it isn't clear from the previous discussion, when I
 say "package" I mean, for example, that the stable bridge-by-default
 bundle, the unstable bridge-by-default bundle, and the experimental
 bridge-by-default bundle are three separate packages, each with their own
 main entry and each with their own non-javascript table. In other words, I
 don't believe the current approach of adding an 'unstable' link to the
 stable entry is workable. Logically there could be an additional pulldown
 for stable/unstable/experimental, but the corresponding non-javascript
 table would be horrendous or impossible. Also, we don't want users
 accidentally downloading a package that appears to run on their platform
 but is wrong for them, and at the same time the other-than-stable packages
 need to be very visible for their target audience. That's why the top-
 level sectioning should be by stable/unstable/experimental. (And if
 eventually there is a split onto a third page, one or more of those
 sections are what would be split off.)

 The current state of the pages is an important step forward, but clearly
 significant work remains to get them fully functional, usable, and
 attractive. I have a repository that builds the website and am willing to
 help with the WML guts, but I don't want to conflict with other
 development or go in an unfavored direction. In that regard, knowledgeable
 and specific feedback and guidance would facilitate accomplishing more.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3590#comment:32>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs