SharePoint loves Ruby

Slides for my talk at the "ShareConf" SharePoint conference in Düsseldorf, Germany.

Transcript

1. SharePoint Ruby
2. how why häh ?
3. ...and are they happy?
4. ...and do they have kids?
5. They do!
6. IronSP
7. ?
8. What are you talking about? Start at the beginning!
9. Julian Lindner - Web Guy at Freudenberg Group - 40k employees - also corporate intranet - also communication - not in IT - but in Corporate Communications
10. 1½ years ago we had a task: New corporate website (actually two) (actually seven regions)
11. Here’s the result...
12. Homepage w/ aggregated information
13. Static content
14. Galleries
15. Locations - synced from internal database
16. Jobs - synced from service provider
17. Well, just have a look yourself, it’s online. www.freudenberg.com ( )
18. Second one, by the way, too. www.freudenberg-nw.com ( )
19. Regions on the way.
20. So how did we get there?
21. We had a look at the others.
22. We made a “self-inventory”.
23. What do we have?
24. (Video: Anarchy Reigns)
25. Actually it doesn’t that much. Most of the time we’re quite happy with our leadership! In this case... ( )
26. Companies Divisions Websites CMS’s 1 16 300 500.000.000.000.000.000.000.000 .
27. We didn’t like that.
28. What do we like?
30. Well, Music too, yes... ;-)
31. Harmony!
32. ORDER!
33. We want...
34. Company Divisions Websites CMS 1 16 many 1
35. Project just went way more complex!
36. Timeframe for first two websites online: 1 year
37. Timeframe for first two websites online, after project approval: 3 months
38. We wrote the specs and got four offers. All similar...
39. Are you crazy?
40. Two corporate websites? On a SharePoint Platform? In three months? Before christmas? With this Budget? You must be crazy!
41. Maybe we /could/ do this for more $$$ ... and maybe until march ... second one in may. Probably. Maybe. Perhaps. If goes well and nothing happe and everybody helps and no o gets ill and we have luck and
42. There was one more offer. Wanna know what they told us?
43. You are crazy!
44. This IS impossible!
45. They also told us...
46. Fuck it! We’re young. (Excuse the language, I’m just quoting.)
47. Let’s just do it anyway!
48. So we took our chances.
49. How?
50. Extreme Programming Agile Scrum Feedback Loops BDD TDD WTF
51. Probably none and all of that.
52. We had to make a few decisions. 12 weeks to launch
53. Content • Content meeting for each menu item • With authors and executives • Improve existing – don’t re-create • No chance for change after meeting!
54. Design • Based on design by agency • Style guide in-house • Based on general corporate design
55. Platform • SharePoint 2010, because of our intranet • No time to wait for 2013 • No chance to go live in beta-state • Multi-Tenancy-Mode • On-Premise (political decision)
56. We finalized our platform setup. 6 weeks to launch
57. Imagine beautiful network- / server-diagram here. ( )
58. Feature Implementation began. One guy. 5 weeks to launch
59. Feature Implementation • Masterpage • Content Structure • Page Layouts • Variations
60. First Deployment of IronSP. 4 weeks to launch
61. First time ever someone actually used IronSP. also
62. First steps with IronSP • SiteProfiles, sync and display • Job Database, ditto • Default content pages • Contacts • Downloads
63. What is this “IronSP”? Tell us already! ...as long as we’re talking about it again:
64. It is the power, structuredness, workflow- and document management capabilities of SharePoint to the power, flexibility, agileness of a dynamic scripting language like Ruby.
65. Nice! How does that look?
66. We edit a page as we know it.
67. Then we have a Ruby “control”...
68. ... and a HAML “template”...
69. ...and a line in our Master or Page Layout.
70. This is the result.
71. More examples in a minute. Live. (Also Christian and Kevin are here for the curious.)
72. What’s your development environment? Which IDE? Compiler? Packaging? ...?
73. Tools used • WebDAV and a text editor
74. Four guys locked up in a conference room. 1 week to launch
78. Our workflow • Develop in dev-env • Test, show, improve it • Push to Github • Pull on prod-env • Repeat. 100 times a day. • (Github is great!)
79. One guy “filling” the website 24/7. Let’s not forget about the content!
80. We did it! 1 day to launch (also 1 day to christmas)
82. We did it!
83. Now you probably wanna see it?
84. (Live Demo)
85. Thank you!
86. /jlxq0
87. Questions?