3stages Wdn08 V3

Slide 1: The 3 Stages of CMS Boris Mann Raincity Studios http://www.raincitystudios.com http://bmannconsulting.com

Slide 2: Bryght tech evangelist open source Vancouver If I had a tag cloud… Raincity Drupal hand waver social software beer XMPP Northern Voice

Slide 3: Uh oh. Is he just going to talk about Drupal?

Slide 4: Dick But I’m not going to be a

Slide 5: Uh oh. Is this one of those talks? (thinks the guy in the back) (be thankful: at the last minute, I almost switched everything to Comic Sans)

Slide 6: Oh, and if I don’t mention your favourite dynamic system, it’s because it sux. (actually, it’s all about interoperable systems, but that’s probably someone else’s presentation)

Slide 7: INTERACTIVE! (I’d like to keep asking you questions)

Slide 8: The 3 stages of dynamic systems. Ugh. Sounds like a thesis.

Slide 9: Do I need to convince you that “dynamic systems” are where we’re at? CMS, web apps, RSS feeds, etc. (there’s that pesky thing about dynamic being great for SEO, too)

Slide 10: So, here’s the think: every single “page” is becoming a dynamic system all by itself. (Insert hand waving)

Slide 11: Dreamweaver Sux 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.

Slide 12: This is the part where you tell me about “static” pages.

Slide 13: Now we’re going to build an OpenID server in just one “static” page.

Slide 14: <link rel="openid.delegate" href="http://home.bryght.com/user/3" />

Slide 15: Bonus slide: Remember when your business model was updating individual pages? (We’re actually going to come back to the business model thing)

Slide 16: ANYWAYS

Slide 17: The 3 stages Designing for dynamic systems Choosing open source Plugin mania Frameworks

Slide 18: frack There is SO much to talk about (Maybe we should just listen to Oberkirch’s presentation again)

Slide 19: The 3 Stages • Simple content management • dude, the client wants to edit their own content • Beyond the blog • calendars. and forums. better add a wiki, too • Building web applications • I’m pretty sure we need a custom function for that

Slide 20: Of course that’s too simplistic. There are stages within those. Upgrades. Redesigns. Budget. Level of technical expertise.

Slide 21: How many people use a version control system?

Slide 22: Web Applications • At some point you wake up and realize you’re adding custom functionality to something that started as “just a website” • Congratulations! You’ve got your very own web application! • user profiles, personalization

Slide 23: 4th Stage “Power of remixable data” (insert Brian Oberkirch’s presentation here)

Slide 24: Me == Oberkirch fanboy

Slide 25: RSS. APIs. Microformats. OpenID. OAuth. Attribute Exchange. (RDF and the Semantic Web…maybe)

Slide 26: Got any other names or labels for types of sites? Does your company slot a customer into a type?

Slide 27: Designing for Dynamic Systems • The new site map • Templates • UGC sux (Note: presenter is not an actual designer)

Slide 28: The new site map • A sitemap used to be literally every page in a site • Now, it’s more like an outline of the templates that have to be built • Type of page • Landing page • Maybe: APIs, different types of feeds…and admin screens, too

Slide 29: Templates • Need to be designing across the entire site • Use a grid • Use realistic example text • e.g. long names; like Really Long Name That No One Will Enter • Oh yeah, and you should probably plan for users

Slide 30: UGC Sux • Your design is finished, then.... • comments! • forum posts! • italics, bold, break tags, and more

Slide 31: UGC Sux Less? • Include styles for UGC • Strip out / close tags • Live preview • Image resizing (crop / scale / placement)

Slide 32: Back to Templates.

Slide 33: Template LANGUAGE?! • This is the ultimate Designer meet Developer • CSS is programming! • And then the developer was all, like, just learn this little code snippet…

Slide 34: <meta http-equiv="X- UA-Compatible"…

Slide 35: That was a cheap shot. But, MSFT made fun of my hair once

Slide 36: Push vs. pull is kind of interesting.

Slide 37: TEMPLATES. Whatever. They’re all painful. Suggestions? (I’m pretty sure any phrases involving XML and/or XSLT transforms is going to be painful)

Slide 38: Choosing Open Source • Open source doesn’t mean free • Become an expert • Small local firms rolling their own

Slide 39: What’s your business model? • It’s probably not selling bits • What are you actually selling? • It probably is process, expertise, design • Maybe a side of services (but, like Josh said, hosting sux)

Slide 40: .NET open source? (Sharepoint, not so much, unfortunately. Plugins, maybe?)

Slide 41: Community Return on Investment (ROI)

Slide 42: Why the frack is this guy talking about open source?

Slide 44: Three choices? • Resell someone else’s code • Use open source • Roll your own (I know we’re in Vangroovy. But rolling your own is not cool.)

Slide 45: A story about local web design dev firms.

Slide 46: Everybody else’s code sux! I’m building my own! I’m going to get $paid$ to code more stuff, too.

Slide 47: Wait…what’s your business model again?

Slide 48: Of course… …open source SUX. It’s badly documented, it’s unsupported, and it doesn’t work like it says on the box. (but at least you’ve got someone else to blame)

Slide 49: We’re all in this together. Going open probably means more of the open web gets built more quickly.

Slide 50: Anyone got some business models to share? (it’s all about the icons and Facebook apps)

Slide 51: Plugins and Modules • Virtually all systems have a way to extend the base • Sweet! New functionality for free! • Except… • Installation, training, configuration • Updates and security • “Just one more tweak” to the design

Slide 52: We’re going to take an interlude to the base of the system you’re using.

Slide 53: Don’t hack the core.

Slide 54: Well, if you’re going to hack, make some patches.

Slide 55: Back to plugins… (They’re like hacking without the hack)

Slide 56: 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. (Like: this goes on the we might add this in phase 1 list. Might.)

Slide 57: Of course, you can build your own. (Oooh! Maybe this is your business plan?)

Slide 58: Designers: make some mock ups. If they’re pretty, developers will want to build it. (can you crowdsource your next website?)

Slide 59: 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?

Slide 60: Developers: please don’t re-invent the wheel. (Except, sometimes, we need a crazy one to do things differently)

Slide 61: Got any cool plugins to share?

Slide 62: Frameworks • 100s (thousands?) of frameworks • Rails (Ruby) • Django (Python) • Symfony (PHP) (Note: building from scratch is not an option) (No, really, it isn’t)

Slide 63: Where is it going to be deployed? PHP tends to run everywhere. (Tip: sneak PHP into enterprise by deploying it on a Java stack)

Slide 64: Real programmers tend to love just about anything better than PHP. Except for Java.

Slide 65: Are there people locally that use your framework? (There are tons of TYPO3 users in Germany)

Slide 66: Don’t forget about libraries!

Slide 67: Yeah, I know the frameworks bit in here was short. Did you think I was going to start a flame war? Got something else to share?

Slide 68: Let’s wrap it up

Slide 69: The web is only going to get more dynamic.

Slide 70: All these things need to talk to each other.

Slide 71: Think about your business model.

Slide 72: And I didn’t even talk about internationalization. (the English web is a pretty small place)