3stages Wdn08 V3


Published on

My WDN08 slides. Kind of only makes sense with the audio.

Published in: Business, Technology
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 3stages Wdn08 V3

    1. <ul><li>Boris Mann </li></ul><ul><li>Raincity Studios </li></ul><ul><li>http://www.raincitystudios.com </li></ul><ul><li>http://bmannconsulting.com </li></ul>The 3 Stages of CMS
    2. <ul><li>If I had a tag cloud… </li></ul>Bryght Raincity Vancouver tech evangelist Drupal open source hand waver beer XMPP social software Northern Voice
    3. <ul><li>Uh oh. </li></ul><ul><li>Is he just going to talk about Drupal? </li></ul>
    4. <ul><li>But I’m not going to be a </li></ul>Dick
    5. <ul><li>Uh oh. </li></ul><ul><li>Is this one of those talks? </li></ul>(thinks the guy in the back) (be thankful: at the last minute, I almost switched everything to Comic Sans )
    6. <ul><li>Oh, and if I don’t mention your favourite dynamic system, it’s because it sux. </li></ul><ul><li>(actually, it’s all about interoperable systems, but that’s probably someone else’s presentation) </li></ul>
    7. <ul><li>INTERACTIVE! </li></ul><ul><li>(I’d like to keep asking you questions) </li></ul>
    8. <ul><li>The 3 stages of dynamic systems. Ugh. Sounds like a thesis. </li></ul>
    9. <ul><li>Do I need to convince you that “dynamic systems” are where we’re at? </li></ul><ul><li>CMS, web apps, RSS feeds, etc. </li></ul>(there’s that pesky thing about dynamic being great for SEO, too)
    10. <ul><li>So, here’s the think: every single “page” is becoming a dynamic system all by itself. </li></ul><ul><li>(Insert hand waving) </li></ul>
    11. <ul><li>Furthermore, implementing basic features (such as comments or forums, or a flexible array of RSS feeds, or a decent site search engine) is needlessly complex and difficult in Dreamweaver. … Because online journalism without such basic features is crippled. </li></ul>Dreamweaver Sux
    12. <ul><li>This is the part where you tell me about “static” pages. </li></ul>
    13. <ul><li>Now we’re going to build an OpenID server in just one “static” page. </li></ul>
    14. <ul><li><link rel=&quot;openid.delegate&quot; href=&quot; http://home.bryght.com/user/3 &quot; /> </li></ul>
    15. <ul><li>Bonus slide: Remember when your business model was updating individual pages? </li></ul>(We’re actually going to come back to the business model thing)
    16. <ul><li>ANYWAYS </li></ul>
    17. <ul><li>The 3 stages </li></ul><ul><li>Designing for dynamic systems </li></ul><ul><li>Choosing open source </li></ul><ul><li>Plugin mania </li></ul><ul><li>Frameworks </li></ul>
    18. <ul><li>frack </li></ul><ul><li>There is SO much to talk about </li></ul>(Maybe we should just listen to Oberkirch’s presentation again)
    19. The 3 Stages <ul><li>Simple content management </li></ul><ul><ul><li>dude, the client wants to edit their own content </li></ul></ul><ul><li>Beyond the blog </li></ul><ul><ul><li>calendars. and forums. better add a wiki, too </li></ul></ul><ul><li>Building web applications </li></ul><ul><ul><li>I’m pretty sure we need a custom function for that </li></ul></ul>
    20. <ul><li>Of course that’s too simplistic. There are stages within those. Upgrades. Redesigns. Budget. Level of technical expertise. </li></ul>
    21. <ul><li>How many people use a version control system? </li></ul>
    22. Web Applications <ul><li>At some point you wake up and realize you’re adding custom functionality to something that started as “just a website” </li></ul><ul><li>Congratulations! You’ve got your very own web application! </li></ul><ul><li>user profiles, personalization </li></ul>
    23. <ul><li>4th Stage </li></ul><ul><li>“Power of remixable data” </li></ul><ul><li>(insert Brian Oberkirch’s presentation here) </li></ul>
    24. <ul><li>Me == Oberkirch fanboy </li></ul>
    25. <ul><li>RSS. APIs. Microformats. OpenID. OAuth. Attribute Exchange. </li></ul><ul><li>(RDF and the Semantic Web…maybe) </li></ul>
    26. <ul><li>Got any other names or labels for types of sites? Does your company slot a customer into a type? </li></ul>
    27. Designing for Dynamic Systems <ul><li>The new site map </li></ul><ul><li>Templates </li></ul><ul><li>UGC sux </li></ul>(Note: presenter is not an actual designer)
    28. The new site map <ul><li>A sitemap used to be literally every page in a site </li></ul><ul><li>Now, it’s more like an outline of the templates that have to be built </li></ul><ul><ul><li>Type of page </li></ul></ul><ul><ul><li>Landing page </li></ul></ul><ul><li>Maybe: APIs, different types of feeds…and admin screens, too </li></ul>
    29. Templates <ul><li>Need to be designing across the entire site </li></ul><ul><li>Use a grid </li></ul><ul><li>Use realistic example text </li></ul><ul><ul><li>e.g. long names; like Really Long Name That No One Will Enter </li></ul></ul><ul><li>Oh yeah, and you should probably plan for users </li></ul>
    30. UGC Sux <ul><li>Your design is finished, then.... </li></ul><ul><ul><li>comments! </li></ul></ul><ul><ul><li>forum posts! </li></ul></ul><ul><ul><li>italics, bold, break tags, and more </li></ul></ul>
    31. UGC Sux Less? <ul><li>Include styles for UGC </li></ul><ul><li>Strip out / close tags </li></ul><ul><li>Live preview </li></ul><ul><li>Image resizing (crop / scale / placement) </li></ul>
    32. <ul><li>Back to Templates. </li></ul>
    33. Template LANGUAGE?! <ul><li>This is the ultimate Designer meet Developer </li></ul><ul><li>CSS is programming! </li></ul><ul><li>And then the developer was all, like, just learn this little code snippet… </li></ul>
    34. <ul><li><meta http-equiv=&quot;X-UA-Compatible&quot;… </li></ul>
    35. <ul><li>That was a cheap shot. But, MSFT made fun of my hair once </li></ul>
    36. <ul><li>Push vs. pull is kind of interesting. </li></ul>
    37. <ul><li>TEMPLATES. </li></ul><ul><li>Whatever. They’re all painful. </li></ul><ul><li>Suggestions? </li></ul>(I’m pretty sure any phrases involving XML and/or XSLT transforms is going to be painful)
    38. Choosing Open Source <ul><li>Open source doesn’t mean free </li></ul><ul><li>Become an expert </li></ul><ul><li>Small local firms rolling their own </li></ul>
    39. What’s your business model? <ul><li>It’s probably not selling bits </li></ul><ul><li>What are you actually selling? </li></ul><ul><li>It probably is process, expertise, design </li></ul><ul><li>Maybe a side of services (but, like Josh said, hosting sux) </li></ul>
    40. <ul><li>.NET open source? </li></ul>(Sharepoint, not so much, unfortunately. Plugins, maybe?)
    41. <ul><li>Community Return on Investment (ROI) </li></ul>
    42. <ul><li>Why the frack is this guy talking about open source? </li></ul>
    44. Three choices? <ul><li>Resell someone else’s code </li></ul><ul><li>Use open source </li></ul><ul><li>Roll your own </li></ul>(I know we’re in Vangroovy. But rolling your own is not cool .)
    45. <ul><li>A story about local web design dev firms. </li></ul>
    46. <ul><li>Everybody else’s code sux! I’m building my own! I’m going to get $paid$ to code more stuff, too. </li></ul>
    47. <ul><li>Wait…what’s your business model again? </li></ul>
    48. <ul><li>Of course… </li></ul><ul><li>…open source SUX. It’s badly documented, it’s unsupported, and it doesn’t work like it says on the box. </li></ul>(but at least you’ve got someone else to blame)
    49. <ul><li>We’re all in this together. Going open probably means more of the open web gets built more quickly. </li></ul>
    50. <ul><li>Anyone got some business models to share? </li></ul>(it’s all about the icons and Facebook apps)
    51. Plugins and Modules <ul><li>Virtually all systems have a way to extend the base </li></ul><ul><li>Sweet! New functionality for free! </li></ul><ul><li>Except… </li></ul><ul><ul><li>Installation, training, configuration </li></ul></ul><ul><ul><li>Updates and security </li></ul></ul><ul><ul><li>“Just one more tweak” to the design </li></ul></ul>
    52. <ul><li>We’re going to take an interlude to the base of the system you’re using. </li></ul>
    53. <ul><li>Don’t hack the core. </li></ul>
    54. <ul><li>Well, if you’re going to hack, make some patches. </li></ul>
    55. <ul><li>Back to plugins… </li></ul>(They’re like hacking without the hack)
    56. <ul><li>Build up a set of features / list of plugins that you know are good. Covet them. Don’t add to them. Have a backup plan. </li></ul>(Like: this goes on the we might add this in phase 1 list. Might.)
    57. <ul><li>Of course, you can build your own. </li></ul>(Oooh! Maybe this is your business plan?)
    58. <ul><li>Designers: make some mock ups. If they’re pretty, developers will want to build it. </li></ul>(can you crowdsource your next website?)
    59. <ul><li>Clients/Users: maybe you have the same pain as other people. Can you fund a common solution? Can you make an existing one suck less? </li></ul>
    60. <ul><li>Developers: please don’t re-invent the wheel. </li></ul>(Except, sometimes, we need a crazy one to do things differently)
    61. <ul><li>Got any cool plugins to share? </li></ul>
    62. Frameworks <ul><li>100s (thousands?) of frameworks </li></ul><ul><li>Rails (Ruby) </li></ul><ul><li>Django (Python) </li></ul><ul><li>Symfony (PHP) </li></ul>(Note: building from scratch is not an option) (No, really, it isn’t)
    63. <ul><li>Where is it going to be deployed? PHP tends to run everywhere. </li></ul>(Tip: sneak PHP into enterprise by deploying it on a Java stack)
    64. <ul><li>Real programmers tend to love just about anything better than PHP. Except for Java. </li></ul>
    65. <ul><li>Are there people locally that use your framework? </li></ul>(There are tons of TYPO3 users in Germany)
    66. <ul><li>Don’t forget about libraries! </li></ul>
    67. <ul><li>Yeah, I know the frameworks bit in here was short. Did you think I was going to start a flame war? </li></ul><ul><li>Got something else to share? </li></ul>
    68. <ul><li>Let’s wrap it up </li></ul>
    69. <ul><li>The web is only going to get more dynamic. </li></ul>
    70. <ul><li>All these things need to talk to each other. </li></ul>
    71. <ul><li>Think about your business model. </li></ul>
    72. <ul><li>And I didn’t even talk about internationalization. </li></ul>(the English web is a pretty small place)