On 27 July 2012 12:53, Peter Coombe &lt;thewub.wiki(a)googlemail.com&gt; wrote: Very interesting. Looks very good already. On 27 July 2012 12:01, John Elliot &lt;jj5(a)jj5.net&gt; wrote: Ouch. This website is aligned to the left, and designed for a fixed width of 1024px. *reads content* Yet again, we remember that HTML is liquid. Is supposed to be, wen is made fixed, is because compromises. On 27 July 2012 12:08, David Gerard &lt;dgerard(a)gmail.com&gt; wrote: Infinite scrolling is not always evil. If you need to show a PDF document as a list of 200 high resolution JPG files. You can make the page height the resulting height if all the jpg where downloaded. But only download the JPG the user is looking at. If you try the naive approach,and create a html that links with <img> all the 700KB jpg files, the page will chocke for most users, because will ask for too much bandwidth too quick. And maybe the users only need to look at the first page, to confirm is interesting (maybe are books, and is the wrong book, or in the wrong language ). http://es.scribd.com/doc/6457786/Godel-Escher-Bach-by-Douglas-R-Hofstadter- By making a document become a computer program, we probably lose the ability to garantee it will end rendering before the end of the existence of the universe. But is often a good tradeoff. -- -- ℱin del ℳensaje.

On 2012-07-27 23:52, Jon Robson wrote: Any idea about when the responsive Athena skin might be ready? 1 month, 3 months, a year?

On 27 July 2012 16:35, Sumana Harihareswara &lt;sumanah(a)wikimedia.org&gt; wrote: Without joining a whole other list, can I just ask what attention is being paid to people less connected than San Francisco geeks with iPads? Editing Wikipedia is presently annoyingly slow on a 1Mbps connection and pretty much unfeasible on dialup, for example. - d.

On Fri, Jul 27, 2012 at 8:47 AM, Jon Robson &lt;jdlrobson(a)gmail.com&gt; wrote: +1 We should be looking at Athena (and other projects like it) as guidance for how were going to approach contribution projects on mobile. Our focus for the next year is to not just grow the readership base but to also grow the contributor base. We've never had as many eyes on Wikipedia as before who can't contribute. Mobile users can't be second class citizens within the Wikimedia projects. We have to build all new pipelines on mobile devices to make this happen. These contributor methods may look drastically different then their desktop counterparts. Responsive design is an interesting technique for layout but it breaks down for functionality. A mobile phone, a tablet, and a desktop/laptop are used very differently. Mimicking the exact same functionality means your failing to understand what's best for each device. I'm going to re-iterate what Jon said here. We have numerous projects going on now and we've been actively mailing, blogging, and tweeting to get new testers/developers/etc. Were always eager to get more people involved. If you need to catch up with what were working on just check the mobile projects pages. http://www.mediawiki.org/wiki/Mobile --tomasz

I think a better answer to your question is: "nothing that's been officially resourced at this time". We currently have a 2-device strategy, which means we redirect some devices to a mobile site, and the rest remain at the normal "desktop" site. The closest thing to responsive design we have in production is the way the Vector skin adjusts it's layout – if not subtly – if the browser is above or below a given threshold. Responsive design is a hot topic, and there are a lot of really exiting projects in this area right now, but there are also some overlooked issues. Many mobile devices are amazingly powerful, but sending the same JavaScript and CSS payloads to all devices still results in a much heavier payload on smaller less capable devices that in some cases may even cause them to crash. This can be fixed using a variety of techniques, but it illustrates how responsive design – when done right – is more than a new skin that delivers HTML and some CSS, only for all the same extensions, user scripts and gadgets that were designed with the desktop in mind to pile on and clog up the "tubes" while wreaking havoc on "simplified" pages presented to mobile users. A good example of this problem's unclear solution is how the mobile site does not load the same extensions, user scripts and styles and gadgets as the desktop site; and what's more is the issue with the use of inline styles throughout the site and how difficult it is to deal with on mobile devices with an alternate – simplified – layout. All this said, MediaWiki is an open source project and you shouldn't ever feel the need to wait until something "ships". I would recommend you start out with an existing skin, tear it down to it's simplest elements, and then start adding CSS and modifying the HTML output until you have what you are looking for. If you need some help, this list is a good place to be, but also make sure and get onto irc.freenode.net #mediawiki where you might be able to get quick answers to simpler questions. - Trevor On Sat, Jul 28, 2012 at 2:11 AM, John Elliot &lt;jj5(a)jj5.net&gt; wrote: