DrupalCon Prague 2013

Cómo reemplazar más de 1.000 sitios web por una sola plataforma Drupal

Yuriy Gerasimov, Rumen Yordanov, Kaja Jacobsen  · 


Extracto de la transcripción automática del vídeo realizada por YouTube.

so how to close a thousand websites and replace them with a Drupal platform yeah as you can see where we're quite a lot of people on stage so it's going to be a bit information heavy so am i hope you had a good lunch and sit back and be prepared to

be bombarded so this session is for LSD enthusiasts that's large-scale Drupal of course it's government government drupal types and it's for strategist and content strategists and for anyone in between these groups just so we have a reading on

you guys and what you're here for how many of you are interested in last large-scale Drupal okay so that's one less all of you okay anyone from government sectors or something like the municipality yeah so that's how far of our colleagues and any

strategist content strategists among us that's of you as well great so what's on the agenda we'll we'll do a small presentation of who we are as individuals and of course as the municipality of Copenhagen and as well a small mention of pro

people then why are we doing this and how we did it and we'll use some examples from our current project the a big internet and then finally of course we'll look a bit into the results so yeah I'm the guy on the top left and I work as a digital

strategist I've been responsible for the internet and I'm working a lot with Drupal and I've been doing it for almost three years now I guess yeah hi I'm kya I work also with the overall strategy for a platform and today I will focus on the

content strategy part that not so many of you are interested in but I'll tell you anyway why it's important I've worked there with Drupal since 2005 so I think that makes five or six years now hello there my name is Serena Dan off i'm from

pro-people I'm licking the dope operation in the began offices pro-people I've been doing japa for five years now and I'm instant intensively doing performance optimization infrastructures and basically creating a really crazy technical project

thank you hello I'm Yuri I also work for pro people and I was involved on technical part of the project and my area of expertise is services and communication between sides and we are going to have we have a lot of them on this project so that's where

I was involved so a bit about copenhagen municipality we might refer to it as k case a few times it's a Danish abbreviation so bear with us yeah we have fifteen hundred five hundred and fifty thousand inhabitants in the city we've got we're a green

city we've got 650,000 bicycles over the next ten years we were guessing that will be around other it's estimated there will be another hundred thousand habitats in the city and this is not only for Copenhagen of course but things are considered the

heaviest population in the world for the last three years running let's see how that keeps on going and that despite the Big Tex Raiders most of you probably know about already and unless of course also interesting if you're working in Copenhagen and

you notice that there will be another hundred thousand inhabitants that's going to be some good projects in the in mid the municipality we've got around 40,000 employees depending on how you look at it and they're organized into seven distinct

administrative branches they each have their own mayor I will show you a small chat later so here's where it gets interesting this is I defects we've got at least a plus a thousand websites in related to to Copenhagen city in one way or the other and

for those 1,000 sites we've got at least 500 editors maybe even more not everyone is registered and considering we have a thousand websites we have a 500 editors and we have a lot of hosting of course that means we have a web budget that we are estimating

goes above at least 10 million euros per year and on top of that to make things even more confusing there's fourteen hundred different IT systems among those there's like 17 time logging systems probably even more we don't have the exact numbers

and these we've got 70 system and same system maintenance those are the guys that work with the systems on a day-to-day basis and yeah we've got XX IT budget it's not even it's a it's not an easy task to calculate this and we haven't

done it in and some of you will then say so we're doing a big system how can we actually derive some sort of business case from it well oh sorry actually we sorry just a quick we introduced this life a bit late this pro pupil of course we have to mention

them they're great guys and they're the IT partner of our project so yeah why did we do it as I just tried to mention it wasn't because we have a big a business case for this I'll read this quote it's good organizational anarchy's organizations

characterized by problematic preferences unclear technology and fluid presentation such organizations can be viewed for some purposes as collections of choices looking for problems issues and feelings looking for decisions situations in which they might be

at solutions looking for issues to which there might be an answer and decision-makers looking for work so yeah this is the garbage can model and it's sort of underlines that we didn't have this sort of distinct the reason for for doing the system if

you look look at it from a business perspective this is one version the second version is this one we've got at least 250 side co sites we've got 21 Drupal sites at the moment that's growing quite a lot of course we've got 11 clone sites 44

WordPress sites at least 200 homegrown unidentifiable systems we don't even know when would they build on and then yeah the rest of the numbers are all the other systems you know Sophie there's less sink on that's a dynamic web joomla SharePoint

type of three Oracle I'm guessing if you can name it it in somewhere yeah and that's of course that translates into a hell of a CMS frenzy and for a big organization like ours that's that's more or less that's impossible to maintain that's

not only from a server perspective that could be from a support perspective yeah anything you can think of it's complicated and that of course translates into a huge overhead and so we're overspending on with stuff we shouldn't be spending on and

it also of course if you look from a developer perspex if it means that we're doing the same integration to our Active Directory maybe a hundred times that's expensive so why we did why we did it version 3 well some other sites are really old this

is our now now buried internet or what remains of it in as you can see it's yeah so it's old so why did we do this in the in actual fact of the summary it was of course but this goal in mind that we wanted to to enhance and improve our a whole ecosystem

of whip that means we want better maintainability we of course one reusability we don't want to do the same thing again and again and again in scalability of course we know where we're going to expand we need bigger and bigger solutions for some things

at least we want to standardize stuff that makes it easier for us to support of course quality if we can put things on one platform instead of having a trillion site that mean sites that mean that we can yeah we can make better quality and then of course we're

a political organization so if we can leverage any form of economy from scale deaths of course yeah that's an obvious benefit so why Drupal and you guys can probably give us a lot of better reasons than than these but but Google is a great system for what

we're doing in the the major decision point in Copenhagen was actually if you look at it now probably mostly that it's open source and of course that there's a big and a huge community us all of us here but it's it's not a glorified sort

of okay Drupal is better than everything else in this temperature so starting to build this platform we we set about some monstrous for ourselves how can we do this the best way m1 is yeah closed more websites and applications than deploying a new ones in

if you think about a thousand websites you know there's going to be a lot of redundant and old and useless information out there and we want to kill this off we want to replace three solutions with one solution that has better quality basically second

mantra we want simple scalable structures instead of meeting specialized needs this is of course quite difficult difficult when we're working with the politicians and in political institutions scalability is not sexy and so is structured it that they're

quite boring politicians want good magic they want to see some fancy websites and they don't really care if there's any sort of reuse unless of course they get the obvious sort of question do you care yeah but they don't so the final one we wanted

to use existing country modules and contribute patches instead of creating our own ecosystem of modules and functionality this is historically what we've done in a big organization like Copenhagen we've used the image of a duck pond for the Danes among

you you know what this means this is sort of a Danish way of looking at the world are not looking at the world i should say we're instead of instead of taking part of a community we have a tendency to maybe say we are so big that we can do things ourselves

[ ... ]

Nota: se han omitido las otras 4.771 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.