 Welcome back. Hopefully, hopefully you can see this. We should be live now on the Reclaim workshop.ReclaimEd.Tech site. I'm going to go check us out just in case. I would do that. While confirming. Yeah. It's okay. That's just me. That's you. Okay. I don't see it live on the site. No. The ID is not. I didn't do something right with the thing. Oh, it's I didn't think I know what it did. Is it YouTube live? Yeah. That's that's what I made a mistake. I don't know. That is a live ID. So what the hell? I'm wondering if because I didn't schedule that session ID go down. Copy and take the session ID. Yep. And then cut it and then put it down in the ID below. Oh, right there. Oh, my gosh. There you go. Yep. I just did this wrong. Okay. So let people know in it's okay. We can kind of people will jump in in a second here. Perfect. But now if I repurchase the page, we got it. Okay. Target to live and we're good. We're live. Okay. Yeah. It's on the site now. The coffee. We did it. We did it everybody. All right. So jumping back into the discussion. We ended last session with asking the question to you all, what is domain of one's own, which sounds like such a simple question, but in fact, it can have many different answers. So I wanted to start first. Yeah. So I wanted to start first by highlighting some of those domain of one's own is a platform where all members of our community can create manage and explore different tools to develop their own unique digital presence. What a punch. That's amazing. Another one domain of one's own is a space to experiment and learn how the web works, how to think like the web and explore learning and publishing in a networked digital world. Very cool. I think it's important that we have some of these answers sort of, I don't know, bookmarked or put in our back pocket to be able to pull out when folks ask us. I know at Reclaim, we get these types of questions all the time. How would you talk about domain of one's own to a faculty member with no technical experience or when you're applying for funding for domains? How are you going to define usage and value for something like this? And so I think, you know, I'm definitely going to bookmark some of these answers because I think that's really great. I just brought in another one. This is from Matt. Domain of one's own is a space. Domain of one's own, unfortunately, has the most incomprehensible acronym, right? That little, oh, I come to love it. But when I first saw the acronym for domain of one's own, I was like, right? We weren't thinking about acronyms going out. But D O O O is a space where folks get to tinker and explore digital tools to develop their digital identity and ask critical questions. And I think, I don't know, I know for a lot of the folks here at Reclaim and me when we were first playing with C panel is that tinkering and playing with C panel and understanding how like subdomains work and domains work and file structures work on a server was my entree into instructional tech and to into a career. And I always thought it was one to one between domain of one's own being a space where if someone was interested and turned on by some of this stuff, they could understand, conceptualize and build out a world, whether it's for hobby, whether it's for professional reasons, whether it's for, you know, completely other reasons. And I still love that idea of the tinkering element of it, like it's a space where you can still play sandboxing was a big term we would use back in the day to talk about domain of one's own and RC panel accounts as ways to give faculty media wiki or WordPress or Drupal who couldn't get access to those tools in any other way in 2006, 2007. And so it was a powerful kind of way to allow faculty and staff to tinker to. So I like that matter a lot. It does resonate with the uses I have found. Just take another look in the chat. Because I know lots and lots of people Moe, I like Moe's Moe from Grinnell domain of one's own is a space to experiment and learn how the web works how to think like the web and to explore learning and publishing in a networked digital world. Let me see if I can bring that up as a I love how to think like the web that's awesome. Yeah, I love that. I think a lot about like the first time I realized how the connection between like folders and directories on a server and how that affects the URL. And that if you know how that works, it may sound very simple, but I think most people who use the web don't know how that works right and the fact that you can do things like have a site that's underneath another site like in a folder sense and what that does to the URL. And there's a lot of power in that sort of interoperability without a lot of necessarily like technical overhead, you know, like you don't need to have like a web developer make you a fancy site that a real common thing we see people do is have like an omega site that lives under a sub domain that in the main domain maybe has a WordPress site to show sort of showcase the project. And you can do that pretty easily you don't need to have like a custom theme or something developed for you, right? That that stuff is so cool, even just how URLs are, you know, reusable and interchangeable is itself kind of a revelation when you get your head around it. It was interesting along those that those lines is I was very talking with Boone or Gurgus who actually is someone who developed the open the open commons, the CUNY commons in a box, which is an open source commons project, which is amazing. Many of you out there already know it. And so we were talking just the other night because he's here in Chicago or close by in Chicago. And he was saying one of the things that he bemoans a bit is the fact that with the new development of WordPress and so much of the the themes and plugins maybe being JavaScript first with some of the block editor, the entry, the point for people to tinker and to kind of create becomes a bit higher. It's a little bit abstract. It was a little bit more extracted. And it's interesting just to think about this platform and what we were talking about with digital minimalism still provides that space to do a lot with HTML or HTML five, like there's still a lot of space to explore and build. And you know, that's one of the things we have to think about when we're providing these tools, like at what level are we going to get to deep in with trying to teach people JavaScript on fly or whatever like that's a different level of commitment, although people learn PHP enough just to get through. So it's interesting because that platform raises a whole bunch of technical questions to and, you know, something we have to deal with. So super interesting stuff. I like the low entry bar, by the way, because it's what I'm good at. Low, low entry. This is a little bit of a pivot, but just coming off of what you're saying about the technical ways that the main of one's own affords to its users. It makes me think about the technical, I guess, aspects of the system itself, just zooming out a level for how the whole thing works. Well, and even thinking right like the so the fact that, you know, I was mentioning how directories and things and were affect the URL, right? So in the case of domain of one's own, we have three systems that all kind of look like one to the end user. But we know that they are not secretly under the hood. And so that's kind of the first step here, right, is understanding what these three systems are and how they work together to make domain of one's own the way that it is. So in kind of this initial refresh before we jump, you know, into deeper dives for each of those systems, let's talk about what domain of one's own is made up of from a technical perspective. To start, I am sharing my screen from a domain of one's own admin landing page. This is state you dot org slash d o o dash admin. Maybe we can add that as a banner here. This is a landing page. You should see something very similar on your end for your institution. If you don't have a landing page, it's sort of sort of a one stop shop for login to these systems. We can definitely get that added for you. But I really love that this will sort of define the three systems in the context of domain of one's own. So WordPress is going to be your home page. It is where you're you're branding this this project for your community. It's where your users are authenticating with single sign on and logging in and signing up for an account. However, you have that workflow set up. We then have WHMCS, which is a little bit of a mouthful, we realize, but WHMCS is your record book. It serves two main purposes. So it's it's keeping a record of what's going on. But then it's also automatically provisioning cPanel in the background for you. So that's the main role. It's automatically creating cPanel and embedding it in the WordPress wrapper. And we'll come back to that wrapper in a minute. The third and final system of domain of one's own is WHM, which is your cPanel server. So it's what's storing the cPanels, it's what's customizing those cPanels, disk usage, cPanel icons, installatron applications, all that stuff is managed there. And this is also Reclaim Hosting's wheelhouse. So we give you the keys to the kingdom, but we don't expect you to manage this on your own. That's, you know, we're there to make sure that your server is performing well, and it's optimized to the best of your ability. And to that point, I'll also mention some of the other resources that we have available, including a status page, which allows you to very quickly check to see if there are any issues with your server. You can always reach out to us. This is at status.reclaimhosting.com. If you ever just want to quickly check to make sure your server is running smoothly. Other server or, I guess, options, support resources you have available, our support documentation is growing almost every day at this point. Our support team is phenomenal, and they're constantly writing new documentation. So not only will you have a lot of cPanel and application-based resources there, but we have a whole section dedicated for Domain of One's Own admins and minds. So everything that we're talking about today and tomorrow is likely documented. And if you have a question and you're looking for a more detailed how to step guide, it will likely be here, and we can help point you to the right place. We also have community forums at community.reclaimhosting.com currently. I will say I think we're kind of working through a little bit of a rebrand with community.reclaim is such great real estate, and I think it needs to, you know, as you need to. Yeah, I think that needs to be a landing space for all of the community resources, not just the forums. So that's kind of a goal for the future, I think. Yeah, because we have brought in new tools like Discord. We still use Twitter. We have the discourse forums, right? We have the guides. So there's events, exactly. So setting these up as a landing page, maybe not with the same layout as the Domain of One's Own landing page, but a similar concept of, hey, what are you looking for? It's all here. Whatever works for you, I think is the concept. And speaking of community, Taylor Jaden has just recently kind of put together a template for a community showcase site. So we have community support documentation templates, which I haven't linked to yet. But we are now playing with this idea of a showcase site too, which I think is really cool. Taylor, did you want to speak to that? Sure, yeah. So yeah, this site is kind of intended, particularly for folks who don't have one already, but someplace where you can showcase the work that your community is doing with Domain of One's Own, your school. And it occurred to me, this is something that most people want with Domain of One's Own, but it's especially hard to, when you're getting started, wrap your head around how you would do one of these things with a form and collecting submissions and things. So the idea with this is that you can just request the template if you don't have it already, or if you're a new Domain of One's Own school, it'll soon be just part of the setup. And basically, you can just install this WordPress template wherever you like it. In this case, we have it at stateu.org slash community. And it's already set up with gravity forms and a very simple form that just says, like, hey, tell us about your project. What's the URL? Please include a screenshot. And then you can customize it to make it work for you. In this case, you're seeing the, this is what you get out of the box. It's just a single test post and a banner just says Domain's Community. But you can obviously change the name of that and the color scheme and all that stuff. And the great thing is because it's built on gravity forms, while it's simple to start with, you can go a bunch of different directions with it. It's not limited to any particular theme or anything like that. And I really love that it gives the user permission to share their content. So it's not up to the admin to go around and pick out sites. And then you're kind of having those conversations. It's, you're giving the user the agency to make those decisions on their own. One of the things that I would, I could see admins doing with it is maybe soliciting like submissions to that once in a while. And you know, if you've got like a class that you know, or maybe you help fact the member with classes doing blogging, maybe you check in with that at the end of the year and go, is anyone want to submit things here? Or you could even email using and we'll show this later, but using like the bulk email tools and WHMCS, there's a lot of directions. I think you could, a lot of things you could make due to make this a useful part of your domain of one's own. And we'll hear more about gravity forms from Tom Orburn himself tomorrow. So that will be part of domains 201. I do think with what I refer to as the Holy Trinity of the domain of one's own setup is as Lauren pointed out, there's WordPress as the wrapper. There's WHMCS is kind of the middleware and account everything that's happened across the entire basically infrastructure by reporting what new accounts were added to WHM. And WHM is effectively your C panel server, right? That's what you pay for. We use WHMCS to automate the creation of accounts and WordPress sits on top of it and doing what a good open source tool will do. It allows us to leverage an open source community to get stuff like shibboleth plugins to allow us to kind of refactor WordPress. So you never know you're in WordPress unless you're an admin students and faculty and staff who are using it just log in there with their single sign on. And what is happening is a C panel account is embedded in a WordPress page. And that's the trick, right? Major kudos to Tim Owens and Martha Burdus for spending a lot of time at UMW kind of playing with this idea and fleshing it out. But it also points to the birth of domain of one's own as a kind of couple of ed techs imagining what's possible within C panel to bring it to a broader community. So I think what I love about domain of one's own and I probably always will is it's born of the work we're doing right now, right? It's kind of like here's what's possible. Here's how we can build it. Here's a series of tools that we're really bringing together, knitting together small pieces loosely joined and some not so small. I guess a server isn't a small piece, but you get the idea that we're tying together these tools or making them look like it's one big seamless system. But in fact, there's a lot of room to play. And then there's also some question with that that we'll talk about in the coming sessions. But I love it. I love the idea that it is a system born of the ed techs who built it. Yeah. Any final comments and discord or any final questions before we jump into a deeper dive into WordPress and I suppose C panel. I'll have to give them at least 30 seconds to hear that. But that's okay. We're capable of waiting sometimes. There are a bunch of links to all of the resources that Lauren and Taylor just talked about in the chat, by the way, a little bit of a link spam. But if you are curious and you want to take a look during the break or later today, that should all be available for you. Great. And I think with that, we'll catch questions in discord as they come in, but I think we're kind of up on time. So this is probably a good chance to end and switch gears for the next session. That's right, which will happen at the top of the hour. So we'll see you there. A five minute break and we'll see you soon. Bye everybody.