On Thu, Apr 5, 2012 at 10:34 AM, Jon Robson <jrobson(a)wikimedia.org> wrote:
The best way
to balance all the pros/cons is to load the chrome+first
paragraph as fast as possible. *Then* load all subsequent sections
asynchronously *while* the user is reading the first section. That way we
have all the content by the time the user gets to each sub section. This
resolved you having to wait for each section as you tap but allows the
page
to load as fast as possible.
How would you say this would work for users with javascript disabled?
I could imagine us having a separate url for a 'complete page' - e.g.
a page like the ones we have now e.g.
http://en.m.wikipedia.org/wiki/San_Francisco/complete
and then having
http://en.m.wikipedia.org/wiki/San_Francisco
be the first paragraph with a link saying 'read more' pointing to the
'complete page'. This provides a path for non-javascript users. Then
we enhance this to load the sections asynchronously as you've
suggested.
That sounds pretty sensible; basically either way you have to click through
something to get at more content. With no JS it's "intro" ->
"complete";
with JS you get to open each section individually.
-- brion