 Turn my phone off. All right, so the session today is a Drupal wet adoption with government. Everyone can hear me fine. I'm assuming. Don't need a mic. A little bit about myself. I'm the managing partner at OpenPlus. We're an Ottawa-based company with nationwide clients, primarily working in Canada. 100% of our deployments are Drupal-based. We don't do WordPress. All we do is Drupal. They're mostly public sector, largely public sector. The objective for my session is to share some insight on some of our government projects that we've deployed, discussed Drupal wet experiences specifically. Review some adoptions, technical debt factors, a term I want you all to be familiar with after we've done the session. And we certainly have a mixed audience here, so evidently this session is a business stream, so we're going to keep it at high level. We have a mix of government, GC, non-GC, technical and not, so we're going to try to focus on that. First, a problem with Drupal. A typical way to start a Drupal session, but it's something that we see a lot of, and it's important when you're talking about governance. So its strength is definitely also its weakness. So, you know, on one hand there's the big pro, it's open, it can innovate freely. That's awesome. That's what built Drupal. On the flip side, it's open, so it leaves itself vulnerable to poor code, poor hacks. And governance is sometimes a factor. So coding needs to be governed and, you know, needs to fall within the realm of Drupal. It also allows for many preferences. There's no set in stone for the most part Drupal best practices, although that's improving. You still need to ask yourself which approach is best, which methodology is best, which CI approach is best. There are pros and caveats, pros and cons to both, and you need to, you know, either go through experiences or deal with people who have gone through those experiences so that you don't end up making some of those mistakes. There are a lot of decisions that you need to do when you're building a Drupal site, especially one in government. You know, the bar is high in government in Canada. You know, we need to hit multilingual at a level that most other people don't even on the west coast in Canada, there's less of that. So right away that poses a big challenge. You know, just because a tool says it's multilingual, there's a checkbox and a flyer, it does not mean it'll properly meet multilingual, especially in a government mandated approach, same for accessibility. So, you know, decisions range from which modules am I going to use and that can be 100 plus. Again, pros and cons to each one is Drupal 8 ready. A lot of people have a tendency to think that Drupal 8 is strictly an evolution of Drupal 7. We sort of see it more as two different products because they're pretty drastically different to a certain extent. So you need to think of it that way as you're biting into big projects. So be mindful of technical debt. I wanted to talk a little bit about that. I've got a few slides on it. So many of our projects are restarts or round two of projects where we're either taking something that's had a shortfall coming out of the gates. And we've been doing more and more audits for clients and, you know, we've had several recent examples that we've come across. You know, this is an example of a typical site, the 3,500 pages, you know, simple site. But when you look under the hood and you see 214 custom PHP templates, 60 custom modules, 33 content types, and when you see segregated French and EM in the same site for different pieces of the architecture, you start to get some red flags. We've also done audits on Drupal 8 sites that we're struggling and, you know, a lot of developers are very eager to jump into Drupal 8, but if you have a government client, you also have a level of responsibility to factor some of those things and look at it from, is there an upgrade path to this module? Our security updates are going to be notified for you. So running alpha modules is something you need to be aware of what that can mean for a project. So there are some red flags that we're seeing on certain projects. It's something that's certainly a factor. So, you know, when you're doing a project, you need to think of what that technical debt might be and what, if you're a developer, what that might mean for the client, both now or later. Maintainability and sustainability. So if you're just very eager to code a lot, you could be introducing some maintainability factors for your site. Migration. So, you know, you could be impacting the ability to facilitate migration later on. Content architecture could be compromised. So those are things you always need to be factoring when you're developing a site. And the way we look at things is, you know, code really needs to be warranted. So if your notion of Drupal is strictly lifting the hood and coding away because you can because it's PHP, then that, you know, that sometimes can backfire. You've got to think about that. So there are some criteria you can go through and try to think about that. You know, every line of code is a bit of a weighted liability. It can impact security. It can impact updates. And you have to ask yourself, you know, why are you doing this? You know, we've been in meetings with universities where they've showed us some of the stuff they were doing. And our reaction is, oh, this already exists. There's a module that does that. So you have to sometimes think, am I the first person that's trying to achieve this? And it's unlikely giving the magnitude of the Drupal community. So that's only one component to think of it. Code is certainly applicable. So there are many reasons why you might want to do code, but you need to reason it with yourself and make the decision to say, I've got a factor governance and I've got a factor the rest of the community. Also, by nature, if you contributed back, you'll iron out some of those questions because the community will be collaborative with you. So if you're trying to do something and you squirrel it and keep it to yourself, then you're not getting that feedback from the rest of the community. Someone could come back and say, oh, this is actually really similar to this and maybe you didn't need to fork that module or maybe if you take this approach or put T strings around this and make sure it's multilingual. I think one of the reasons Drupal Web did well is a lot of the community was going back to those modules. I keep thinking about accessibility, but a lot of them was just improving the modules, making sure they were multilingual properly, making sure they were WCAG. A lot of people might be developing a module and not thinking about accessibility because it's not mandated for them so they might not care about it as much. But just going back to source, don't fork all those modules and then try to rewrite them just to fit your own need. Try to go back to the source and fix the original modules. A bit of an example of that real quick is, we've taken over projects where we'll see on the left side it's someone who's aware of a checkbox and on the right side it's someone that wasn't. So they'll just do some PHP hack to try to do something only because they weren't aware that there was a checkbox. So there's implications to that potentially, right? What are they doing in PHP or are they impacting the upgradability of the product, et cetera? So we're always apprehensive if we see someone who's a great PHP developer who's brand new to Drupal, there's a weighted factor there. You still need to be very oriented with Drupal. We won't solely talk about Drupal-Wet. We're still an element of Drupal with government, but for those of you who don't know what Wet is and of course there's always the WetBow, WetKit, WebExperience Toolkit that's all the same thing. It is a government of Canada open source code library that helps with accessibility. It's primarily Bootstrap with jQuery. But we also see it as a bit of a rule of governance, right? So there's more to it than just the library and the code. It's also the expectation, the expectation that sites will work this way. It's an example set if you will of responsive will work properly because that's been ironed out in all of these browsers. Multilingual should look like this. So the interoperability, if you will, is beyond accessibility and multilingual. And responsiveness. And Drupal-Wet is essentially a non-proprietary Drupal distribution. So I say non-proprietary because effectively all it is is a set of modules and a set of configurations that come for you. So when we say it's done properly, core is never hacked and neither are the contrived modules. And we see it as a set of accelerators. So if we're going to start a project, if it fits within the guidelines of what we think Drupal-Wet and if we think there's added weight, when we start there and out of the gates, the yardstick is already way ahead. So it's a set of accelerators, that's how we look at it. It incorporates the wet library in it, but you have to be careful how you define that. So it's pretty easy to make wet available to anything out there. You can just share the JS libraries and then say it's in your CMS. And some people have attempted that with Drupal. Some people have done that with AEM. But we like that it's actually incorporated into Drupal-Wet. So what does that mean for us when we say it's incorporated? It means that when you're in your WYSIWYG, your styles will come through, your classes will render, and you can choose that from a style. Your style paintings are familiar with some of the bootstrap classes and it will render the way you would sort of expect. So some of the markup, and it's important if you're thinking of a decentralized published, so if you're not looking to dream weaver your site, where everything's going to be HTML and you're passing through everything and you're going to be using the site, then it is important to know that the HTML filters are clean. It's going to turn it out and get rid of the junk. It's going to remove inline styles and it's going to try to make sure that the proper wet classes that are proving to work will be applying in the right areas. And that also helps a lot for upgradeability later. I didn't mention it here. The Drupal 7 branch was vetted by Equia. So Statistics Canada was commissioned to come in and review the distribution. And they did say it was one of the best interest reasons that they had seen. And as far as D8 goes, some of you probably saw Will's spiel this morning as fast as he was going, of course, but it's based off Lightning, which is largely premised with Equia. So there's some good alignments there. It's currently maintained by the Statistics Canada team and the Open Data team. And TBS is getting more and more involved with that and we'll see where that goes. Will could make the session and Andrew is not here today, but I always feel it's good to point those two guys out. They've done so much work on it. So, you know, getting started. This isn't a demo, but there are some pieces in here Will was hoping I was including and here they are. So if you want to find out a little bit more, you know, call it marketing wise around Drupal wet, there are some flyers that we have here. There's Drupal wet.org that has some information there that we tried to keep up the date. The projects themselves are off Drupal.org and that is difficult. You need to follow a protocol to have a distribution hosted on Drupal.org. You can't just, you know, the code is evaluated and you have to sort of qualify to get there. So one thing that's confusing for some people is there are two different naming conventions for the namespace. So Drupal 7 is in slash wetkit WXT. So I think that's just the decision that they wanted to refine how they were calling the product, no longer wetkit and now wet. So you actually have to go to a different URL in Drupal, whether you want the 8 version or the 7 version. So, you know, D8 is still alpha. You'll be cautious with it. It's on Drupal.org now. We were running it out of Github Repose prior, but you just run Composer and away you go. There are some simple test mail links there and in this way you can experience those two platforms. So by clicking those links, it'll effectively install the distribution for you remotely. It'll give you 30 minute window to do whatever you want with it. So it's a fun way to at least experience them. Sorry, as far as hosting goes, we've deployed it on everything. So whether it was shared services or on-premise, we've had to do with clients. We've had to do this with clients. Also, we were completely off the grid to do that. We've done Amazon, Canadian Soil, Azure, Acrea, I believe we'll be launching a first GC site on Canadian Soil in the next few months. Another quick way to get off the ground as far as trying the environments, if you will, it is one of the few recognized distributions by Acrea. So if you're running Dev Desktop, you just click start from scratch and right at the bottom, you get the web, you click install if you have an Acrea Cloud subscription and it's one of the three public sector distributions, so it's pretty easy to get one fired up. Once you've got an install of Drupal Web, this is what you get by default. This is the seven branch and it starts with a basic web site. So for a lot of people when they think web or they hear web, they just think it's federal government of Canada. No, the web library is used by a lot of projects, whether they're government or public sector or what not. If you've got similar needs where you've got to meet similar thresholds, then you can leverage when itself is open source. But so is Drupal Web. So the base theme you get is a sub theme that's vanilla, so you can modify it yourself on Drupal Web.org. There are instructions and even a video on how to create a sub theme. And if you see the leaf on the top of the page, it's what this renders out. So the Canada theme is in here by nature and by default. But if you're not the government of Canada, you don't need to run this theme. This is the Drupal 8 equivalent. So this is just a vanilla install and this is where you land. It's where you get the only thing we did to this theme to this install is turn on the Canada theme. And we also turned on the CDM, and the boxes on the bottom of footers are inherited automatically for whatever happens in AAM from the government of Canada. So that's a big benefit if someone is looking to, whether you're your own set of, if you have many sites you need to move and you are running a CDM, it's a neat approach. This isn't proprietary to the government of Canada, but it's neat to see that they do it that way. It's a great way to have a CDM to do so in AAM or WAM. It propagates to the CDM and then it's automatically inherited to your site. So no one needs to worry about sinking information for headers and footers. This is a new theme. I asked permission to show the screen. So some of you might have seen Digital.Canada.ca, the CDES if you will that Alex was talking about this morning. So we've got a youth portal off that same bootstrap theme that they've done and we're evidently open source and share this theme back to the Drupal community. Touching base on sort of the top 10, I'm a David Letterman fan and anything top 10 is fun for me to read, but key benefits of Drupal went. So evidently there's a notion that meaning accessibility, multilingual responsiveness, guidelines defined by TBS and I spell that because you know multilingual is a big one in there. Of course accessibility, but we've all gotten much better at doing that and especially even in Drupal 8 by nature it helps with accessibility. But multilingual is one that we see the most failures with. You know having access to characters, uppercases, we still see spaces, percent 20s, even the toggle and not jumping to the copper pages. So even Dries and some of his status poor requirement for treasury board for multilingual. Those are factors that we look at so we often hone in during our audits on multilingual. And responsiveness, you know same goes we have I believe the threshold for TBS if I remember correctly is 5% of your browsing analytics you have to support that browser. That was a threshold back then. I'm getting some nods I think that's right. And then comes with it. So that's a benefit to know that it's got bootstrap and wet there for you out of the gates. So if you need a candidate.ca theme then even better it's there for you. It comes with workflow staging moderation, versioning and audits things that in Drupal 7 you don't get. Workbench is there so there is a way to deal with content workflow moderation that's tested into the environment. That's good for you to experience if anything it's a set of templates. These are how the content types are built. Here's how the taxonomies are. Here's how they translate. So it's a good basket of seeing how things are built that we don't comply. Account roles and it is group ready so we've done many Drupal deployments where LDAP or Active Directory we plugged it in with Domino and inherited all of their roles and users automatically to 15,000 employees at a government department and work with other environment so it's certainly proven in that sector. I'm just continuing the list here so number six. It's extensively tested. I can't say enough about this because you know in Drupal 7 there were a lot of decisions that needed to be made and of course same thing applies for Drupal 8 but it's nice to know that all of those modules in this case with this theme you know goes through unit testing goes through security testing has cross browser testing so it's a shortfall that we see when we do our audits so we appreciate it even more and we use Drupal wet but we also tend to take it easily for granted. Maintenance so patches and updates of course is an element to is one way to look at it but by nature you don't want to only update modules it can have side effects to your site so it's good to know that the Drupal wet team will evolve some of those modules for you and will also evolve the wet updates for you so you can align yourself with the distribution but you can also decide to maintain it on your own it's still just Drupal so you don't need to necessarily you know hit your rag into that cart but it gives you some real slides this morning so this is one of the reasons we chose Drupal is because it's got vested interest to work with as many things as possible web services, APIs, you have to just not worry about that you know it's going to try to adapt and integrate with anything so we're seeing more and more of that we've done integrations with various databases Oracle, SAP, Microsoft will spoke a bit about that this morning around CCAN but we were doing that with Crown Corporations where we were harvesting four or five other databases and presenting them in Drupal and they look local but they're not in Drupal the benefit of that is you can take an environment that's very expensive or take a legacy environment and then you can harvest it with solar and then present it for Drupal and now you're meeting accessibility on your needs so that's something that's even come up with we're working with the Preview Council for the Youth Portal and of course some projects start off with a simple I need a website and that's where it starts but it's always going to evolve most web environments do so later on they might want a survey, they might want a poll they might want web forms commenting or social well it's nice to know that they're there they evolve when you sleep even the stuff you didn't think you needed they'll be available to you and I wrote features there because that's a lot of how we tend to work if I know that the department is running Drupal web and some of the department is running Drupal web it's easier for us to take a feature put in all the modules you want configuring them and now it's more interchangeable so it's easier for department to say take my feature so the more things are similar the easier it is to co-develop and co-development is a big topic with governments we want to leverage that equity and stop having all of these departments reinvent their own in the wheels which gives a lot of credit the stats can they could have easily said hey we're going to do Drupal but we're just going to do it on our own and a lot of departments do that it's hard to contribute but it's nice and it's a lot of venting we're hoping to get them back off the ground and the last one also incredibly important is bulk scripted migration friendly so I'll talk a little bit about Canada dot CA and AEM around bulk migration but it's got a lot of options there's been several sessions I think even here today on options for bulk migration whether you're using feeds there's all kinds of approaches about that and you're also building up technical acumen and some of your scripts so we have some migrations where we can help you move from 3 to went 4 we know which classes are deprecated we can try to deal with it on the fly when we're doing a bulk migration process we can automatically apply HTML filters and we'll look for certain things and strip that out so there's some neat things you can do but I'll get into that later so four boxes that we sort of look at that we know Drupal Web has worked well for us evidently if you've got a web renewal initiative you've got a lot of websites you've got a deploy or even one but if you've got a very simple site Drupal Web might be overkill Drupal might even be overkill so depending on what your bar is if it's a static site with brochure site where all sites go we always lean on Drupal and if you've got multi site on Drupal Web and at the very least distributions that you can manage yourself if you've got a lot of sites is a big consideration my account apps evidently if you've got authenticated log in Drupal Web is a good fit as Drupal is on its own online digital services we'll look at a couple of examples of digital workplaces with so it's certainly a consideration so why consider Drupal Web evidently for us and if you followed Alex on Twitter which is hard to do because he does so much of it you'll see some of the trends that the government has learned from some of its mistake prototyping I think is more and more important so they talk about failing forward trying things build prototypes don't go all in first and hope for the best a little bit like what they did so we believe Drupal Web is the best way to prototype almost anything A, you have access to the tools you know I wish I could download GC docs or even AEM to build from Government of Canada and work with it but you can't so having access to the tools is a big piece to build my app in it and meet a theme whether it's Government of Canada or not but if you are Government of Canada then it's like an amplifier of five because if you have to meet Web it's hard to integrate that and really only an open CMS will be able to do that we believe so if you need to meet a Canada.ca theme then it's a huge amplifier to build your prototypes on that we'll actually look at an example of a project we did on that so that gets you fast results and it's easier off your budget probably thinking that as I said but that leads to better buy-in and it leads to your pilots a lot of like the GC tools example you guys were able to do a lot quickly and that gets buy-in people see results and it's when everyone gets on the wagon so it's also future ready so it's nice to know that you know even this morning we saw a wheel show the like button which ironically we were struggling with one of the Drupal 8 bills that we wanted to flag so it's just nice to know that as a distribution and as a module or framework like Drupal you'll inherit a lot of those things if you just go looking for it even the stuff you didn't think you wanted is there that's one of the big benefits and I wanted to point that out because you know I've been promoting open source for a long time and now what's dotnet open source so now I keep hearing that now well dotnet's open source too is that in Drupal you have pure play access to the capabilities and the functions where for dotnet that's not exactly applicable at that same layer so you know a lot of that stuff is still tied to a licensed product somewhere that you need to get to so it's not instantly available so a critical mass of a lot of people using dotnet is not the same evaluation as saying a critical mass community of Drupal because there you have the capabilities you have the tools of course nice to know that it will be supported and it's proven so if you put a lot of effort in trying to get wet into Drupal well you're going to have to keep evolving that so there's another technical debt you're going to have to sustain and keep working at that so if you know there's another entity doing that for you all the better and if you leave wet out of it at the very least it's a distribution that you know is tested I mean it's had thread risk assessments and that testing has taken place so you know we tend to rely on it and so do our clients usually they like to hear and see that oh it went through all of this just recently I got an email from Andrew from StatsCamp because the Treasury Board was asking what about cyber security and we're just trying to get them to point to themselves and I literally got one department to give me a list of everything they had done for cybersecurity testing and provided it to Treasury Board and making them realize the benefits that they have across the table you know don't start from scratch this doesn't imply directly Drupal wet you could have other distributions if you're a good size Drupal shop now you're probably rarely starting from scratch on your builds you might be off-penopoly or have your own recipes there's a lot of ways to not have to do things manually but on the flip side if you're just getting going with Drupal and you've got a tall order you know that could be a steep learning curve and you've got to be you've got to be thinking about the the bigger aspect of the project so some examples of Drupal wet deployments I put all of these on the same page because most of you saw it this morning but this is the open.canada.ca the open by default the far far right corner one is interesting because I think when StatsCamp launched their site they wanted to do a bit of an exclamation mark so it's nice that there's actually a user account you can sign in you can rate things and you can comment and you can control your own dashboard and you can register for RSS fees all things at a typical static site or that AEM sort of was not addressing right away it was just to show that hey a good database driven content management platform can do a lot of this stuff for you fairly easily so it was sort of a again an exclamation mark to keep the melodies that they could come out we wanted to talk a bit about this industry Canada project that we did and it's got its own exclamation mark to see that in 30 days we were able to prototype a site even down to doing the bulk migration of the users the data and getting it fired up hosted and launched so that's a pretty incredible timeline when you think of government I wish I had the before pictures but effectively we were able to start with Drupal website build a custom front end again the headers and footers automatically inherited from the CDN from the government of Canada authentication from the top so it's easy for them to create their account there's an approval process evidently to allow them in there but this is for scientists to put their resumes online so they go in create their profile there's a whole moderation process that's already in Drupal and once it's published and approved by industry Canada then we fall into a sort of a search interface so you see some similarities there from what you maybe saw from the open.canada.ca but again the same search API facets are available to us we didn't next to know code on this it was understanding the architecture of Drupal Web so we called it browse profiles instead of search that a client wanted but that's sort of the modern day experience a big keyword search string with facets on the side so you can sample down in your data set this was sort of just a bit of a mind map of the approval cycle from creating an account to a scientist putting up their profile and getting it approved and then getting it posted Web renewal initiative so we'll talk about what that's not Adobe I guess about a year and a half about two years ago already we started with the province of P.I. to do their own Web renewal initiative so they had around 50 sites 80,000 pages and they had around 80 staff members that they needed to train and adopt a new platform what I like about P.I. is they're a very small province with a lot of the same needs as some of the big provinces so it was nice to see how they they had no choice but to leave Vember on there they had not touched Drupal at all they ended up training all of their technical team and they're pretty much self-sufficient now as they work with projects so from design to content architecture this is their primary site now they've got all their health site is on there all of their basic content they pretty much rewrote a lot of their content so there wasn't bulk migration but we're real big fans of good content architecture so we find that a good example of that is when you look at search results so if you've done a good job with your content architecture it usually comes through on the search results so if you've got good facets that can define your types clearly and then your topics come through and even having a search experience where your files are in there and it's looking inside the PDFs inside the word files inside every content type and then it's all refined on the side that for us is a good example of a good search experience and we even had some big competitors from Drupal and Toronto contact us on this and say how did you guys do this because it was interesting and they even had their developers pointing back to this actually their client was pointing back to this saying well it's got to be done look these guys did it and then they went online and said well there's such API issues too they also moved all of their online services so we talk a lot about digital services with government now it's a big topic with the federal government but again they had to leverage a lot in order to achieve this and to put more things online so there's a bit of a I know the bottom diagram doesn't necessarily come through but it just shows a lot of the politics to monitor some key performance indicators where someone starts a form and then abandons it well that's an indicator that's good for government to know what's happening at which stages along the way decision points so when someone went through and went online to buy something or even pay taxes it needs to then be sent off to an archival system that they were using so we needed to map all of that out and this was just to sort of identify that they had a big variance of forms that were electronic forms that were PDFs or just a link that would point them to someone else for just a 1 in 100 number and those sort of encompass a lot of the typical gamut of web services we were able to sort of put all of that together so that at least they could go shopping in one area so here are all of our online services it doesn't matter which type it is or the delivery mechanism they were sent off to other sites and they were all in one area so you could search for all the services that were there you could refine them, filter them and get extra information so it's sort of like providing a stub record once you found the right service we would then punt them to a really sophisticated web form that allowed for some interesting variances some of the slide panels are just to show here that someone could register for notifications they had a small feature that says add a reminder that I got to pay my taxes or that I have to do this or that my permit is going to expire it's sort of like a self volunteering approach to have as a reminder mechanism so some neat little features that we were able to do there for some real good value because they're sort of available in Drupal this sort of paints a picture of some of the forms and processes that they go through one of the big things we were able to do is say they had about 1,000 services that they had to fulfill I want to say that maybe 85% or 90% of that fit into a bucket of six things and there's a lot of commonality to those six things so you either had to pay or not pay it was either a web form or not so there was a bit of a criteria that when they go and need to put a service online they were presented with that first screen saying I got to add a service pick out one of these six and when they picked the service we were using some common templates where the metadata wasn't the same so there's a lot of commonality to a lot of the services online so there's no need for them to specify ask for the phone number ask for the first name a lot of that stuff was common so there was a template machinery when they would fire up a service I think they were saying they were growing online with a service in like five minutes it took them longer when they had to get a payment authorization code to put in there than it was for them to deploy a service online a table that adds rows like an electrical permit where it's based off volume so depending how many items you were buying would define the price we were still able to put some conditional rule logic so they didn't need to know code they just needed to be trained on some of the rule logic machinery so that they could put their services online and then we tied that in with a payment gateway but the other thing that TBS had been talking about and what we should have is users first so a lot of everything should be governed by the public's need versus reverse engineering to what the tool can do but for us it was really telling that there was a CBC article I believe it was for a restaurant license that they commended the PI government for removing all the red tape they were able to get approvals for something that was taken months now they are being able to do it but we have a lot of other projects we wanted to show so this is actually the same project and that's an asset in itself so on the left we've got the Canadian Transportation Agency they struggled a little bit deploying their own custom version of WET and that was a little bit difficult to maintain so we recently relaunched them on Drupal WET but the benefit there is a good side that you've got a good architecture in your Drupal site it's good it's usually a good indicator but in this it was fun because everything we were doing in the WET 3 even though that's actually WET 4 markup the look is associated to us WET 3 we were able to toggle to the new look for Canada.ca so it's literally a toggle to experience a bit of the difference so that's interesting for the client they're able to experience it a little bit differently so this is the department and I think they're trying to resist the AEM approach right now another project we've done is official languages so the closest one to me right now on the left is premised largely off the Canada.ca theme this is an intranet it's called Echo and on the far right you've got their public site right now and I think that's still on 3-something but they're upgrading now but both of these are premised off Drupal WET this is Health Canada's intranet which we have to remind them they actually had the new look and feel ready so I think they're still running the older look but again a similar benefit they were able to update the WET 3 look and go to a more updated look by just updating the theme so this is what the 15,000 employees will see when they log in it identifies them automatically these are all linked to their authentication in the morning when they get into the office it's got group capabilities and it's got a user dashboard similar to that it's actually NRC they're actually in the room as well so they've premised their intranet off something very, very similar again the users can set their dashboard and I believe there are some components of this that are governed so a user can say well I want to see this on the far side and maybe I'm in Regina so I want to see Regina news to the other things that they don't want them to control and then we have some prototype components that we had worked with some of their team on municipal level this is City of Hamilton great looking site you see that they've got their alerts at the top so we helped consult we didn't build a theme for this but this is a Drupal WET build custom theme over it deployed, they added alerts but one thing that was fun with this project was the version features earlier which is a really bad name but it's like an app it's like an add-on bolt-on app because we knew that they were Drupal WET we knew a lot of how their architecture was built so they needed to build a lobbyist registry application so effectively we were able to package up going to the Equia Cloud and install it for them and it just worked because we knew a lot of we knew that they translated this way and made it more easily to bolt-on addition of features and capabilities so in that lobbyist app there could be four or five modules configuration a couple of CSS tweaks to make it what it is but it was a great example and if you had several other departments let's say that were needing a similar app then it becomes a good example of co-development and sharing Environment Canada some similarities there but very similar to the Industry Canada one where they've got partners from around the world that come in and track issues around environment and it's got a lot of interesting capabilities you can authenticate yourself select a bunch of documents export to a CSV so you can see the benefits of what maybe the open data team had done Drupal WET as a whole search API, facet API those are all things that are giving us a bit of a shift I'm sort of leaving government but this is United Nations commissioned us to deploy Drupal WET this is on Azure so this was for UNESCO for their equivalent of Open Data, if you will so what was fun with this one again is we premised it off Drupal WET there was a lot of custom theme I need DataX4 for visualizations, for data so there were some very neat components to this and again it was all through Drupal you see on the bottom you've got four or five little visual graphs that show indicators and the screen at the top to the right is Drupal managing that data for you so there's a data API integration but Drupal is still playing a role in facilitating them putting up an indicator and referencing it in their data API so it's a big factor for them as well so we made sure that we had sort of an all-encompassing search results whether it's data sets, indicators news pages, documents all goes into your main search another province that seems to be leveraging Drupal WET this is a project we've done with the Yukon government this was a learning a labour market site which effectively pulls speeds so it actually goes to jobs for Canada job bank it can pull feed from various sources and re-aggregates that data from our assess sources into a search result so it's pretty neat to be able to do this because again someone goes to this Yukon site searches a job bank and it's all coming from remote data sources but it's like if it's local you can't even really tell that they're from remote sources and it's not from Drupal WET but again we harvested a lot of the known capabilities we could get it out of the build and we think their main site is moving to Drupal WET at least that was the intent this is a new site that we've gotten to go and I wanted to point this one out we just won this project but what was interesting with them is it's nice to see an RFP come out where they're actually asking for a WET compliant CMS and we've heard people saying well I can't go and ask for Drupal I've got to ask for a content management system that's not entirely true so no different than a government department can go out and say I need help with SharePoint they can also say I need help with Drupal and in some cases this is a .gc domain site this is when you go through security at an airport it's this group they actually went out to Tenor and said we want a WET compliant CMS so we ended up working with that already on Drupal now they'll be moving to Drupal WET evidently there are some interesting high security requirements that they had and I believe this will be the first Aquia Canadian soil project which I've been told by Aquia that in the next few days that the Canadian soil region might become available but getting contracts like this I think it's helped pave the way to sell the AWS finally landed on Canadian soil it was just a matter of time before Aquia followed suit some other Drupal WET projects that are open plus everything else before this was but we certainly know that other people are also harvesting the environment so the PMO site has moved to Drupal WET I believe our CMP is I know it's using WET I just don't know if it's Drupal WET or if it's the add-on theme I think NRC's got some projects in here some of you might have used that so that's another Drupal WET site I wanted to talk a little bit about again web renewal initiatives so you know for us it was a good example and a good starting point it doesn't mean that it's for everyone but building a distribution is also difficult we worked a lot with the University of Ottawa and at the onset you know they learned a lot from the Drupal WET distribution and they had a lot of developers and they had a good size team and they were able to harvest some of the know-how from that and build their own distribution they had a big requirement themselves and they had close to a thousand sites and you think that Federal Government of Canada has 1500 sites well they're like a small government and they're unrated maybe even arguably a big government so they decided to build their own distribution and I believe at the TLM we were able to port a site over some of their institutions so it's sort of a good example to say open plus was commissioned to come up with the look and feel theme and through a bit of our know-how from the Drupal WET distribution we were able to recommend but they did a lot of this internally themselves so now it's pretty easy they've got a whole site dedicated to all of the online documentation here's how you manage your WYSIWYG here's your governance here's all your online documentation here's a request to fire up a Drupal site and there's even site copy capabilities if you need to fire up a site they've since done their student portal their employee portal and they also integrated a lot of their black site or communications so they're sort of a header on every site that they do if there's an alert scenario then it's going to blast out an alert on all of their media so when there was the firing of Parliament Hill they got to use this and it was remarkably successful all of their screens all of their social networks went dark and alerted everyone to exit campus very similar the PEI government the examples I've showed earlier they were on the news maybe six months ago they had a school of an issue and again they made an alert that there are several criteria you can say this is a red alert it's an emergency or this is just a notice there's a water main on Main Street but they were able to send out and appear on all of the pages for all of their sites so adoption with government not going to spend too much time but I get asked a lot about WebRidual it's just a point out that it's a big challenge so anyone who's doing many sites there is a big information architecture challenge so there's a lot of good people working on this and it's a tall order but a lot of people don't realize that Drupal was not factored for the Canada one it was an Adobe win by default so it is a direct result of a poor RFP so I think the government had to make lemonade out of lemons and it was just a matter of time we feel but whenever you put so much energy into a big RFP not unlike what Alex talked about earlier today this was a few years in the making multiple RFIs multiple questions calls for cancellation from history it was a mess and we don't have one qualifying vendor at the end that's usually a bit of a red sign that just shouldn't happen and a lot of governments that's not even the competitive process Drupal WetWe offers some better government options it certainly has better bulk migration options we know that for certain Adobe actually approached us to try to help and they gave us the build it's got a lot of component uses and it's a very different architecture that we don't even feel lends itself well to HTML for the most part so we're certainly telling our own clients to say hold out for AEM we think that that's got a bit of a shelf life and I think there'll be more and more Drupal options coming to the table if you're doing your own work or doing your own initiatives whether it's for your own department or your own government or an open platform a critical mass is a big factor I don't think there was one AEM certified person in Ottawa when the contract was awarded yet work with experts and stay away from proprietary lock ins it sounds like common sense but apparently it isn't some procurement considerations for Drupal so few things that we typically see I only have a few slides after this something we typically see is don't expect one dream resource so we'll often see this where we did one Drupal guy and he's got to know everything front end, back end, hosting, period of performance AI, information architecture, theming you're going to get what you get if you expect that so usually we've seen some concerns with that Value is definitely important more so in public sector I would argue but rates alone is a mirror of value so we've experienced that with clients you know, restarts are more expensive than anything else and when you only look at rates the government typically teabips it's often erased at the bottom or if it's a solution that you're buying that often will just translate to less time being included in the bid so sometimes you could just hurt yourself if you're putting out tenders that look like this isolated resources can sometimes have some problems on learning on the job but it can work well so we've seen some good examples of this usually if you get a few resources working together or even a few vendors you'll get some good opinions if you get one person that's working alone evidently they're going to be a bit isolated it's not the same to have one person who's learning on the job sounds like a bad term there's always a learning curve to something but it's very different than when you're working for a vendor where they've got a bunch of Drupal resources even if they're working outside with a client they're incubated into a space where they learn a lot faster agile procurement approach that sort of goes without a say but just in a matter of time here I'll jump to the next slide so some tips on deployments start small I mean it sounds like you have to review where you're at if you're a big university you can still learn a lot from Drupal Wet or start doing your own distribution it's sort of a road map to try to get to how you can manage things an agile iterative approach again it's something that how you look at it so if you're going to prototype it's a great place to start you have conceptual prototype that can sort of pitch the approach it's like validating what you're looking to do so often referred to as a minimum viable product so D8 is still very new so be cautious there that you don't go down a rabbit hole and you might start up with Drupal 8 and then you've got a lot of little components that aren't known yet or there's captured modules that aren't yet on Drupal 8 now you're in the bed of a catch 22 who's going to have to part over that is it going to be you what's the extra weight for that certainly Drupal 7 is more mature if I just look at web forms there's a lot of components that are available in Drupal 7 Drupal 8 web forms is coming along nicely but there's not as many components there that even want to try both streams get help so even just going to the open plus site there's a chat box if you hit a roadblock you can always chat with us online we'd like to give guidance good content architecture and a good content strategy is key so you've got to think about some of these big decisions so it's important to get a vendor that's got some expertise on technical debt so every decision you make early on can amplify if you don't want to do a restart and I think that last bullet is interesting as it relates back to the first thing I talked about is by nature being open amplifies the value of experience in here so as a client someone might not look under the hood and evaluate and approve everything that's the nature of how some things work but you need to be mindful of having a lot of rope to someone who's in an open environment so if you don't have someone on your team that knows Drupal a lot then you've got to factor that when you're working with a consultant and yet it's still just Drupal so when you're deploying Drupal wet you can certainly learn from it take pieces from it we'll talk about how a lot of this is now premised off lightning which is a vetted andquia distribution if you will so you can either start off lightning with a set of modules you can turn off what you don't need a lot of the bills we do with Drupal wet we still were turning off Panopoli or Panopanapanelizer so there were some components that we would undo because we were spreading out the architecture a little bit more deeply my last slide we're looking for more talent more partnerships whether you're a consultant or someone looking for a job please send me your resume if you have a lot of audits of late you can email me or send me some any questions you might have but I think we got a few minutes because no one's come knocking in yet and we got going a bit late so does anyone have any questions yes regarding D7 versus D8 I saw that D8 is in an optimal what's the future of it when it's going to be better so great question extremely difficult to answer only because the dependencies are linked to the community so it's very tough for us because like I mentioned earlier it's a natural tendency to think that oh it's an upgrade so first and foremost you can't upgrade from D7 to D8 some of you know that but you're also tied to specifically with Drupal wet to some of the right contribute modules so I know some of the last for example where we had a few issues with break crumbs there was a couple of components that were an issue so I don't know what the roadmap is as far as saying if you were out of alpha a lot of that does point back to there's a couple of modules in there that are alpha and even if those let's say you pull all of the alpha or beta modules that are Drupal ain't wet if you start to use it and you're now on a release of all the right modules it's not ready yet then you're back into that so it's been a very circle there's a timeline to that people keep saying well Drupal ain't been out for you know two years now yes but it's dependent on a lot of modules keep in mind a lot of people that don't need to hit government sites at the level we do they've got a lower bar so it's a bit easier to transition to Drupal ain't wet so that's our first Drupal ain't wet build we've done some simpler Drupal ain't sites that had simpler requirements even somewhere whether it was a small alpha or beta module or whether it was an issue only to get our learning curve up but as far as and even in that build there are a couple of alpha modules in that one but we spoke into the main team we know exactly which ones and there's a bit of a roadmap for those so but we're on the cusp and I think for almost a year the open data team says I had Drupal ain't kind of at three months at three after months it's been a tough road to get to Drupal ain't through that build but they're certainly getting there now yeah what would you say and not whether the site goes to Drupal ain't now it's the proportion of these 7 or 8 playments that you're doing the reason I asked that is largely because I'm a mechanic scientist at museums and we were recently going through that debate and we didn't want to sort of lock ourselves into the an end of life situation sooner or later so that's a good question a lot of our even some of our we've got RFPs and proposals that are out there which are still recommended in Drupal Senate there's a decision point for each one so there's the vendor aspect of that you know there's a if an RFP was written in a way that you're just considering it's a deliverable project and you're holding the liability and all it takes is one feature a component where wow there's no module for this yet in D8 I've got to write it I've got to port it I'm on the hook for this so we know that in D7 it's at least mature so a lot of the decision factors will be in the number of capabilities or number of requirements that you might have we've seen this with the Ontario Legislation Assembly they're demanding 8th we sort about out just because it was very strongly worded in their proposal and we know that they're going to have some experiences with that that will put a few sticks in the spokes but now we are trying to get us back into harvest some of that expertise that we know there can be some challenges that said the good thing about Drupal Web was a lot of the decisions that were made along the way they were big but you know there's no no translation it's all entity translations but that's how it works in 8th it's workbench workbench now part of core for 8th panelizer now part of lightning so a lot of the decisions that were made collectively with Drupal 7 Web are showing that they're moving over to 7th so Drupal 7 and Drupal 7 Web are pretty different in the sense that Drupal 7 Web is much closer to 8th again all entity translations etc so it's an easier port over to go from Drupal 7 Web to D7 Web than it would be from so I agree with you it's a bit of an end of line to say well I don't want to release on this now there are some caveats that you have to consider if you're looking at it that way I think you guys are on open text platforming I'm not sure but right yeah Alex and I actually spoke about that so there's you know there's the notion of looking at a few phases to say what would be some you just have to factor time so you might be able you might have to buy time on a couple of those features but all you have to do is go in with that eyes wide open just the fact that you're asking that question puts you in a bit of the driver's security you're asking the right thing so vendors like us love to hear those types of questions because you're aware as opposed to preaching and saying I want D8 there's no reason you shouldn't be able to do it no that's an naive approach so we would probably come to the table and say yes we can do D8 we can still do common things still do certain things but you have to understand that it's either probably more of an agile approach you know you do spritz these four or five last ones we would recommend you wade the next phase so if a client is you know open minded that way then yeah we'll definitely work with Drupal Drupal 8 so with Treasury Board we wanted to go with Drupal 8 because we also had the backing from the data team I'm done so I don't know if anyone else had another question but that's about it for me there are some brochures here if anyone wanted a little bit more takeaways a little bit of a dated version but