Podcast Episode 43: Episode 17: v5 Is Coming

Description

Learn about the v5 update and what's new with the core team.

Transcribed Content

This episode of Rockcast is brought to you by Rock partner Triumph Tech, a full service specialist partner. Rock partners provide crucial support for Spark Development Network and important services for the Rock community. Connect with Triumph Tech today at rockrms.com/partners. Welcome to the Rockcast Podcast. We are here today to give you an update on what's going on with Rock and we're really happy you've joined us. We have some exciting things to talk about. Let's first discuss what's going on with version five. Yeah. So version five is close. We have a lot of the features completed. There's just just one or two more features we wanna put the final touches on. But we are hoping to have, something to beta in the May time frame. So that's coming up pretty soon. So we're looking forward to that. Lots of of new features in that. We'll kinda talk about some of those features a little bit today, some of the stuff we've been working on. But definitely excited about that. I would say if you are a beta tester, , you might be planning on what what you're gonna be doing be able to do in in May to really help us get get through that. I think one of things we've talked about in the past is we really need to make sure that our beta program is going into more of the features and really doing a a deep testing. So we're be trying to really push that through on this update for this release. Good. John, can you remind us how we can become a beta tester if someone's listening to this and they're not a part of that already? Actually, that would be a good segment for Nick since he oversees that group. Yeah. I would, go to our connect page. Mhmm. There is an an item in there for beta testers, and there's also one for alpha testers, which is slightly different role. You need to have slightly different skills. But you just fill out that that form and we'll get notified. You'll be on added to the beta team. And as John mentioned, for v five, we are gonna change the beta program a bit. We're gonna ask you guys who are on the beta team to go through a little bit more formal formalized checklist. So you won't have to test everything, but we're looking for people to test certain sections of the system and then probably add other items that we haven't really added to that list yet. But we'll have more news on that at the next podcast. Podcast. Great. Speaking of more news, we know you've been waiting a long time to have some updates on the conference this year, and it's finally time. So registration is live now. And if you sign up today, you will be able to go to Rx twenty sixteen at Bel Air Church in Los Angeles, California, and join the rest of the Rock community on August for the early bird pricing of $3.49. Now that early bird pricing is only available through June 20, you don't want to delay too long. Get those budget things in order, get your approvals in place, because the price does increase starting June 21. It will go up to $399 Again, lock that in early for your early bird pricing before June 20 at $349 We're really looking forward to bringing the Rock community together for the second time this year and already have a great feeling. Lot of people are commenting. One of the things this year that we want to do a little differently, if you joined us last year, is we are really looking for the community to come together and share their lessons learned, best practices. We feel that's the best way for us to grow together and learn together. So if you're listening and you have, experience with Rock, you've been working on implementing it at your organization, you're running live on it now, we'd love to hear from you, and we would be very interested in your speaking at the conference this year. Reach out to us, let us know. If you, feel you have some topics you could speak about, send us a couple bullet points on what you think those might be, and we'd love to work you into the schedule. We're very excited to help the community learn from each other this year and to hear what you have to say too. We are looking forward to hearing from you on that, and we want to share with you some things that we've been working on. We have some projects, we know that you don't always get an update on what that looks behind the scenes, so we'll pull that curtain back for you a little bit here today. Sounds great. David, why don't you go first? Sure. Something we've been working on is another giving gateway, NMI. Mean, with our philosophy with Rock, we just want to have a lot of different options, especially when it comes to giving. And one of the things with NMI that lets us do is really take off some of that PCI compliance. It lets us do a kind of a redirected post back to the gateway without ever having sensitive data touch your server. So that's a nice feature of that gateway and that will be available with v five. Awesome. There's another new feature coming in version five that we're calling Family Analytics. So what that does is it allows you to collect some interesting metrics about your attendees and members. One of the metrics is something that we've we created years and years ago called ERA, which is stands for estimated regular attender. The e is critical. I mean, it's estimated. We we can't know exactly the the attendance patterns of every person in your church, oftentimes because they don't check-in and they don't give. So we use the data that we do have to create an estimate, and so we've baked in a recipe for that, and that will automatically calculate for you. It also gives you more attributes about their first attendance or last attendance, their first gift or last gift, and even their participation in certain group types. So that's a really cool way of of gathering this kind of complex stuff in a very simple way. And it's really just the beginning of what we hope to add in terms of being able to have analytics about people. So pretty excited about that. Just put the finishing touches on that as documented now in the v five docs. So really interested about rolling that out. Is that something you could give us an example of maybe a couple things you could do with that information once you have that in hand? Yeah. And we really spent a lot time in the documentation focusing on, , how this data should be used. Because I think with any data, it can be used in a very positive way, but it can often be used in a very almost negative way. And I don't think that's such a problem in the church, but in sometimes it can be. One of the things that we did when we when we did this feature is we had to pick an icon a lot of the features do in in Rock. We had pick a font awesome icon. And for this one, we really picked a shield because that's really kinda what we wanna show is that this is a way of of protecting people in a way for you to have ministry moments with them. It's not big brother watching over you. Oh, you change this, we change that. Let's, , let's attack. , that's exactly what we don't want. So for instance, ERA is a is a a dual faceted metric. So there's a facet for how you become an ERA. So you have to give or attend a certain number of times. And then then the other facet is when do you stop being an ERA? So again, there's a different set of criteria of where you have to stop giving or and stop attending for that to happen. So if you if you have this pretty regular attendance and all of sudden that those change, that should probably, , be flagged and someone should probably reach out to you. I mean, that that's something's going on in your life. , either you perhaps have lost favor with the church or something's happened in your life, maybe a life event a divorce or a job change or or some other things that could happen and all of that warrants as as if if we are supposed to be pastoring people, all those warrants some kind of touch point. So this really indicating that there's an opportunity for ministry. Right. And I think in today's churches, it's they get we get bigger and bigger and bigger, plus just the nature of how I think society works is we're becoming less and less connected to people in the church. And there's so many more people who are just not connected at all. And we have access to some of the state, and we're just trying to present it up to the church staffs and lay leaders to say, Hey, here's some opportunities and maybe touch points. Now, all that touch points are bad. For instance, if someone's not giving, but they have attendance or children are checking in, and maybe they have high schoolers, and now the high schoolers went off to college, and that only source of us knowing that they still attended has now stopped. So you're gonna stop being an ERA. You might still be coming. Right? But we're gonna flag you as not being an ERA anymore. But even in that touch point, a pretty significant life event happened. Right? , your kids left Right. To go to college. Of the nesters. Right. Or they even if they're still living at home, which happens a lot. , there's still something there that you can make a touch point with. Now in all of this, you never wanna make an accusatory touch point. Hey. I noticed you stopped. That's exactly what you don't want to do. But you want to reach out in a very general way of saying, Hey, I just want to touch base. I want to reach out to you guys, see how things are going. And we found that it really has created a lot cool experiences and cool stories. And honestly, that's what the church is supposed to do. Right? We're supposed to be shepherding. Consider this twenty first century sheep management. It's warning you that, hey, perhaps the sheep is out of the corral. Let's go find them and make sure they're okay. Mean, even if there's something wrong with they just have a disagreement with the church, it's still a good touch point that you at least know about that. And you can make sure that they get into another church. But there's no reason that if those criteria shift, that they had this attendance pattern, and now they don't, there's no reason that you should not reach out to them and find out at least what's going on. Right. And show you care. Right. And that's just one example of some of the analytics that are in there. But there's more in there in V5, but there'll be even more in the future. And we'll start working on ways that we can start exposing some of these things in different ways. , right now, my biggest concern is , let's get in there. Let's start getting this data. Because it takes, , the more data you have over time, historical data, the more powerful it is. So, let's get it in there. Let's give you some features today. There's some badges. There's workflows that can get launched when you stop becoming an ERA or if you start becoming an ERA. And I think a lot of times we always focus on the exiting of an ERA, but entering an ERA is actually a pretty significant thing too. I remember when I was just starting out as a Christian, I started giving a little bit. And I have to say, it was a little bit. Looking back, I thought it was a lot. I was expecting a note from the pastor. But I didn't get one. And again, was immature in my faith and that's why I was expecting, grew up, you threw a dollar in the plate. That was what you did. So when I was throwing $20 in the plate, I'm thinking I'm a saint. Again, that's very immature. But this allows you to actually reach out and say, hey, again, you don't wanna say, hey, thanks for starting to attend. They might've been attending for a long time. They just weren't doing anything. But it gives you a touch point because something changed. Mhmm. Something dramatically changed. It could even be that they had a baby, and that's the only reason why they became an ERA. But again, something changed. It gives you an ability to reach out to them and and have that showing that you care. Because honestly, if someone had said something to me back then, that would have meant a lot to me. Mhmm. Even though it was immature and the wrong thinking, it would have meant something to me. So now that how immature I am, we should probably move on from that. So about some of the check-in changes or Sure. We are V5's going to have really just an alternate way of using check-in too if you choose to. The old, , the current way will work the same way it has, but we're adding a new method to kind of streamline kids being checked in or your family, , if you have more than one child rather than having to go through each one individually picking the child, the room, the service, you'll be presented with all your children or all the kids that you can check-in and you can select them all at once and move forward that way, doing it as a group. If there's only one option, one room for them and one service, it's just a matter of checking your two or three kids and then you're done and the labels print. But after installing V5, will change. You have to enable that. Right. Okay. And I think we're also trying to make the configuration of check-in a little bit easier. Yeah. To try and streamline that. It does get a little complex the way we have it now. We're hoping to do just if it's a kind of a simple configuration or provide a simple configuration for those scenarios where you don't have a lot of different rooms for the same age group and things that. Yeah. That's great. I mean, we've kind of talked about in the past too how we're trying to circle the globe with getting all the features in there and then keep polishing and adding new features too. But I think this is the start of going around the globe. Yeah. I mean, eventually, vision is to make checking even simpler for very small churches. I think the first time around the globe, we're trying to add all the power. Now we can come back and and simplify a little bit. So we also have talked a lot about the dynamic compiling of Les files on Rock. Still working on that. It's pretty much done. I'm planning on pushing it into develop probably on Tuesday. I've just been working on the documentation. I find that writing documentation sometimes the best form of testing. So I just want to make sure that I get that done. But I'm hoping to get that completed this weekend. And is that a feature, John, also that you'd have to enable on each theme? By default, will they all be not set to compile? By default, they all set will be to compile. You can disable that if you and that will be documented. But we think there's just a lot of benefit to having it compile so that when you do updates, when you add when block developers put things in the store, they can assume that their less has the ability to be compiled in. I think so. I think there's a lot of benefits to it. You can still compile locally if you want and push up your CSS. I don't see why you'd want to do that. It almost seems a benefit. But if you write a custom theme and you're just , what, I want to handle all the compiling, there's a file you can put in your theme and it'll keep it from being compiled. So but you can opt out of it if you if you . But with that also comes some features of being able to manage the themes on the server. So a lot times we say, hey, if you wanna start a new theme, , go out there, grab Stark, copy it, put it back up. You can now just clone the theme right on the server. You can say, go to Stark, say, clone this theme, give me a call this. And now you can, , go from there. There's also the ability to have some styling options on themes. So assuming the theme developer creates these styling hooks into their theme, you can actually change colors right from the GUI and pick the color you want. It's all dependent upon the theme developer to do that. But we definitely have provided that for the Rock theme, the stark theme, and to some extent, the flat theme. This is just the the start of what we wanna do. There's some other features we wanna add to that styling in the future. So especially for, , check-in themes, you can really start getting in there and changing your check-in theme just by, , clicking images and stuff that. That's coming in probably v six. And would the hooks in the documentation for those things for theme designers, would that be in the creating websites guide? Yeah. In fact, all of the documentation on this last topic will be in the website guide. So from a theme developer, you it I wouldn't say it's complex, but there's a lot of little little, , hooks you can do. And so we're gonna do our best to document as many of those as we can. But as you guys have questions on it, theme developers, , please ask because it it might be something that, , we didn't document clearly or maybe forgot to document. So if you see something being done in the Rock themes and you can't figure out how it's done by the documentation, let us know. , a lot of the time things we work on are core, but a lot of things aren't core. So just the consulting that we've talked about that kind of helps pay the bills. So we've been doing a lot of that with Newspring and with CCV and with a few others. So I've been working on some metrics and some steps with CCV. And, , Dave and I have both been working on some stuff for NewSpring, which is pretty cool. I think, , some of that is very custom, but a lot of it is. And and actually some of these that we're gonna be talking about coming up here are are in core but came out of consulting. And actually, , just to kinda back up, the the whole family analytics was came out of the consulting. That was something that Central Christian wanted and helped us get into core. So it was kinda killing two birds with one stone. They wanted it, but they were also gracious enough to to allow us to put it into core. So the consulting actually is having a a positive effect on on CORE, but we still want to get to the point where 100% of our time is doing that kind of stuff. So let's see. So there's also some registration enhancements that we've been working on that you'll see in V5. Payment reminders is one that a lot of people have been wanting. I think it's pretty cool. Even in V4, it's so easy to go back and make additional payment on registration that you owe money for. But now we provide some really rich tools to remind people that they owe money. Because the ability to do it is one thing, but the ability to easily get back to doing it and have a one click link into it is another. So there's a lot of features and capabilities on payment reminders. We've also made registration instances more powerful. A lot of times, some of the feedback we're getting back was that people the templates and instance separation of concerns, but that they're finding that they're having to create too many templates because the costs were just different for each instance, which would and before requires a different template. But we've actually added the ability to change some of that on the instances. So now you don't have to create as many templates. And I think we'll continue to add more and more capabilities in that vein in v six and seven. So we're always trying to polish up the registration. But there's a lot of new little features in the registration I think you're going to . One of those other features is group filler. So a lot of times when you finish the registration, you're not done yet. there's still work to be done. you have a camp or maybe a youth sports team. You still need to fill up sub teams for each counselor might have a team or each team who is a sports team will have a team. There's now a really cool group filler that can take all the registrants off of a registration and help you move them into a series of groups. And it's pretty cool. , it's very easy and very quick. Lots of other small changes to registration. But another thing that we finished up recently is a change to the caching engine in Rock. So the caching engine today is very fast, it's very powerful, but it is not cluster friendly. So if you were to run Rock on two different servers, same one church, one database, two different web servers or application servers, it's not super friendly. Because if you change some security settings on one server, you're on the interface in there and you're changing some security settings, that gets changed into a local cache of of that server. The the second server, server b, has no idea that those security things changed. It's in the database fine, but that server b's cache is still stale and it doesn't have those. And a few people who have tried to run Rock as a cluster have found that to be an issue, which it certainly is. So what we did is we've made Rock's caching cluster friendly. And the way we did that is, each server is still gonna have their own local cache, their own local memory cache. It's just so much faster than having to read across a wire to get their caching information. So they'll keep their local memory cache, but we've added this ability to have a a Redis cache that's separate from any one of those servers that's just basically listening there. And when you enable these features, each server, when they start working with the cache, will tell this third party, hey. I, flushed this piece. Everybody else should flush it too. So the best way to think about it is kinda a chat room for for Rock's caching engine. And all the servers join the chat room. And as they do stuff to their local caches, they're just gonna tell everybody in the chat room. They don't have to know who's in there. They're just gonna broadcast to the chat room. Hey. I did this. You should do it too. And that's exactly, what that does. So it's pretty cool. I think it will definitely expand, the scalability of Rock to large deploys. Smaller churches definitely don't need to worry about this. Working on the project Redis is pretty cool. , I've always heard about it. I've always, , read that how people use it, but actually getting to use it, for real in a real project was kinda fun. It's definitely something we'll probably expand how we use Redis in the future. But it'll always be an optional thing. We'll never we'll never make a feature that requires you to have, , Redis. It'll always be an enhancement type thing. So we don't want to rule out features for a lot of the smaller churches, and, , having Redis and needing Redis is definitely something we don't want to require, but it is. It is pretty cool. Anything else you wanna add, David? No? No. I think we have one thing that never gets attention is just all the minor tweaks and fixes that we do. As we hear stuff in the community, , lot of times we'll just go fix things right then and there. Even things aren't necessarily broken, but just , oh, that could be easier. I think people would be surprised how much time a lot of that stuff takes. Right. And they're not always tied to an issue. Sometimes you just go fix it. So the commit log probably is the best indication if Yeah. If you're interested in looking at the commits. I'm surprised when people watch that on the Slack channel, the develop channel, but you get a lot out of that. , in fact, we get a lot out of that too because sometimes people find things that maybe we haven't thought about. Yep. So, yeah, I would definitely pay attention to that. And sometimes you might even see we're kinda quiet about it. We'll see someone talking about something in the Slack community. We'll actually just go fix it in there, and it'll be ready in b six. Or I often sometimes I'll see people talking about a feature in Slack, and I'm , oh, come on. That's documented. So I'll go look in the documentation , yeah. It's documented. That's that's their I can see how unclear it is by looking at their question, and I'll just polish up the documentation while I'm in there. So, , we're watching. We're polishing things as we see it. But that does take time. I and I wish well, maybe we'll try to do on a podcast before v five where we'll go over almost every single micro feature, albeit quickly. Yeah. There's a lot. I mean, just working with NewSpring and CCV, getting them up in production. We've done a lot of things since v four. But some things that may not have a big huge name tag for a feature, but just a lot of little improvements. Bone Central has done a lot of that stuff too. A lot of of you might call them a micro polish, but those add up and those mean a lot. , I think that really makes a product feel Yeah. It's it's robust and and mature. And if you'd to be a part of that conversation on Slack, you can do that too. Rockrms.com/slack. You can get your invitation there. We gotta get over 200. , the one nine nine six six. We're getting there. There's no reason why we shouldn't be over 200 in a day. And a caveat, you do not have to be a developer. In fact, most of the people on that channel are not developers. They're learning together. Great conversations happening there. So don't feel intimidated by who is this crowd I'm joining. You can get in there, ask the questions you need to have answered, and it's an awesome community feel. Yeah. And I would say most people aren't aren't the developers, but think there is that perception , you should be, but I would say most people aren't. And and I think some of the best conversations come around topics that are not programming. In fact, most of them aren't programming. There's more , how do I do this? Yeah. So that's a great list of some of the bigger things that we're working on. We've talked that there are a lot of smaller ones out there, but I just want to reiterate something that you said a little earlier, John, is that we're still spending a lot of time working on consulting versus core. Just imagine if we had a greater percentage of time that could be devoted to core work and documentation and work with the community, how, how many more features we could bring to you, how much more polish we could give. And, trust me, there's no end to the ideas and all the good things that could be done. There's really just an end to the amount of time we can commit right now because of our funding. First of all, I want to say thank you to the many personal donors that have stepped up recently with small donations personally from our Rock community. We're so thankful for you, and your commitment means a lot to us. We do still need the churches that are using Rock and that are finding benefit from it to step up, join the community. We're trying to give you as much as we can, and that's a two way street for Rock to be successful. It's a full ecosystem, and we need you to invest in it as well. So if you're a part of a church that is using Rock, we'd encourage you to go to your leadership and say, hey. This is something that's doing big things for the church. This is going to change the way churches and ministries are able to impact people, and we're a part of it. So let's let's, participate. If you need an invoice to make that happen, you can go to our donate page and create an invoice. A lot of organizations need that, and that sometimes we found is the one block that we have between knowing that we need to invest in Rock and being able to do it is just a piece of paper for the accounting department. So you'll find that there if you need it. So just wanted to pop that in there as well. I think that's a surprising thing is I never would have considered that people would personally donate to write. I know. And I think that first of it's humbling. It is. They believe in it so much. And every time that happens, it's just , wow. That's amazing. But I think think it's another message to to to churches that there's no church using Rock that can't afford to give something. , if if people can afford to give out of their own pockets That's right. They can afford I mean, it doesn't have to be a lot. , $20. If that's all you can afford, that's great. Know? But many churches can afford a lot more than that. And there probably is a misperception there too that if I'm not writing a huge check right now, it's not gonna make a difference. It is gonna make a difference. Right now, what we really need are recurring monthly donations. So a donation that your church can afford on a monthly basis that you'll commit to, we know then how much time we can commit to the features that we wanna bring to you, and ultimately, how quickly we can release the new versions. So it is all tied in together. Yep. So it's kind of a lead into to, , , just how are things going in general, and I think things are going really well. One of interesting things, , as you work on the projects week after week after week is just , what's the pulse? Yeah. And, , I think the pulse is going really well. But I mean, we so look forward to the day where we're just working on core stuff. And, , someone was asking me the other day, , well, how's everything going? It's , oh, it's going good. But, , we're getting tired, , because it's basically working two jobs. One pays, one doesn't. But I think more than more than being tired, because we're kinda used to that, is it's so hard when we can see the vision of where you wanna go and what needs to be done and what you have to have to be successful, , and what these churches really need. You you can see the vision but you it's frustrating when you can't devote as much time as you need to to to get that vision seen, , pushed through. So, one of the things that's been really eye opening for me is I've had the opportunity and I really can't think of it as an opportunity, to volunteer for a church who's small. And they're just starting to get a church management system. And it's so interesting to see the product through their eyes. And honestly, I see the deficiencies. Not necessarily in technology or in the sense of what we think of as the product, but in terms of how , I think we're we're kinda missing the boat in some areas in terms of, , processes and how how does someone approach this? Because I think when they come in their mind with they with what they need and what we give them are two different things. , we're giving them a great technology with good documentation. That's not gonna say what they need. They need to understand, , okay, why would I do this? And how do I have these processes? And what should I document on their side? And it's interesting to see that disconnect because, I think so many times we just say, okay. Well, yeah, here's exactly what you need and boom. And I think there's a, , there's a difference there. And it and some of the training that we have always had a vision to do, , video based training and and honestly, there's just not time right now for that. We're we actively do work on, , ideas and brainstorming that, , what training topics need to be done, and and we're creating, , a kind of an outline for video training. So we are we are working on it, but, not to a level that we'd to. That's definitely one of those projects that's has to be on hold until we have the ability to put more time into into the core. Yeah. Or it's on the slow churn. ? It's but I think in in some cases, it's God's timing because I think being able to volunteer for a small church who's just doing this is giving me ideas , oh, wow. , I think if we had done it, , even, , a few months ago, it would have been We would have had a different perspective. Yeah. Yeah. Perspective has totally changed. So I think that's one of the angsts is just , okay, , do you see the vision where you need to go, where it needs to be done? Or even some of these core features that we really, really, really, really wanna work on. It's , okay, well, , it's got to sit on that, put that on the shelf. And another thing that's just driving me nuts too, is the power I'm sorry, I'm just going off. The power that's sitting inside of the database that we and then now there's some great tools to be able to extract it and and do some real, , , dashboarding with. , Power BI is blowing me away. , there's some seriously cool stuff there. And we're playing with it, we're helping, , a couple churches with it. But, man, if we just had more time to devote to that, to create recipes for you guys to be able to easily do it yourself, it just kills me because, , that is a pot of gold. And every month, they're just improving it. And every month, it gets more and more exciting. There's some stuff that came out in the last, in this last week, which is really cool. Microsoft just had a whole conference about Power BI last week. And this week, they did build, which is a different conference, but they're talking about Power BI too. This is crazy. , that's the kind of stuff you guys really, really need to get your your hands on. And I think if we can help make that easy by showing you and providing a few quick tools, it would totally, , , jettison you up into the stratosphere of what you could do. So can I expect to see a session on Power BI at Rx two thousand sixteen for you, John? Maybe. I mean, it's I I can show some stuff, but I just know what the vision of what wanna do in that presentation. I I feel I don't have time to to to get all of the stuff that I'd wanna show, , lined up. So it'd be a teaser. I mean, I could do something quick. , we've already done some work in it. But I guess it's a hard time because I know what I want to show, and I know what it would take to to get there. And I there's just no time. ? You always say, okay. I'll do it I'll do it, , tomorrow night or on the weekend. And then by the time the weekend comes, you're , okay. Yeah. But I still have to document this, and I have to do that. And the documentation list actually for Rock v five is building fast. , it's a pretty long list. And, I mean, a documentation takes a lot of time to make. I was working on something this the other day, redocumenting one small feature. They ended up having to make this huge screenshot again that had literally 17 callouts. And so, okay. So three hours later, I'm done. I'm , yay. Oops. I'm not kidding you. Two days later, we add a new feature to that page, and I'm in there redoing it. Ouch. Yeah. So it just takes a lot a lot of time. But it's so it's needed, and it has to be done. So just gotta do it. So that is some serious behind the curtain that we just heard there. Yeah. And documentation is It is. I mean, you work in that too. I mean, it's very technical, all the different things you got to get lined up right for the tools that kick in and do their thing to highlight when things change. It's tedious, but we put the work into it because, well, you're here with us on the podcast and this is where you can hear from the team what's going on. This is where you can catch the vision and see through our eyes what Rock could be, what the community can look , and it's exciting. But don't forget, if you're new to Rock or if you've been using it for a long time, the documentation is where you get done what you need to get done in Rock. So if you are just starting out, you have to dive into the documentation. You can't be successful without it. And that's why we invest in it the way we do. It's essential to what you're doing. And if you've been with Rock for a while, don't forget about the documentation. It changes as the product changes, and there may be things in there, features you didn't use originally that now you're moving toward. That documentation is going to be the difference in many cases between success and wondering exactly why it's not working the way you think you think it should. So don't forget about the documentation. It seems , it may not be as as big of a deal, as as we know it is. So that it's essential. When we look at the page views on the documentation recently, and I was actually blown away by how many page views they they they get. I was I had a , you always have that kinda, , gut feel with and then you run the SQL statement, and you're , woah. , sometimes when you do that, sometimes things are a lot lower than you thought. Sometimes they're a lot higher. This was a lot higher. And I was , that's pretty cool. I I kinda , I see people, , on the site looking at documentation because we can kinda see who's active in the Rock, and and that's cool. But when you actually see that number, it's a huge number. And and you said, rereading it is important. , on the Lava documentation, I find it's funny how much I forget is possible. And so I go in there and , oh, yeah. I think I documented it. I think I even wrote that filter, I forgot the suggestion. That's true. And if you find that you're confused by something in the documentation because it doesn't seem to be laid out in a way that makes sense. There is an ability to send a suggestion for documentation update right there on that page and in that section. Just say, Hey, I'm not sure this is clear, or, This grammar is incorrect. It happens sometimes. Let us know. We make changes on that constantly. Or you might have figured out how to really do something and it should be in the documentation. Right. I find that again, I'm checking , oh, that's documented. And I go and check, and yeah, not really. And we just had someone make a suggestion. , it took me coming through three documents before I found out where this was located. It makes sense to me that if I need that feature, interpreted, I would find it in this other documentation. We put in some links in the other documents that made sense. So that kind of thing helps us and helps you. Let us know. Actually, reminds me. Gotta document what is bulk email, how that checkbox gets Mhmm. Mhmm. Because, , conversation on Slack. I was just the whole time, I'm, , going, okay. And that that was actually an example. , I think that's documented. I looked no. It's not. And now I'm, ugh. It's documented in the code. Yeah. Features don't exist until they're documented. Right. It doesn't exist until they're documented. So, yeah, we gotta get that in there too because that's just a negative of wisdom that just needs to be there so that So you don't have to look at code. Right. And again, the documentation is not gonna be perfect, but when we find a new discovery, should be documented for the next generation of people. Good stuff. How about we close in prayer? Father, thank you so much for everything you've provided this team. The list would go on all day if we just itemized so all the details, but the team, the community, the funding, those are the big three. Lord, we also thank you for the protection that you've given this team from hostile takeovers or un hostile attempts, but we're just thankful that you keep those temptations away. And we look forward to more protection in the future. Lord, we're also thankful for the successes and the rollouts that have happened over the past month. And thank you for the knowledge that you're bringing those teams into the community. And Lord, we just ask that you'd continue to bring the right people and organizations and teams into the community. And also some the funding to finish out the year and bring us to our goals so that we can all work in the way that we want to. We just ask for these things in your son's name. Do a church that loves the idea of using Rock but hasn't taken that leap yet? With managed hosting, churches of any size can get access to Rock's amazing technology, hassle free. With just one click, Rock's managed hosting removes the roadblocks that might stop a church from switching to Rock by making the process simple. Churches get the ease of a SaaS church management system without losing any of Rock's powerful features. Are you ready to take the next step or share with another local church? Visit rockrms.com/hosting today.