The body of a missing Bemidji woman has been found in a heavily wooded area down the street from her home. 26-year-old Chelsea Bochelder was reported missing by a family member who had last seen her at home 11 days ago. Investigators were able to determine through surveillance videos and interviews that she was walking north on Little Norway Avenue southeast before she disappeared. Neighbors tell Lakeland News that they are shocked and saddened to hear that the body was found nearby. The Beltrami County Sheriff's Office says an autopsy will be performed to determine the cause of death. Law enforcement officials are asking anyone with information pertaining to the case to contact the Sheriff's Office at the number on your screen. If you've enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland Public Television.


that the site has a top navigation, essentially. And the problem there is that since legacy has been around for 15 years, there's 15 years worth of business logic that has been baked into their older .NET platform that had to be exposed. And those preferences had to be properly mapped and migrated. And the same will talk a little bit more about that migration in a little bit. And then the last component here is this concept of infrastructure and the appropriate infrastructure and understanding what kind of trade-offs we make when we have certain caching strategies at different layers.  The Node React web applications was being hosted on AWS, but we also had this separate data center which was hosted in Chicago, which was the .NET platform that also needed to consume these APIs. And there was a very specific SLA which needed to be hit in order to ensure performance across the ecosystem for these APIs. So as I mentioned, since we are dealing with two different teams, so managing velocity around that so that there are no blockers for each other, right? So we chose a common methodology, which was crum for this project. And in terms of Drupal development, we were always one sprint ahead of the front-end team. And we showed that we were very proactive in sharing the API designs up front, and so we basically one block the team to manage. Also, it was very important. Since we were excellent by nature, it's a very distributed organization. We spread out all over India and the rest of the world too. And there's another client who was also distributed. So they had three different offices that we had to work with. So it's really, really important for a project of this size and scope that we keep the communication channels open and we over-communicate to see the success. So we used tools like Slack, Zoom, Skype, email, phone, even pull requests. So there were a lot of commenting that was happening on the pull request itself to ensure that we were never really blocking each other. We got the information that we need and we kept moving on because it was such an aggressive timeline to be hit. And they had defined a pretty hard deadline. Then some of the Drupal best practices that we followed during development were having consistent environments. So we knew pretty early on that the solution would be hosted on Acquia Cloud. So we said, OK, what's the closest environment that we can get our hands on and bring it into our development early so that there are no surprises. We could test it and all of that. So we took Jeff Gierling's Drupal VM, brought that as part of our code base, actually. So we pushed the environment as part of our code base. Anytime someone would check it out, they would have the environment within it. It's a vagrant image if you don't know it. And that's how we developed it. That was our consistent environment that we followed throughout the lifecycle of the project. We also established a Git workflow within the team. We followed release branching and feature branches here and ensured that we were maintaining release nodes diligently. It was very important because we were constantly delivering solutions or delivering the developer product over to the front-end team. We had to communicate that. And release nodes became our de facto document that everyone would refer to. We also used Drush build script and established that early on in the project. So this helped us maintain updates to core contrives, any patches that we are putting in the system. It was all automated. So this would, again, save us time, any new Drupal core release that came out. It actually did in the last four months of our working. There are a lot of contrives. So we could easily just run the Drush build script, get the new updates in, and we were done. Again, feature-driven development is not new to anyone, but we ensured that we followed it to the best. All configurations were checked in into the features. And it brought a lot of consistency in terms of output. We also had created a bunch of different checklists in the project, both automated. We used a Drupal module called Site Audit, which sort of checks for Drupal best practices. And at the same time, we also created a bunch of our own checklists that we followed. Because there were APIs that were being developed. There were a bunch of different aspects of Drupal development that we looked at, and created a pretty holistic checklist that we would follow after every release or before every release. Since we were deploying to multiple different environments, there was a QA team from like you see side. There was our own internal QA team. There were a lot of features that were being developed. We were constantly deploying to our solution. We were constantly releasing it. So there's a Drupal module if you guys haven't used it. There's a module called environment. You could kind of plan your entire environments that you are deploying to in that. And we basically scripted it all. So we could simply kind of just figure if it's a QA environment, we know what configuration the QA environment needs, which modules should be turned on and off, all of that. So it was completely automated. So I highly recommend if you guys haven't used environment, do go use it. So just to give you some stats, we had used about 80-plus contrips in the project. I wouldn't go into too much detail around what was being developed, and 40-plus custom modules. This sort of gives you a high-level architectural overview. There's Akamai. There's the Node.js layer. We're hosted on Acquia. And it's the Drupal ecosystem that's there using the REST APIs. We are delivering content back to the Node.js layer. So with that, Lakshmi will kind of give you a deep dive around this component of the platform. Before that, any questions around what you've covered so far? So no headless implementation is a complete without RESTful API. So we chose a module called RESTful for doing that. The Drupal ecosystem already has got a couple of other modules which are popular for doing this. You might have heard of services. And there's one more called RESTWS. When we evaluated RESTful, it was in its early stages. But the best part about RESTful was it was very developer-friendly. The only prerequisite you needed is for the resource to be present in your Drupal database. So you could tweak it and export it as a REST resource. The other thing is RESTful allows you to configure and fine-tune every aspect of your API, like caching, headers, the way you structure your payload, the authentication mechanism on a per endpoint basis. You can have authentication scheme OAuth for one endpoint. And you can have a token-based authentication for another endpoint in the same system. So it was highly configurable. No API is useful without having any documentation because we are used to consume that documentation because only computers can consume an API JSON payload. So there are a lot of competing standards for specifying how exactly an API spec should look. You guys might have heard of Swagger. There is RAML. We choose RAML because it closely resembles YAML. It is readable both by computers and humans. Quite a lot of parsers exist in various languages for RAML. And the best part about RAML is it allows you to auto-generate test cases out of the specification. So the only thing we need to write, even before we start coding the API itself was to write down an RAML spec and share it with all the API consumers and stakeholders so that they get a heads up of what exactly they will be expecting to consume when we publish the API. The other goodie about RAML is there is a PHP RAML parser which allows you to parse an RAML specification and convert it into a Drupal web test case so that you need not spend your time writing manual test cases for an API endpoint. You have a lot of other better things to do. So if you guys can see this, this is how an RAML looks. Pretty textual. You can read it and infer or make something out of it as to what the endpoint does. So this is an example of an RAML format. It very closely resembles its cousin, the YAML format. Like I said, the authentication is pretty configurable. And RESTful comes with its out of the box authentication, which is pretty secure. But not being a public-facing API, we didn't have any such security requirements which were very stringent. So we just cut some corners on that and we wrote our own lightweight authentication to squeeze out more performance out of the whole system. Because we used RESTful, we were able to do this. I'm not sure if we could have done this if we had used any other services-based module. There is a lot of literature around how you should version your RESTful API. Even the very fact that where you place it is a question of debate. Some people say that you have to place it in your URL, in your headers and all that. Unfortunately, RESTful only allows you to place it in the URL. But there is even a bigger question as to where you, how you increase a version number when you are creating RESTful resource. We had this policy of increasing the version, minor version number by one, every time the payload changes or the behavior changes. The underlying concept here is your RESTful API version is a sort of contract between the consumer and the producer as to what the payload will be and what will be the authentication scheme and everything. So any of these changes, it's technically a change in contract. So you bump up the version number. So versioning was pretty useful in describing a contract. The same way RML was useful in describing a spec. We did have challenges with RESTful. We had an endpoint which had to imitate a URL alias in Drupal. So given a URL alias, you have to get all the metadata and fields for that entity. It could be anything. It could be user, node or taxonomy term. There were some tricky parts here as to what do you do in case the alias is not formed or what if there is a URL redirect. You have to do a lookup on the URL table every time and fortunately there are a lot of modules which had exposed APIs for that. So we had to make use of those in RESTful. And we need to expose the metadata of each and every entity along with that URL alias. So we had to consume the endpoints provided by, sorry, not the endpoints, the functions which were exposed by meta tags module to get the meta tags or metadata for that entity. RESTful ships with batteries included, caching functions and provision. You can integrate it readymade with either Redis or Memcache. We have to do it with Memcache because our platform was having Memcache only. There is a need to clear your cache very diligently based on the context because you have to take a digitization between caching every time resource changes versus caching only those endpoints which change when you change a particular node or entity. So we have to perform this sort of mapping. So I've detailed those in a few blog posts which I have linked here. We thought this is a very generalized use case so we have put it up as a contract module in d.do. You guys can check it out. I mean, not yet because we've not put any code. Probably will. Any questions around RESTful? Yes? Yeah, you can do it.  That's it. As you mentioned versioning and REST, you bumped up a minor version. So is it like the older version will still keep working? Yeah, the older version will still exist. That's a good question. I was expecting somebody who'll ask this actually. So we closely followed the inheritance mechanism for versioning. Anything with changes in 1.3 from 1.2, we just inherit the previous class and then only change the function which has. So let's say if there is a node just a.k.a. working right now on 1.2, it will still keep working. It'll still continue to work as long as you don't decommission it or disable it. So you can have multiple versions working at the same time? Simultaneously, yes, yes. Because there may be consumers who will be consuming the older API as it happens in all REST APIs. So you don't want to disable that. Okay, thank you. Hello, yeah. Okay, so I'm Hussain. I'll be talking a bit about threshold panels and migration. So one of the requirements of this project was that even though it's a decouple system, the editor still wanted to maintain control over the layout, over the content in the layout and so on. Now, of course, it's a decouple system. I mean, if it was not a decouple system, the answer is easy. You just use panels. You've got a very great interface and your whole fleet of tools that works with panels and you're done. This is decouple, right? So you can't do that here. Actually, before starting, we also looked at presentation framework. How many of you here know presentation framework? Who is the fan? No one. So this is presentation framework. I'm talking about it's a module developed by media current. That's right, media current, yeah. For weather.com. You know weather.com runs Drupal now. And presentation framework is something they use to make handling panels easier. We started off this part, but quickly realized that this is not really what we're looking for. We are just actually looking for the exact opposite. Something like in a different direction. And we built this. Yeah. So this was our problem. We can let editors use panels. They have access to Drupal back end, of course. And you have your standard panels configuration. You create pains and all that. But we wanted to, I'm sorry, we wanted to make it available via regular JSON output, you know, in a RESTful endpoint. And basically what you see on the screen, that is what we wanted. Your regular pain configuration, converting it to JSON. Something which you can work with in code. And we built this. It's Contrib-LL scheduling. So this is like the overall working of RESTful panels from very, very, you know, from Eagles, I view. I'll not go too deep into this, but if you're familiar with RESTful at all, you would know that data provider classes are kind of common at RESTful. We use the same methodology. And to actually render the panel, the panel which the editor builds, we are using the standard panels renderer. This is probably what you're using anyway on the front end. You know, there are, out of the box, there are two choices. Standard panels and IP. We went with standard panels just because it's simpler. And in RESTful panels, you have something called Structured Render which will kind of make it suitable for JSON output. And in our custom namespace, you know, very specific to legacy, our requirements, we built a model called LegacyPane, which would, so in legacy, these were not really panels, they were nodes, whatever we wanted to return through this endpoint. They were panelized nodes. So RESTful panels also has a class called RESTfulPanelsPanelizer over there, which you can just extend and use it, just extend it in your custom module and you'll be able to output panelizer as JSON. And another thing that this module provides is it passes in a RESTful context. Do you know what I mean by context? As in panels and C tools context? Okay, some do. So yeah, basically what this helps in is, like you saw in a screenshot before, so if this pane, so this is the legacy pane you saw in the diagram, you can, if it is being rendered normally, you know, on a normal page or something, it's being rendered as a bulleted list. But in JSON, it comes down into structured JSON object, your regular JavaScript object, key value pair, right? And this is made possible because RESTful context is passed in and the content type can take a decision. Should it render as array or should it render as a bulleted list? It's basically the flexibility is on to you. You can do whatever you want with the data. So this particular module is already contributed. It's available for use. There is a dev release. You can go try it out. I'd love to hear from you if you try it out. It's d.toe slash project slash RESTful underscore panels. And what this module currently lacks, basically the reason it's in dev is because it's not completely tested with a variety of context, right? I mean, we never had a use case in legacy and that's why it's not tested as of yet. That's one thing we want to look into. Another thing is meta tags. So you know meta tags module, I'm sure. So you would panelize the nodes. They would have certain meta tags information along with it. And by default, of course, RESTful panels does not do anything. Right now in legacy pain, we are doing this, but I'm looking forward to add some support for that out of the box because it's a very, very common scenario. And panels variance, again, so a node you can have multiple variants, right? But they are actually really different displays. Even now you can use them, but the owners of determining the display is onto you. Maybe that is something which the module can do as well. I'll quickly cover migration, it's a very big slide and then I'll be open for questions. So here we migrated from SQL Server and this particular database was built over 15 years. So you can imagine what kind of tables they might be. But one thing about that was it's very different from your regular Drupal content module, nodes, fields, field collections and so on. Right, and so that was one of the challenge in correctly translating the source data into Drupal specific data. It was just a different form of normalization, I would say. And so what we basically did, so this is like a best practice which you should be following on your migration projects anyway, is that you should map everything. I mean, if you probably, if you don't know what I mean, then I think it would not make sense now. But I'll go with it anyway. Migration module, the framework allows you to map only the required fields. But as a practice, we map each and everything anyway. So what happened here in this case was that migration was iterative. So the development went hand in hand and while the side build was not finalized, we're already migrating data. So what if fields changes? Like the field name changes or fields get dropped or added all the time. Migration framework would be able to tell us that if there is any such change, it'll give up an error. If you don't map everything, you will get all the errors and you'll just ignore them. But if you map everything, you will be on look out for any such errors, which is really helpful. We also migrated different types of data over different times and so we just split them in migration groups. Again, if you're familiar with migration, I'd really encourage you to look into this best practices. It's a great framework, great module. So using these mechanisms, we basically migrated around, you can see 2500 articles, 5000 media items, various galleries, around 1100 affiliates. They're all very, very discrete. I mean, you can probably see five bullet points on this, but actually they are very complex structures and we probably had like 15 or 20 migrations. I don't really remember, but we had a bunch of different migrations covering each and everything. You can see the data structures get really complex. That's about it. Any questions? Do you call it for migration? Do you mean the development or the running of migration? So development, I mean, it was spread out like I said. It went hand in hand with the development of site itself. So each print, we would identify that these are the elements that have been built and we would write the migration along with that. So it went hand in hand. So, I mean, if I say it was spread out over weeks, it doesn't give the correct picture because it didn't actually take weeks. It was interspersed with other development. The entire run depends on the server. I mean, Jordan, do you remember how long it takes to run a migration? Yeah, it's, migration happened quite a while back. I don't really remember how much time it took, but yeah, I think that's 15 to 30 minutes. Yeah, okay. So that's, since there are things which field collections does, which makes it very, very heavy on performance to delete them. Creating them is easy in this case. Deleting takes time because our migrations were structured. Like I said, these data structures were quite complex. So we had a migration just for field collections. So if you try to roll back that migration, each rollback for a field collection would roll back in node, sorry, would re-save the node. We actually submitted a patch to fix this. It is subsequently fixed, I think, you know. I mean, we found a lot of things, you know. So it's not just RESTful panels and RESTful purge that came out of this, you know. We, the variety of patches that went in over the course of the development. So it was this use case. I mean, field collection was suitable for the job. I mean, do you have a more specific question because I really, I mean. We can make a field collection side issues with the regions and all. Field collections themselves are entities, so they would have their own revisions, yeah. And I see what you mean. It just happened that it worked great for us. And I mean, like, do you want to add on to the answer? Anything? It was more about migrating the data and the work on flex. I mean, that's the only thing. And that was really fixed, actually. The structure was so long-placed, so you decided to use it. Yeah, well, of course, the content structure is pretty complex, yeah, for certain kinds of entities. I mean, some are just articles, simple, but others are- One, two, three. Yeah, pretty much, yeah. Yeah, one, two, three. When you're quotes, videos, and images, you go to legacy.com, slash news, slash galleries. You check out some of those books. Because of the interoperability of different kinds of media, we needed to deliver all of those in the payload. So once in a while, you have a video, and depending on what was uploaded by the editor, in that specific collection, that's what we wanted to do. So it's very use case-specific. Okay. All right, I'll pass it on to Basam. Am I audible? Yeah. Okay, cool. Yeah, so as you can see, the front end at legacy was quite diverse. We are using everything on top of the node layer. We use Express to consume the APIs that Drupal provides. So these APIs are then taken by React and Flux implementations. So they take these APIs and render the client UI. So we use other tools, open source tools, like Babel for transpiling from ES6 to ES5. We are using Webpack as our build system. And we are using stylus for writing modular CSS. So yeah. So why did legacy choose to write a client-side application using React? Well, there are these three main reasons. Performance, developer productivity, and to avoid content injections from the affiliates and third parties.  But every subsequent page transition or every subsequent request is extremely fast compared to what you get with your conventionally developed applications. In turn, this leads to an experience that's similar to what you get with native applications that are there on desktop and iOS or Android phones. Another reason is developer productivity. So with React, you get a composition, easy composition. So your React application is built of small components that form of huge applications like legacy. So with React, we were able to easily add new features, remove features without affecting the existing UI or breaking any tests. So that made us age island, we were able to rapidly make the new changes. Similarly, event delegation and writing inline styles was extremely easy. We use inline styles just to avoid cascading problems that are common in large code bases. This was pre-CSS modules era, so we rolled up our own solution for this. Coming to testing, your React components just consume a particular API and you get the component on your page. So what we did was we took the component, we passed it some JSON data and rendered it on a headless or a real browser to test it out. So we used Phantom.js and we used various versions of Chrome and Firefox for testing our React components. Similarly for testing out events or simulating events, we used a library that React provides called testutils. So it's as easy as calling a function. You just call a function like click or key press and that's it. You can replicate those features just by writing some code. So coming to some solutions that we implemented while working on legacy, one of the most important one being server-side rendering. So this helped us solve the SEO problem that is common with single-page applications where usually the SEO crawlers get just an empty body tag and a bunch of scripts so that's not useful. You aren't able to track any of your page content so what we did is we rendered the React components on the server using node. So what happens is that the first time the browser gets the page, it's the whole markup and once it's there, once you have the whole page there, client-side rendering kicks in and reacts their takes over. So that helps improving the initial page load time that is common with the single-page applications. Another side effect, good side effect of this is that since we are rendering the client-side application on the server, we were serving just the plain static HTML pages so that made caching very easy. Solutions specific to Drupal were like, as you already know, we are using Drupal as a data source and as Hussain mentioned, it's providing the layout configuration as well. So we consumed the layout configuration to build out the page structures and these structures were later filled in with the data that was coming through Drupal. So you were getting a free, flexible drag and drop you had to create your structures and that were built using React. Some solution specific to React were like, React doesn't play well with raw HTML, that's because the main feature of React, virtual DOM doesn't come into play if you pass it raw HTML. So just to harness that functionality, what we did is we took the raw HTML on the Drupal layer, we stripped it out, took out the HTML tags and attributes and then passed it to the client-side as a JSON object. So on the client-side, we consumed this JSON object and built the React components there. So we didn't have to compromise on the virtual DOM layer there. Similarly for complying to specifications like schema.org, what we did is we passed the metadata as JSON objects and it was consumed on the client-side using React. Any questions specific to front-end? Infrastructure, it was an additional pain to render first using Node.js and then pass on the HTML. Yes, yeah, like there are benefits to it, so yeah, you have to do it if you are implementing a client-side application. But then so it was like you at last mentioned that you were passing the metadata using JSON objects. Yeah. So that was for Node.js or for the final? That was for Node.js and for the subsequent request, React consumes that. So initially Node takes it and then once it's rendered on the browser, React takes it after that. Anyone else? Yeah. You mentioned there is a new line style. Right. It means that you have a style attribute that you are actually using. Like, isn't the client-side's list correct? It will make the CSS 600 expert automatically. Right, like since React has come out, like conventions have drastically changed, we are even writing the markup, the JavaScript and the stylesheets in the same file. So it depends on the developer productivity and how well you can manage your code base. So this worked out very well for us, organizations like Netflix and Facebook have been doing this for a while now. So it scales very well for large code bases. No, no, no, there is no theming done on the Drupal layer. All right. You just take this. All right. So some final thoughts as we wrap up the presentation are kind of want to say final learnings having just gone through this very large decoupled project. Continuous integration and continuous deployment best practices are really important when it comes to making sure that a decoupled project goes well. If we had not accelerated our continuous delivery, then we would have left the front-end team blocked whenever there was missing data or new requirement or some kind of bug that they had uncovered. We couldn't release on our sprint cycles every two weeks. We needed to release when they needed the solution in order to unblock them. And so continuous integration, continuous deployment is really important to have in place if you're gonna take on this kind of project. Personalization for decoupled Drupal architecture requires specialized infrastructure or middleware in looking at things like the affiliate universal navigation, the menus which are deployed across all of those affiliates. The performance is that kind of level of uncached requests are I guess indicative of the need to host that kind of solution outside of Drupal. There's a lot of requests that we're coming in for these menus that have a lot of context and a lot of personalization for these affiliates and there's more performance solutions in node and other architectures that we're considering at this point, looking forward. Another thing to keep in mind if you're taking on a decoupled architecture and you're working across two different teams, you're planning for architecture across two separate systems and the decisions that you make in order to perhaps deliver some kind of technological solution within Drupal greatly affects the kind of solution that needs to be delivered on the other side and vice versa. So if there is a gap that the front end has Drupal is required to fill it and if there is a gap that Drupal has the front end has to fill it. An example of this would be we provide metadata for a lot of the discrete articles and galleries as they're rendered on the URL resource from RESTful. On other pages such as some of the RESTful panels pages we actually serve up tokens which are contextualized based on the specific use cases of other parts of the ecosystem because we're using RESTful panels to kind of create this configuration layout we needed a solution where metadata was contextualized based on the front end instead of within Drupal. When you're planning this kind of architecture a coupled system you really need to take a lot of careful consideration with where you're introducing points of failure. One of those is for example this RESTful path resource all of our redirects and 404 errors all come from this resource and so this needs to perform well at scale for the system in order to serve up all of those 404s and redirects and everything. And again this is a final thought this is a great I think case study for example of a progressively decoupled system. It's something where we're continually innovating as we work on the project to deliver new open source contributions for the Drupal community in order to continue to decouple certain parts of Drupal and deliver that. Questions? And not just for me, for anyone, the team members. How is caching validation handled or invalidation? Lakshmi, you wanna talk about that? Most of the times there is no one to one mapping between your data and your resource. So whenever people make a change it's more of a mini to one. So we have to have a prior configuration as to when X or Y changes. Let's say bundle A, bundle B or bundle C changes then we invalidate the following end points. So we have this set up in code. Resoul allows you to do that or rather has a provision to do that. So every time there is a change in any of these we have the proverbial hooks, right? So they take care of purging the respective end points, caches and that's how we handle it. Did I answer your question? Products. I think one of those would be Adobe Edge as an alternative and I think it has some restful resource. What's the content full? What's the hosted content full as a hosted resource? It's really easy to build content architecture and expose those pieces of data to be consumed. Content full is actually the use case where I was talking about earlier or the business decision that Legacy made. They wanted to own the platform and own the data when you choose a third party service like that that's hosted, you don't actually own that system. If they go out of business then you're in a tight spot. So that's one of the key decisions I think that we made in going with Drupal. Any other questions? All right, thanks you guys. Thanks everyone for coming. Welcome to Drupal Con Asia, it's a real pleasure to be here. We're presenting today a case study on legacy.com migrating a top 50 most visited website in the US onto Drupal. First I'd like to introduce the team. My name is Jordan Ryan, I am a CTO of Fast and Interactive and I was the Solutions Architect and product owner during the delivery of legacy.com's migration to Drupal. And Ankur, CTO of Xcelerate, would you send it to the team? So Xcelerate was brought in to do the implementation work for the project and Jordan and I, we worked together including some of the team members that are here. That's me that the API developer plan who said that not only migration work, also an important component of the project was managing presentation and there's a module and was almost part of the front end team implementing Node.js React solution. So before we get started, I'd like to just introduce legacy a little bit. Legacy is, as I mentioned before, a Concast Top 50 website. They have roughly a few hundred million page views a month. They've got maybe 20 to 50 million uniques on any given month. And they serve most of their content traffic through affiliate partners. They serve obituaries across roughly a few thousand newspapers in the continental US and also internationally and they consume obituaries from these newspaper partners and serve them up on their channel pages for those newspapers. Legacy's business as far as the Drupal solution that we're presenting today is just focusing on the features or the news editorial section of their site, which just drives a lot of their consumer engagement once they have users that come into the site from these affiliate channel partners. So one of the questions everyone always wants to have answered is why Drupal? We'll talk a little bit more about why legacy specifically wanted to, let's see here. How's that, better? Sorry. We'll talk a little bit more about why legacy wanted a decoupled architecture in just a little bit, but first we have to talk about why they wanted to use Drupal. And the answer to that is very simply that they were building a team that was gonna create an innovative and progressive front end in terms of design and they wanted to be able to quickly iterate on the design and implement new features. And so in order to do that, in order to deliver that kind of solution, they wanted to have Drupal as a service, they wanted a service architecture so that they could continue to deliver a high quality consumer experience, but they didn't wanna spend a lot of time innovating within the CMS space. And so they looked at Drupal for that kind of expertise and delivery. So as I mentioned before, why decoupled? Legacy was really looking to innovate on the front end. They didn't want to innovate in the CMS. They were looking to a tried and true implementation. And Drupal was kind of the enterprise standard for them based on their requirements that we went over in their discovery phase. Content was a small part of a much larger ecosystem. When you look at, when you look at legacies, when you look at legacies architecture, the content system only serving a few million page views a month compared to their much larger few hundred million page views a month means that the Drupal application itself did not need to be scaled up in the same way that their Node React application needed to be. And using React and Node, which was the decision by legacy for their front end application, that lent itself to componentized widgets that needed services in order to be populated with data. Again, another reason why we chose decoupled. Legacy wanted to own the data and platform. This kind of goes back to why Drupal as opposed to why not use an additional hosted service. There's certainly some other solutions out there that can provide restful APIs for content. But legacy's goal of owning that content and owning that platform was another key decision on why they decided to go with a decoupled Drupal implementation. So I'm talking a little bit about what we did. This is just a quick overview and then we're gonna go through each of these pieces in detail. The initial, in context, all of this happened over a very fast paced six month timeline. The initial discovery engagement was about four weeks to six weeks. And then after that, I was working with legacy in order to bring in additional partners in order to deliver this solution. After executing the discovery and deciding on some of the architectural components, we brought in Accelerant. Yes, so on the Accelerant side, we covered the technical architecture for the solution. We did a lot of the site building and any custom development. And then the core of it, which was the API development, we migrated data from MS SQL and continued to help their front-end team. A lot of performance optimization work was done and we continue to engage with them and there's a continuous discovery that's happening on the solution and we've been working since. So some of the key challenges that we are trying to address using the Drupal solution that we are proposing. So there were actually two teams. So legacy already had their front-end team which was going to implement a Node React solution. And so they had a different velocity than we did. So it was a challenge that we had to sort of take care of when we were implementing the Drupal solution. Then managing presentation. So there was a unique requirement. They wanted to give editors control over the layout of a page. So as you know, if you were working with a decouple system, controlling layout in Drupal, how do you do it? So there's been a couple of different approaches to that. We came up with a unique solution which was saying we'll talk about it during this presentation. Also, power of Drupal is really to manage metadata. The SEO value is the key. So you have content, you have metadata around it and that's what enriches. It's great for search engines. How do you bring that value onto a decouple platform? So that was another challenge that we had to consider when we were building the solution out. Since there were a lot of APIs were being developed, we had to ensure that we were constantly versioning APIs so that we weren't causing issues for the front-end team. Any contracts that we laid up front were adhered to and any new changes that we would make were versioned in the APIs. And also legacy by nature as a business, they work with a lot of different newspapers. And so they had to serve out a lot of menu content to these newspapers. So it was highly customizable, but it had to be extremely cashable so that the performance, the kind of volume, traffic volume the site gets, so that we could continue to serve it. So there were a lot of varying page elements that needed to be addressed. And likewise, there was a caching mechanisms had it to be put in. So we considered all of these problems in our solutions. Also on the React and React is unlike HTML as most of you know. So we had to sort of look at componentizing HTML for the various React elements. Now we'll talk about some of our methods, how we went and did some of this. Sure. So going back to that initial discovery, some of the things that we executed in order to deliver the most value to the client is this concept of value-driven development. The concept of value-driven development is the idea that we define the business metrics or key goals for each of the epics or user stories and document those in the tickets so that when a developer implements a solution, they have some context with which they can actually deliver that solution that's gonna have the most value for the client as opposed to a less defined user story which may not capture those specific business values. Another element that we focused on early on in the discovery process is API designs first, focusing on what that contract was gonna look like based on the initial comps that were delivered by the client and they had executed. And that allowed us to take a look at things like the content architecture, how that content architecture is gonna be built out within Drupal in order to expose those fields. Another key item is legacy was really looking to Drupal to become a platform solution and when I say that I mean the delivery needed to be such that the interface was dependable. There's a lot of additional complex business logic that we also had to extract over the course of the discovery. This actually is what spurred the continuous discovery that needed to take place over the course of the project because as we work with the client and work with the front-end developers, requirements changed. I'm sure you all have been through that before. And most particularly where requirements continue to change and be revised is around the affiliate partners or the solution which was explicitly being developed for those affiliate partners which was a universal navigation. It was a menu that was being delivered across everywhere.


The governor Amadou Fintiri of Damawa State has called on residents of the state to remain calm and peaceful as a coalition of results of the just-concluded governorship supplementary election has been suspended by the Independent National Electoral Commission, INEC. The governor, who addressed the news conference in Yola early today, has commanded the National Headquarters of INEC for its prompt action holding the declaration of the APC governorship candidate Aishatobinani as the governor-elect. He expressed optimism that eventually the electoral empire will collate and announce the win of the election, saying only 11 local governmentaries were collated out of 20. The red this morning took up a tax he is not constitutionally empowered to do by making an illegal announcement of the outcome of the election without a result. This action is no doubt provocative but in this situation I appeal for calm as always.  The Independent National Electoral Commission has demonstrated its empire staffing by first distancing itself from the act of direct and I assure that the writing will be done. The writing in this context is the conclusion of the coalition at the designated location and declaration of a winner by the returning officer in person of Professor Mele Kerri. I must thank you for your resilience and resolve not only exercise your democratic rights but also protect it where on this justice until it is done. Hello hope you enjoyed the news please do subscribe to our youtube channel and don't forget to hit the notification button so you get notified about fresh news updates.


This study evaluated the long-term persistence of anti-hepatitis B surface, HBs, antibodies, and the response to a HB-challenge revaccination in children who had received a primary series of DTAR-PIPV-HBPRPT, or DTAR-PIPV-HB-SPRPT co-administered with PCV7 at 2, 4, and 6 months of age. The results showed that anti-HBs geometric mean concentrations, GMCs, and seroprotection rates were high and similar in both groups post-primary vaccination series, and declined to a similar extent in each group at 12 to 18 months. Antibody levels further declined at 9 to 10 years of age, but a strong an amnestic response occurred in each group post-HB-challenge revaccination. The study demonstrated that the kinetics of long-term anti-HBs antibody persistence were similar following a primary series of DTAR-PIPV-HBPRPT, or DTAR-PIPV-HB-PRPT, and that the response to a subsequent HB-challenge revaccination was strong and similar in each group, demonstrating persisting immune memory. This article was authored by Pope Kosseler-Axa, Kulkarnia-Chokify-Bulkit, Suwot-Benjapompatak, and others. We are article.tv, links in the description below.


So we're here with Alion and Hi. So who are you? Yeah, I'm Brian and who are you? I'm Monica. So what is Alion? Alion is the third party testing lab. We are performing certification testing and engineer validation testing. So you test the stuff for the HDMI? Yeah, we are also testing center for HDMI. So you test all kinds of different things? Where are you based? All over the world? Where's headquarters? Headquarter is in Taipei, Taiwan. But we have a global facility in USA, Oregon, China, Shanghai, Shenzhen and Tokyo, Japan. So who's your customer? Everybody who makes a product? Yeah, everyone makes a cable? Yeah, cable, TV, computer, laptop. So everything with HDMI? Yes, we can. HDMI port, cable? Yes. Encoder chips or not? Just a speck? Just for the product. We cannot put all the testing on the chip. We have to produce the product so we can do the compliance test and certification test. So how do you do the testing? Do you have many different equipments? Yes, we follow the CTS, compliance testing specification. CTS. And then you have specialized software for it? Yeah, for the test tool, we have developed the HDMI controller, EDID test feature to help customer test in-house. Alright, but HDMI 2.1, are you ready to test the 2.1? 2.1? Yeah, the HDMI 2.1. Yes, we have the pre-test capability because the CTS, the test spec is not final yet.


The Minnesota Department of Public Safety says more people lost their lives on state roadways in 2018 compared to the year before. Initial reports show 380 people were victims of fatal crashes last year, which is up from 358 in 2017. Traffic safety director Mike Hanson says there are four things that would prevent 80% of the fatalities on Minnesota roads. Seat belts obeying the speed limit, driving unimpaired and paying attention to your surroundings. The figures show 70% of the fatalities were mostly men and 42 pedestrians died last year as well as seven bicyclists. If you enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland PBS.


The mathematicians in this college have informed me that they have been playing around with strange attractors for quite some time The adjective strange as we all know fits some of them They are like field goal kickers or like those extra point kickers we have out at the stadium on the football team You learn and I'm their chaplain and I go down to try to to assist them But I what I learned some years ago is that you don't talk to them about what they do That's the same the same is true with these mathematicians. They say it's mental they say So chaos mathematics had to come to me along another route Then third floor old main so it came For me in 1987 at Christmas I went down to visit to visit our organ builder in the village Charles Henriksen Who was building an organ just now for the cathedral in Sioux Falls? and I stopped in for a little Christmas cheer and he handed me this book that his sister had just given him for Christmas And he said here LB. Take it along. It would make a good Nobel conference so when Professor John Holti and the math mafia pressed This conference on me said hey, we want to do a math conference and we want to do chaos and so on and so on I said I was ready for them. I Had read the book Now I suspect that this book of James Glick is also the reason that this commons is so full tonight Triple last year's dinner gathering That it was his reconstruction of this piece of intellectual history its people or characters its Journals its meetings its ideas its conversation in his book chaos the new science that Really finally inspired us those of us who were not mathematicians to help to organize This conference and I I think inspired many of you to come to it James Glick is a native of New York City. He's a graduate of Harvard He's a writer he's Residing in in New York with his wife and a new child son He is currently working on a biography of Richard Feynman. I I expect when that book is finished we may have to do a Feynman conference In any event We owe James Glick an enthusiastic welcome to this gathering and his title for his talk his chaos And beyond James Glick Well first of all before I say anything else President Kendall The organizers of this conference our faculty and student hosts All of the speakers want to thank you for what has really been a very unusual event for us extraordinarily stimulating and a Treat, thank you very much. I'm told that my job here is to wrap everything up and and then I've got roughly 38-minute window between dessert and unconsciousness I Think instead it might be it might be better if I try to unwrap everything One of the dangers in a conference like this is that after a while You might start to think that it all makes sense You listen to the the eloquent presentations we've heard over the past two days And you begin to glimpse an intellectual framework with structure logic beauty You feel it's only natural that Mitchell Feigenbaum found Universal laws Governing systems that make a transition from order to chaos You you feel it makes perfect sense that Benoit Mandelbrot spent the battle the better part of a lifetime uncovering the strange Patterns that exist in the paths of lightning bolts and the clustering of galaxies You think what else would someone like Steve Smale do? But invent a new approach to the mathematics of dynamical systems. What else would Heinz Otto Peitgen do but explore the wonders of computer-generated fractals Unfortunately, what you've witnessed here is a little like what happens after a crime when the perpetrators have had time to get their stories together Sure, it makes sense now Now chaos is a recognized movement in science It's it's trendy.  He thinks that's great But it wasn't always that way We tend to suffer from the false impression that the progress of science is tidy rational somehow inevitable and that somewhere there's a List of problems to be solved and that scientists pluck the next one off the top of the pile We tend to assume that ideas are communicated more or less smoothly from one place to another That when a scientist discovers something worthwhile The discovery finds its way to the other scientists who need to know about it What I've learned from the short recent history of this business called chaos is that none of these assumptions are true None of them and they are they are least true when scientists are producing something truly new The scientists who have come together to address this symposium were all Each in a different way pioneers they all experienced the difficulties of Working on Problems that their peers did not perceive as legitimate They all experienced the awkwardness of trying to communicate discoveries that lay outside the ordinary way of thinking about things discoveries that Didn't have the decency to observe the customary boundaries between scientific disciplines chaotic dynamics and Fractal geometry weren't on anyone's list of unsolved problems. They simply weren't a Natural subject of study until these scientists made them one There's something about the the ordinary way of portraying the history of science that works to clean up messes like the screed sweeper Coming up behind the parade In reality the most creative science involves mistakes guesses false steps miscommunication uncertainty a sort of Stumbling through the fog that makes the exhilaration of true discovery All the more remarkable the set of ideas that come under the rubric of chaos in particular run Counter to a conventional way of thinking about things It's not always easy even for scientists to see that all of us have preconceptions About the way the world works the way nature works these these preconceptions these biases Can be very hard to shed I? Want to give you a simple example Imagine a river Not a real river surface rippling in the squall trout quivering under submerged rocks Currents carving the banks.  In fact Go ahead use your napkins You heard Benoit Mandelbrot say yesterday a river is not a straight line But I'm willing to bet that virtually everyone here even those of you who thought you were paying attention to Mandelbrot Has imagined a line of some kind Maybe in your mind's eye you drew it with some sort of curve or wiggle That's the way that's just the way people think a river is shaped when we when we speak of a river by name We think of an entity flowing from one place to another from source to outlet from a mountain spring down to the sea a Geographer might ask for example What is North America's longest river? Is it the Mississippi the river whose source is a little north of here or is it the combination? That doesn't quite have a name the the Mississippi, Missouri In reality the question makes no sense in reality a River's basic shape and it does have a basic shape repeated wherever nature empties the land of water Is not a line but a tree a River is fundamentally in its very soul a thing that branches So are most plants Trees themselves of course bushes ferns like the ones you saw today and computer simulation lightning Contrary to our common stereotype a sort of stretch Z So is the human lung a tree of ever smaller tubes bronchi bronchia bronchi owls Intertwining with another tree the the network of blood vessels the circulatory system so North America's longest river is actually a very messy object Spanning 31 American states and two Canadian provinces it embodies without distinction The great tributaries that we think of as separate rivers the Mississippi, Missouri, Ohio, Tennessee, Arkansas Minnesota and so on Except in human perception and human language Nothing really separates It's few wide and deep stretches from its many small and narrow ones Although it flows inward Toward its trunk in Geological time it grew and continues to grow outward like an organism from its ocean outlet to its many headwaters Now as all of you know by now in the vernacular of this new science it is fractal its structure Echoing itself on all scales from river to stream to brook to creek to rivulet Branches too small to name too many to count When a child draws a tree You get a green mass sitting on top of a brown trunk as if the basic shape were something like a popsicle a child's cloud is a smoothly rounded bulk Perhaps with wavy or scalloped edges These are not the clouds we see they are highly stylized forms like the like the international symbols for railroad crossing or no smoking as Children or as adults we own a Repertoire of such stylized images. They're they're like Idiograms in Chinese painting they they help us see for without these templates Our minds are powerless to sift the welter of sensations that bombard us, but they hinder our seeing as well Before they were scientists Mandelbrot and Feigenbaum and the other pioneers of chaos were people who saw Nature's complexity a little more clearly than the rest of us the rivers the clouds the snowflakes of our usual Perceptual toolkits miss the point the intricate recursion the convoluted flows within flows within flows our mental lightning bolts are Z's our volcanoes are inverted and Decapitated cones our rivers are lines Nature's are not so simple This is not just a matter of terminology. It's a matter of of true understanding of Recognizing and avoiding a kind of foolishness about nature Again think about the Mississippi River How many tributaries does it have? How small is the smallest tributary? How long are all the branches added together? to make sense of such Innocent seeming questions begins to require at least a feeling for the infinite One hears such questions Constantly questions that cannot be answered as simply as people imagine What is the average height of an ocean wave? What is the average size of icebergs breaking off the Antarctic shelf? What's the average? Duration of the El Nino climate pattern or of an economic recession when you when you hear questions like these a New kind of bell should go off in your mind In the case of a river the number of branches and their total length Approaches infinity just as the size of the smallest branch approaches the infinitesimal And it has to be that way What is a river anyway, but a thing that drains water from the earth's surface? In some sense if it is to function that way its fingers must penetrate every part of that area Furthermore a river is a dynamical thing The microscopic rivulets that feed a river Appear and disappear with the rains at its at its farthest edges a river's precise shape and size fluctuate dynamically With the day's rainfall or the year's wet and dry seasons one brook appearing as another dries out There is no simple dividing line between the transient and the permanent parts of a river fluctuations Affect every timescale from the seconds of an ephemeral rain shower to centuries and millennia if you could If you could film the life of a river and replay it in fast motion You would see a symphony of rhythms from the base notes of the great branches to the treble flickering of the tips The traditional view of nature overlooks such rhythms many flows escape our perception because they're too slow or too grand in compass a cloud Floating overhead gives the illusion of a static object Simply born from one place to the next by the wind, but that's not how it is Even when a cloud looks most like Frozen cotton candy it it slowly seeds and tumbles in the air a motion picture film of clouds Played ten or a hundred times too fast Always chose the wildness that lurks in what seemed like gentle puffs the contention of this new science of chaos the motivating contention Seeming irregularities in nature even in rivers and clouds contemplated Sorted measured and understood Traditionally looked for a more Conventional order in nature and treated the erratic as a side issue and unpredictable and Therefore unimportant kind of marginalia Not anymore If any of you for example follow the technical literature of population biology ecology You may have noticed a striking change in attitude just in the last few years For several generations Less time than you may think actually the dominating assumption In ecology was an attitude of prejudice that can be summed up in a single phrase the balance of nature When people go into a wild area and start tinkering spraying insecticides What is it they're disturbing the balance of nature the idea is left to itself a wild Ecosystem finds a a harmonious balance and equilibrium. It settles down. It regulates itself Now of course, there's some truth to that idea complex non-linear systems do become self-regulating when suddenly perturbed They can be thrown into regimes of behavior that are unexpectedly different witness for example the Frightening appearance of ozone depleted holes over Antarctica in the past decade But ecologists led by chaos theorists have begun to realize that the balance of nature idea was Profoundly naive by and large Ecosystems may seek a sort of equilibrium But that equilibrium bears as much resemblance to the traditional idea as as a roller coaster does to a golf cart In their natural state left all alone Ecosystems can fluctuate wildly Populations rising and falling dying out and springing up again. Wildness really does mean chaos not the Slightly saccharine kind of harmony that ecologists used to imagine The same is true in economics if you think the natural thing would be for a complex system made up of all the Interacting intertwining commercial activities of humanity to find some sort of static equilibrium or To rise and fall in regular predictable economic cycles Well, you're not alone, but but you're missing the boat If you've listened carefully to the speakers over the past two days You may well feel that a richer view of the possibilities is in order now I'd like to offer another somewhat deeper example of a sort of Perceptual prejudice that I believe has skewed the path of science in this case of fundamental physics for much of this century Consider the following statement At bottom the root of unpredictability in the world is Quantum uncertainty the subatomic measurement uncertainty first expressed by Werner Heisenberg in the 1920s This is sort of a true false test true or false The uncertainty principle of quantum mechanics is the fundamental cause of unpredictability in nature. I Say on predictability, but I might also say indeterminacy or In the evocative phrase that John Polkinghorne used yesterday every day openness It's it's not an easy question.  Nor is it easy to know what most physicists believe But I think it's fair to say that many physicists anyway have talked or acted as though they believe this is the case Here's an example. I'm gonna quote The uncertainty principle Signaled an end to Laplace's dream of a theory of science a model of the universe that would be completely Deterministic one certainly cannot predict future events exactly if one cannot even measure the present state of the universe precisely exclamation mark Now that could have been any of a dozen prominent physicists But it happens to be Stephen Hawking in his in his recent book a brief history of time He adds quantum mechanics Therefore introduces an unavoidable element of unpredictability or randomness into science Well, there's an inverse corollary to this statement, too The corollary is if it weren't for quantum uncertainty The laws of elementary particle physics would allow one at least in principle to calculate and to predict everything Hawking doesn't shrink from this implication I'll quote again Since the structure of molecules and their reactions with each other underlie all of chemistry and biology Quantum mechanics allows us in principle to predict nearly everything we see around us within the limits set by the uncertainty principle Well, you can see why the question starts to seem far from trivial In practice as Hawking goes on to say you can't do the calculations The equations are too complicated and so on but but those are just details messy details In principle according to this point of view the laws of elementary particles are the fundamental laws and The ultimate limit on predictability comes from quantum uncertainty Now I don't happen to believe this and I think that as the lessons of chaos sink in both versions of this statement are going to start to seem somewhat disreputable Are the fundamental laws of physics the laws that govern elementary particles they are if you mean fundamental in a sort of Geographical way or anatomical way to refer to the tiny things of which larger things are built up But if by the fundamental laws you mean the laws with the greatest generality The most profound laws the laws with the greatest planetary power Then I think you have to look elsewhere How do the laws of quarks and gluons or even the laws of quantum electrodynamics Help us understand bigger things like the great red spot of Jupiter or the general problem of turbulence and fluids or the formation of clouds and snowflakes or the working of the human brain or the Balance of nature or any other mystery of the universe as it exists outside of particle accelerators Well, the truth is that they don't really I Would contend and now I'm Since I'm not a scientist. I have the privilege of waving my hands wildly here I would contend that if you could imagine a universe with no Heisenberg uncertainty principle you can imagine that right It's a universe in which the position and momentum of a subatomic particle can be specified Simultaneously if you can imagine a universe with no Heisenberg uncertainty principle You would have a universe in which it would be Precisely as difficult as it is in our universe to predict next Sunday's weather Or to predict What will happen to the price of oil next month or to predict just about anything about the behavior of any macroscopic complex system much of this the standard language of The physics community over the past two generations has embraced a reductionist perspective Yesterday you heard John Polkinghorne declare that he was an anti reductionist Just a few years ago It would have been about as likely for a high-energy physicist to declare himself an anti reductionist as to declare himself an Anglican priest physicists have believed and have stated proudly that Before one can understand the whole one must understand the parts Chaos is anti reductionist this new science makes a strong claim about the world namely that When it comes to the most interesting questions questions about order and disorder decay and Creativity pattern formation and life itself the whole cannot be explained in terms of the parts. There are Fundamental laws about complex systems, but they are new kinds of laws They are mathematical laws of the kind that smell Figenbaum and Mandelbrot and others have discovered they are laws of structure and organization and scale and They simply vanish when you focus on the individual Constituents of a complex system. I think we all understand that intuitively From our own everyday experience. I think that most of us now believe that when science comes to understand The interesting things about how the brain works The things we all want to know what is memory what are thoughts? What are emotions? How are symbols? Stored and processed the answers to those questions are not going to depend on the particular chemistry of Individual neurons that chemistry may be what it is because of a thousand Accidents in the history of life on earth intelligence is something else something dynamical Oddly I think that the very best quantum physicists if not most quantum physicists have understood this all long Having stressed what a great new surprise chaos has been now. I'd like to quote something Richard Feynman said 28 years ago. I know at least one person in this room tonight was there when he said it he said The complexities of things can so easily and dramatically escape the equations which describe them Man has often concluded that nothing short of God not mere equations is required to explain the complexities of the world We have written the equations of water flow From experiment we find a set of concepts and approximations to use to discuss the solution vortex streets turbulent wakes boundary layers When we have similar equations in a less familiar situation We try to solve the equations in a primitive halting and confused way to try to determine what new qualitative features may come out Our equations for the Sun for example as a ball of hydrogen gas Describe a Sun without sunspots without the rice grain structure of the surface without Prominences without coronas yet. All of these are really in the equations. We just haven't found the way to get them out There are those who are going to be disappointed when no life is found on other planets not I I want to be reminded and Delighted and surprised once again through interplanetary exploration with the infinite variety and novelty of phenomena that can be generated from such simple principles The test of science is in its ability to predict Had you never visited the earth could you predict the thunderstorms the volcanoes the ocean waves the auroras and the colorful sunset? The next great era of awakening of human intellect Feynman said May well produce a method of understanding the qualitative content of equations Today, we cannot Today, we cannot see that the water flow equations Contains such things as the barber pole structure of turbulence that one sees between rotating cylinders Today, we cannot see whether Schwerdinger's equation contains frogs musical composers or morality or whether it does not We cannot say whether something beyond it like God is needed or not And so we can all hold strong opinions either way Incidentally, whether Feynman's God and John Polkinhorns are the same. I'll leave it to you to figure out. I Want to finish by saying that there is a danger in all of this Steve's mail was right to warn us today that if scientists use the language of chaos and fractals merely to describe what is there Then they will not have accomplished much Furthermore, there's a danger in listening too much to people like me. My language is not science at all It's metaphor. I believe that chaos Offers some useful ways of thinking about the world beyond science, but metaphors don't always work Not every good idea in science survives the process of translation Darwinism for example was one of the great triumphs in the history of science Social Darwinism on the other hand was one of the great disasters Survival of the fittest turns out not to be a helpful guiding principle for those thinking about human society As a description of space and time Einstein's relativity works beautifully but contrary to a good deal of 20th century philosophizing The laws of physics do not mean that everything is relative Nothing in science tells us that relativity must apply to ethics to art to human values Another well-known gift from science is the second law of thermodynamics the law that says that the cosmos is winding down That entropy always increases that the universe and any closed system within it have an inexorable tendency toward disorder As a rule about thermodynamics the second law is undeniable But too many people have taken it too much to heart. The second law has been called on to explain decadence in civilization Decay in cities the decline of manners as though science were telling us that Disorder is our destiny. I Don't believe that I believe Ilya Prigashin is right when he tells us to look again at the science underlying dissipation and pattern formation Billions of years from now the universe may well wind down to a featureless heat bath of Maximum entropy, but in the meantime it is managing to create some interesting structures Just look around and you know that the important laws of nature The creative laws lie elsewhere Thank you


Hello, everybody, and welcome to another hobby-cheating video. Today it's time to return to basing. Let's head into the Chaos Wastes. Let's get into it. The strict techno-mancer that is Vinci-V. Let us get to the technique and learn it... So today's base is going to be relatively simple. It's about making a wasteland base that looks appropriate for the forces of chaos. We want to keep it simple, and I want this to be something you could easily replicate across your whole army. Now, I'm going to be working on a relatively large base for a figure today, just because it makes it easier to see on camera, but everything I'm doing here could be easily replicated all the way down to even the smallest bases and broken up. I wanted to give you something that you could mass produce easily, but would still look very eye-catching and impactful on the tabletop and feel like the forces of chaos were marching across it. So let's head over to the desk and let's get this base built and painted. So we're going to be working today on an 80mm base. Let's talk about our materials. So these are little crushed glass beads. I got them at a garden store. Yeah, it's just broken up colored glass. These are bigger chunks of broken glass. They're not sharp in any way, because of the way they're rolled around and stuff. There's no sharp edges. You don't cut yourself. And then finally, it's some very finely ground... Well, not super finely ground, I should say, but like medium ground sand. And I actually like that sand because it has more of the texture of rocks. Again, all of this is from a garden store, just your normal garden center area. So look around and see what they have. A specific section that you can look in. It's become very popular for people to build these fairy gardens for their outdoor gardens. And so hence, there's a bunch of stuff that's in those gardens that's in scale. People use for rocks and things like that. I have found that to be a goldmine of basing materials that are very, very, very cheap, because people are normally building things that are quite large. So I start by spreading this sand over some super glue. I could have used PVA glue, but I wanted it to dry a little faster, and super glue works just as well here. It actually looks like pretzel salt. That's what it looks like to me, but trust me, it won't look like that once painted. But I just make sure over a couple applications, you know, puts more glue on, puts more of this big rocky sand on, and we get to a relatively good place. Now, I don't want to leave just that. I also want some finer texture. And one of the keys with sort of any kind of outdoor base is to often mix your textures. So here I'm using super fine ground sand and just mixing it into some of the open spots. I'm not making it regular across the thing. I'm not trying to cover all my work. I just want there to be some variation in the natural texture of the actual base. That will both make it feel more realistic as sort of rocky barren earth, but it'll also just make it more visually appealing as well. Once we're all done, tap off the excess, and there we go. You can see how we get these different patches of textures. Next up, let's go ahead and get some rocks on. And that's what these crushed glass things are. They're just rocks. They're perfect in scale rocks. And the texture on these, because the way they're cut or broken or shattered or however they're made, I don't know, but they have this wonderful sort of striated texture that really makes them feel like natural in scale rocks. So there I just glue them down into what I think are some interesting positions. The area that's marked out on the base, by the way, is where the figure is going to attach. I set him down and then drew the circle that way. I knew roughly where he was going to be and I didn't put material down over top. Once my big rocks are in place, then it's time to do some small rocks. This is just the smaller crushed glass, but again, the same thing. You get these wonderful edge textures and this crushed glass kind of a broken glass or whatever you want to call it. Please don't just break glass and then try to do this. It's very sharp by the actual stuff. It's only a few dollars at your local garden store. I don't want anybody cutting themselves or anything. But this stuff is perfect for just doing like lots of different scale. And the hope here is between the big rocks, the big pieces of glass, these medium ones, then the sort of white pretzel salt looking stuff, and then the fine sand. We really have a complete biome of this sort of rocky wasteland earth created where we're seeing how the earth is broken down from these large, rough, sharp, jagged rocks into this small finely ground stuff. But of course, no wasteland would be complete without some cracked earth. So our final step here is again to pick some interesting patches, not the whole thing, and apply some Martian iron earth. Now you can use any kind of crackle paint or medium I happen to have this stuff and I like it and know how it works. It is a bit expensive, but when you're using it in sort of small amounts like this, it's relatively manageable. I just create some patches of it where I think it'll be visually interesting around the miniature and apply it very, very thickly. Notice how thick that little glob is. If you want it to really crack, then it's got to be thick. So I leave like the central area is very thick. And you can see then we get those nice cracks over the whole thing. It really looks like that barren, wasted earth. No cast wasteland would be complete without skulls. So we have to go to the best terrain kit GW has ever made. The skulls box couldn't recommend enough. And let's add a few more skulls to this base. The miniature itself, how it connects to the base actually has a skull on its base as well. So we'll just have skulls everywhere as would be appropriate for the forces of chaos. Once we get our skulls in place amongst these rocks, we have a nice, simple, easily repeatable chaos base. Remember what I've got here is just sort of a sample of the kinds of things you can do. When you think about this chaos wasteland, you could also have bits of fallen soldiers, broken swords, broken shields, all those kinds of things can do incredible work. You could have little, you know, fallen chaos stars and emblems and rusted ruins and all those kinds of things can be used if you want to take this up to the next level. My goal here again was to keep this relatively simple to where you could replicate this if you need 20, 50, 100 of these bases for your chaos armies. But feel free to spice this up. You know, get crazy. You could have some tentacles on the base. You could have, you know, puddles, a sort of strange colored goo that feels very chaosy. Really, the sky is the limit here. So wherever you feel like setting your ceiling, you should do so as you replicate this across your army. I do love how priming brings everything together. And you can see how once this base is all primed and ready to go, of course, everything now looks appropriate. You can see how the rocks really do look like rocks now that they're no longer sort of pseudo-translucent. I'm going to start by just laying down a little bit of thinned rhinox hide. I think this is a perfect color for sort of a chaos wasteland mud. It's very dark. It has some like purple tones in it. I just like what's going on and it gives me a nice base to work from. Once that's done, I'm going to lay down a little bit of this sort of jade blue-green onto the rocks. And again, here's where we get super important. When we're dealing in the chaos wastes and chaos wastelands and these kinds of things, we want there to be color, visual interest, things going on that are more than just black and gray. Rocks do not need to be gray. In fact, most of the time, they should not be. Very few rocks in nature are actually just gray and white. So instead, we're going to start from this base green color and that'll give us something really interesting and visually poppy on the base against our desaturated dark brown earth. I give it a nice dry brush to basically pop out some of the texture and details and get some of those initial edges of the rocks popped up. I focus a lot of my dry brushing on the front of the base. What will be sort of the visual front. It's hard on a round base. But I want to make sure that's the brightest area. You can create interesting travel of light and shadow just by choosing where you dry brush more versus less. Next, I'm going to work some colored pigment in. I pick both blues and reds here because again, chaos. It should have the sort of hints of other color iron oxide and blues and stuff like that that make the ground look more visually interesting. Now it's going to be really strong when I initially apply it, but that's okay. Don't worry. We're going to kill a lot of that out with our next step. Our next step is to give the base a sort of wash of Agrax Earthshade. This is the new mix so it'll really run into the recesses. I am washing the skulls and the ground. I am not washing the rocks. I don't want to get brown into my cool blue-green rocks. That's kind of the opposite of the color I want. Those are meant to be cold and to contrast against the warmer earth underneath them. Again, we're always looking for more ways we can work in that contrast. Now it's time to actually paint the rocks. We've got that base coat down. We've got a little bit of the edges picked out, but now we're going to just start working roughly.  You'll see me use a couple different brushes over the course of this. But the idea is pretty simple. Let's wet blend out some interesting transitions on the rocks. Make them look more visually appealing. I want them to pop up into a sort of warm white. So again, they're sort of a warm base. Then it goes into the brown, then it goes into the cool rocks itself, and then up to the very warm highlights. This also matches the same highlight color I used on the figure that is going to go on here. So really just trying to create that overall ambience of a vaguely warm light. So what I do is just keep refining the rocks, popping out edges, pulling out texture, glazing on them, just making them like visually interesting. There's no singular thing you have to do here. What I really wanted to show you is that rocks are a really fun thing to paint. I sound stupid, but I really enjoy painting rocks because you can use almost any color. Here I'm using green to a sort of off ivory and this sort of blue-green into ivory, and it just makes for something that's really visually compelling as it stands out on these rocks. And you know, if you go out in nature, there's just rocks of every color you can imagine and with every color infused into it because nature's real messy and elements of all different kinds or different colors and get worked into these rocks. So have fun, experiment, play around with textures, stipple, scratch, hash, dash, dot, and it will really make for a more interesting visual presentation of your base. The next thing I do is I actually find those areas that cracked under the crackle medium and I'm going to paint those roughly the same as the rocks themselves. I want it to seem like the cracked earth is almost like these rocks have emerged up out where that cracking is happening. Again, it helps to both break up that brown over all of the base, but it also helps to then tie the individual rocks into the ground. Toward the front of the base, I then do some light dry brushing with the exact same mix as my highlight color on the rocks just to bring it all into the same visual spectrum and add a little more visual contrast and travel as we get toward the front of the base cooling it off. A little final extremely light dry brush just to pick out the very edges and everything like that over the rocks and some of the just a little bit of the dirt here and there, especially toward the front and we're all set there. The last step is the skulls, just getting those nice and painted and picked out, making sure that those just kind of pop, and that's just working around with some of the ivory tone here that I have, as well as some of the browns. Once that stuff's all done, then of course I want to do one more final pass with pigment.  Because my rocks are infused with a little bit of green, this very weak desaturated red will be yet another place of light visual contrast. All these things are very desaturated, but they help sell it. Now that the miniature is attached, I need to sort of hide the line there where his little rock went into the space, and I can do that through both putting down a little more sand, which I did already, but as well I can put down some tufts and things like that. So I'm just using some dead grass tufts. These have basically no life in them, which would be appropriate for this chaos wasteland. Only the most rugged and dead plants. Each of these tufts gets a little wash around its base, and then I take that same highlight ivory color that I used on the skulls, on the model, on the rocks, and I give the tufts a nice dry brush. Doing things like putting a little bit of drop of wash into your tufts and around them at their base, and then dry brushing the tips of them with the same highlight color as you used around the miniature help to really integrate them into the environment.  This base is finished. Ready to go, ready for my warlord. There we go. The base is all done. The centurion is all attached. This guy is ready to lead the forces of chaos. This is kind of, as I said, I like this basing scheme because it is pretty simple, but it is very eye catching. The very dark earth against the bright poppy colored rocks makes it so it really stands out from a distance. And to me, I really like that kind of thing, especially because that pop color for the base is the same as the pop color for my army. If you have different pop colors, you could always change that up and do the same in your own army. But I hope you enjoyed this. If you did, give it a like. Subscribe for additional hobby cheating in the future. We have new videos here every Saturday. If you've got any questions, pop those down in the comments below. Always answer every question asked. Don't forget, we do have a Patreon if you want to support the channel and take your next step on your hobby journey. That's really focused on review and feedback and lets you join an awesome community of very enthusiastic hobbyists. But as always, I thank you so much for watching this one. And we'll see you next time.