On Thu, Dec 27, 2012 at 10:13 AM, Adam Harvey <ahar...@php.net> wrote:
> Ladies, gentlemen, droids, > > I've spent part of my afternoon working through the beta site and > trying to deal with the last few issues that we have left before we > can make a decision on when to make it live. There are undoubtedly > still styling issues that should be dealt with, but at this point, I > feel as though we can fix those post-launch — the site is definitely > usable, and I think it's a definite improvement on our current layout. > > What we do have left is either splitting out the "get involved" > content to roughly match the links in the mega dropdown or > consolidating those links. I've started breaking the content out on a > branch called get-involved — for the most part so far, it's been just > splitting and editing what was already on the (overlong) get-involved > page, but we'd probably still need to write content for the process of > creating a pull request and contributing to the documentation, even > assuming what I've done so far is OK. > > So, here are the remaining issues I'd like people to weigh in on: > > 1. Should we keep the mega dropdown? > > I know there are some varying opinions on this — I personally like it, > but it definitely needs to be constrained to be relatively short for > each of the categories. I've had a stab at (significantly) reducing > the size of the documentation menu based on the stats on us3 and my > own gut feelings on what's actually commonly used. Hopefully that's > helped! > I'm not even sure what the "mega dropdown" is, but I'm assuming it's that top menu that slides down when you click on it? I think it looks OK. I don't see anything particularly wrong with it that would suggest changes. > > 2. If yes, should we split up the get involved content per the branch? > > Basically, what I've done is to separate out bjori's contribution > article from php|architect and the test suite section onto separate > pages, which turns /get-involved.php proper into more of a landing > page. Is this worth pursuing (and having someone — most likely me — > write more content for pull requests and the like)? > Is get involved really that big? I wasn't even aware it had its own branch. > > 3. When should we launch the site? > > As far as I'm aware, there aren't any functionality gaps relative to > the stable site now. The design seems locked down, and this has been > dragging on for way too long. I'd like to suggest an aggressive > timeframe: I've got a bit of spare time in the next few days if we can > come to a consensus on the previous questions, and I don't see why we > couldn't flip the switch to be the new site by default and the /my.php > option to be to return to the old site on January 1. > Right, the beta looks pretty functional to me. Your suggestion to wait until Jan 15 is probably best to at least give everyone a chance to weigh in after they recover from the their individual holiday hangover/spirit. > > New year, new start, and all that. > > Thoughts? > > The only thing I worry about is how end users might perceive this change. I have to admit the manual pages actually did look more readable to me in the regular site than they do on the beta site right now. Everything just seems way too compact for my taste. Some of those CSS rules are also fairly rigid and I'm willing to bet that if it were to come time to start changing them it would require a lot of re-factoring. At least that's my take at first glance. Perhaps it would be rare that the CSS will change, but it should be the case that any CSS change should not introduce a need for re-factoring HTML. It was quite a long time ago when I tried to fix the CSS for the user notes changes I introduced and I remember it being very awkward how the divs had such unexpected inheritance from positioning rules in the styling. Could probably be an easier fix than I remember, however. All in all I'd give my thumbs up on this. Sherif, The one who makes very scary commits. > Adam > > -- > PHP Webmaster List Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >
