Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59271
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain cubiclesoft.com designates 74.208.167.7 as permitted sender)
Message-ID: <4F772D78.2060909@cubiclesoft.com>
Date: Sat, 31 Mar 2012 09:14:48 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: PHP Development <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Confusing Windows Users 101...the download page is UNUSABLE.
From: thruska@cubiclesoft.com (Thomas Hruska)

I've been writing software for Windows in Visual Studio since forever 
and also know user-land PHP like the back of my hand and, even after a 
few Google searches, I'm still scratching my head over which PHP Windows 
binary download I want to use.  If *I* can't figure out which version is 
appropriate, neither can the average web developer.

Fixing the Windows binary download page so that it is USABLE by the 
average user should be priority #1.


If I want to download PHP, I usually go here:

http://www.php.net/downloads.php

Which in turn, because I want Windows binaries, now takes me here:

http://windows.php.net/download/



Here are the specific issues with the Windows binary download page:

* The "Which version do I choose?" box is confusing, out of date, 
doesn't actually address all the real questions users will have, and 
most users will just give up before getting to that box.  Even if they 
do get to the box, the end result will be an even more 
confused/confounded user.  The box should, at the very least, explain in 
clear English the difference between the Non-Thread Safe and Thread Safe 
builds.  Also, assume that most users won't even know what Visual Studio 
even is.  Hold the user's hand here and you'll have less cruft on the 
mailing lists later.

* The ordering of the downloads seems backwards.  But until you get the 
"Which version do I choose?" box fixed, I won't be able to determine this.

* The "Select an option to direct access..." dropdown is completely useless.

* The previous page says "Windows binaries and installers".  In that 
context, the user mentally asks:  "Why is there source code on the next 
page?  And why is source code listed first if I'm after binaries?"


And, last, but HARDLY least.  Listed last because this item requires 
rethinking and redesigning the entire Windows binary download page:

* The two column layout is confusing and not really necessary.  If users 
are not going to know what they need (which they won't) and you are 
going to maintain a complex set of binaries (which it appears there will 
be for some time), consider making a "wizard" instead.  First step: 
"Choose a version of PHP".  This step is pretty self-explanatory but 
affords explaining which version the user should choose and why.  Second 
step:  "Choose a build type".  In this step, explain the differences 
between the builds and then *RECOMMEND A BUILD TYPE!*  Third step: 
"Download".  In this step, include the links to the appropriate VC++ 
runtimes and Apache in addition to the correct downloads for the 
previously selected version and build type.  This approach also affords 
adding a "What do I do next?" section to be on the download page to get 
the user started on the right path if they've never used the PHP 
binaries or PHP before.  Maybe also inject a short blurb somewhere on 
the download page discussing ZIP vs. Installer vs. Debug Pack.

-- 
Thomas Hruska
CubicleSoft President

Barebones CMS is a high-performance, open source content management 
system for web developers operating in a team environment.

An open source CubicleSoft initiative.
Your choice of a MIT or LGPL license.

http://barebonescms.com/