Okay, this approach is probably wrong. Better to have all the changes be via a CSS card called instead of *css when a mobile browser is detected. Starting again with http://en.dwagn.org/*cssmobile

When we think it's good enough:

1. auto-detect and redirect mobile users to, say, m.wagn.org (m.sandbox.wagn.org, etc.)
   (document or at least point to how to do that for people installing Wagn)
2. have m. addresses use *cssmobile
3. migrate *cssmobile

What to accomplish in *cssmobile:

1. fixed #menu
   (http://test.dwagn.org/wagn/fixed_top_bar not working - not a WebKit issue since it does work in Safari. see keep top bar always on-screen)
2. #menu - put span#logging on a second line (can that be done without making it a div?)
3. √960px width
   (Test on iPhone 4, maybe okay as is - tried 960pt but didn't look right. What about mobile devices wider than 960px?)
4. √primary/secondary full-width
5. (ideally you wouldn't even download it, but that's not possible w CSS-only, right?) √drop logo
6. √footer and tabs and "page" icon always visible
7. bump up card menu (in header) and watch link (in footer) font size (why are they smaller than left-side text anyway?)
8. detect orientation and adjust width?
9. ??

An older approach, leaving as is for now: http://www.wagn.org/wagn/add_mobile_layout?layout=mobile