Difference between revisions of "Design and Prototyping"

From DevSummit
Jump to navigation Jump to search
Line 1: Line 1:
 
Start with a branding style guide
 
Start with a branding style guide
  
Planning ahead of time
+
2 different ways of building a branding style guide : Wireframing vs. Prototyping
  
Prototype is the fastest way to validate an idea
+
Prototyping is the fastest way to validate an idea
  
Wireframing vs. Prototyping
 
  
Wireframing > Sticky notes > Agreeing on structure /what goes on each page
 
  
Prototyping > Coding > Show you what's on each page > Allows you to show to client > Save time > a tool for bye in
+
* Wireframing > Sticky notes > Agreeing on structure and what goes on each page
 +
 
 +
* Prototyping > Coding > Show you what's on each page > Allows you to show to client > Save time > a tool for buy-in
 +
 
 +
* More traditional workflow : designing > developing > re-designing > re-developing. Prototyping allows you to do that
  
More traditional workflow :
 
designing > developing > re-designing > re-developing
 
  
Prototyping allows you to do that
 
  
static site generators
 
  
 
planning vs. making
 
planning vs. making
Line 22: Line 20:
 
static site generators -> metalsmith
 
static site generators -> metalsmith
  
having conversations early -> if you know how drupal will spit out -> develop CSS file to structure
+
* Having conversations early -> if you know how drupal will spit out -> develop CSS file to structure
  
psych tool -> making them think they're in good hands -> first site looks good while not putting in too much work
+
* Psychological tool -> making them think they're in good hands -> first site looks good while not putting in too much work
  
be about the design . design a framework before you code half
+
* Be intentional about the design . design a framework before you code half

Revision as of 00:15, 2 April 2016

Start with a branding style guide

2 different ways of building a branding style guide : Wireframing vs. Prototyping

Prototyping is the fastest way to validate an idea


  • Wireframing > Sticky notes > Agreeing on structure and what goes on each page
  • Prototyping > Coding > Show you what's on each page > Allows you to show to client > Save time > a tool for buy-in
  • More traditional workflow : designing > developing > re-designing > re-developing. Prototyping allows you to do that



planning vs. making

static site generators -> metalsmith

  • Having conversations early -> if you know how drupal will spit out -> develop CSS file to structure
  • Psychological tool -> making them think they're in good hands -> first site looks good while not putting in too much work
  • Be intentional about the design . design a framework before you code half