* Robert Collins <robe...@robertcollins.net> [2011-06-01 14:30 +1200]: > Rather than repeat the wiki page here, I'd love it if you were to go > and have a read, and reply to this thread with your thoughts. All the > discussions I previously put off - e.g. should we use a message queue > as the default internal protocol - are now up for discussion!
Regarding the Template/API service part of the ServiceRoadmap wiki page, if I understand correctly, the solution proposed by Gary at the Epic would consist of mostly serving static pages where the content would be dynamically retrieved by JavaScript. This is something I considered myself until I came across the concept of Progressive enhancement [1] which proposes first making the site compatible with the lowest common denominator. Then, while maintaining compatibility, adding functionality with technologies like CSS and JavaScript. This is important for accessibility reasons because some users still need to use Lynx. I would be curious to know how providing content with JavaScript might conform to the various levels of accessibility on W3C's three-level scale... 1. http://en.wikipedia.org/wiki/Progressive_enhancement -- Marc Tardif <marc.tar...@canonical.com> Freenode: cr3, Jabber: c...@jabber.org 1024D/72679CAD 09A9 D871 F7C4 A18F AC08 674D 2B73 740C 7267 9CAD _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
