 I think we're good to go. I'm guessing, originally, on the schedule set, we're starting to take the JASER office a little bit of time so I will get started. I think we're all where we're supposed to be, so this is going to be a session on Drupal and higher education. My name is Dan Fitzsimmons. I'm from the University of Calgary. So we're going to be talking about the process we've gone through of designing and developing websites for everyone, so I'm going to do some of the bad. So then we'll think about higher age institutions in general so we have a distinct set of challenges because we have to make websites that really do fit lots of different use cases, such as for faculties, departments, sometimes small groups, services, personal sites at times. So it does make it sometimes difficult to make sure that we're achieving a solution that would work for everybody. So that's one thing that we've, I think all higher education institutions can struggle with is to make sure that we actually have a product that will work for everything, a template that will work for everything. We can have different customers who want things like, especially when it comes to the executive, they might want specialty client services that will work, especially for them. That is not always something that can work for everybody, but we should use a product. So one thing that we have to do in higher ed as well is make sure that we support it as much as possible because there is always a, may need to support as much as you can because when you don't, we find that people will often try and go outside. Go to a contractor, go to some kind of vendor, get them to make the website that you want. And then we run into more problems and have to support long term because people try to bring their sites back on the campus and we can't really support them. So we're trying to develop a product on campus that will work for as many use cases as possible, have the support model in place. This is what we've done, so that people can actually rely on us to get what they need done as much as we can. So we have that in general. We're trying to support as much as possible. One thing I'm going to be talking about today as well is the evolution of the University of Calgary service. So where we're starting, where we're going. So we kind of got an idea of a school that's been doing it for a very long time over the course. And what we've been able to achieve. We're also going to talk about our set up with multi-site, with pros and cons, as well as a little bit on where we are now as far as the second vendor we actually have some of our services on campus. So, again, my name is David Simmons. I'm a senior web developer at University of Calgary. I've worked with Drupal now since about 2006. I originally came on as a student doing contract work, doing a few of the very first sites that were mostly service level sites that were trying to move over into the system because they were more student-facing. We wanted to get all the new things that were coming out of Drupal. And just to take the best advantage of the product. Right now I'm assisting and hosting over 900 Drupal sites that are in production. We have 500 or 500, though, that are in different stages of development. So it's like development sites, testing sites, training sites that are still in business on the production server still have to be maintained, but we have about 900 that are actually proxy and available to the world. We also do development for the University of Calgary's new home page, which is posted on Campions from there for about a year. And so part of the work I do is how it's all of that, and right now we're working in mostly development space, but there's a lot of other things that I do. I've also worn many, many hats over the years I've been there. First starting out as a student going on to be called the Head of Web Migration for a while, that we move people into Drupal. We need somebody who dedicates the site building aspect, who dedicates the team in. Also working as a lead developer for a while, as we're working on the Campion home page and some of the special projects there. As we continue to work on the entire project. So why would you use Drupal in higher education? For schools, why does it work for University of Calgary as well? For us, the big one was, of course, there being no annual renewal fees from software. That's a big thing as I do, I just often play Drupal in institutions like University of Ecologists. We often have to be concerned about how much things are going across. When we were looking at things like, when we save money on the software, having annual renewal licenses, things like that would be a big problem for us going long term. We have a lot of other fixed costs. So there are a lot of things that can happen. Of course, software, things like that, we have to be paid for other vendors. That's fixed, can't be anything much about it. So one place where we could actually get some kind of cost saving was by looking at different web software that we looked into in 2006 to make our movement into something a bit new. One thing as well with being on this department of technology, this is the area I'm part of, because it wasn't a centralized department, one thing we had was a lot of people who could do things like install SQL, PHP software, set up a server to put in middleware applications. So we can get them, that was something that was set up on a machine. So we had some dedicated and most old machines that were kicking around, so that's kind of how we got everything started. So in the early days, one thing as well, we had a pretty good developer community out there, especially in Drupal. We had some developers, of course, who did no problem working at UC. So it was nice that there was both people and the community out there that could work on some kind of applications. So that's one reason we decided to deal with it. The nice thing is, of course, they don't even have the customized we wanted to. And we've done a lot of work on that, we started out in 2004, we're doing too much trust development. But as we've done, of course, in Drupal 7, as we are now, we can't have to customize and we do have to customize, particularly with the can't be on the credit run now. We've done a lot of custom coding, there's no way to be more close at the end of the presentation, about some of the things we've done to try and improve the service. One thing that's nice about Drupal, of course, is if someone's not in core, there are these missing features you can add on. So we've been doing that a lot, because they're only adding on treated modules that would fit our needs, trying to be careful about that as much as we can, because we have this running in an enterprise application for us, so we have to be quite careful. It's flexible with these kind of things. It's got lots of flexible options. I think we can change. System integration is a big point too for us, but of course, if you connect with any of our systems, some of you don't know about it when you're first starting out the project. So we've had things like setting it up with a lot of JSON connections, XML feeds into different systems. We have a large profiling system that we have still alive versus gallery. We can connect to various systems like PeopleSoft that can actually get profile data of professors and other staff members. So that wasn't so many huge pluses for us, and the nice thing about being able to build is it's both sizeable, big and small, because you can customize the software as you go along. So we adopted Drupal in 2006. So we've been doing it now for over 10 years. It basically became our our website station. We just said, like, this is what we're moving to. There's no room really for you can have now your old product and we have this product. We're like, no, we're setting up a new service with Drupal. We're going to set it up a team and they're going to support it. So you have a decision to make with these faculty departments is that you can move and we'll give you support. So we try to focus on transitioning to a more modern look at the time 2006 look of websites. So basically, they just have structure and left navigation links that would actually connect together. They get a whole lot of people to create content on their site. And it basically kind of might template a film. So, they try to make it quite easy for content administrators in particular to just get your sites out. But you can do images and do files and all that kind of stuff. Quite easily, we're recording a kind of FTP stuff up and you will have talked to a lot of these and they weren't actually doing that work. They were often hiring somebody to do that work. So it made it so they were paying a lot of money on that kind of thing. So you can do it yourself. That would save your departments also lots of money. So in part of this, our old system was very decentralized. We had lots and lots of different kinds of websites out there. We had dual courses and things like trainweaver, front page, all kinds of things just thrown onto any server they could find. Sometimes they paid a lot of money to host a service. A lot of companies that were big, especially in Calgary around the time, they were hosting different environments and very customized sites. So, one thing remains, we thought of doing this change over to do something else and we looked at a few different products. It wasn't what we chose. But when we looked at different products, what we wanted to do was make sure we had that brain. Because one thing the old sites have a problem was different. So it was like, when you hit a University of Calgary website, you know, this is the University of Calgary. They looked the same. So the idea was to get people over to the system as quickly as we could so that we could have a consistency frame. So, one thing we decided to do when we made that was of course go with the non-cost recovery model a little bit more. One other thing that motivated us to do the push was we were featured on web pages that suck.com because of our old look. So, on that site, what they were basically focusing on, they made it in the video capture they made of our site was that it's changed by the time they actually posted the video. But we had what they called mystery week navigation on the old site. So what that was is that you have to hover over links to see what they were. So almost everything was taken. So when you try to find out like looking for information about faculty and engineering for example, you had to hover over all these links and be like, oh, which one's the faculty engineer? You might forget where it was and have to go back and look again. So, you know, there were legitimate criticisms and we luckily at that point were already on our way to this new idea. So we were trying to use these new layouts as well to get the clients moved over. So we decided for the whole new service that we're going to do we're going to build a team that had most of the points people needed. So when this team still exists, yeah, it's changed a lot over the years but really what it was is we were focused first on the service. Get customer service people there who know how the service works. They understand it and build training and documentation. Videos where we can basically style guides, things like that to be able to understand the brand and how we can use the brand. We're trying to basically move the purpose of content updates to the site administrator so it takes it off of the centralized web team because just with the number of people we had it wasn't possible. So we made it so we can help them in the early stages to move the content into Drupal and that was part of what we wanted to do with the non-customized web race. Let's encourage people to move to this brand and we know we had problems with the old brand we know we were having decentralized and that wasn't working. So let's get people moved to Drupal we'll hire people like myself and site owners. Get the content moved then the people who actually worked in these different faculties and departments didn't have to worry about it. We moved your stuff. Do you like your new website? Cool. Put it online. So generally we got this moved over quickly by using this model but when people had a question I don't know how this platform works which never really would come up So one thing the University of Calgary did as part of the idea like let's not have people be charged for the service is we set it up as a critical service by information technologies to have websites. We need them. We need to also control ourselves of course we always want to have students come to the University of Calgary so we have to be sure we have good websites that people understand and navigate and we'll get continuous support. So we've been trying to encourage people to move to this service the whole time because this is something you're always going to provide. So it's always going to be there for you as a service. Another thing we wanted to do as I mentioned before is we had a lot of people using contractors. Of course summer students, if you get in the University they hire somebody like for a few months in the summer time and be like here, build me a new website if you're a professor. And then in summer you may have a free base site I'm going to support this while in terms of being completely unique. So we wanted to prevent you from doing that like don't go out and just hire some random person or a vendor who doesn't understand the brand. So we have tried to make sure we had guidelines on the brand and they would stop doing this and stop going out and actually just hire a random vendor or person to build their website because we're going to have a free option. We have something that works, it's stable you can just put your stuff in there if that's really all you need, if you just need a web presence. Then by basically setting up pretty strict at the beginning standardization like here's what we've been going through before when we started. No, not much to stress. This allowed us to basically have sites, folks with information and knowledge that would maintain a pretty rigorous standard. So we had policies in place where we were like we're not going to allow you to go out to get a vendor once it's not Drupal. That's like some random technology and you're going to say hey, can you host this on your machine? Is it going to be hosting costs? No. You have to use Drupal. You have to build within our template if you want our support. Now we can have another thing we never hosted those kind of websites. They do get hosted sometimes but you're not going to get a support model. So the nice thing was, yeah, there was no service costs from the Web Team at all. So like, you know, if someone wanted custom development on the Drupal site they would have never started out before focusing on just getting content over but there were some people who needed like, sorry to realize there was a developer community out there. Let's get some models that solve a bit of custom code that you guys are doing. Now we still don't do cost graphics right now. I mentioned before we have PanPam as well and they're hosting our university home page as well as some other microsites. So we got set up in the last year or so but we decided we're not going to be like everything's free. Basically most of the new development is going to be PanPam on-site but we're just trying to figure out like once that platform is completely ready we can actually loop people over there and it's not going to change the service model. They're used to not paying for anything they're used to having. Basically a team that will help them out all the time so we're still here. So there's the Web Services team that you have seen. So we've had different names over the years as well. We are now not a management team but we just kind of pigeonholed us a little bit too much to be like you're the Drupal team but now we actually have to handle different products that just Drupal Drupal is of course our biggest thing that we work on. We basically provide two or three level support for people so we have two to one that go through the general IT support desk with the university but then when they have higher level questions they tend to go to one of our customer service staff or any more technical resource like myself and we try and offload those problems that would go to the site and the industry to try to solve like they're going to PhD or they don't know what to do with it so they send it to us. So it helped out a lot to basically not have the people have to go back to the previously going back to a venue like they're paying hundreds of dollars for them to fix a problem now the Web Services team generally on campus could do it for free. As we move along the site building aspect has become more limited because we now are focused much more on development and new technology and of course there are different events that comes from running enterprise software you have to make a lot of old sites. So most of you did things in the early days when you were using panels just like trying to modify those slightly here in the early years too. We also tried to better Drupal as much as we could though. So in Drupal 7 we used things like the features module to set up basic functionality defaults, things like that on sites. So we're trying to use Drupal as much as we can still but we have some development support in terms of CSS, HTML, PHP so you have the designer so you can do that. We can do of course you know you need custom queries they need things to be installed or built we can do a lot of those things which is kind of just an intake model over time. There's also a lot of websites to be hosted on the university's campus which would make things a bit easier for us. You know of course a lot of people aren't going to do a lot of cloud based services you know we're of course as well looking into that but right now we're hosting a lot of things on campus because it allows us to have the control. One thing we can try to do as well even if people have had custom domains they've registered with various services like Odadi or a lot of other Canadian ones too. They will try to keep ownership of that have control of the domain but people forget people leave the university so people will be tied to an email address that might be disconnected so easy addresses with something inspired some will buy after the domain once they realize it's free and they never know. We've had a couple of cases where we had random stuff we put on like our old residence sites and things like that it just points to someone who's trying to spoof the university and that kind of thing so we now refer to people to like let's take ownership of the University of Calgary and the ITC and we'll take care of domains so when they fire they basically won't be smart enough to worry about cost so that's one thing we're going to try to correct. I'm sure there's lots of cost going into this and of course we'll take numbers but there's a lot of cost that we're now controlling that's been taken away from the city of Minnesota they don't have to worry about what we're doing they don't have to worry about the server cost so that's really helpful for them. One thing we've done that's we think has been very effective for us in what's called the University Relations Department so they are basically the external facing marketing department of the university so they came up with a brand and then they came of course in that way responsible for the brand so one thing that they've been very helpful for us in is basically business owner so one thing that was talked about by Alex in the beginning in the CIOs when the presentation for the keynote was about our cases where there is no business owner one thing we've tried to be very good at was to start out as if we had a business owner the web at U of C in terms of Drupal is owned by University Relations so we deal with them they get to answer the tough questions we get to make the service work like they tell us what needs to happen and then we try to make it work as best we can with the technical limitations so there's lots of business that come up there's lots of things that people try to actually operate and it still happens because our main way of kind of sitting on the university can to see the last of the year changes the template at some time in 2021 so we have a live screen version but it's not on the screen so if you go to the University of Calgary website for the most part they're not responsible sites, we're in progress so we're working on that at the University's whole page which is going to be rebuilt into a new model as much as we can look at how respectful they are so if people come in and say I don't like your websites right now I want to move off-campus I'm going to go with some outside vendor but of course you're not going to support they'll try to bring out your website back to us because they're not going to post it and if you have questions about general things about what you can and can't do within your site talk to University Relations so if they want to change things like colors like you talk to University Relations we've worked that out with them so they're the police for us so that's been really great for us so we now focus in our key on the type of University Relations tell us this is the direction we're going if you're on the road now we implement it so we've worked directly with them we've done that model since 2006 when we started it's gotten more tightly integrated over the years and actually in the last few years so it's actually probably the most it's ever been so we've run different parts of campus before always close we've met regularly with these guys but now we're actually sitting in the same office space so every meeting we go to is usually someone from University Relations there too so they know exactly what we're doing we know exactly what they're doing so when they are making decisions on the future of the brand we're right there so we can meet around for a second oh that's not technically possible like all types of things so the evolution of U of C so this is how we got started to where we are now so we did start out in version 4.7 so we were pretty early days in terms of like the more stable build over the whole and that's what I got stuck in so it just came in just after making me the decision to move but I helped move so when we started on 4.7 we were using the very small models like basically core, bus modules which we felt really were getting the kind of major support thing we did so a lot of times it really is like install another module like a system admit they're running the server at a time because they needed like their they were doing a lot of things so this was actually one piece of their pie and just what they had to do in an average J so when they first started out we were small of course just being in the first few seconds over we wanted to get some turned to modules and let's have some fun with this thing let's do what the module or approach that Drupal provides so basically we expanded once we did that initial we were like yeah that's the cool stuff so let's add more modules so as we did that we were adding more and more modules we had other people who were early adopters of Drupal some people actually didn't do it directly through us they realized we were doing Drupal so they made their own server as well they would bring them in later on but they shouldn't do this themselves let's do it with a central IT but they would be like okay I found a organic group so we can install that and they necessarily know what it did what its main purpose was so they would sometimes later on realize that okay well I've installed organic groups and now how do I do it so that worked confident in the early days of Drupal luckily between version 4 and version 5 there were huge architectural changes so the move over wasn't too bad when we got there but we had to look into things like because we were just installing modules without any kind of thought of like how are we going to standardize them what's our process as far as review what's a good module, it's not a good module does this fit a broader use case sometimes there are installing modules that of course were like one site that I don't want I didn't look for my teaser so I was like teaser module for you but I wanted to think about what everyone would be because we were kind of we were thinking about the service because it was early as like okay we just got a couple of sites and they're all different but we had to think about it later on it's more like a general enterprise level service we have to all be doing the same thing so we did perform a major upgrade from version 4 to version 5 and a few hundred sites around that time we tried to make a few changes as possible but we had to also contend with but some modules just disappeared in between those two versions just on we had to figure out something else and as we moved along though we started getting into like a 500 plus sites that were on Drupal we got into Drupal 5 days we started customizing they were asking for like more they wanted like more features that we could build that were didn't necessarily exist out in the Drupal developer community like you know they wanted they're specialized and reduced and then it's often used in universities we have to have those kind of things so we would start working on that making customized solutions we built a custom profile and system that integrates with things that people saw which used for a lot of our financial parts of the university but also had a lot of just data about people's phone numbers and all that kind of stuff all that data was always stored so we leveraged it and brought that data into Drupal by getting a bunch of custom modules like next to the .NET so a lot of crazy development happening at the time and that's still there we also worked on this sort of a system that was an ink into SharePoint basically a file sharing service but you know check in check out files so a lot of that kind of stuff we started to look into again upgrades from 5 again right into even bigger problems because we were thinking about like there's even more modules that don't exist past people 5 so we were still not thinking about the long term implications of what we were doing we needed standards we needed a process of how we would view everything every concerned module that goes in what's the future state do we see what's happening do we see the community as you supporting this module so the majority of our sites we're still on Drupal 5 actually this slide is not quite accurate we probably were there until about 2015 he said portion we're there so between 2013 and 2014 we did our meeting with the question get us off Drupal 5 because we were in Drupal 2 somewhere in Drupal 5 and of course Drupal 7 had been out since 2011 or well in January 2011 it was the date so Drupal 5 at that point was end of life so we had to contend with the fact we're not going to get security up we have to manage this whole thing on our own so we can't do this long term so what we did was made a decision in late 2012 still moving like a bureaucracy we made our decision quite late we had to actually make a change or go something else we could be on Drupal 7 this is the first time we'll be cutting it we could be on Drupal 7 but we waited a couple years kind of saying a little bit behind the curve for a university and that we waited until everything we needed was already there like views was ready panels was ready all those different components we've been using on Drupal 5 are all available so when we did this we set up everything to make sure that we had all the two modules made we had to actually do an entire process of working with the features module to build all of our default standards in Drupal 7 and rebuild pretty much everything we did in Drupal 5 in terms of custom development for all of our things we can use and events and all those things that people now expected were going to work on their site we had a couple of other random things to contend with like we used, I'm not sure if anyone here used the old event module that was in Drupal 5 guess nobody anyway we had a workhorse of our Drupal 5 something like that that was powering both events back in those days that module ceased to exist partway through Drupal 6 like we did in Drupal C very much before it got there and it died so we realized that yeah this Drupal 7 port is never going to happen so we need to get off this thing so we developed an entirely new event system based on features custom dev from there for as far as migration so we migrated about 900 to the site well not quite 900 probably about 700 to the sites removed from Drupal 5 to 7 so it spent a great deal of time over those years figuring out every little problem that might happen as we moved along generally starting out with very simple sites that like just used portable, nothing much else they went over pretty well and then we were moving over sites that were a lot larger that had a lot of custom dev a lot of fix up cck and lots of views and all that kind of stuff like we needed a lot of structure to happen between Drupal 5 and Drupal 7 just trying to make sure that all that stuff was removed so it's been a great deal of time with that and that's a lot of our popular now so that's actually an update from 5 about 20% of the sites probably decided to rebuild that just started we're at that point in our cycle of the site anyway was figuring out all the stuff you don't need anymore and that kind of thing so that was nice for us some of those larger players that had a way a little bit longer they decided to go to the point in their life cycle that they wanted to rebuild anyway so that helped us to not have to make some of them but as happens in some of the enterprises there are some legacy systems you have to keep around so we actually still have Drupal 5 in a very limited capacity a few sites running on it I think at most like a couple of dozen for a variety of reasons many of them are running a little profiling system that just remains and right now there's no suitable thing for it to move to the people who built it are in various different positions now so it's not going to be moved by them it's like dude what are we using steps so it's remained sitting there for a while as you try to make those decisions so a lot of our customization we're preventing the upgrade or anything else one thing we've also done is been looking at some other consumer models that were finally important to some of these sites that kind of made us stuck so there's a few sites we have some of the magazine sites I think like that that would be like high to a model that doesn't exist past Drupal 5 and that's where we ran into these problems where we had to think about future state and we didn't have the time to let this model fit exactly what you want until we put it on and then when you realize that you're on you're like okay we just didn't have the upgrade there's a Canadian Drupal 6 port that's not really stable and of course known as Drupal 7 port and now in 2017 Drupal 7 was in 2011 you know that port's not happening so it's like you need to either rebuild or we have to make the port for you and when it comes to an open source product like this unless someone else wants to use this thing we just take it to almost completely we don't feel the need to port this kind of model anymore so we are actually some of these sites you really need to rebuild it this happens in enterprise I think a lot there's a lot of systems that just have to stick around for a variety of sometimes political reasons so we do have a few sites that still run Drupal 5 everybody else under Drupal 5 can I query how many sites are on Drupal 5 but how many are left the same number the same number right there that's the reason I'm there so we have remained to maintain this large on-prem service on-campus service from the 2016 to 2016 that was the one service we had it allowed us to basically think highly centralized was great we made a lot of decisions as we went along about how we were going to try and improve things but the decision was made at that time to let's move things to maybe another system let's look into products like Campion and Aquia, things like that one particular site that was a bothered by some of those that didn't remain on Drupal 5 for a long time was our home page now, Richard's answer to that was it wasn't like any other site the home page was used about 16,000 kids a day so it's a high-fax site I mean a lot of little digs down the server so if we did, especially in early age when we didn't have enough processes now we would actually try to offload that processor time to scrape the site so amazing for those who don't understand what we're talking about when I say scrape we just made static versions of the pages so we made it into HTML files images files and stuff like that we made sure they were on together so we had a static version of the Drupal site just for this one page so even working on that for many years we had stresses, we did this for people like once they published something they'd go to the Drupal site, make their change then go to the website they'd take a scrape for the home page and they would make a copy but the problem with this model was how long it would necessarily take to do that scrape it was unknown there was no real great way of monitoring what it was doing during the process so it would be off and we would receive support calls halfway through the scrape as the site got bigger and bigger and bigger for more files to copy over so there would be some panic especially with time sensitive releases and things like that that where's the home page? why is it updated yet? is the script broken? it's so nice it was broken legitimately but other times we'd just have to wait 5-10 more minutes and it will be there but this panic comes with time sensitive things that have to go out we have announced the school name is changing new it's going to be 15 minutes late so it was unpredictable we couldn't determine how long the script was ever going to take to run so we had to look into something better so we were like of course we're going to look at on-campus service we moved this into Drupal 7 maintaining sort of the same idea but improving it upon in some way we looked at a product goal and did an opposite and other things but we decided that it's we're going to look into vendors so right now it's hosted on Pantheon so they are actually doing just hosting the university home page and some of those microsites and that's what a lot of our custom development is going to now we're going to look at the home page so it wasn't justified we just moved the Drupal 5 home page out there we completely rebuilt the thing so I'm going to go into that a little bit more a bit about how it's going to be rebuilt but we will be keeping the on-campus service to the 900 other sites in the state for a while how long it's going to take we're not sure but considering it took us like 3 or 4 years to move to Drupal 7 in the first place it's going to remain for a while and then the next step is then you show all the components we need and are there so the two environments that push the need for us to really standardize so we learned a lot as we went over this through the years there's a lot of custom development we did the three models we added we weren't necessarily thinking about the long term implications so we tried a couple of things like how we're going to review modules how soon it's going to happen and I'm sure it will be made we saw the embrace that's soon as everything and part of that is working with the university-based department there you had their needs and what they wanted built but we had to make sure like okay this is the module that's going to do the work we're going to do some doubt from there but we have to understand these databases this support just has to have a long term for it so it's going to really be very careful about one thing we developed as well we moved to the first place is the entire concept of module review so we actually have a website that actually has just all module review we set up a building to post modules from Drupal and from there you basically say hey I want to install this what if the rest of the group think just talking to the web services team we would have to use someone else when they're improving you could just improve yourself we disabled purposefully on that site so we try to fix that full and with that our scripts that actually allows us to do the installations would require that site to be improved that's right, it won't be improved before it would actually install it for you so it didn't show up on the list of approvals, it was just a chase on services that's working it wasn't even that a lot of chase on data it was not about the installation so it prevented especially those who were in the service side of our service customers or the people they didn't have the ability to sell mine unless it was in the process so it made it a little bit better for us to have a bit of more control with the pantheon environment with the university relations people all the time we scrutinized every module, every brick every permission and I say brick because that's the language we use at U of C to talk with a new website so bricks is kind of the terminology used to do a lot of our custom dev which is mostly built around panels and page manager there's a lot of custom dev being done there to basically build the fully responsive content through panels and page manager and that kind of thing we also wanted to move of course to standardize field types because before on our on-prem stuff we built a lot of custom stuff that was making up our own things and we wanted to make sure that when we decided that brick would be so complicated beyond what we've done in custom dev so this is U of C as far as our service so it all of course showed pantheon to add insight into exactly what it looks like on their end but basically it was coming into the internet when we came out and hit our F5 machine which we basically wrote traffic into our proxy machines that we just called C4 or C5 the classification was and they basically decided are you an on-campus request or are you an off-campus request an off-campus request for going to pantheon so from there though, we really wanted to direct your attention more to the second half of the graph where we have those three machines in a line that is triple seven for us, we're on-campus versus this we have it's kind of point of pride for us to be able to machine nine percent multi-site and only on that's actually what we're saving the third machine in there is actually one of those three machines making one database server that is our triple seven setup we have the web pre-machine does exist but it's not actually hooked up so you can have the same file system as shared, the same database information as shared but the web pre-machine actually is not in production so we don't want to actually go to web three from the USCA and actually get the site hosted off there we use it for releases right now makes things a little bit easier for us we don't know what else is on this machine we're trying to run some Jeff's web services so for a while it's what we're doing hopefully speed up our releases a little bit so that's it this is a I'm just showing you like you can run a service as large as possible I'd say there are never any headaches but it is possible so just quickly to wrap up a little bit so we have some time for some questions most of our sites are now hosted on this triple multi-site on for the on-campus system 900 sites in production and 500 in various other states of existence development testing training sandboxes one random test and sometimes because we are a very busy team unless somebody tells us or reminds us of it it doesn't always get cleaned up right away so we have a lot of sense of just sitting out there we're like okay we got another query but I don't know it's just last updated so one thing that was great about the site the multi-site was allowed a lot of cool reuse you can actually reuse the same code have the same setup as far as directories and everything this is where you link off to all of the modules you can use if you want to we can set the basic standards out of the box and deployments were quite simple because we just really had to most of these are similar on the system to be like here pointing to the new version of the module the deployment is done because we are already on the same system one thing I didn't touch on it I just realized I missed it when I talked about pancans so we did a couple of other interesting add-ons to that system and I think I just skipped over it just to be more aware so we've done some things like panels cloning so we now have ability to clone panels a lot of integration would be on the panel things people use that module a lot we had to use that module to do our development breaks so there's a lot of things like now the ability to use schedule order publishing so it's kind of a schedule order module idea but integrating with the old panel things so that was a lot of how we built it other things like another one of those kind of group ownership modules so this group, there's like aniverse near the work perfectly for us because we were heavily involved in the little panel things we had to develop a test of integration anyway so we built our own version called concept ownership right now it's going through some trial and tribulation we're actually working on reverses of that but it allowed us to basically say if you are part of the marketing department you own this section of the site you can just check off for the old and that and they have their access to we don't have to worry about other permissions and things like that so it just kind of all rides everything it makes it very easy for people to assign an entire section of the site to somebody as far as we built that it was kind of a just a few of the things we can cost some debit so when it comes to the multi-site some of the things we have is some of the good and some of the bad so we have some drawbacks here since we have a single-core installation there's not a whole lot of room right now to do big changes so you are kind of stuck with everyone sharing this so you can't grant changes to configuration or anything like that so we kind of have to be droolful itself even though you'd want to if it's core you're not talking about touching core and editing core you know you can't make broad changes to server anyway because everyone's there so we shut down the site are there any problems with the names of the multi-site sites that are actually already in the graph that show up there a single site can affect the entire network if someone is just doing something crazy on their site they can eat up the memory of the whole machine so we have to be careful of monitoring what people are doing what you have along the way what we have to stop to and it gives us an insight as well when that happens though into like we can tell when models are feeding a little bit tweaking so we have some tweaking here and there to actually make sure these models are not running away with memory so that's going to be part of what we have to do on a day-to-day basis one thing that happened to us is that this is from Alberta going over to release their compensation disclosure list a year ago look at the time oh I am sorry I forgot to start at 1030 okay so anyway we released our compensation disclosure list and when that came up we were very busy with page action so we kind of took down some of our services for a little bit I should try to figure out what was going on and if any of the prices changed to our configuration of course again if that's everyone so we have to do that balance between performance and stability so another thing is sites for everyone who has caused a headache should all these sites actually exist we have now 900 sites is there a good business and marketing plan for why these sites exist so that's what we will be trying to push now to make sure that people have a good plan for what these sites actually do for them before we actually allowed them to have a site because we now have lots of stale content on these microsites we spent a lot of time on monitoring scripts like we had a lot of bash scripting now to actually check what our services are doing and warning us when we see spikes and so we have a lot of administrative tasks come up people we have to manage cross-seeing and all that stuff for like 1,800 sites so this is a major motivation so to conclude here the non-profit model is the key the adoption of the platform the rate of adoption I think was a bit of an issue because we were living at websites so quickly we weren't looking at a standardization and we had to think about it in the early days so it was sort of a lesson learned for us that we really needed to think more about standardizing as we moved in into the service so we put a lot of effort now into the platform to come and do building so of course I don't know how much time I have for questions because there are people moving on to the next one but I'd love to answer some so my handle is dp5c pretty much everywhere that's my university college my address, that's twitter, that's gamehub that's dupal.org so no one else has that name so that should work really well for me yes I was just wondering if you could get your thoughts around Google 8 and then also I see that there are kinds of things like paragraphs paragraphs and acts different ways yeah so something we've been looking really into now is of course the future in terms of like where can our development we have done especially on the pantheon environment and around this whole idea for us to move into something like Google 8 so we're aware of things like paragraphs and all kinds of things but we haven't actually used it yet because we focused kind of on being a little bit behind the curve to make sure that we are actually just there with modules that we know exist on Google 7 we know some of them aren't quite ready for Google 8 so I know the paragraphs are the big one that's kind of jumped in to fill the void a little bit and I've heard it's really great but I haven't myself used it much and I have to see how it can fill the gap with what we have now but I think it sounds like it really can in terms of how it's managing the stack and everything now but Google 8 I've been looking into that it's got a lot of great things I would love to use but it was more we kind of had to wait behind a little bit to make sure that every piece that we now use across these 900 sites is available as much as we can what's the size of your team? our team is small so we now have it split up a little bit between three different general areas so we have a service area that has four people so we have a service lead well two students one just recently left so we're going to hire somebody back on so it's mostly students centered it's doing a lot of the customer service side as well as a very experienced person meeting them we have a planning group which has a couple of people in there like a QABA and a planning person doing a lot of project management kind of stuff and then there's the development team which has a lead junior developer and two seniors including myself and then we have our manager as well so it's a small team and we have a person in the dozen to manage all of this stuff so we have in the past hired contractors to fill the gaps particularly when we first moved to KFM we had contractors with us for about a year and a half to help us get into the system because we had so much development to do with a few people that's right then we have another question with that I only want to ask that question how big are we? is there anything else to go to ask? I know a lot about how to get out I don't know if you want to rest about this whole thing I'm 43 I've been talking about any of this I was just talking about what you see me but as I said that handle is pretty much everywhere also to me and people and everything great thanks guys