 Welgrwm ar y trofod, ddweud yn y cwrtod, felly rydyn ni'n dweud. Yr oedd y newydd, y newid. Yn ystafell, wedi'i gydag, rydyn ni'n amser. Rydyn ni'n Cyran Sambrick-Smith, yng Nghymru Cymru. Rydyn ni'n Scott Hooker, llawer yng nghylch mewn tezglôr, yng nghymhysg Llywodraeth Rhywbeth, Ac mae'n ddwyddo i chi wedi'i gweithio'r ffawr o Oxbow Lab, y drwpal agenciaeth i'r USA. Yn ystod yma'r ffawr agenciaeth i'r platform, felly mae'n gweithio'r hynny yw, mae'n iawn i'r 5, 4 o 5 oed yn ymddangos a mae'n ddweud i'n ddweud i gael eu komaeth o platform. Ond we'n gwybod i'r sgol a'r wyf ar y twyd o'r cymdeithasol yma, o'r cymdeithasol ar y dywedig yw'n gweithio, ac i'n cyd-fynol fod y pethau'r cyfrannol yn ymdill. Ac mae'n rhaid i'ch wneud gweld i'r cyfrannol. Ond o edrych, eu gweithio'r cwrsiau o'r perthynau gan gweithredu. Y cwrsiau o'r perthynau? Mae'n gwneud i ddweud eich rydyn ni'n ddweud yn ysgrifetydd. Wrth i wneud ai wneud, onty mae'r bliddlofiwch iawn o blynedd ac yw mwy ffasmor a'r holl. Yn ddalaf ai bryd, mae'n holl eich meddwl, mae'n yn ysgrifetedd, mae'n ein bod yn ch Fanserbyn'r gweithio'r cerddydd gywed yn yr rewind dyfodd ac mae'n gofen nhw'n cael ei ddefnyddio gyda ar y cyflaedau. Mae gyda wneud wedi bod aelodau yn y rhan, mae'n cael eu isu ymgyrch yourselfau cyfeisio hefyd, gyda ditw am y cyngor felly dyfliadau a gwrs gynnwys yma. Yr Hoagau yn rhaid i gyd yn fwy gyd, byddwn i wneud gan unrhyw o bryd. Mae'n gwirionedd o amgylcheddau a gweithio, mae'n meddwl cyngoręfau, mae'n meddwl cael ei gaelig a mwy o bethau ychydig. Mae'n fwy gwirionedd o dudodf ymddiffio maen nhw! Yna y gallwn ni efallai am effaith bryd? Efallai yna cael ei ddweud, ychydig yn bwysig, fydd yn bwysig, maen nhw'n byw ddim. Felly, rydyn ni'n gweld i'w ddweud eich ddweud o'r ffaint o'i ysgrifennu cywbeth ar hyn o'r ffordd. Felly, cyflawn, ychydig, rydyn ni'n cyflawn. Felly, cyflawn yw'r byw, o'r byw o gweithio, o'r gwleidio'n byw o'r byw o'r byw, a'r byw o'ch gweithio'n byw o'r byw o'r byw o'r byw o'r byw o'r byw o'r byw, er mwyn peth sydd am trefnu hynny mewn ymddangos.fa yng nghylch ar gyfer ymarhwyr, o gyfrannu'r peth ar bobl, sy'n~] ar ôl. A chi'n wneud fyml, mae'r gweld hefyd yn gyfrannu'r mae'r gweld hefyd yn cyfrannu'r gweld hefyd ar ôl. Mae gyllenni'r bobl yn gweithio. Mae'r gweld hefyd yn gyfrannu'r gweld hefyd yn gyfrannu'r gweld, neu yn cyfrannu'r gweld hefyd. see a lot less unplanned work coming back at you. If you can get that right then you're cutting the effort at both ends. My point here is that this is a difficult thing to achieve and it can take a lot of effort to achieve it. So should our focus be on doing DevOps better? There's a lot of tools and experts in reading material out there that's all o'r bydd o'r effaith, ddechrau, ffongol, a'r ffordd, ddweud, y byddol, ymrwynt yw'r wneud, yw ffordd, yw'r lle i wneud, yn y cyflwyn, efallai i'w hi, yw'r dweud, yw'r dweud, mae'r ffordd, yw'r cost, yw'r dweud, yw'r dweud, yw'r dweud, mewn gweld, mewn gweld, yw'r dweud, yn y cymdeilio gweld, mae o'r dweud yn y dweud, yn y dweud, yn y dweud, ond mae'n ydw i fynd i ydw i ddoelunio, i ddod i gweithio, i gweithio, rhai'r amser, sydd yn oed i'r ddantasol ar gyfer y glaw. Felly ei wneud y gwirioneddau. Mae'r drosbeth yna'r unrhyw ei fod yn ymddangosol yw byddai eich ad seats llwyddon o gychwyn bwysig. Goisonwch, ei gweithio y ddantasol ar gyfer y gwirioneddau, gallwn yn y gweithio. A llwynt i'r argyf quicklyd, mae'r coid, yn yr ad sefydliad. Ac rydyn ni'n ymweld y platform, rydyn ni'n ymweld y platform, ac rydyn ni'n fwy o gwybod. Mae'r cyfaintau fel hynny'n gyfweld o'r rai cyfaintau. Rydyn ni'n gweithio'r cyfweld Cymru, dan ni'n gweithio'r cyfweld 100 o cyfweld i'r cyfweld i'r cyfweld i'r cyfweld i'r cyfweld i'r cyfweld. A'r cyfweld sy'n cyfweld i'r cyfweld i'r cyfweld, While we were delivering all these projects, basically fixed some recurring problems that we saw throughout pretty much all of those project deliveries. When we started the past project, it was always based around the concept of abstraction, high level abstraction. Starting with the application going down rather than the infrastructure going up. The intention was always to allow you to run very complex hosting infrastructures, but without needing to know about all the nuts and bolts that made them work. This is where Platform will continue to head. We firmly believe that our industry shouldn't be forcing our customers to become cloud experts. Our customers need to concentrate on their business and implement new ideas and fight off their competition and stay ahead of the market. All those things that they need to do, and we just shouldn't be expecting them to become cloud experts on top of all that. We believe the ideas that they can turn into code should just run, should be that straightforward. So, are we an idea to cloud application platform? Well, I think we probably are heading in that direction. We're already helping development teams move with speed and confidence through our rapid cloning. When they need to, they can branch hundreds of times a day to test with certainty and then continuously deliver and deploy. We're already giving our clients the choice to mix and match many different services and stacks to create the best possible solutions. In order to give you end-to-end control out of the box, we're extending our CI, CD capabilities so that you can run all your testing directly on platform. That's all your unit testing and integration testing, security and compliance and so on. We will also become a CDN, allowing you to put your code as close to the clients as possible. These are some of the exciting things in our roadmap. On that note, I'm going to hand over to Scott. Good afternoon everyone. I think this presentation starts with English speakers. I'm hoping that there's no Americanisms in my presentation that will confuse you or Englishisms, should I say. Let me start with an introduction. I work for a company called Tez. We're formally known as the Times Educational Supplement. We're about 120 years old. Obviously, back then we didn't have the internet, it was just a magazine that was published. But now we're an international organisation that deals mainly with education. In terms of tech, when I started at Tez, we were a massive .NET stack, which would make anyone gasp in horror. We embarked on this massive digital transformation to a series of Node.js microservices, which is not really my area. I'm not a Node.js guy. I'm a Drupal guy, which is why I'm here. For content management, we decided on Drupal, which is why they brought me in. One of the initial problems we had was whenever we would make a deployment, the site would go down for about 20 minutes, which isn't great. Definitely not great. I was tasked with identifying and reviewing different cloud providers. The first thing I looked at was, okay, wow, I have all of these different applications, and they're all going to need engine X, Redis, Solar, you name it, all manner of different services. The man hours that would be expended on building all those is quite a lot, right? It's something I didn't want to have to maintain myself. I don't really like to care about infrastructure. It's not what I'm good at. I'm good at writing code. I'm good at building modules. I like to contribute to open source, and if all my time is taken up in DevOps, I can't really do that. I'm evaluating the different sasses and passes out there. We settled on a platform, and hopefully over the course of the next few sides, you'll understand why and look at, I guess, how NoOps is a thing, but also if you like to get involved with your business logic, you can have someOps with NoOps. I guess a good place to start is we all use Drupal because we get good free things out the box, right? We use login systems. No one really wants to have to write that again. Content revisions and all that kind of stuff. We get it for free. We're all hosting these same kind of sites, so why should each individual here care about engine X, memcash, and all the kind of things I mentioned? Why would we build our own info when all of these cloud services are out there? Cloud for the win, I guess. So, not only did we need a place to host our sites, we needed a pass that would enable us to have our own workflow. As I said, we had no JS and a lot of different microservices, but we needed to mix that with Drupal. Platform SH lets you have deploy hooks. Here's a really good example of our development workflow for one of our sites. This was actually quite an interesting project. We were tasked with building free sites on the same code base, and this was all on Drupal 8. One of the things we wanted was to have the deploy hook decide which installation profile to install when we pushed the code up. Platform lets you have environment variables, so if you look up there, it says a CMS development rebuild is true. On any of our staging branches, it runs the first block of code, and if it's a live database, it runs the rest. That's something that you couldn't really do with other platform as a service provider, I guess. With a large team and lots of sites, onboarding was quite a challenge, so if you had a new developer start, I would probably spend maybe three to four days onboarding them, talking through how you deploy to live. That's three to four days of my time, three to four days of their time. Talking about two weeks of development. They hated it. They hated the response time, the downtime, the entire infrastructure. I come along, and I go, let's go to platform. I showed them how quick and how simple it is to deploy a site without having to write any specifics that are required. They liked the fact that you can have the multiple branches, so they had their project managers who were very disorganised. Ask them very last minute, oh yeah, we want to see this bit of functionality. You push your code to GitHub, GitHub will then push to platform, and voila, on platform you can show your project manager the branch working. It would increase the process of deploying the site because they had a very tight schedule that came out of nowhere. I think they're looking at moving everything away from that query, aren't they? Okay, thanks, Alex. I have to say that anything you've heard at today's session is not necessarily the formal views of the platform management team. But anyway, yes, we have a question, John. Yeah, okay, that's a good one. So our t-shirts just arrived. There's a ton of t-shirts. Yes, okay, all right, great. So thanks for your time. Thank you very much.