 So I'm gonna talk about the a little bit of the history of Fedora websites and Have we got to where we are today? And then kind of end by putting out a huge call for help because we really need help on the website steamer So just out of curiosity Anybody in your part of the project when this was the landing site for Fedora? Does anybody remember this? Yeah, so this was actually before Fedora was using its own domain for the website. This was actually fedora.redhat.com back in 2004 so Little bit of history for you and then so more recently a couple of years ago We switched to this kind of design. There were designs in between there, but This is what we were using for a number of years and Then today, this is what the landing site of Fedora looks like. So if you're gonna get Fedora.org This is what you'll see. This is what our users see our new users who are Wanting to download Fedora or get involved. This is the landing site they see. It's simpler than the needle design. It's Less less going on at once so you can kind of focus in on individual components and Yeah So how did we get there from the previous design to what we have today? So mid-2018 We had a volunteer contributor who was kind of leading the Fedora website's team His name was Robert Mayer, Roby Duck on IRC and He was doing this for a number of years and it got to mid-2018 and he had other commitments come up Which happens and he was no longer able to devote as much time to maintain the website So around this time Fedora 29 beta was pending due in a couple of days and we had no website prepared and that was a problem So a couple of people reached out to me internally because I had worked on the websites before and They said hey like we're in trouble. We have Fedora 29 beta coming out. We don't have websites help so I Worked it was the weekend before release. I worked updating the websites getting everything ready to go Same kind of thing happened for Fedora 29 final We got to the end, you know the release was approved ready to go to GA and We had no websites same kind of deal so started noticing a trend here and a little bit later in that year kind of had a heart-to-heart with Jim who was my manager at the time and this controller is going crazy And I explain, you know You know Originally working on websites was not part of my job description. I was like, you know, I enjoyed doing this I've worked on websites before I'm happy to keep doing it But I have a request a condition and that was I really want to redo the tool set that we're using for the websites because well, I'll go into why but Around the same time Matt Miller the through our project leader came to the web team and he had a request. He said, you know for fedora 30 We want to redesign get fedora. We want to have a new face for fedora You know we had had the previous design for Five years or so probably at that point and it was time for a change the facelift also at that same time When Ryan Lurch from the design team saw that request he started working on the the new get fedora the one that we have today But he also emailed a couple of people internally and externally and said Hey, while we're redoing this website while we're doing the redesign should we also look at our Tooling should we like see if we should switch to different tooling? you know a different static site generator or whatnot he wants to open that discussion and His email about that he had no idea that I reached out to to Jim earlier and there was a totally independent thing like we We came to the same conclusion. We need to redo the tooling as a totally separate thing So I guess great minds things alike, but why why didn't what drew us both to this this idea so The old fedora websites repository is the give repository that has All of our websites kind of crammed into it has the landing site get fedora.org It also has armed up for our project or all thought for our project or expands labs Iot all of the floor websites crammed into one repository And that has a couple of problems. So first off the repository is huge All the static assets for these websites the images CSS JavaScript. These are copied for each and every website There's a lot of custom code so In the old websites repository, we were not using a static site framework We were using gender to two templates and a lot of custom Python code that kind of compiled them all together You were not using an official framework to do this There's a 557 line config file called called global bar dot py which gives you some indication of how this is going There were a lot of legacy code and hacks that were added in over time so for a given release for example There would be a spin or a lab that that didn't get done in time to go out in GA So we would have to go into all the templates and comment out just that one spin Or sometimes we'd have a particular release or version that has a different Download path from all the others. So we'd have to go in and find that just for that one release And then remember to undo that change for the next release And a lot of those never got undone So the templates just became a mess of all this legacy stuff added over time so It was hard for our developers to set up and contribute I mean just cloning the repository alone takes a significant amount of time because how big it is I Mean I have fiber at my house now, and it still takes several minutes to clone the repository so Ryan from the design team, and I started kind of exploring new static site generators And we looked at a couple options the first one we looked at was Hugo which is written in go-lang and I had some new ideas had this idea of themes where You kind of have a set of themes and you reuse them for all the the sub components of the site But it did a little bit too much it was trying to be a little too helpful I had had a very specific specific idea of what a static site should be and how it should be laid out and We kind of had our own ideas that we wanted to do and Hugo was kind of getting in the way of doing that We looked at Jekyll we looked at hackle which is like a Haskell version of Jekyll We looked at Pelican, which is a Python one And we also kind of asked what does the team already know what do we use what are you know? What is our skill set in story infrastructure in Fedora websites? What are the what are the tools that we already know? And the one thing is we use flask these Python flask for all of our modern web apps in Fedora infrastructure It's kind of something that we've settled on over the last year or two Previously we're using every framework over the Sun, but you know, we're we're kind of consolidating on one framework now and A community member said hey you guys are familiar with flask as a team like the Fedora project uses flask for things Have you checked out frozen flask and? Spoiler spoiler spoiler alert that is what we settled on So frozen flask is basically you lay out the website as a flask app You have all your endpoints and your functions that they define Templates and template variables and whatnot and then it will go through and it will crawl the site and generate static HTML files from Your flask app, so we tried it and we pretty quickly settled on so a lot of design work with with Ryan and Moe to any mock-ups and myself implementing A lot of work later. We deployed the new get fedora in may of last year The sad thing is it's still not the one true place you get fedora, right? So get fedora.org But we still have alt for all thought for our project order for the alternate architectures We still have armed up for our project or for armed specific stuff We still have spins around their own sub-domain. We still have labs. We still have all these other sites that if you don't know You know where to look for a particular version of fedora, like, you know, it's hard to find It's not one umbrella site that has everything on it and that's kind of what we want to move to So So we need help we we really need help to to get there So kind of some goals that we have in the short term Maintenance so people file bug reports, you know, people see typos on the site You know, there's translations that They get updated over time Or strings that we forgot to add to the translation system Every fedora release and fedora beta release The website needs to be updated in the new system with with frozen flask. It's really easy. There's one YAML file It's kind of all self-documented So you go in you update a couple variables and the site is updated. It's it's pretty nice In the long term like I said, we want to merge all the other sites into get fedora So that get fedora.org is the one place to actually get fedora So also there's There's still work that we need to do on the old websites until that until that migration to get fedora happens The old websites still need to be maintained until then so every fedora release You know, it's it's Not fun. It's there's a lot of tedious work there. Like I said with all the legacy templates and whatnot But as of right now that still needs to be maintained and we still need a lot of help doing that so This is kind of a call for help if anyone is interested in in helping out on the website scheme It is highly rewarding rewarding work You know, the websites are highly visible anybody who's interested in fedora looks up fedora wants to contribute to fedora They're going to start at get fedora.org. It's the landing site. You get to work with really cool people mostly other volunteers Really smart people really good designers people who want to see fedora be successful and You get to help fedora be successful So a couple of resources if you're interested in helping out we have fedora websites on free note That is probably the best place if you have immediate questions or you know kind of want to introduce yourself or show interest That's probably the best place to get started We have two really badly named repositories right now We have here pig your dot.io slash fedora websites That is the old repository that has all the websites kind of combined into one repo We have the new websites, which is through our web slash websites Really badly named, but I'm hoping once the once all the other subsites get merged into get fedora We can get rid of the first robot story And we also have a mailing list and So there's updates to get thrown there sometimes you can also feel free to introduce yourself there and Kind of say hey, I'm interested. I would like to help out You can also contact me directly. I'm more than happy to kind of help some people Get started and kind of show around what we have Like I said, we really need help with this this the fedora websites are what people see when But they want to get involved in fedora when they want to try out fedora for the first time And the website team is really lacking mandala right now. It's something we really really need help with so That's about all I have. I'm happy to take questions, but you know, this is Mostly just wanted to show the migration to the new website what that looked like and kind of throw out a call for help because we could really use it There's questions. I'm happy to take them, but otherwise that's good That was really the main reason it was like we had a lot of familiarity with flask already We've been using it quite heavily in infrastructure All the team members were pretty familiar with it. The old website 3po was Python it was a lot of custom code, but it was still Python So that's why, you know Flasking and Python was an advantage Yeah, I mean that's that's the main reason it's just familiarity again We looked at other kind of compared other static site generators Some of them we could have made work some of them were again trying to do more trying to be more helpful than we wanted them to be but Yeah, mostly familiar Yes, there is Yeah, so there's a on the fedora documentation website There's a whole walk-through. It'll help you set up the container It'll you know the the container image has all the dependencies and everything already there So just go through the steps It'll set it up and you can go to the site in your browser. You can make changes and you'll see them right away Thank you