Designing in the Browser
summary
Argues that websites should be prototyped in the browser using HTML5 so interaction and real data drive design rather than Photoshop mock-ups; recommends scaffolding with DocPad or Jekyll and HTML5 Boilerplate, styling with Sass/LESS and Twitter Bootstrap, and seeding content with faker.js and LoremPixel to reveal layout breakage (example: a rolodex prototype shows the logo fails with long names). Advises low‑fidelity first, ignore pixel perfection and old IE during prototyping.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:32Text Wrapping
- 3:11What Is Web Design
- 4:25Design the Interaction
- 9:37Lorem Ipsum
- 13:16Wireframing for Web Apps
- 14:34Responsive Web Design
- 14:59Responsive Design Workflow
- 15:17Html Prototypes
- 16:17Pointless Semantics
- 17:18Old Ie Compatibility
- 18:33Static Site Generator
- 19:35Style Preprocessors
- 20:13Naming Conventions
- 25:37Documenting Your Styles with Style Doc








