Elsewhere...
Another excellent piece by Andy Rutledge, an admonition/checklist for being a professional designer/developer.
Both the BBC and Fox news web sites have recently been redesigned, with the BBC losing its looks and Fox getting neat and serious.
jQuery diagramming with jsPlumb — cool.
Another wonderful blog post by Walter Russell Mead, this time hoping that the blogosphere find a not-so-distant mirror in 18th-century London.
Google argues that its mobile YouTube site is better than its YouTube iPhone app.
Jakob Nielsen tests reading usability on the iPad and Kindle and reports that they’re almost as good as reading on paper. People didn’t like reading on PCs — it reminded them of work.
Falling out of love with the iPad. None of this surprises me.
Wow, icons made entirely in CSS3 (currently Safari, Chrome only).
nce we’ve populated the system with content data and produced the screen mock-ups, it’s time to knit these together and build something that the world can actually view and use.
Following the industry-standard Model/View/Controller pattern, we’ve already produced the Model with the architecture and configuration, so next up is to produce the View. To do this we convert the screen mock-ups to web pages using HTML for the document structure, CSS for the visual design, and JavaScript (increasingly relying on the jQuery framework and jQuery plug-ins) for the interface behavior.
After producing the View we move on to the Controller. In the case of ExpressionEngine, this means converting the HTML/CSS/JS web pages into dynamic templates, where the variable areas of each template are swapped out with dynamic data by the content management system.
The reason we begin coding only after completing the design work is that wireframes may require modifications once they’ve become mock-ups and visual impracticalities appear.
The entire process, with dependencies
Next process:
Testing
Previous process: