Shivansh Shrivastava developed these mockups which he presented at the WikiConference India and shared with me at the Mumbai hackathon:
https://svn.wikimedia.org/viewvc/mediawiki/trunk/mockups/ajax-mockups/
* English Wikipedia main page mockup with newsticker and gallery * Sliding login/account creation panel (based on existing GPL'd jQuery plugin) * Floating table of contents tab
Some interesting ideas there, I'm sure he'd welcome any comments on-list or off-list :-)
On Wed, Nov 30, 2011 at 8:27 PM, Erik Moeller erik@wikimedia.org wrote:
Shivansh Shrivastava developed these mockups which he presented at the WikiConference India and shared with me at the Mumbai hackathon:
https://svn.wikimedia.org/viewvc/mediawiki/trunk/mockups/ajax-mockups/
- English Wikipedia main page mockup with newsticker and gallery
I'm not too fond of moving tickers like this; it's a bit distracting, but it's also an accessibility issue: some people may have a hard time getting at that text because it's moving around.
The gallery is more intriguing; we definitely need better support for showing sets of nice pictures, and something in that direction would be very nice in a number of places.
Again, automatically shifting through them can be an accessibility issue, so shouldn't be generally relied upon but can be good for autoplay-style stuff as long as you can pause it easily and navigate manually.
* Sliding login/account creation panel (based on existing GPL'd jQuery
plugin)
This looks super cool! Main practical problem with an ajax login form is that we'd like to migrate all logins over to SSL (required, not optional) somewhere in the medium-term.
If you're browsing on http: and then open up a login page, it not being on SSL is a bit of a turn-off (even if it submits to SSL automatically, you can't trust that -- a MiTM attack could change the form easily).
Of course if all readers were directed to SSL all the time this wouldn't be an issue, but I believe ops says we're not ready for that yet. :)
* Floating table of contents tab
I don't like the particular implementation, but I like the basic idea: it's a piece of UI that's important for navigating around a large article, and it really ought not to be hidden up at the top where you can't get it once you've gone somewhere.
-- brion
HI,
On 1 December 2011 22:12, Brion Vibber brion@pobox.com wrote:
On Wed, Nov 30, 2011 at 8:27 PM, Erik Moeller erik@wikimedia.org wrote:
Shivansh Shrivastava developed these mockups which he presented at the WikiConference India and shared with me at the Mumbai hackathon:
https://svn.wikimedia.org/viewvc/mediawiki/trunk/mockups/ajax-mockups/
- English Wikipedia main page mockup with newsticker and gallery
I'm not too fond of moving tickers like this; it's a bit distracting, but it's also an accessibility issue: some people may have a hard time getting at that text because it's moving around.
The ticker is mainly so that we could have more news rotating, that has a functionality of stopping onmouseover(). It might be a bit distracting, but on the Main Page, it might be a great feature. This will actually grab attention of many users. It can have the latest News, fed from, lets say BBC World (for people who want to stay up to date with the latest news). I want to bring the best features of the most visited sites around the net, & implement it *efficiently* on the Wiki main page. Even the Featured Article can be made more interesting, with the gallery. We could implement a few more features in more Tables like "On this Day" too.
The gallery is more intriguing; we definitely need better support for showing sets of nice pictures, and something in that direction would be very nice in a number of places.
Again, automatically shifting through them can be an accessibility issue, so shouldn't be generally relied upon but can be good for autoplay-style stuff as long as you can pause it easily and navigate manually.
Agreed.
- Sliding login/account creation panel (based on existing GPL'd jQuery
plugin)
This looks super cool! Main practical problem with an ajax login form is that we'd like to migrate all logins over to SSL (required, not optional) somewhere in the medium-term.
If you're browsing on http: and then open up a login page, it not being on SSL is a bit of a turn-off (even if it submits to SSL automatically, you can't trust that -- a MiTM attack could change the form easily).
Of course if all readers were directed to SSL all the time this wouldn't be an issue, but I believe ops says we're not ready for that yet. :)
Yeah, even I had thought MiTM could be a problem as Session is susceptible for highjacking during AJAX. If we have a valid session identifier/data passed is encrypted decently (SSl has to be used here), various attacks like Session capture/prediction/fixation can be dodged. In case of fixation, new Session ID's might be generated or IP's could be verified. Though I have to learn more about this, I think SSL can be a solution to a lot of AJAX problems, if implemented properly.
- Floating table of contents tab
I don't like the particular implementation, but I like the basic idea: it's a piece of UI that's important for navigating around a large article, and it really ought not to be hidden up at the top where you can't get it once you've gone somewhere.
1. The implementation of the Contents Table is that - while you scroll down a page, it drags down with you. Ergo, in real long articles like World War 1, Sovereign Debt Crisis, etc to name a few, such an implementation might be helpful.
2. It is static, so the table of contents will remain at one specific position on the browser.
3. I added a hiding onclick() functionality - as the table appears above the text/paragraphs/content, so that a user can hide it ot let it remain unhidden & still the table would drag down as the user scrolls down. It is mainly intended for long articles, say >1.50 MB large pages.
Regards,
-- brion
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
wikitech-l@lists.wikimedia.org