156
edits
Mozilla.com/Mobile in Mind: Difference between revisions
Jump to navigation
Jump to search
→Design Plan
Jasongrlicky (talk | contribs) No edit summary |
Jasongrlicky (talk | contribs) |
||
| Line 32: | Line 32: | ||
== Design Plan == | == Design Plan == | ||
=== Expectations === | |||
Giving mozilla.com a responsive design will be a difficult design exercise, but worth it for our mobile users, for site maintenance, and for future web design projects. | |||
* Ideally, desktop users would not know anything has changed, since we're trying to change as little as possible with the site design. If anything, we will be subtly improving the site content and navigation. Most of our design effort will go towards finding unique solutions that don't degrade our existing experience. | |||
* On many design challenges, we should be able to provide seamless fallbacks that will not be shown to users on wide screens. | |||
* We will document our findings along the way to make sure that knowledge gained here is reusable on future projects. | |||
=== Timeline === | |||
The Design Team is Sean, Jason, John, and Chrissie! | |||
* The Design Team will meet to review the [[Mozilla.com/Mobile in Mind/Challenges|list of mobile challenges]] on a high level, and agree on a list of pages we will not need to pay attention to (first run, etc). | |||
* Sean & Jason will set up a series of meetings to discuss each challenge in depth and come up with a list of fallbacks and workarounds to be included on the [[Mozilla.com/Mobile in Mind/Challenges|challenges list]]. | |||
* Sean & Jason will produce wireframes for each page to be designed this quarter at each target resolution. It might be best to start with the toughest pages and work our way from there. | |||
* From wireframes, Sean & Jason will produce hi-fi mockups of pages at each target resolution, highlighting the changes on desktop pages for clarity in implementation. | |||
== Other Pages == | == Other Pages == | ||