First and foremost, thank you guys so much for coming to this session. This is a topic that Randall and myself are very excited to talk about. And obviously from the look of the crowd, you guys are pretty excited as well. So thank you so much for your support, for being here, it means a lot to us. Let me just start by introducing myself. My name is Travis Tidwell. I'm the co-founder and CTO of Form.io. And to my right is Randall Knutson. He is our lead architect at Form.io as well. And we're very excited to talk about Jason-powered forms in Drupal. Also, just so you know, if you wanna find us on Twitter, you can find us at form underscore IO. And as well as on GitHub, we have a very robust open source offering. That's something that we're very proud of, is that a lot of our capabilities, a lot of our renderers, the form builders, a lot of the stuff you're gonna see tonight is open source and it's on GitHub. So please check that out, come and star our repos. That means a lot to us when you guys do that. So just to kind of give you a little bit of a history about Randall and myself, we actually have a very long and fruitful history in the Drupal community. We've, both of us, started in Drupal about 10 years ago and had a wonderful experience with Drupal. As of recently though, just kind of as a disclaimer, we've somewhat kind of left Drupal. We started to go off and do our own thing with Form IO as well as some different technologies. And really our journey looks something similar to this. We started off with in Drupal, we loved it. In fact, whenever Dries asked that question, did Drupal change your life? We were among of you that stood up. Drupal definitely changed my life, it changed Randall's life, and it means a lot to us. However, as most of you guys are very aware, about a couple of years ago, the market changed. There's a lot of things that have been happening with Headless Drupal, new technologies coming out. And there was this call to adventure from being a developer myself and Randall as well, that there were a lot of technologies that we wanted to explore. Those included AngularJS, ReactJS, something I'm very passionate about, NodeJS, a lot of these JS JavaScript, you kind of see the trend going on here. And out of that kind of came this rebirth. We had this almost awakening of this new way of thinking, this new way of building applications and it really excited us. And out of that came this revelation, if you will, on this new way of building applications, but even more importantly, this new way of dealing with building and managing forms, which is what we're gonna talk about today. And out of that came this transformation and we formed a company around that. That's this concept of JSON-powered forms, which we will be talking about today. And through that experience, we realized kind of retrospectively looking back on our experiences with Drupal that what we have done at Form.io has a massive implications on the Drupal community. In fact, what this concept of powering your website with JSON-powered components really could serve as a massive benefit. In fact, for a lot of the discussions going on in the Drupal community right now, where people are talking about Headless Drupal and people are talking about, how are we gonna deal with this? This idea and this concept really serves as an elegant bridge where you can keep the power of Drupal in place because Drupal is an amazing technology, very powerful, while at the same time liberating yourself to handle and deal with all of these new technologies. So I'm excited to talk to you guys about that capability.  There is a big video involved, so you guys might bring down the network if all of you sign on at once, but it should be fine, right? None of you guys have had wireless issues this conference have you, so I'm sure we'll be okay.  We will be talking a lot about Form.io in this presentation, but just as a quick synopsis, we are a SaaS, a software as a service company, built around this concept of JSON-powered forms. Essentially what we provide is a form builder interface that allows you to build a form using a drag and drop easy to use form builder where developers or even technically savvy people, not developers, can build forms and those produce JSON schemas. And then that generates a REST API where you can immediately connect those forms to the REST API and then your world opens. You can do all kinds of things from integrating it to third party providers. And very recently what we've done is we put a lot of effort in building a module which we'll talk about later in this presentation where we've taken that concept, brought it to Drupal and to really bring this JSON-powered form concept into the Drupal community. So this talk will be a headless Drupal talk and all of you guys know this, that Drupal is kind of the hot topic right now. It's very hot, you know, it's so hot right now. But at the same time, I actually feel like the Drupal community is getting somewhat fatigued by this conversation. And I sense that because there's a lot of banter going on about, oh, it should be this way, it should be that way. You know what, Drupal is just not good enough, let's just not use Drupal. And that's going on right now. And I think a lot of that churn is happening because this has been somewhat of a disruptive thing that's happened to the web where you have the separation between front-end and back-end and I'm gonna talk about how Drupal got to where it is today. But I would like to frame this conversation and just say that this will be a headless Drupal talk, but it's gonna be a much different approach than I think what you guys are probably used to with a typical headless Drupal talk. And I think this different approach in my, as far as I'm concerned, is a very elegant bridge. It allows you to fully utilize Drupal to its powerful extent while at the same time introducing these capabilities of building these next generation web applications.  One of those is that these applications can now really kind of exist on their own. These applications can not only have the templates included in the app itself on the front-end, it can also include databases. And then in conjunction with all of the JavaScript libraries what you really end up with as a product is the front-end app. And that front-end application, and I'm gonna talk about this in a little bit, can be deployed anywhere. It's not constrained to the web. And I think that that's one massive thing about headless Drupal in this movement is the reason why it's becoming so popular. If you actually point the direction back at the server on the flip side of that, even from a server side's perspective, we have a number of benefits as well. No longer do we only have to deal with websites. We can now deal with all of these IoT devices because now Drupal can suddenly handle APIs using JSON schemas, XML, whatever. The point is that that is also a massive benefit as well, not only from the application perspective but also on the server. There is one benefit that I feel though almost eclipses all of these. And unfortunately in a lot of these conversations that I've been hearing about headless Drupal, it's almost like this one benefit that I'm gonna bring up next is something that's kind of not really thought about. And in my opinion, this is the most powerful aspect of headless Drupal, which is that the applications are now deployable anywhere. And this only happens if you construct your applications in a certain way where there's total separation between the application and the server, meaning the server should never send markup to the client. And whenever you build your apps this way, you really open up the world to deploy that application in a number of devices using Apache Cordova. You can install your app on an S3 bucket. You can use a CDN. In fact, if you go to form.io, our entire application is served from a CDN. And you can't serve a server-side web application on a CDN. You can also deploy it on a smart TV. GitHub Pages is becoming a big deal as hosting your website for you. And also another thing, I put it down there at the bottom. I don't know if any of you guys have experimented with this, but this is an amazing technology that came out of GitHub called Electron that allows you to compile a web app as a desktop application. And I know you guys are saying, oh, why would we wanna do that? Well, there's a number of enterprise organizations who are still locked into IE7. And this actually serves as a remarkable solution. You compile their entire web app in an Electron desktop application, you deploy it to their entire enterprise, and now you're suddenly dealing with modern-day web browsers, and you don't have to deal with that anymore. It's a remarkable capability, and it's something that, in my opinion, is getting lost in the conversation. Like when we talk about big pipe or things like that being a solution where the server is still sending the application to the front end interface, you cannot do this. And so it's important that whatever solutions we come up with, you don't lose this. And JSON-powered forms and JSON-powered components enable this type of deployments. So I know a lot of you guys are seeing all of these benefits, and it's, in my opinion, in fact, from taking a year, a year and a half of actually going down the road of building applications like this, to me it's obvious we should be building apps like this. This is the future. And hopefully it seems obvious to you guys as well. And I think the whole Drupal community has accepted that this is the future of Drupal. There's just a couple of things that make it hard. In fact, there's the big massive problem with Drupal is that it just was not built to work like this. And if you really kind of stare at it and say, what is really the problem and why was Drupal not built to work like this, you run into one, in my opinion, one single massive issue, which is that Drupal is handcuffed to these PHP renderings where it, and it's hard to break it from that, where the entire foundation of Drupal was built on this concept that in order to get markup rendered, the PHP has to be responsible for rendering it in a PHP array. In my opinion, that is a handcuff. And really if we stare at that one single problem and solve it and break it, we have the ability to use Drupal to its full powerful capabilities while at the same time enabling front end applications to consume these new modern technologies to build amazing applications. So just to give you an example, and I know a lot of you guys are gonna, this is gonna strike home for you. In fact, this really puts us into the context of this discussion because what we're really here to talk about are JSON powered forms. And if you guys know, as most of you know, the Drupal has its constructs in PHP, which is the form API. Everyone is very familiar with this. In fact, this was revolutionary whenever this came out. And really all you're doing is you're taking a form definition and you're breaking it up into a PHP array, which is defining the schema of that form within a PHP. You guys already know this. What I do want to mention is that while the form API in my opinion serves as a great example and actually a really good place to focus to start off with, there are a number of other pieces in the Drupal CMS where this happens. And so we can almost take the form API as a pattern to apply this to other renderings within Drupal. And so what really happens out of this, and if you actually think about it, a lot of you are looking at these renderings and you're saying, you know, how did we get here? How did Drupal get to a point where this is okay, where this is the accepted solution? And in fact, I kind of have to take you back to the beginnings of the web, where web forms really came out of the very origins of the web and actually Drupal came from that. And this will kind of take you back to web forms, you know, 1.0, where you would have this website and it would quite literally request a single file on the server and that single file was an HTML file. And if you wanted a form, that form in HTML would be on that file.  You know, we don't have to be recreating the wheel for every single one of these pages and then when a request comes in, we can dynamically create these templates and send it up to the client. And then Drupal came out of the PHP movement, created the Form API, which was amazing, allowed us to essentially take that one step further where we could create these very well structured PHP arrays to essentially generate the forms that you have on the front end. The point that I'm trying to make is through all of this and even today, the server is sending the form to the client in all of those cases. And that, in my opinion, is what we have to break. And for a long time, life was good. If you guys remember, I mean, life has been good. Drupal had a massive boom, life was amazing. And for a long time, this PHP rendering was doing very well and then, as all of you guys know, this happened. Apple introduced a revolutionary device that really kind of made us stare at how we're implementing these websites and we had to rethink it a little bit and rejigger it. In fact, out of this came, all of you guys are gonna know this, the mobile first movement, which where you said, okay, now I need to make my forms or my website look good on a mobile device. So I'm going to still have the server send me the interface, but I'm gonna rejigger it so it looks good on a mobile device. And Drupal was great at this. You would send a request to Drupal. It would happily use the form API to happily use the form API to render the form and then it would send the form up to the client and the client would render it and it'd look beautiful on a mobile device. And guess what, life was good again. So life has been good even with mobile first. Then this happened. And so what has ended up happening is that now the server can no longer be responsible for a single type of interface. It now has to deal with all types of devices. And these devices display how they want to display. They are responsible for displaying the content in the way that they want to display it. And now at this point, this is really what's brought on the headless Drupal movement where Drupal has to figure out, how do I render this form and all of these devices that are requesting the form from me? And so headless Drupal is basically saying, you know what, the rendering should happen on the client. The client knows how to render itself. It should be responsible for that. And that's the right approach but now we have this problem because we're still building forms using a PHP array that can no longer serve the AngularJS and the ReactJS communities. And so what's happened out of that is a lot of developers, as of right now, there's kind of this vibe going on where developers are kind of like, you know what, they're throwing their hands up in the air and saying I don't really know how to solve this because Drupal has really anchored itself on this PHP renderings concept. And in order for us to get these front end applications we have to do API first development. We have to build APIs. We've been doing that, it's great. But even today we are still anchored to these PHP rendering arrays. And from our experience building a platform founded on JSON powered forms, it's very clear to us that the solution is actually far simpler than a lot of people realize. And we can do it piecewise. We don't have to throw the baby out with the bathwater. We can take little components out of Drupal and take them in piecemeal our way to a big solution. And in fact, we can not only get the best of the AngularJS abilities, but we can also get the best out of our CMS. Drupal is an amazing tool. We should not let go of that. Drupal's amazing and it serves a purpose. And so I really believe that we can actually get the best of both worlds. And I actually did a Google search for the best of both worlds. And this is the image that came up and I was like, I got to go with that, right? You know, Hannah Montana just kind of put you in a good mood. So anyway, so with that said, this really kind of gets us into this new way of thinking that we can take these old PHP constructs, rejigger them a little bit and we don't have to throw the baby out with the bathwater and by doing so we introduce this new capability called JSON powered forms which is the next generation of web forms. And I'm gonna hand it over to Randall at this point. Thanks Randall. Thanks Travis. So we're gonna talk a little bit about JSON powered forms and we're gonna look back just a little bit. If we look at kind of what's been happening in the last few years, Travis has touched on it a little bit. You can't probably read a lot of this but this is kind of the Google trends of things like Angular and mean and REST APIs. The last couple of years we've seen like just this tremendous takeoff of that. In fact, Dries even touched on this in his keynote yesterday and he kind of just stuck them down in there and he said they're building bespoke solutions with Angular and I think today he's very correct in that. I mean, if you look at what it takes to really do this, if you do it on Drupal with the headless Drupal you gotta install Drupal, set up all your entities, set up either RESTful or RESTWS or services or something to get the data out of it. In Drupal 8 you automatically can get an API and then you have to custom build the entire client side application or iOS application or whatever. So they're very hard to do. There's a lot of work and they're very bespoke. What really struck me in the talk and I wanna challenge him a little bit on as he says they have moved up but will always be for bespoke solutions and I think that always is dead wrong. How many of you can think back to life before Drupal and what it did for us? Anybody in here program in PHP before Drupal? It was a lot of work. It was bespoke solutions, right?  Client would fill it out and submit it back to the PHP and then you had the logic in there to do all the validation and if the validation failed then you gotta rebuild that form and put those old values back in there without clobbering the default values, send it back to the client to fix it all and they would submit it and then you got that data and it's all good and then you gotta figure out how to go store it in the database, right? It was a lot of work and everything was bespoke. Some might've even said then that it will always be bespoke. Along came Drupal and made it so we didn't have to think about all the nitty gritty details. Instead we could build our entities at the time it was node. Now it's entities, right? You could build an entity and you knew your database tables would be built for you. The validation would be handled for you. All of the complexities would be handled for you.  So we are currently living in the world of client side front end applications where they are bespoke. What Travis and I are working on with Form.io and JSON Powered Forms is making it so it's no longer bespoke and works in a way that you just describe what you want and everything behind it is taken care of. So we're trying to get us to that next level. So how do JSON Powered Forms work? How do we do that? Well the first thing we do is we have a form builder. It's a, on our site is a drag and drop form builder but at the end of the day you're building forms and those forms actually live as JSON schemas. And kind of like that PHP array it's a schema that defines what the form is. It have like a title where the form submits to as well as all of the fields that are contained on that form. Now we can take that schema and do a couple of things with it. One thing is we can actually render it in the client side. That could be the browser in Angular, could be in React, we can render that form. Could be in iOS or anywhere else. You've got the schema of the form sitting wherever you're trying to render it. Instead of getting handed HTML you get handed the schema and can figure out what you want to do with it. But here's the really cool thing. At the same time we can build a REST API that corresponds with that form. We don't have to build it custom every time. We already have a definition of what we're looking for, what the form's gonna provide. Let's build the REST API behind it as well as the database behind that. So, and then that schema, so we now have a REST API and a form schema that the front end's gonna consume. We can actually serve up that same JSON schema as part of that REST API. So the front end application can just say, tell me what this form should look like and tell me where to submit the data and they can get all of that information, render the form and send the data where it needs to go to. So that JavaScript library can just do all of this and it doesn't even have to be JavaScript. It's JSON, right? We can do this anywhere. So I'm gonna give you a quick demo of kinda how our technology works around this. So this is a code pen of our form builder building a schema. So you can see right now we already have a form in the form builder over here on the left and a series of fields that we can drag and drop onto there. So let's say I wanna drag a company field on here and I'm just gonna label it company. And now if we look over here, this is the schema that defines that form is being defined into. And if we can see there's the last name and you may not be able to see this real well, but here's company. It just added into that schema dynamically. Now, if you notice there's no placeholder in that field yet. So I'm gonna go over here and configure it and say, enter a company. And now when I save it, if you look over here again over there in the JSON, there's enter a company that's been added to that JSON object dynamically in real time. So now we have that JSON that's the definition of the form and we can render that. So if we scroll down the page a little and it's not scrolling, I'll do it manually. As we go down the page, if you can see up there it says, we have our FOMEO directive in Angular and we pass it into it the form definition and then it will render out that form based on that definition. And so you can see that company field is now added to it. Now, inside of Drupal with our Drupal module, it can create an entity with those same fields on it and create a REST API using the RESTful module that can then send that data into and then it lives in it. Now by default, we are a company, software as a service, no JS, express backend. So if you don't need it in Drupal, you can send it to our service as well. And that API is like I said, no JS, MongoDB. We have lots of connectors to third party services as well. So as you're building out those forms, those REST APIs automatically will build out in our service but you can also create entities for them in Drupal as well. So that's kind of how this whole concept plays out. So let's talk a little bit about the benefits of JSON-powered forms and what that looks like. So one of the great things about JSON is it is ubiquitous. Pretty much everything out there nowadays knows how to talk JSON. There was a time when it was kind of like XML, PHP arrays, only PHP really knows how to talk them but everything talks JSON. So we're able to use this across pretty much all the devices, watches, phones, you name it, smart TVs. And this allows us to deploy our forms anywhere. This could be in a website. You can drop that into a website. You could drop it into a tablet application, into your phone. And if we think back to again bespoke applications and how much work that is, imagine if you've got a form inside of an application that somebody wants to make a modification to. That never happens in client services, does it? Nobody ever makes modifications in the middle of stuff. So they wanna add a new field or change a field. What do you have to do in a bespoke one? You have to go in there, go talk to the database people or add it in the database and then change the REST API, which might be in Drupal, might be in Rails, might be in who knows what that's written in, right? And then you have to go into each of the front ends, maybe computer, tablet, phone applications, wherever all of these forms are embedded. Each one of them, you've gotta go add that field and make sure everything all syncs up correctly. If everything is JSON powered, you literally just drag the field over there, save it when the schema is updated, your REST APIs update, your front end forms all update because they're all looking at the same schema and everything across the board just changes automatically, everything updates. So this does away with a lot of those problems of having a bespoke application that takes a lot of work to build and update. Another really cool benefit of using JSON powered forms and this separated architecture that Travis talked a lot about is you can actually have offline form rendering and data collection. You can't do this with server based applications. What that means is with browsers nowadays, they have application caching and databases built within them that we can utilize when you have these separated architectures. You can actually cache a web app into the browser so if they have no internet and they go to the URL, it will still come up and then as they fill out things and hit submit, it will cache them into a database in the browser, wait for an internet connection when it's there, we'll send that data up to the server. We actually have clients that are using this today and how it worked, like one of them, they sign medical waiver forms because they do scuba diving and snorkeling in the middle of the Great Barrier Reefs and stuff. So they are on a boat in the middle of the ocean. There is no internet and they need people to fill out these forms and hit submit and save those data and then when they get back to land and they can turn it back on, they will sync all the data back up to the server. We're able to do this with JSON powered forms. Another, a couple of other examples are customers that have service workers or clients that are going on site. Sometimes it'll be like drilling locations or remote places in the middle of fields. Again, no internet, they need to enter a work order or a sales quote for a large vessel or something. They can fill out that information right in the field, hit save, it gets stored until they get back to a place with internet and then sends it up. This is a pretty cool thing. Again, by doing everything based on schemas, we're able to do other things like those REST APIs behind it. When we were doing our Drupal module, it was pretty easy to just say, oh, just create an entity based on this schema and just build it out. So these REST APIs then are able to update automatically the back ends and the front ends all at the same time based on these schemas. So our Drupal module is at Drupal.org slash project slash formio. It's gonna be released probably around the end of the month. We are looking for beta testers, so if you're interested, come talk to us. Right now, this one's gonna be Drupal 7. Once that's done, we'll start working on the Drupal 8 module, which probably will be easier because we don't have to do all the REST API stuff. So I'm excited about doing that. So let's take a quick look at a demo of what this all looks like in our platform. So here, this is on our portal, so we're gonna create a form, or a project in formio, and that will allow us then to go create a form. So we're gonna create a form using our drag and drop form builder, so a new form. What's cool about this, you title it, and then we have a whole bunch of different form components that we can use to build these forms. So we also have layout components. So I'm gonna drop a columns on there, and that will give us two columns. Then I can drag over a first name field and there's lots of different validations and other settings you can do. Last name field, you can do input masks, placeholders. We also have some other, more special fields, like we have a phone number field that will automatically force people to enter phone numbers. We also have a really cool address field that does a Google API lookup, and will validate the address and include additional location information like the GUIP coordinates and all that kind of stuff that gets saved back to the database automatically immediately. So there I add another text field in there. So there, we've created our form. We can preview it really quick, put some numbers in, see how the input masks all work, the address, I'm gonna look up an address here, and there's one World Trade Center. And so now that that's selected, it's actually storing all of the information about that location in the backend, and we only see the little bit on the front end. Now, let's go back over to Drupal and see how we can integrate this into Drupal. So if you've got the project set up, you need an API key in your project URL, it will automatically populate the list of forms down here. And when I drop it down, we're gonna embed a much larger, more complex form in here. And you can see there's a ton of stuff. I'm gonna go back up and we can more slowly see. You got a ton of information. Try building this with the web form. Good luck. We also have conditional visibility, so you can say only show this, that's this value, and so stuff can hide and show. You can save it to Drupal or save it to our service either way. If you choose to save it to Drupal, it will create a Drupal entity and a REST API, and when you submit the form, it will save it back to that entity. So here I'm creating a panel page. It is panelized or blocks either way. You can display it either in a panel or in a block. It's up to you. So here I'm gonna add the Formio form. It's gonna pick the demo one. You can select another one as well and save it. And then we're gonna preview it inside of Drupal to see what that looks like. And this is just a vanilla Drupal install. I did it like five minutes before I recorded this demo. And here you go. There's your form, all in Drupal, ready to go. And then when it submits, if you choose you can save it into an entity in Drupal, all that data. That's kind of how those JSON forms are gonna look. So where do we go from here? We've got a really great solution. We operate outside of Drupal. We have a really great Drupal module coming that's gonna allow you to use these things in Drupal. But this is something that Drupal could do more natively. And if that happened would really enable people to build front end based applications, client side, single page applications more easily. So what does that mean? Well, here's what we currently have, right? Everybody's probably familiar with REST APIs. This is all the full crud. You've got the index, create, read, update and delete, right? Your standard crud operations. And that's typically what REST APIs do. Kind of the innovation that we're talking about is that we add one more endpoint. And that is something like form. Could be something else, but we typically call it form. And that, when you get it, will return you the definition of the form that's needed to interact with this API. We could base that on the entity definition, right? You could just grab the entity definition and say what should a front end form look like that can interact with this API? That's all we need. And once that happens then you have a rendering library in Angular, in React, in Ember and whatever else you wanna have it in. And it can take that JSON form and render it and submit it to that exact same old APIs. So that's kind of what we're proposing here. And we really think, so here's an example of, if you were to translate the entity definitions into a JSON schema. So we really think that something like this for Drupal could really pull us into the whole Web 3.0 single page applications next generation without having to make everything bespoke. We could make a lot of, we could connect everything from A to Z without all of that extra work. So thank you very much for your attention. That's what we've got. So we did leave plenty of time for questions. So we really wanna get y'all's, first of all, get your input as well as answer any questions that people may have. So I'm gonna go ahead and answer that. You don't have to follow your presentation. Do the what? The address. The address for the presentation. Oh, the address for the presentation? Yeah, sure, absolutely. So let's ask questions, sure. I saw a signature field up here. Oh, there's a microphone up there. Sorry, go ahead. Yeah, go ahead. Yeah, go ahead. I saw a signature field up there. How are you guys capturing that and storing that? So the signature component is actually using Canvas so that you can actually sign with your finger and it uses Canvas. And that actually stores the base 64 binary of the signature. And so we're not actually saving it as an image. We're just saving the binary, base 64 binary as a blob, really. And so then whenever we render it in an image, you can pass that directly to the image tag and it happily renders it and we don't have to store the actual image. Yep, go ahead. So currently when I make a form in Drupal, I can pull all sorts of information out of my database, user ID, whatever other information I have and use that to customize the form. So it looks like what your module does is pretty much one way. I build the form on form.io and then I import it into Drupal. So it seems like I'm losing a lot of flexibility. So great question. To be able to pull information from your existing, let's say entity collections, we have a number of components that allow you to hook them up to custom rest endpoints. So for example, the select dropdown. Let's say you wanna be able to select an existing entity within your Drupal solution. Our select component actually has the ability where you could hook it up to its own REST API, which would essentially be the component endpoints so that you actually can get some of the data into the form for people to select certain entities and the like. So you can do that with certain components. So to continue on to that, a good example that might be like customizing what options are in a select dropdown, right? And I'm curious on a use case, but so let's just talk through that. Typically it's really important to start wrapping your mind around when you're doing front end applications that a lot of that logic takes place in the front end application, not when you're building the form and rendering it from the server. So in that instance, we still build the form and we send it, but like Travis is saying, you have a REST API in that select list that says go get the options for this select list. And part of that is the user token and then you can customize in the REST API for that select list and say, oh this user only has access to these five items, only pass them back. So the logic is actually happening in the front end and in the REST API. You don't do that when you're building the form. Hi, two questions. Hopefully they'll be fairly quick.  But what about a form that collects more sense of information? So like how do you do encryption? How do you help protect data as it travels from the form through various systems? So that's one major benefit of having our forms point directly to Drupal and the entities that were created from Drupal. So essentially you're sending the same requests that you would be today with a server rendered form. I mean the server rendered form is going to the client, the client's filling it out and then they're sending that request back to Drupal. That still applies with this system. So any SSL mechanisms that you have to protect the transport of that data over the wire is still in place. You're not sending that data to our service and then we're kicking it to Drupal. That's not happening. Yeah, a quick follow up question to that. Yep, sure. So say we use your Drupal module, have a form module, but say we don't want to go to Drupal, we want to plant to another system, is that possible? Absolutely, yeah. So that's another major benefit of using JSON powered forms is you can choose to point that form to Drupal. You could also choose to point it to Form.io and have Form.io execute its actions, or you could choose to point the REST API to some other service that you may have. It's really up to you on where you want to point that data. Okay, final question. How easy would it be to configure a form to pull hidden value? So say you have an Analyze system that cookies somebody with a specific ID. Yep. I want to go ahead and get that value passed into my CRM. Yep. How can you pull hidden values through your forms? Yeah, we actually do that all the time, and that's another major benefit of a JSON powered form. With that, you actually get full JavaScript control over the form itself, and you can inject certain values based on just setting a certain data model within JavaScript. So in your particular example, you would have a hidden field, which is the Google Analytics or whatever you need for Google Analytics as a hidden field in the form. And then within JavaScript, you would just simply assign the data model in the client to that value, and it'll automatically populate that hidden field within your form. Hi, first of all. Hello. First of all, thank you for the presentation. I thought it was excellent. Thank you. And my question is, in regards to AJAX forms or conditional forms, do you support that? Yeah, yeah, and that's actually configured within the JSON schema. So whenever you're configuring the schema, you actually on a per field basis get to decide this field should be showing under these certain conditions. And that's actually part of the schema definition. And as it turns out, our renderer, the renderer JavaScript library that takes that JSON schema and renders the form in the front end, honors those conditions that are within the JSON array. So yeah, absolutely. Is this on? Yep. Thank you. Your demonstration pretty much showed an English related situation. What about sites that need to support multilingual translations? Great question. Actually, the renderer is capable of translations. We're actually standing on the shoulders of giants there. There's a very common AngularJS translate library. And that actually uses Angular filterings. And so the way that works is you have to just provide one additional JSON object to the renderer, which is the translations. And so based on whenever the client is rendering the form, it can also say, okay, what language does this form need to be in? And that additional JSON schema is used to configure the filtering mechanism within the renderer so that it actually dynamically translates based on their language. And a great example of that is the waiver forms for the scuba diving. As you can imagine on the Great Barrier Reefs in Australia, not everybody there speaks English. And so for that application, we actually translated into, I think, six different languages. And all that was required is we took all the strings in the form, had the different translators, give us the different values, pass those JSON objects into the form, and then the user can pick which language they wanted and immediately translates the entire form into all those different languages. Yep, next question. Yep. For a bootstrap includes like a form system, is that something that would work with form.io? And I was just looking at that recently, and it's, you know, somebody like me with no aesthetic taste can make pretty decent looking forms with it basically. Yeah, and that's actually a very common use case. And I hope I got your question correct here, but a very common use case is to offload the form building capabilities to other people. And it's actually, once the developer gets the mechanism in place, we actually kind of showed you the workflow of form building. Imagine handing your entire marketing team and say, you live in form.io to control your world. Build whatever forms you want. And all the developer has to do to get that form into Drupal is create a preset, select that form and add it to a block. And you suddenly have that workflow that you described where other people control the creation of forms. If I understood your question a little bit, all of our rendering is actually bootstrap compatible. We all use templating from bootstrap and all of the themes from bootstrap. So what you saw in there actually was a bootstrap theme for the form. I was wondering if you guys have like standard clients, like that you have a renderer that, I mean, do we have to write the client in AngularJS for every platform or do you have a standard client that we could configure that would interact with form.io so that we could run it on the browser, run it on iOS or run it on Android or something like that? So right now we have two renderers available. One is for AngularJS and the other one is for React. And the way we get that into Drupal is we actually add those dependencies to the page. So those two renderers are what we support right now. However, we've actually created them in a way so that we've essentially established a pattern so that if you need a rendering capability and let's say Android native, you could take the pattern that was established with these other renderers which are all open source. I wanna also throw that out. All of the renderers, builders, MIT licensed open source. So you can take those patterns and actually use that to construct other renderers but out of the box you have AngularJS and ReactJS which should cover you on most devices. And in addition, if you do the web view components inside of Apache Cordova or Electron, you can actually compile desktop, iOS, Android, Windows Phone, all of those different devices as well. So if you're not going native, you actually can still use those Angular and React components as well. Yep. So a question about say business rules that you would like to put into the front end like a date, can't be after today, a date of birth for scuba diving, right? You have to be 16. So those kind of validations, where would you put those? How would you manage the library for that? So the validations are actually also described within the schema itself. So when you're building the form, you're actually, there's actually a section within Form.io where there's a validations tab where you can say these validations should apply. And the module, what it actually can do is whenever that request makes itself into Drupal, it can perform a simple validation request to Form.io. Right now, what it's doing, it's actually using the standard entity validation criterias, but eventually in the future versions of the module, we can also make it so you can configure it to also do a quick ping over to Form.io to say is this form a submission valid? So the follow up from that, then following the example from the Great Baby Reef, I have no signal. So in other words, you know the old saying Gaga, I want to validate the data that I put in. That's a great question. So our forms, not only do they validate on the front end, but they also validate on the back end. So to answer your question, we actually have two validations in place. One is front end validation, which means as they're typing it out, it's actually validating the request. So you put all of those rules in the schema and the renderer is actually compatible to say, is this valid as you're typing it out on the front end? And then we actually, with the offline mode and talking about offline mode, because things get kind of complex there, because what if they type in something and then they connect to the internet and it tries to submit it and there's a validation error that happens. In fact, our system, the way it works is, whenever there's a validation error, it knows the form that the validation error occurs and the app sees the validation error, shows the form again and says, hey listen, we're trying to re-sync this and can't. Here's the validation error, fix it. When they fix it, it moves on to the next item in the queue. Does it go on entity reference? Not right now, it does not do entity reference. But to achieve references, now Form.io, if you were building and highly leveraging Form.io's API platform, Form.io's API platform absolutely does resource relationships and all of the like, but if you really want to anchor yourself to Drupal right now, that's not a capability, but it's open source so I see we could add it soon. It could? Okay, yeah, he knows more about the entity creation. Well, I mean if you have an API and you're feeding that into a select list. You're feeding it into a select list, you would select it and that would be part of the payload. The ID would be the value you selected so that would save into the form. Okay, let me put it this way. We haven't tested that. But it could work. We have, yeah, I think we have time for maybe like a few more questions, go ahead. Oh yeah, go ahead, I'm sorry about that. I didn't see that microphone. I just had one quick question. Do you have an easy way to pull URL parameters and feed them into the form or does that just need to be done in JavaScript? Well, JavaScript is the easy way to do that for our forms because it's all in JavaScript and so it's very easy to write the code to say, just grab some query strings and feed it into the form. So that happens very easily. I just thought maybe there was like a, there's no checkbox for that. Okay. All right, thanks. Yeah. So yeah, I was wondering if I had a bunch of existing Drupal entities. It can be done. We'd love to have a patch for that. I'll work on it. Thank you. All right, well, thank you guys so much for coming to the session. I really appreciate it.


Everyone should read Tales of the City because it captures a magical time and place in San Francisco that should never be forgotten. I first read Tales of the City when I was a freshman in college. It just got me through a very long first cold snowy winter in New York. San Francisco's changed a lot and then we lost a lot of friends, a lot of our city, and we got in a whole new group of people that don't know about San Francisco in that time and place when it was more safe, more fun, more open. I almost feel like it was more sunny which is ridiculous. I think the book will make people laugh and cry and smile and everything in between. It reminds you of the way that the world should be.


Pockets, stuff like that, anything hanging. Make sure you hold on to everything to unjob it so you guys don't have feel for it.


y sector, Alzheimer's and so on, they all came to the event very much in their chimneys, so to speak, you know, when I'm extra and I do this, and this is how we do it in our world, but when you brought them all together and they started to hear those stories, that group gelled into one and began to say, we need to address some of the problems here, and one of the things that became very clear in Northern Ireland, and it may be the same in Scotland, I can't speak for Scotland, is that depending where you are, will depend on how you are treated as a person with dementia. The postcode lottery was a term that was used quite frequently. The benefit of the innovation lab in that case was that that group of disparate people with disparate views coming from different parts of the health sector for the voluntary and data from academia is that everybody corrald around this thing, we need to do something about this, and we need a regional model for dementia services, we need to do something about supporting carers, support for carers 24 hours a day so that they can access help, and so there were various things that the group agreed needed to be done. Then we brought those ideas forward and then the NHS started to address some of those things. Yes, you would have thought that those conversations are happening and maybe they are, and maybe I'm speaking as a rank outsider to the health system and having had that experience, but there was a real sense amongst even the professionals in the room that, I'm not going to say a shock, but a recognition that this isn't really working at the minute and we need to address it and change it, so I think that that would be my observation. The suspicion is that that is the case in Scotland and that we also have subjects, be it dementia or other subjects, where there's a lot of people interested in that subject, committed to it, but they're not somehow all joined up together. Is that what the lab is best at, is bringing people together who are not normally coming together? I think that is a big, if that is all we achieve in many cases, that is the richness of it. In that example, we had one overnight and I sat dinner with a number of people and there were clinical psychologists from different parts of Northern Ireland and they'd never met before, and yet Northern Ireland was a small place. They were starting to tee up and then to share ideas and then agree to meet. I see part of the innovation lab as being a gathering point or a collaborative and pulling people together who have an interest in a particular subject and looking at it in a collective way. Do you always need the sponsor behind it and the decision maker behind it who can take the outputs from it and then begin to test them and start to implement some of them? In a case like that, you might have more than one implementer in that you'd have the statutory services in the voluntary sector and they would be able to both implement things. The way in which we have tended to view it in the innovation lab, we go to the owning department. Which is the public sector? The public sector and the health service. In our case, it's the department of health and social services and we find our sponsor there so that the outputs from the innovation lab have the sponsorship of the most senior person who owns the particular policy area and they can start to influence change in the actual health system. Dr Sullivan, one of your answers you talked about is the need for testing and not just having ideas. Could you just expand for me a little bit what that actually means in practice? I think that that's the challenge for us. If we think of the evolution of our lab, our lab has been to date very good at bringing people together. I can give other examples where, again, I've been involved in conversations where people have said that we should have met together before and yet it was the lab that brought them together. But if a lab is really going to do what a lab does, which is to test, then it shouldn't just come up with recommendations. Some of our early work has been around getting the right people together, making sure that you're dealing with the right problem and then coming up with recommendations. What the memorandum of understanding that we're now developing with the sponsor is that they will give us permission to test things in the lab, so with that group we will actually go and do something. Assuming that the legislation is in place to do what depends on what the circumstance is, so that it's not just recommendations that is the end point of the lab when we hand back to the sponsor, but we actually have some, albeit fairly small scale, albeit rough and ready, but we have some pilots to go back and respond to. In the dementia case, could you say how that would work? If it hasn't worked so far, how might it work? That would be about trialling different service provision with dementia sufferers. You might take, for example, the diagnosis process. There's an experiment in Bristol where diagnosis isn't the reserve of all circumstances a consultant and they're trying to get GP to do some of the diagnosis, so the lab might say, well, let's design a similar trial in Northern Ireland and you would go out to the system and say, look, we want to test to see if this has value, does this speed up the diagnosis process, does it help to get people the support they need, and so that's just an example of what we might do and trial it. Okay, thanks. Mr McCall, you gave a kind of hospital example, and part of me believes that we should just close down hospitals and put the resources into the community, but there is some resistance to that. Your suggestion of an elderly person turning up, going to A&E, having had a turn or whatever, and being turned away, part of me is attracted to that, but part of me says what if they had a stroke, what if they had a urinary infection? Surely social services couldn't cope with that. How do we get the balance in there? The approach in that case is that social services provides somebody to be with the person, so if they have a stroke, then the care worker will identify that they've had a stroke and have them admitted to hospital. The reality of hospital care is that there are risks associated with it as well. We underplay those risks and we overplay the risks of care in the community that you've identified. I think that the approach that we need to take is one that's based on the evidence around this, and that we identify what would happen in that circumstance, and we identify what the costs are associated for the individual with admission to hospital. How many of those individuals get dehydrated? How many of them have poor nutrition in hospital? How many of them pick up hospital-related infections? Admitting to hospital is not a guarantee that nothing will go wrong. Any more than being sent home is a guarantee that things will go wrong. It's a lack of information or understanding, perhaps, on the part of the public. I was interested in one of the pages of your report that says, by giving people in communities more power over decisions, we can move public services to co-production, enhancing their ability to be preventative. However, I'm feeling amongst the public is that they want A and E, they want hospitals, so is it just that the public doesn't understand? I think that what the public wants is a guarantee of good care, and they see the NHS as a guarantee of good care. In many cases, that's correct. In almost every case, that's correct. The problem is that, often, the NHS is not the appropriate destination for an individual, and we need to build the case that that is correct. We need to be able to say to people that admission to hospital is not always the best thing for you in every circumstance. In the same way as we've moved from a culture where people used to go in for long stays in hospital to more day surgery and much shorter stays, and we've built an understanding amongst the public that that is a better way of doing things, that if you have major surgery you don't go into hospital for two weeks, you go in for a much shorter period of time. That, I think, is the circumstance that we need to move to, because doing things, because people believe erroneously that they're better for them, is not good for anyone. Okay, that's very helpful. Thanks, I'll leave it at that. Okay, well thank you very much, and that's concluded questions from the committee this morning. I'd like to thank all our guests for an extremely interesting question and answer session, I mean this is something that's still leading the thoughts of the committee. I would, of course, however, add that shutting down hospitals is not that this is Scottish National Party policy. Anyway, thank you very much for that. Any further points you want to make before we wind up? Okay, well thank you very much. I'm now just going to call a two-minute recess to allow our witnesses and the Fisher report in public to leave, and then we'll press on with them, final item on our agenda.


HBCU Digest Radio, welcome back. I'm your host, Jared Carter. We are continuing our coverage of the HBCU community's response to the COVID-19 pandemic, global pandemic, speaking with the best and brightest of our leaders and stakeholders from around the HBCU community. And today, I gotta say, this is a special treat for me. This is the first time in the decade or more that I've been doing the digest that we will have an opportunity to converse with a presidential transition. That is the outgoing president of Central State University, the esteemed Dr. Cynthia Jackson-Hammond and the incoming president, brother Jack Thomas. And so I'm really excited about this. Thank you both for your time today. Let me begin, brother Thomas. First, give us some of your feelings about coming into this particular presidency and what attracted you to Central State? What was most appealing about it and has any of that shifted or changed because we're now going through this public health crisis? Jared, thank you so much for having me on along with President Hammond. I must say that I am excited about this opportunity, more so because President Hammond has done an excellent job in positioning Central State University to where it is today and having the opportunity to work with her along with the Board of Trustees to make this what I call a wonderful transition. And answering the question that you oppose, as you look at my background, you would know that I have been fortunate to have a career where I've held various kinds of positions and particularly increasing responsibilities in higher education. I've worked at HBCU as well as I've worked at the majority of the institutions. And during my over 30 years in higher education, I've been able to develop key relationships, produce academic intellectual property, and most importantly, to cultivate and develop the next generation of leaders. I was a first generation college student and I'm glad to accept the presidency at Central State because it's an 1890 land grant institution. I am a product of two 1890 land grant institutions as well as I held positions at two 1890 land grant institutions. And I want to embrace the heritage, the legacy and traditions of Central State University. And I saw this as an opportunity to bring all of the skills and experiences that I've had over the years to Central State University. And Central State University has become what I consider to be a game changer and an institution that not only develops students into holistic citizens, but to make sure that students provided a quality and well-rounded education. And it's quite funny that you asked that question about when I first accepted position, I know the institution was on solid foundation, but now that, and it's still on that solid foundation, don't get me wrong, but at the same time, now that this COVID-19 pandemic has hit, that means that it's going to bring various kinds of challenges to the forefront. And we've already begun to address those with one of the committees, which we call the IRT, which is the institutional response team that President Hammond and I held put together, and we're already working towards that. So there's gonna be some major challenges in terms of the cause of the pandemic, which kind of changes my overall view and those that I initially had when I was first accepted the position at Central State University. Madam President, you never thought, I'm sure, when you announced your plans to retire, that you would do so under these kind of circumstances, but have these circumstances given you a different view of the work that you did over your time in Ohio, not to say that anything changes about the value or the impact of it, but as Dr. Thomas mentioned, because there are some challenges ahead, do you look back at your work and say, you know what, that is even more valuable than I thought it was at the time. And thank you so very much for having both of us on this morning, Mr. Carter. And I've been on these conversations with you in the past and I found them to be very, very enlightening and helping to share what institutional values are, values especially, but the broader community. My work at Central State and the achievements that we have got over the years is the result of a team effort. Sometimes the President is out there in the front, but it's really the entire university working collaboratively and in sync to make things happen for the betterment of not only the institution, but particularly for students and the communities that we serve. COVID-19 has been a complete change for everyone, not just for Central State, but for the state, for the United States and for the world. So naturally we will have to reassess, rethink our past going forward. One of the things that has been instrumental in the success of Central State was becoming an 1890 land grant, which allowed the institutions to have more focus on research and extension. And extension means how do we serve the people of Ohio in their communities? And COVID-19 has certainly raised our awareness of how we serve. And I know that going forward, Dr. Thomas and the administrative staff and the university will continue to keep that focus paramount because if ever there was a time that the community needed the interactions and the resources that can be leveraged through the university, it is now. Let's talk a little bit about those details because I think people need to know the impact that Central State really had on Ohio and in that region. So the things that you've done, training skilled laborers with new levels of education, you mentioned the land grant status acquisition, which was a historic thing. Do you think that some of those gains will better position the school, that those things that even with the pandemic, even with the new way we will social distance and all those things, those changes are to last. We're always going to need agricultural extension. We're always going to need workers to be trained up and skilled up. Those things are going to last, but do you think that the logistical challenges of that may change in the future or that that will be a new burden for Dr. Thomas to look at as he comes in? Well, of course everything is going to change the way we deliver services. But we are just not reacting to COVID. We are trying to be as proactive as possible, taking into consideration the students that we serve and the communities that we serve. Social distancing means more access to technology, more utilization of technological devices, more opportunities to engage at our platform that we did not have to engage on before. But going forth, it is what it is. And we make those changes to adapt to the needs of the community and to our students, whatever those changes might be. Right now with COVID-19, there are so many unknowns. We don't know what's going to happen a month. We can only make plans and those plans have to be adaptable and fluid enough that if we had to modify changes in any kind of way, we would be prepared to do that. So like everyone else, Mr. Carter, we are planning for the unknown, the best that we know how. Dr. Thomas, you mentioned before the other stuff that you've had over your career, you've led other institutions in interim and permanent capacities. In Ohio, it's a little unique in that it's at the forefront of a lot of conversation about how the country reopens, right? And there are a lot of political imaginations about that. There are a lot of economic considerations. In your experience, how do you think central state will play a role in helping Ohio to either reopen safely or to consider the ramifications of doing such? And this is particularly for black folks in Ohio. What do you think the school will do to help drive that conversation and that execution? I believe in centering everything that we do around the students. I'm a student-centered person and we wanna make sure that we continue to have a student-centered university. So my priority in all of this would be on the students to make sure that we have a safe environment for our students as well as our employees. And none of us could have imagined the impact of the COVID-19 pandemic. And the experts, I think, are learning more every day and they are discovering new discoveries as President Hammond has already stated. These are unprecedented times, so we really don't know. But as you're aware, Central State, like other institutions, moved its academic programs online this past semester. And I would say that based on my discussions and all, that we fully plan to be open in the fall. Our opportunity is to gauge our students and faculty to share how things worked with state officials to provide a perspective that may influence their planning and decisions. And we will be looking for guidance from the World Health Organization, the Center for Disease Control and the State and the local leadership and health officials. And this will actually help guide what we will do in the fall as well as in the summer, but more so in the fall and what that would look like. We'll, with the IRT committee, which is the Institutional Response Team, we are coming up with various kinds of scenarios because this pandemic is changing every day. But we will also take guidance in our discussions from the state and from the governor. But we're committed to being here for our students and equally committed in exploring the right solutions to continue our mission in educating our students. I have confidence in our state leadership and it is important that we stay aware and aligned and in lockstep with our state leadership as we gain a better understanding of what we're dealing with this pandemic. And as I stated, these are very unprecedented times. So we wanna look at best practices. We wanna look at what's happening around us as well as with other institutions and both best practices across the country. So we look forward to the fall, but we are still planning and discussing what that would look like. And just to echo what Dr. Thomas has said, again, the safety, the health and safety of all of our constituencies associated with Central State University is probably paramount to everything else. Let me focus on that real quick because one of the things that you guys mentioned to me before we even started recording is that one of the assets of this transition is that it's being done the way it's supposed to be. There's not a sudden retirement, a sudden departure, there's a planned exit and a plan entering into the seat. But do you think that because of this particular period where there's so many other stakeholders with whom you gotta talk, the governor, the health department, local and state, does that make the transition a little more complex because so much of what you would have wanted to get done in terms of arranging an executive team, in terms of organizing new strata of, what is our institutional spirit, is that different because there's so many people involved in the conversation now? And I would pose that to both of you. The transition really started the day that he was announced, that Dr. Thomas was announced, which was back in February. And of course, March hit with the pandemic. But we had a little time in transitioning prior to COVID-19. And it just sort of, the time that we spent together, the time that we talk on the phone, the time that we had the Zoom meetings to just sort of escalated because of this situation. And being able to introduce Dr. Thomas to the various stakeholders, the various committees, I think has probably just grown every day sometimes I'm always concerned that I'm giving him too much information or exposing him too quickly. But at the same time, he's a seasoned leader. And so he's able to receive and participate very fully. But absolutely COVID-19 was not on the transition agenda, but it is now and he certainly has adapted well and has been very participatory at all levels. And I would like to thank you, President Hammond, for those wonderful remarks and your kindness. I think that as President Hammond has stated, I think because I've been in various positions prior to coming to Central State and have served as president for eight years at another institution in all of the positions that I've held and experiences that I've had over my 30 years in our education, I think those have really helped me tremendously, particularly because I kind of find it sometimes kind of challenging because we're doing everything remotely and even in meeting the leadership team as well as talking with board members and those kinds of things. I think because of the experiences that I've had that has really, really helped. But at the same time, I think it has brought us very close together in a good and very healthy working relationship because we're all concerned about our students, we're concerned about our faculty and staff, and we're concerned about the university community. And again, we have to go back to health and wellness as well as safety. We're very passionate about that and we're passionate about our students, we're passionate about what we do and we're passionate about the mission of Central State University. And I think that really comes out in this, what I call the remoteness that we do in all of the meetings that we have, phone calls and Zoom meetings. I think that has really brought us closer together. And President Hammond and I, I'll just say this, we decided long ago that no matter what happens, we're gonna have a good transition and we're gonna have a good working relationship. And that we have had because in any transition, you're gonna have things to occur. But at the same time, what I really like about her is that we both, she'll pick up the phone and call me, while I pick up the phone and call her and you're not worrying me at all, but it just really helped me in this transition. To make things stronger and better. So I'm just excited about even this relationship with President Hammond, it's been great. See, Alpha's and AKAs didn't work well together. That's what I hear. All right. That's what I hear. That's what I hear. I will round out, I will round out. You have to go there. Absolutely, the AKAs take care of the brothers. I know that first hand. Absolutely. I will round out with these two questions, one for each of you. Dr. Thomas, if we had a preponderance of Central State families for incoming students and continuing students listening to this right now, what would you want them to know about the first year of your tenure and what, as we try to get back to normal, knowing that there's a new modus operandi for that. So what would you want those families to know that they, for as much as you can, could and should expect in the Thomas era, particularly starting with year one? I want the families and the students to know that we care in being a first generation college student. I know the needs of our students. We wanna make sure that students come to our university and that regardless of the pandemic, that these students will still get a quality and well-rounded education that is second to none, that we're gonna provide an outstanding education and that we are passionate, as a president, I'm passionate about what I do. I'm a people person. I'm reachable, I'm touchable, and we're here to serve and to make sure that the students who come to this university, we will put everything in place in terms of the various kinds of support that we have, the various kinds of academic programs that we have and that we would do all that in our power to make sure that these students, that the students are our priority. I go back to being a student-centered institution. Everything that we do is that, and every decision that we make is what the students best interest at heart, that they can get a quality and well-rounded education, and an education that means not just what they learn in the classroom, but those things that they learn outside of the classroom as well, and that we're going to provide a nurturing and safe environment for the students. And that's just from the first year here all the way through graduation and even as the alums of the university. And then Dr. Hammond, I would ask you as you embrace the new chapter and so much of your career and so much of your work, particularly in Ohio, has positioned you to be one of the mothers of our sector.  When you look back at the sector as a whole, what advice would you give HBCU presidents even with all this uncertainty? What is the number one thing that you think that we all ought to look out for or to be joyous about or to be concerned about? What is your piece of advice for the HBCU community as you walk away? And before I respond directly to that, I want to send a heartfelt congratulations to the class of 2020 of Central State University and all of the 2020 classes across this great nation. They have overcome, and that's what education provides. It provides them with a mechanism to learn that this is not the only mountain that they recline, but there will be other mountains that they know how to get over, around, or through that mountain if necessary. My response to other leadership in higher education is to be faithful to the cause. And the cause is quality academic assurances and to be faithful to the mission and the visions of your institutions. COVID-19 may change some of us in a way that may require us to look at things differently. That's okay, but we should always, and all leadership should always be faithful to the mission and the vision of higher education. And that is to uplift and to help young people, especially become changed ages, not just for themselves, but for their communities. Central State University has three tenets, service, protocol, and civility. And we believe that our universities, Central State University should be about service. And then secondly, understanding protocols as we never gate this very changing environment. And then thirdly, to act with respect and civility to ourselves and to everyone else around us, our families, and our institutions. So to summarize, stay true to the institutional mission and vision and act with service, protocol, and civility.


I was a prostitute. I would not shower for that day and I would take this stuff that's called blackout And it blacks out your teeth. It paints them black. So I have perfect teeth from having braces So I was like well, that's a I'll tell sign what hooker on the street has perfect teeth So I would black out teeth to make it look like I didn't have certain teeth Oh, wow, and it worked.  They're wearing next to nothing. No


Hi guys and welcome back to this video. So today I want to give a little cappella update and talk about some exciting things that are going on and talk about where I'm at with my Masters and the Flexpack program. So as many of you know, I'm a sponsored Flexpack student at Cappella University and I am currently getting my MSN in nursing education and guys, I feel like I'm in the final stretch I'm really like just have a couple classes left and I'm super stoked to be where I'm at. I feel like I'm learning a lot. I just wrote a couple papers on nursing technology and in specific low fidelity and high fidelity nursing simulations and their implications in nursing schools, how we can implement them, which was really cool and creative and it's just kind of a fun topic. I feel like a lot of the assignments that I'm doing are really pertain to what I'm interested in which is nursing education and is awesome. So I'm super stoked with where I'm at in my program right now. Also, I'm very excited to announce I am attending NTI 2019. It's the big critical care conference that's in Orlando. I will be there May 20th, 21st and 22nd and I will be speaking at the Cappella booth in the Expo Hall. So make sure you go check that out. I will have the times that I will be speaking down below. I will be touching on emotional intelligence and more specifically how to balance a healthy work life routine schedule which as you know, I'm a mom. I work. My husband works. We have a seven month old daughter. I run my social media business and I am getting my master's right now. So I am busy not to mention all the other stuff you have to do in life like buy groceries, brush your teeth, all those like, you know, important things have to do those as well. But I'm thankful for the FlexPath program because honestly, I tell everyone all the time it's been the least stressful thing I've added into my life because I just feel so in control of it. And I am the type of person that I like to feel in control of my life and what I'm doing. And I make lists. I have a routine. I have a schedule. And it's nice that I can schedule the FlexPath program all of my assignments into my life versus the other way around. And really quick, I just want to touch on three small things that you can do to help balance your work life routine when you are busy like I am. First, find something that only takes 10 minutes that makes you happy and do that every day. Whether that's drinking your cup of coffee, taking a shower, maybe doing your makeup or just going on a quick run, meditating, whatever you do, find that 10 minutes and just do it. We all have 10 minutes in the day to do something for ourselves. Next is give yourself grace to say no and don't feel guilty about it. We can't do everything. It's literally impossible to do everything. I am one that I want to take on so many things and I want to accomplish them all. But in order to be our best selves and put our best foot forward, we just can't do it all. I'd rather have a couple of things that I'm really good at and invest my time in than a bunch of things that I just can't put my full self into them and they don't turn out as well. And number three is talk to someone about your day and ask them about your day. I know this sounds kind of silly, but it's so important to have that kind of social balance in our lives. A lot of times, especially when you become a parent and you're working or in school, it's just like the constant motion of things and it's the same thing over and over and over.  But take a second, talk to someone in your life, whether it's someone that you know or maybe a stranger, ask them how their day is doing and then tell them about your day. Tell them about something that's exciting for you, something that may be bothering you. And it's going to make you feel good to relate to someone else in your life versus feeling kind of like you're just alone and caught up in the hustle and bustle of everything that's going on. So that is my Capella update. I'm so happy to be a sponsor FlexPass student. It really has been great in my life. I know I've said a million times, but you're going to pry here to a million more. So thank you for listening to me. Thank you for watching this video and I will see you in my next one. Bye.


We trust our homes to Schlag. With Schlag custom, homeowners and designers have a lot of flexibility. You can mix and match the door hardware. Take your front door, for example. You can have one finish on the exterior of your front door that matches the outside of your house. But on the inside of that same door, you can have a totally different finish that matches your closet and hallway doors. At any time, you can change your door hardware from a lever to a knob or function passage to a privacy locking door simply by adding the innovative locking pin.