The next/prev page takes way to much space there and isn't very
important feature to have such promonently in-your-face, creating
imbalance at the top.
Moved the language chooser to just above the version info
With two releases, this should be identical to the previous positioning. With
more than two releases, the text is vertically aligned, then moved ever so
slightly up to avoid the feeling of the chunky Begin Tutorial button being too
far off centre.
This has mostly been done by feel, so everyone else may find this horrible, but
I think it's an improvement on the previous iteration where that block was just
at the top.
mega.
Feedback is definitely welcome on the documentation dropdown changes.
Squashed commit of the following:
commit 6c282d4558e77c2f9943db318691bef596e4fd4b
Author: Adam Harvey <aharvey@php.net>
Date: Thu Dec 27 19:30:16 2012 +0800
Update the community links.
commit 82edf79fff4a500e3ca4a349b4c100e70d651f7e
Author: Adam Harvey <aharvey@php.net>
Date: Thu Dec 27 19:12:38 2012 +0800
Move the calendar of events link under news to better balance the community
dropdown.
commit 809d2a9f6044db71a117453575a9882c5607d8a6
Author: Adam Harvey <aharvey@php.net>
Date: Thu Dec 27 19:07:10 2012 +0800
Add a direct link to the manual TOC, and replace database with date/time in the
function reference, as that seems to be more commonly hit per Webalizer.
commit 73ca38258415f275a148fc8f74c91833eaf4ac71
Author: Adam Harvey <aharvey@php.net>
Date: Thu Dec 27 18:55:44 2012 +0800
Attempt to cut the documentation mega dropdown... er, down.
At present, this is more than the height of my viewport on a MBP. This is
obviously a bad thing, and nobody in their right mind is ever going to read it.
I've cut it down to a maximum of one heading and five entries per column.
For the time being, I've tried to guess what the most hit and important pages
are in the manual, but hopefully we can get some metrics on this before the
beta site is launched and adjust accordingly.
welcome! A couple of important notes:
- I've largely dropped references to Subversion altogether, even knowing that
php-doc hasn't migrated yet. We may need to put a few more "Git/SVN account"
references in there if php-doc isn't going to be migrated in the near future.
- I've removed the quick start hints from git-php.php after an account request
has been sent in. The documentation there was pretty skimpy anyway and
probably wouldn't have been enough to get a developer going, plus it's harder
to distill the Git workflow into three or four snappy commands and I'm not
really convinced that a form confirmation page is the right place to have
learning materials, since it's a one-time page for most users. Instead I've
replaced them with links to the relevant Wiki pages, which seem more likely
to be the right place for new developers to learn.
News post to come, but I wanted to separate this out for easier review.
Elephpant images are pulled from flickr via the php-master server hourly.
The web site now provides a simple PHP script to serve a random sampling
of these images in JSON format.
The web browser now loads the elephpant images via JavaScript, requesting
only the number of images that are required to fill the viewport. Images
are inserted into the page using the data URI scheme. This ensures that
only one http request is needed to load all of the required images.
If the browser window resizes, the JavaScript will fetch additional images
as required to fill out the viewport again. There is a slight delay built
in (250ms) to avoid excessive requests while the window is being resized.
Some browsers (e.g. older versions of MSIE) do not support the data URI
scheme. For these browsers we may wish to provide a fallback mechanism of
aggregating the images (e.g. MHTML, aka MIME HTML).
If the images fail to load, the elephant banner is hidden automatically.
correctly if the browser window was too small. Now we fix the width of
the main content area to 960px and center it in the page.
Made the announcement text slightly bigger.
Note the current page is now set as a class on the body tag so that we
can better target styles for specific pages.
look and layout of the home page mockup, not the functionality. We still
need to flesh out the footer, replace placeholder text and make content
dynamic in places (e.g. elephpants, announcements, news, conferences,
user groups, etc.)
