StoryCode Tech Immersion 1
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


StoryCode Tech Immersion 1

Uploaded on

A high-level overview of web architecture geared specifically towards storytellers. (

A high-level overview of web architecture geared specifically towards storytellers. (

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 29 29

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. March 6, 2012Tech Immersion 1
  • 2. AGENDA• Web Architecture Overview - 45 Minutes• Quick Break• Social Samba - Saga Writer Deep-Dive: 1 Hour
  • 3. OVERVIEW• Domains / Domain Registrar (Go Daddy,• IP Address - Think of it as a Phone Number (its a unique identifier "")• DNS - (points the domain name to the server IP Address)• Good overall reference link: http://
  • 4. SERVERS• Servers - can be a machines and/or an applications (Apache)• Protocols - Mail, FTP, HTTP (FTP is what is used to load files to a server)• Hosting - Internet Service Provider (ISP) Mail and/or Web Shared or Dedicated
  • 5. WEBSITES / WEB APPS• Static (index.html) vs. Dynamic Pages (index.php)• Dynamic pages are driven by a database• Databases - Like a spreadsheet (MySQL, Oracle, Etc.)• Languages - PHP, C#, Python, Javascript, Ruby on Rails• Common Web Applications (Blogs/CMS Tools): Wordpress, Joomla, Drupal
  • 6. COMMON TERMS• Cloud - ability to expand/extend capacity without investing in new infrastructure• Linux / Unix / Microsoft - web server operating systems• SSL - Secure Socket Layer "https" - needed for Facebook “apps”• API - Application Protocol Interface. How you interface with a third-party technology (like Twitter or Facebook).
  • 7. CUSTOM vs. OFF-THE-SHELF• Skinned or Themed Blogs vs. Content Management System• When Creating Custom Software Consider:• Creative Technologist or Designer/CTO Combo• Process: Information Architecture/Requirements (Use Cases, Wireframes), Design, Development, Testing, Launch• Developer Resources: Front-End vs. Back-End - these are often different people
  • 8. ADVICE• Reduce functionality and prototype heavily• Release early and ongoing (continuous process)• "Agile" development• Procedural stories work well with technology - create the rules then let the technology construct the story.  [User] watched [favorite movie] and really liked it.  [John] watched [American Beauty] and really liked it. 
  • 9. @storycodeorg