 So we're here and we've changed the name of the session slightly because yeah, we've been calling this effort fedora websites 3.0 and that usually ends up with a lot of Blockchain jokes and this is nothing to do with blockchain. So we're going to call it fedora websites 2022 in the the old fedora websites tradition where we'll name every revamp off the year it started. So let me get in the right window here. So what is this talk about and what is it not about. We're talking about fedora websites. We're not talking about applications like say moat or I don't know that infrastructure apps like say We're talking about the websites. So like the fedora website, the flock website, start that fedora project at org. That's sort of like the space we're talking about. Okay, so like what is the point of the website. The point of fedora's website is to share our story. It's our main front door to the world. Anybody who is interested in learning more about fedora anybody's interested in downloading and using fedora joining our community. That's the front door that they've got to go through. Right. And that is our opportunity to tell our story. Now we've been telling a lot of different stories from all the different aspects of fedora and we're trying to come to sort of a unified strategy that Matthew talked about in his state of fedora talk this morning. Right. So once we have the story and we agree on it, we have to tell it to people. So I have this model. I posted it a while back and like the fedora community blog. But this is what I call the conceptual model for the fedora project. Right. So this is not to do with like the community and the people. This is to do with what we deliver. And I would say like a lot of our users based on Matthew's state of fedora talk are here. But we're getting more users here where they're deploying fedora IoT and we're getting more users. Well, we've always had users here and the server space too. But the idea is you start, you know, the doorway you start using fedora as a workstation. And what we want to happen is for people as they use fedora as a workstation, that we make it very easy to pick up the best to breed open source tech for development. So you never have to become a developer. We're not only focusing on developers, but we want to enable developers who are using fedora to develop the open source way. And we have a specific prescription for which technologies we think are the best that we're behind that we deploy by default. Like for example, you know, we'd like people using podman to create containers. So why don't we make it so it's very easy and seamless to use podman once you're using fedora, right. Okay. So this is the community side of it, right. And this shouldn't be new to you really, right. So the first thing is fedora is the community. If you say fedora, a naked fedora will call it, you're referring to the community. If you're referring to the actual what we produce, what we ship, what we give to people, that's fedora Linux, it's an OS, or it's the addition fedora workstation fedora iot, etc. And then the other half of this of course is the fedora projects vision, which is, you know, everyone benefiting from free and open source software. That's why we're all here. We want open source and free software to win. We want everybody to benefit from it. And we want that built by inclusive welcoming and open minded communities. That is a key part of our structure as well. Okay, so we have the story. Great. Awesome. How do we tell the story. So I'm just going to walk you through like a speed run to the websites history and sadly I've been a part of it since the beginning pretty much. So don't ask me how old I am, but this is going to be like a speed run right so we started out this was like 2004 2005, just a dump of links. Then we set up a moin moin wiki. And that was our website a moin moin wiki got slow, got a bit disorganized and chaotic. Okay, all right. So then we kind of, you know, we got complex and then we simplified again. This was the website and you may actually like I got a 404 message this morning that use this template. Well, it's from 2007. This was just a simple static website. It was like three or four pages that started us three pages and went to four pages. Okay, so, but that was a little too simple, right. So then this was like our first real website, like felt real. It had like these these sections like we interviewed this was before how do you fedora that interview series. We would interview for our users and ask them how they would use it and, you know, ask them what their favorite apps were. We had little suggested activities and stuff like that. So this one was like host a photo booth party using cheese and fedora that was whatever, maybe a cheesy idea. And then we also had sort of an open source principle section where we would talk about the four f's of Fedora. It was great, right. All of that content was written when the website was first rolled out in 2010, and then it sat and it never got updated and do you know why. Because number one, there was no CMS. Number two, to actually modify that content, you had to be like, I think at the time we were using get it might have been subversion, but in either case, you had to have a skill set that doesn't normally mesh too well with people who are very good at writing content like this. So it just sat and it went stale by the time we had to update it. That was part of the fedora next initiative that Matthew also mentioned this morning where we decided we're not just shipping one fedora. We're shipping multiple fedoras and they're fit for different purposes. So, you know, this design was focused on one single thing. It didn't have that in mind. So with that in the stale content, we decided I will just start from scratch again. And that's, you know, the last generation before our current one where here we focus so much on the additions. The actual front page was just like a splash you clicked through. It wasn't a place you spent time. And this was part of a larger strategy which I'll talk about where we were trying to separate user oriented content from contributor oriented content. And this is part of that strategy. So this idea was here. This is like the front door when you come to Fedora as a user. And we didn't want to put pressure on you. You don't have to become a contributor. We just want you to use it. Please just use it. And then once you're a contributor, you have like all these different places you can go. And the split was not just user contributor. The split was these are the Fedora additions we want you to focus on. And then these are sort of the emerging or community maintained modifications on Fedora like spins, things like that. And these are part of our ecosystem too. But there was a split between those two things because we didn't want the users to start using a random spin and think it had the same level of support as an addition when it didn't, if that makes sense. So there was like these two splits we'll talk about a little bit later. And then this is today's Fedora website. And as I can share the slides like all of these I have I did dumpster diving will not dumpster diving but you know what I mean I went into old mailman archives on hyper kitty and I dug up all the old discussions and mock ups for everything and there's links here. You could waste a lot of time exploring that stuff. But so this is like today's website and you can see it's focused on the additions. It brings in a little bit closer some of the extra downloads like these spins and labs and alternative download sites I don't even think were mentioned on the first brochure style website that we had talked about as the previous version to this. And part of this was this was an effort by Ryan and Ricky to sort of revive the website make it static a static content website like a statically built website so it was very fast it was less security issues less performance issues. And it's great. But it's still part of that split between the community and the users and between the additions and the rest that Fedora has to offer. So these are some of the mock ups of the new website that Fedora 2022 website that we're working on. And what you'll see places throughout the mock ups when you examine them and there's detailed descriptions and feedback loops about them in the discourse so if you just look up Fedora revamp website you'll find them all. We're trying to integrate the community up up ramps I don't know what to call it so taking people from being users and sort of guiding them gently into how they can be contributors. There's things like when you go to the download page it suggests hey, you know, we see you're downloading with no clippy, you know, why don't you try downloading the beta and then test it for us and then submit this form and let us know how it went become a contributor so we have all these little on ramps that are embedded contextually throughout the site. So clippy maybe a beefy it would be nice to have a little beefy but anyway, yeah. So, just an overview. This is sort of what came out of this whole history, right, like we need something that's performant and secure, like running your website with moin moin behind it, not a great idea. It needs to be managed it needs to be accessible to people generating the content they need to be able to not be an uber kernel hacker to be able to contribute and maintain content sorry but that's how it has to be. It has to be fun to contribute to. You shouldn't have to learn a new new exotic unique custom stack, just to change some minor thing on a webpage, we should be using modern web tech that everybody has familiarity with right. And then it has to be flexible and expandable so that was like the problem with our first real website. It was oriented towards one fedora deliverable so when we decided to change our strategy and have multiple additions. Oops, it didn't account for that and the way it was built didn't allow us to just graph that on. So these are sort of the four things I think that we've learned. And then we also have this other issue of the split right so we split additions versus the rest of fedora. Why aren't they more together why can't I find them all in one place why do I have to go through all these different sub domains. I blame me for that that was my silly idea. And then also the split between users and contributors that was a deliberate decision that we made and the idea is that we would have a very minimalist user centric sort of user oriented website, we called the brochure site. And then we would have something called fedora hubs, which is a long dead project at this point, where it would be sort of a contributors area like an integrated everything where you could just go to your teams page and like see issue like a widget for issues and whatever. It was a great idea but it didn't work out. So it's time to get the bands back together again so that's fedora revamp 2022 so how are we doing this now sciac can speak more to this. So I will hand it over to you unless you'd like me to do it to I'm happy whatever. Sure, I can go ahead. Feel free to step in anytime you feel. Okay, so how are we building it right. So we have an awesome intern that is actually not so when we were going through this initial efforts. She did a lot of evaluations and after a lot of evaluation of platforms like views as react fast API and a bunch of other options out there and with the consultation of the websites and apps team. We found out that there was a certain configuration which we felt was the best way forward for us. And that was this particular step that you've seen in front of you. We have huge years on the front end, which is basically a very popular accessible just framework for front end components and we are using white to create the bills for on the on for enabling. The sites will be static. We're using plus chairs behind and for this is part of the things we're using that if I am not a conscious decision that we made was to use tailwind CSS because of all the utility classes that provides. But yeah, this is the base that we are building the next set of websites and applications going forward. If you want to go through the repository, you can go to the kidnap site. I'm sure we'll be sharing this slides later on. You can use that to check it out. And with that, we can move forward to the next slide. Oh, sorry. So, oh yeah. So yeah, where are we right now? So what's the current status of the current status is we are in a stage wherein we are at the same time. Going through a lot of design models and also developing on the go. So at this moment, we have had multiple rounds of feedback around the design models that we have had. And we have sort of established a finite set of models that need to be implemented. Work is still going on with that, but we have a good idea of where we want to go with the design. Now, where are we on the code? So we have decided that with the set of models, we want to convert them into interactive uses by creating a relevant front end and back end pieces. So what we are doing right now is that we have created kind of, we are experimenting with a kind of framework using which we would be building the future sites. And once we have a good framework ready, we would be using that framework to create the initial websites. And we will start entering the content and preparing it for the final rendering of the websites, translations, localization, everything. So yeah, right now we are in, we have already started the work and we are moving forward to the next phase. So now what's the next phase? The next phase involves setting up the staging, gathering feedback and facilitating the finale. A lot of people might think that documentation would also come in the next set, but we have already started with it. So once again, we believe that starting with a good set of documentation to go with right from the beginning allows the community contributors to be more limited. Just more easier for contributors to understand what are the different pieces that we are developing and how things work together, how they come together, and wherein they can start to contribute by directly jumping into the project. So how are we going to do this going forward? That is the facilitation of the final and stuff. We are planning to start with two sites. One is the Flock to Fedora site, which is about this event that we are in. So Flock to Fedora website is about Flock, Nest, Hatch, and all such events. And as we go forward, we are planning to do with the makeover of this site. And the other site that we are working on is the start page. So start.fedora is the page that whenever you open up Firefox, for example, in your Fedora machine, that's the default landing page that it takes you to. It's basically an aggregation site which puts in stuff and shows it to your work there. The scope of work is small, but it is a great starting point for newbies and people who are new to the project who want to get started with contributions. And so where do we go from here, like after we start this? The long-term goal is that we have a bunch of other sites that we want to go on with. But really the plan is to keep evolving as we go. And what do we need for that? We need a lot of contributions. So this is also a kind of a shout-out to probably everyone who is out there right now to just come forward and help us with this effort. There are a ton of ways to get involved with us. You can join us on Matrix. You can join our weekly calls on Jitsi. So we have weekly calls at 1,500 UTC every Tuesday. And we have two types of new contributor trains planned for the future. One is we are creating components like we want to have videos which help you to get started with creating components for Fedora's websites in Vue.js. And also we are also planning to do a hack list and review feelings for content entry. If anyone wants to check out the code, you can check out the code at kitlab. It's kitlab.com slash fedora, websites, apps, and fedora websites. And if anyone is interested in going to our documentation, you can go to docs.fedora.org and slash websites. And with that, let's back to you more. Yeah, and I just want to say Ashlyn has actually given us as sort of a trial. She's tested her training for Vue.js component writing on both me and Madeline Peck from the Fedora design team. So we did sort of pair coding sessions with her where she walked us through how to create new components from scratch. And it's very accessible, do you know what I'm saying? So it's something that you don't need to have a high level of coding familiarity with to be able to contribute to. And I think it's fantastic because it means that designers can have more impact and control over how their design shows up in the code because they can contribute to the components directly. If building website components is something of interest to you, what it's going to end up being is Ashlyn is going to take the content from the one-on-one sessions she did with me and Madeline and a couple other people and record sort of a training, a video training, you know, we'll post it, you know, I'll post it on PeerTube for the design team and we'll post it on YouTube, I'm sure. And then what you could do is we'll have like a little kit where you could get the link to the video and then some tasks that you could start building components out and you can kind of self-directed training and so you could kind of learn, you know, you'll get the skill set of learning how to build components with you and then you'll also be able to be contributing to the Fedora website at the same time. The other thing that we've been talking about is, and this is on me, so watch for communications from me probably in the Fedora community blog and in our discourse, but we're talking about organizing a little mini hack fest with some invited guests from different areas of the Fedora project to make sure that they feel that if they want to maintain, like say you're on some, I don't know, the working group for the workstation site, right? And the work for the working, the workstation should have some control over the content that shows up on the workstation website, right? So we want them to be able to come and say, okay, here's the content on our website, oh, we need to change some tags or update something or add something. We're going to do a training where they can actually use the CMS that is built in. It's the Netlify CMS, it's open source. So they can actually practice entering in the content and whatever, and then have a hack fest where we all grab a task of entering content. So we're given the text and then work on entering it in. We'll take the feedback from that process if there's anything that needs to be tweaked in the CMS configuration or anything like that. Fine tune everything and then again do sort of a self-service recorded video session that anybody who wants to grab a ticket off the queue from our repo and entering content can do that. So it can be sort of an asynchronous help as well. So that's what we were thinking. And I think that's it for the presentation. Yeah, that's the last slide. So if anybody has questions, now's a good time to ask. Let's look. I'm sorry, but my mousing is a little weird. I have a Bluetooth mouse and the battery is dying. Will the new website be WCAG compliant for accessibility? Yes, I would hope so. I mean, certainly accessibility is a big goal in Fedora moving forward. It's going to be one of our focuses. So the thing about it is that because we're picking modern stacks that have accessibility testing and components built into them, we're hoping a lot of this will get a little bit for free, but it's certainly something that we want to build into testing and everything in the websites to make sure that our sites are accessible. Yeah, let's see. Here's another one. Oh, okay. So I could tell you a little bit about Netlify CMS and the way we have it configured. So yeah, the content ends up going into Git. It's a Git focused workflow, which is actually quite nice. It's not some kind of database type of driven thing. It's Git based. And please correct me if I'm wrong, Siak or Ashlyn in the comments. But what ends up happening is when you fill out the content using the web UI of the CMS, it gets committed to the repo as a YAML file. So the content just lives in Git as YAML. Yep. Yep. Okay. Cool. I didn't lie to you guys. Yay. Any other questions? Anybody you want to help that needs guidance on where to start? I don't know what time we have either. We have like, I think five minutes ish. We have five minutes. Does anybody have questions about the old websites? Perfect talks that everyone understands. Yes. I will tell myself that. We already have. Thank you. Let me just go back through the history and see if there's anything. Oh, by the way, I'm sorry for like, I'm just listening to the Beatles a lot. I could not resist. This gives me life. Yeah. One of the things I guess that might be worth pointing out is with the splitting sub-domains, you know, the SEO stuff. I see SEO and like people talking about SEO and it reminds me of like blockchain people, you know, like this people who are obsessed with SEO and you get spam emails about SEO. Oh my God. I just don't care. But having your website split across different sub-domains instead of all in one website actually hurts your SEO, search engine optimization. So we're hoping that the big reunification here getting the band back together will fix that. Let's see. I think there's another question. I would like to work on FedoCal, but theming this site is a thing I'm not sure how to address. Okay. So FedoCal is an app and it's not part of this effort. I'm not quite sure how FedoCal is written, unfortunately. So I don't know if I can give you guidance on that. I'm not sure if I can also give, but I'm sure someone from doing the calls can help. So Edward, if you want to help. You can join us during one of the weekly calls. And probably someone from the team would be able to help you with that. So yeah. The history of the FedoCal project's website should be preserved. Something for the museum, don't you think? Is there a museum? Do you mean like the RPG little social party thing, work adventure? I think so. Oh. Yeah. I mean maybe. I really like this one, but it was just so manual. It was hard to keep updated. The site is then generated from Git and Staticus form or is it dynamically generated by some in background running server? I think Syac and Ashlyn can probably speak more to that. Yeah, I'm just reading the question. And sites then generated from Git and Staticus form or is it dynamically? Okay. So right now it's generated static in Staticus form, but going forward we are planning to play around a bit with SSR and stuff like that to see if we can have dynamically generated sites. Right now everything is pretty static. Yeah. We are playing along with various capabilities in Nuts. And we want to see where that takes us. Yeah, I guess the last question and then we'll cut it there since we're kind of almost at time. How soon can we torpedo the old repos? Yeah, that's like a question. I think Ashlyn has already answered that. We are already, we have already moved our development flow to GitLab. So hopefully once the GitLab repos are a bit more mature, we can start looking at torpedoing the old repos on Azure. Awesome. Well, thanks everybody. And let me just go back to that last slide. So if you want to contribute, here's pretty much all you need to know. And of course feel free to reach out to me or Syac or anybody else on the website's team. Join us in Matrix. That's like the central place to go to get involved. So thanks everybody.