Webdev:Web Design Best Practices: Difference between revisions

Jump to navigation Jump to search

Webdev:Web Design Best Practices (view source)

Revision as of 18:40, 8 April 2009

1,079 bytes removed ,  8 April 2009
Blanked the page
(Created page with '(culled from [https://intranet.mozilla.org/User:Morgamic/Project_Management#Common_Hang-ups here], will be cleaned up and expanded) = Common Hang-ups = * l10n ** right to left, ...')
 
(Blanked the page)
Line 1: Line 1:
(culled from [https://intranet.mozilla.org/User:Morgamic/Project_Management#Common_Hang-ups here], will be cleaned up and expanded)


= Common Hang-ups =
* l10n
** right to left, left to right
** text as graphics
** too narrow elements that can't handle more text (buttons)
* QA time
** Not enough time to properly QA
** Not enough time to fix bugs found by QA
** Specs not clear enough for QA to follow
* Poor predictability
** Estimates asked for before specs, wireframes and designs are started
** Webdev not fully looking at copy or providing inaccurate estimates
** Not tracking everything as a bug and grouping them per release
* Setting a press date before product is finished
* Lack of requirements
** no wireframes
** no spec document
** no central place to track tasks and dates
** poor note taking, so requirements get lost in email, comments, grouphub, etc.
* Webdev not involved earlier in the design process or
* Once we start working on it, we find a lot of additional cases that were left out of the original spec (or have feature creep) and it is not managed well
Neilio
180

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/138983"

Navigation menu