The document discusses designing websites in the browser rather than solely in design programs like Photoshop. It argues that deciding designs in the browser allows for faster iteration, prioritizes content over aesthetics, facilitates responsive design, supports features like icon fonts and SVG, and enables better testing of performance and accessibility from the start of the design process. While Photoshop is still useful, the workflow should quickly move decisions into the browser to take advantage of its capabilities.
9. Typical Workflow
• Set clear Goals and Objectives
• Content Inventory/Strategy
• Wireframe
• PSDs (Design)
• Front-end Development
• Back-end Development
• Testing
10. Typical Workflow
• Set clear Goals and Objectives
• Content Inventory/Strategy
• Wireframe
• PSDs (Design)
• Front-end Development
• Back-end Development
• Testing
Most of the design
decisions were made
11. Design
• Create the PSD
• Get feedbacks
• Make millions and millions of edits
• Get sign off
• Start building the website only when
clients/stakeholders are satisfied with the PSDs.
12. Typical Workflow
• Set clear Goals and Objectives
• Content Inventory/Strategy
• Wireframe
• Design (PSDs)
• Front-end Development
• Back-end Development
• Testing
Most of the design
decisions were made
36. Past Workflow
• Set clear Goals and Objectives
• Content Inventory/Strategy
• Wireframe
• PSDs (Design)
• Front-end Development
• Back-end Development
• Testing
Most of the design
decisions were made
37. Present Workflow
• Set clear Goals and Objectives
• Content Inventory/Strategy
• Wireframe
• Design (PSDs)
• Front-end Development
• Back-end Development
• Testing
Make MOST of the
design decisions
Make SOME of the
design decisions
73. Workflow
• Set clear Goals and Objectives
• Content Inventory/Strategy
• Wireframe
• Design (PSDs)
• Front-end Development
• Back-end Development
• Testing
Make MOST of the
design decisions
Make SOME of the
design decisions