Upgrade to Pro — share decks privately, control downloads, hide ads and more …

10 web development concepts a designer should know

Rachel Andrew
November 29, 2011

10 web development concepts a designer should know

Presentation from Future of Web Design, May 2011

Rachel Andrew

November 29, 2011
Tweet

More Decks by Rachel Andrew

Other Decks in Technology

Transcript

  1. 10 web development Concepts - a - designer should knOw

  2. 10 web development Concepts - a - designer should knOw

  3. Rachel Andrew

  4. edgeofmyseat.com Rachel Andrew grabaperch.com

  5. Writing - a - Brief 1

  6. Writing - a - Brief 1

  7. E x a c t l y What - are

    you - building?
  8. Separate WHY - from - HOW

  9. Describe What Users DO

  10. Be clear - about - what you will provide

  11. - consider - programming constructs 2

  12. - consider - programming constructs 2

  13. - consider - programming constructs 2

  14. Conditional Logic if... then... else

  15. Conditional Logic if... then... else

  16. Loops

  17. Loops

  18. why is that Thing different?

  19. Storing Data 3

  20. Storing Data 3

  21. “The UI is not just an interface between the browser

    and a human, it’s an interface between a human and a database. You can't have an interface unless you can connect to both things. If you don't know how your interface connects to a database, what are you interfacing to? Ryan Singer - in an interview at Future of Web Apps London 2010
  22. None
  23. None
  24. None
  25. None
  26. This costs time money -&- developer Sanity

  27. Source C o n t r o l 4

  28. Source C o n t r o l 4

  29. Source C o n t r o l 4

  30. - What is - Source Control?

  31. Git Subversion Visual SourceSafe Mercurial Bazaar

  32. Do you use any kind - of - source control?

  33. Do you use Source Control? NO 37% YES 63%

  34. Do you use Source Control? NO 22% YES 78%

  35. Do you use Source Control? NO 56% YES 44%

  36. Why bother?

  37. Back up

  38. -Pick up- a project anywhere

  39. Rollback - to a - Previous version

  40. Bring in another team member

  41. Hosted source control

  42. beanstalkapp.com

  43. -Professional - Development Environments 5

  44. -Professional - Development Environments 5

  45. -Professional - Development Environments 5

  46. Developing directly - on the - live site

  47. 5 percent

  48. Developing - in a - subfolder of the live site

  49. Developing locally - Without a - web server

  50. Mirror the live environment

  51. Run your own server

  52. Create proper staging servers

  53. Code Re-use 6

  54. Code Re-use 6

  55. Code Re-use 6

  56. Lazy is good

  57. - Code - Snippets

  58. snipplr.com

  59. S t o r e common interface elements

  60. Standard Test elements

  61. - Form - Validation 7

  62. - Form - Validation 7

  63. - Form - Validation 7

  64. - The - forgotten states

  65. None
  66. Protect your design from Progra mmers

  67. Consider front - & - back end Validation

  68. Don’t make spam - a - user problem

  69. E-commerce - & - taking payment 8

  70. E-commerce - & - taking payment 8

  71. Welcome - to a - whole new World - of

    - Pain
  72. Welcome - to a - whole new World - of

    - Pain
  73. Welcome - to a - whole new World - of

    - Pain
  74. What do you really NEED?

  75. Don’t forget

  76. Special Offers

  77. Shipping Options

  78. VAT - & - local taxes

  79. Taking Payment

  80. Options

  81. Storing card data to process later is nOt aN OptioN

  82. Make someone else responsible

  83. Pci Dss

  84. Pay Page can be a comfort to your users

  85. Pay Page saves you money

  86. Designing for Pay Page solutions

  87. Pay Page

  88. Send page

  89. Hosted Page

  90. hOsting 9

  91. hOsting 9

  92. hOsting 9

  93. Cheap hosting is expensive

  94. Don’t be at the bottom of the foodchain

  95. Types of hosting

  96. Shared hosting

  97. Virtual Private Servers

  98. Dedicated

  99. Cloud services

  100. Should YOU become a host?

  101. Security 10

  102. Security 10

  103. Security 10

  104. - Be - Paranoid

  105. S p a m defacement - & - stealing details

  106. It’s Not Personal

  107. - The - hidden cost - of - Free

  108. Software Upgrades must be part of the Spec

  109. Hack at your peril

  110. Be extra paranoid about 3rd party plugins

  111. Keep server software up to date

  112. Only store - What you - really need

  113. Never store plain text passwords

  114. Shift liability where possible

  115. HALP!!!

  116. rachelandrew.co.uk edgeofmyseat.com grabaperch.com @rachelandrew Thank you!

  117. rachelandrew.co.uk edgeofmyseat.com grabaperch.com @rachelandrew Thank you!