 I am Matthew Miller. I am the Fedora project leader, and this is a Fedora Council video meeting. So in the Fedora Council, which is kind of the top-level leadership and governance body for the Fedora project, we try to do our business as much as possible without actually requiring meetings. First, we had no meetings at all, but it very quickly turned out that you actually need to have a cadence of meetings to get work done. So we have regular meetings. Firstly, those are text-based meetings in IRC or Matrix now, but we also every month or so do a video meeting where we have a high bandwidth conversation about something exciting or important or hopefully not in trouble, but occasionally that in the project and kind of make something that we can have this real-time conversation and also show things off and we record it. So if you're watching this later, that's there. So you can see what's going on. And this week, we are having a presentation from the Websites and Apps team about that project and particularly about the new website design for Fedora, which I am really excited about because it's been a long time, 10 years since we had a major website redesign, and this is going to be something more than just a refresh of Git Fedora, the whole everything, FedoraProject.org and everything has been rethought, and I am pretty excited for it. So we have a number of people from that team here to present, starting with Ashlyn who will, I think, go through the new design and talk about things and then some other folks will cover other parts. And I guess I'll hand it over to you and let you introduce yourselves and go for it. Sounds good. So I'm Ashlyn Knox. I'm one of the contributors to the Websites and Apps team. And I just wanted to start by grounding with some of our top-level goals and an overview of what we've been working on. So one of the big focuses for this revamp is to make a new website infrastructure that's really easy for other team members or team members from other teams to be able to contribute to, such as editing content on their editions pages or changing out images, things like that, without necessarily having to have Web and Apps, text-ac knowledge. So for that, we've been working on setting up a CMS that'll be pretty lightweight. It's pretty easy to access. And it allows just simple changing of basic page content. And then for more complex changes, things to the actual layout and what not, a little bit of knowledge of our text-ac would be necessary. But yeah, we think that this is a really good way to move forward to keep our sites a little bit more modular and to keep it so that we can update our sites regularly and easily without it having to put too much stress on any particular team. Along with that, we're also changing out our text-ac for NUXT 3 and Vue, which is a JavaScript front-end framework that does static site generation. On the NUXT side, at least. And we want with this because Vue is a pretty easy to get used to framework as far as those things go. And a lot of the syntax, if you're used to regular HTML and JavaScript, isn't too separate. There's some specialized knowledge, but there's pretty good documentation for it to make it fairly easy to onboard. We did some early training sessions with members of the design team, with whom we've been collaborating with very closely to work on this, work on getting the prototypes and the designs to implementation to happen smoothly and just to get it so that we can work on each other's stuff a little bit. The website's members are able to provide feedback and talk about the mock-ups and everything as we're working on them. And likewise, the designers who wish to get into a bit of coding, they're able to also start getting involved with that. And so we've made some training videos and such. So right now, we're on track for being able to launch for the F-38 release. So that'll be all the main edition pages and their subpages. This will be the first draft of our new navigation system. That's pretty exciting. We've been working on building a nav that will have a version that lives on the domain that we've been working on. But we'll also have an exportable version that we'd be able to put on to the other sites or other sites throughout Fedora. So I believe Niko's got this up on the screen here. This is a bit of what I'm talking about. And Niko's going to do a more in-depth walkthrough of this design and end of our current state of our deployment in a little bit. But some of the other exciting things that we're looking at long-term is... The F-38, sorry. The F-38, that's basically the end of April, May timeframe we're planning on that. Oh, yeah. Would be proposed, yeah, if there's no blockers. Okay. That sounds great. Not everybody knows the schedule as well as we do. So I wanted to put the actual month on it. And then also, is this going to, at that point, be kind of replacing parts of Git Fedora or all of Git Fedora? Or will that also be FedoraProject.org domain name change at that point? This is Niko Fedora, project.org. And we should have Git Fedora changed by this point as well. Okay. Cool. Thank you. Sorry for getting ahead of things. Oh, no worries. Sorry, Ashlyn, let me know what you need to see on the screen, right? I'm in the HackMD right now. Oh, okay. You can just leave it on the website landing page there. Yeah. That'd be fine for right now. I'm just going to wrap up this little bit here. Some of our long-term plans for the next steps of this following our launch with around springtime is going to be to build a components library that we'll build based on what we've done with this site. So that would allow people to be able to build other sites using the same stack and the same component libraries that we've been using to build this, which is all ran, managed, and maintained by Fedorans. So that way we'd be able to have a really cohesive environment. It won't require nearly as much view and nuts knowledge for people to be able to build sites for their additions or their projects and whatnot using our tooling because we'll have done a lot of that background work to get things worked. And so we really hope that this is going to be a great initiative to pull together teams across Fedora and to be able to give a really exciting and fun way to refresh the front-facing pages and allow new contributors to be able to navigate our really vast ecosystem a lot easier. So yeah, once we finish our first launch in spring, we'll be looking to focus on mentorship, team building, and then optimizing and enhancing our components, our component libraries, and our sites and code to make them faster, leaner, smoother, and funner to use. And that's about all I have there. I was thinking that it would be a good plan to pass it over to Emma a bit to talk about the work that's been done on the mock-ups and designs there just because that's really what's led to the building of all of this and this tight relationship between the design and development team. So yeah, if you'd like to chat a little bit about what you've been working on. Yes, of course. Are you able to hear me? Okay, first of all. Perfect. Okay, so my name is Emma. I am part of the community platform engineering team at Red Hat, and I work alongside Mo in the newly founded community design team as well as the Fedora design team. So Mo asked me if I would help out with this project around a year ago. And the onboarding process and the collaboration process has been really good. I attend as many of the meetings as I can and I keep up with the chat to keep in the loop of things. In terms of my workflow, so initially I do outreach to addition teams. So I interview the respective teams about their addition and what they would like to see on their additions page. I keep them updated throughout the process so that they can have an input on the designs as well. After that then, I make an initial draft and I share it with the community on discussions as you can see there for the Cora web page. I usually notify the team as well about this post so they're able to leave some of their comments as well. And then I update any changes that were suggested there and once everyone seems happy with the design, I implement the recommended changes and I mark it as done. Yeah, so that one's a bit big there though. Yeah, but still working it out. But yeah, so in terms of the CMS integration then, so during this whole life process, the web and apps team kind of build a page with the draft elements that I have on Penpot. And since Ashlyn and the team have walked me through how the CMS works, I'm able to go in and update the content then as needed so if I'm making a small change on the hero image or anything like that, it's really simple for me to just go in and change it myself. For coding sessions then as well, there was a workshop that Ashlyn ran with members of the design team to show how the website was built as well as practical sessions where we took part in peer coding so that was good because it was interesting to see then the developer's perspective and how their whole process works then as well. Well, yeah, it's from the design side. It's been really good and a very enjoyable project to be part of. I'll hand it back to you. Can I ask about, you said hero image, that's jargon to me. I guess that's the big image at the front top of the page. Is that the? Yeah, exactly. Yeah, like the featured image at the top, yeah. And then the content management system, the CMS, that's basically what someone like who is in the IOT team would use to update or the desktop team here on that one, the trusted Linux desktop. If they wanted to update those phrases, that's where they would go to do that. Yeah, exactly. I wanted to make sure that's clear. Yeah, so I can hand it back then to you guys. Yeah, thank you very much. Ashlyn, do you want me to quickly do a walkthrough? We've, I think we're probably ready for that at this point. Yeah, yeah, totally jump into it. Great, okay. I'm also realizing that sometimes demos are sensible first or since that everyone knows what we're talking about. But hey everyone, I'm Nico. I've been working on this project for about a year and it's been really fun collaborating with everyone. This is our main repository and then we've mainly collaborated to have a chat so far. So this is our GitLab repository currently for this specific project. We then refactor certain components out into a separate kind of component library repository, as Ashlyn was saying. This is our, this is kind of what we always try to link to. So, you know, issues emerge requests here, but then we quickly explain our tech stack and then our main strategy has been to have these static deploys that are always being updated basically daily with each, with each, you know, merge so that people can always see what we're working on. GitLab pages is what I'm going to show you today. That's built on GitLab's CI itself and that's the most up-to-date in the develop branch. But then Francois has already set up a staging website on adoraproject.org to confirm that the whole build system works there also, just to kind of anchor you. This is our same workstation page that we've been showing off. So, I'm going to quickly walk you through the Fedora kind of test deploy and then also the CMS deploy which is critical to this because as Emma and Ashlyn were implying, this is the first time that you'll be able to, or one of the first times that you'll be able to edit the content yourself without getting into HTML. So, let me interrupt again, sorry. If people go to stage.fodoraproject.org, STG.fodoraproject.org, I just pulled it up over here and I can see the live website. Is that actually updated daily as well? Yeah, that's updated weekly. So, how we've done it is we're pretty kind of, we're pretty, I want to say, trigger happy with the merge requests to develop and then test things out there on our GitLab pages and then once things have stabilized somewhat, once a week we deploy to stage.fodoraproject.org, what happens when the main branch actually gets deployed to fedoraproject.org if that all goes smoothly at f38, I'm not sure. Maybe this becomes the main branch, fedoraproject.org and then staging with either state idLab pages or the staging.fodoraproject.org, we can kind of mix and match as we like. Okay, so someone who's casually interested in seeing what it looks like at this point, that's a good place for them to look. And then if you're interested in getting more involved, more up to date on what's actually changing minute to minute going to the website section on the fedoraproject.lab is where to go. Totally, great point because the idLab pages, we try not to break, but sometimes it breaks just because we're trying new translation stuff or whatever. Yes, I think stage.fodoraproject.org is a good one to share because that kind of confirms non-broken always. Great, okay, I'm moving on here. Let's do a quick click through finally of the website that we've all been working on. So this is a statically rendered, there's no backend to this website. Based on Nuxt, as Ashton was saying, which has helped us componentize all these things so that we're not duplicating each other's efforts. So as an example, Jefferson built, let's say the cloud page recently, one of our contributors, and he could reuse all of the titles and designs from the main workstation landing page. We worked hard to get mobile responsiveness, so Ashton and everyone was thinking hard about how these things respond mobile from the very beginning and how that experience scales down. And we've also been thinking about internationalization from the beginning. Francois has done a lot of work on that, so this is fully translatable. As you can see here, we're not sure about the placement of this actual language switcher yet, but that'll get there at some point. And we also support Dark Mode now, which is a much requested feature for all the late workers here. So I'll leave it just on default light and default light mode and English for the time being, but you can basically mix and match this as you see fit for your personal experience. Cool. I know one of the main design goals of Ashlyn and especially Moe and the design team as they were originally doing this was to put more weight on community and that it is community. So each kind of... Each edition page here has of our five main editions has a download and community edition. And then we've also really tried to... Ashlyn was really trying to get all the editions, like on that discussion thread, up in our nav bar for, I think, the first time. So as an example here, we have currently editions, emerging editions, Spins and Labs, they're all here, along with stressing things like the community and all the things the community does, how to contribute and all the things on how to contribute and how to get support. And that looks really nicely flexible for if we want to change around some of the things with what we call Spins and Labs and that sort of stuff that gives us... Completely. Yeah. Ashlyn fought tooth and nail to get this nice and scalable, so thank you for your efforts there, Ashlyn, and Mo. And yeah, although it's a relatively complex nav bar, there's a lot of precedent for this on the internet, be it even just our downstream projects like Red Hat or then also ibm.com use similar kind of switches to have a lot of products like we do. And yeah, but all this is basically a work in progress still. Yeah. Cool. So let's say you arrive at the index page, which would just be the straight, you know, the root domain name. This then, this is still work in progress. You'll basically see a list as you do now of the different OSs that we offer, and then this download is going to switch into a get fedora soon, because we don't like how download appears twice on certain pages. So you'll hit get fedora and let's say switch, you're looking for the, I don't know, the IOT version. Then you'll be able to see the benefits here and edit them in the CMS. And then let me just switch to Workstation again because it's most built out for download. If you hit download now, this will link to the download page where we have all our editions. And the nice thing about using Nuxt here is certain pages like CoraOS, as certain editions like CoraOS actually pull their downloaded links on the front end, like in JavaScript, because they're regenerated so frequently. And so it actually really helps us doing this in Nuxt as opposed to something truly traditionally static, like let's say Jack or Hugo, because we have kind of a framework on how to build some front end heavy interactions into the UI without it getting chaotic. So I think future maintainers will thank everyone's decision here for picking Nuxt. I'm about to wrap this up on the demo, but last thing I want to say is, yeah, so communities stressed more. That was part of the main design goal. So each page has a thing explaining how to contribute. What happens for editions, the initial idea was for F-38 to switch the five main editions and certain other pages, like let's say Flock, we have built out under events, thanks to Francois. But not every single page yet on all the various sub-domains. So as an example, still the blue, we're in collaboration with them already, but we'd still just link to their external page for now for this initial release and then migrate more of the pages once we've kind of ensured that this initial release goes well. We'd migrate more of the pages, let's say spins, labs or whatever, to this new format if we want, or we can leave them on a sub-domain. So long story short, we don't have to have everything on this. We can link it out to external site. And that kind of concludes my main overview of this. Let me know if you want to see any more sub-menus here, or sub-pages, that's the GitLab pages I just demoed, stage.pedoraproject.org looks similar. But then one of the main pushes here was despite this being statically rendered content, we did want to CMS to let's say if someone hates how it says, you know, browse a great collection of apps, we'd want to say browse an open-source collection of apps. How would you do this without editing HTML? Well, you basically click on this CMS deploy link here, we can obviously link to this better. And this links to our same GitLab pages here, but with a slash admin at the end. And this, if you have access to a certain permission on the GitLab repository, we'll log you in to this front-end called Netlify CMS, which can edit, which can commit to Git. So it's all a Git-based workflow, but it masks this all in a relatively user-friendly manner. So it's not complete what you see is what you get, but it's about as close as we can get without having a fully hosted WordPress instance. So let's say I'm looking to edit the that I think it was fantastic apps on the features for everyone. I open up the features for everyone card, and I can simply here edit this into a great browser and an open-source collection of apps, and it works the same for images, it works the same for pretty much everything else. And here I will get a quick preview of this string, but once I hit Save, it will actually open a quick merge request on our GitLab page, but then we'll see this as a draft in here. But let's say this is ready, and I want to publish it. We can publish it right now, and this is meant mainly for fixing benefits, and you'll do this maybe once every two months, I'm thinking changing the actual text on the website. That then gets merged into our developer repository, and the CI rebuilds the static site, as you can see right here. And then that change will appear on this test deploy in roughly 50 seconds a minute. Right there. So that's kind of our main create and edit flow. You can't completely create new pages from scratch, so if there is a new addition, you will need to have an engineer or a contributor build you a new one here with existing components and just add it into pages. But for editing strings, which from our thought was one of the main use cases, and replacing images, you'll be able to do all of that in this CMS deploy, which is open-source and hosted on our own infrastructure. And that way we get the benefits of a serverless static site with some of the benefits of a CMS. And that concludes my overview. Let's say I'm somebody who works on a spin that I have only some amount of spare time to work on, and most of that goes into improving the spin, and then it's like two days before release day and I realize I want to change something and I don't remember where to find the CMS. How will I find it? Can I find it from the page? Or do I need to know to go somewhere to find the CMS? Great question. 100% we can link to basically slash admin at the end of this under let's say contributors you know, wherever we want basically. There could be a link here that say the CMS of the site and that would simply add slash admin to the end of this and well not with slash workstation. Live demo. But you see we get to the CMS if we just basically add. What do you think about actually having a edit this page link on the pages themselves if we do for the docs? Anyone feel free to jump in here but I will say that you do need permission to edit or make merge requests on this repository to login to the admin dashboard so that may be a little confusing if people understand it is a true wiki where you can create an account right there that wouldn't be as straightforward here which I think probably makes sense for such a high profile project because vandalism as we know is a thing for wikis. Excuse me, an idle thought there. Yeah, for sure. But I'm open to it. Depends on what everyone else thinks. I guess I'm thinking at this point maybe a link somewhere in there to just a document explaining what to do. Yeah, 100%. That could be an edit right here. Because I'm definitely thinking people will forget where to go when they're not in it all the time. Yeah, that's a great idea to add for our documentation and just how we make sure to have good tool tips for contributing and getting involved with the websites. That's very much like our next base kind of plan. We'll chat about that one in the future. That's a great idea, Matthew. This is just really amazing. So amazing I'm losing my voice apparently. Yeah, I'm really excited to see this and actually more than that I'm just excited to see this and everybody working on this and Ashla and then Akash and Emma, Nico, everybody. This has been a few years ago we were at a point where the website there was a release coming out and we actually didn't know who owned updating the website. We actually had a release where the release came out and we had to scramble, oh no somebody actually update the website because nobody owned that. It was really in a bad shape and it's just been amazing to see all of you come together and build an amazing team that has made this really great website that's going to be so nice for the project. I'm so impressed, proud, I don't know happy it's amazing. Thank you everybody. That's a very rare moment we see Matthew speechless. I do like to talk. Of course. Is there anything else to show off here? No, sorry I'll stop by sharing my screen. I think what we're looking for today is yet thoughts from the council and sorry Ashla and I'm paraphrasing here but get those from the council and basically get the initial kind of tentative go ahead for this direction and also our rough timeline of F-38 using the index page and the main five editions and the download pages of F-38 moving to this new format. Yeah wow I think it's great. I think if you can hit that timeline let's do it. I don't think we need I guess it's a big change to the main view of Fedora so it's good to run it by the council. I don't think we need a full council vote for this but yeah I think if anybody on the council has concerns they should say so in the next couple weeks if they don't let's consider it go ahead for F-38 and I really like also the piecemeal approach there where we can do parts of it as we go so that means we can do it in a less than ambitious way if some parts work and some don't. I see some blue jeans video comments here coming from people they're going too fast for me to read on my screen here but also they won't get into the video call so if people have things to say feel free I'm going to put this into gallery view here I can vocalize my my comment here that I put in chat I was just curious I also just to echo off Matthew like this is really awesome and just kind of seeing the evolution of our websites strategy and approach has been really cool I was just wondering and this could be obvious like maybe I just missed it but has there already been any community blog posts about any of this work or updates on like hey we're doing this new thing? Yes it has been said multiple times in combo we even made votes we even mentioned it we made workshops we basically show off a lot of places so it has been very well should be known I mean we did what we could a lot of awesome awesome might be a good thing then might be a good thing then especially now that we have a official Don presence there and we are pulling in some new folks who I think are engaging with us now there if we have a recent post has maybe some of the kind of the demo or something close like to a preview that we saw here might be nice to share that with the marketing team is something to highlight I know they're always looking for new content and things to highlight and promote happening in the community video to when once this video what the recording goes live yeah the like the pasta I think correct me if I'm wrong Niko the past month or two we've been really getting into a lot with some of the weeds of setting this up like with Francois getting the deploy going to get a fedora project or getting our translate working on a translation pipeline the nav yeah the past month or so has been a pretty big deal on our end so I know we're quite vocal around nest and before and after nest with our updates I don't think we've written anything too much since then but now that we're coming through to this point of usability I think yeah it might be a good time to to publish something again I agree plus we kind of little bit dormant is because as if I'm the wrong please correct me we decided to team most of the Ashley and Niko and others and Francois mostly and I was in the meeting I remember we said that I think we need to finish more and show more finished product first than we show it let's just say we trust this one now we should ready to show it that kind of moment we're also waiting for as well so maybe as Ashley mentioned it's a good time to do another tour and give the marketing team some tools to content to play with it so it will be awesome congrats everybody as well thank you thanks yeah I think we can go ahead and test it on way more people just to go off what everyone else said now I think we were mainly trying to a not jump the gun and say hey this is our new website for F38 before the council had at least had a moment to yell nay and also this new nav bar that kind of pulled everything for Dora together didn't land until a couple weeks ago and we were we didn't want back on the old nav bar so that's one of the reasons we weren't sharing it but yeah now I think we're ready to to get as much feedback as we can that sounds great Tomantro you had a comment there in the Tomantro just left it some reason yeah just from the comments Justin said there's some feedback on our progress since next do you want to speak to that maybe I can we're kind of reply there I think from the time around then might be helpful depending on how much feedback you're looking to take at this point versus like keeping a regular pace because I know managing feedback is also something that takes time and can slow down development a bit I think reaching out to Joseph in the marketing team or any of the folks there in the matrix room I was just looking at this and I was like wow this is amazing we should let more people know we have some exciting stuff coming down the pipeline for Dora 38 and we're just clarifying that yeah depending what's useful for your team or for the team doing the work that might be helpful to get a little more like wider look at some of the work that you've been doing since nest over we should chat about that in our upcoming meetings and just how we want to approach that I think we all because we've been working so hard on this when we release and go to launch we really want to have kind of a boom wow factor too so there's a little bit of like not wanting to over in and date people with it as we're as we're still doing it so it doesn't feel like an old hat by the time it gets there I think there's going to be some boom wow I'm not worried about that plus one just to echo I don't know Steve you want to come on Mike and ask your question or you rather have one of us rep it for you here but just a question from from Steve daily here about who he should reach out to about getting the fedora server page updated he's here representing the server working yeah I just write it an answer most of us Nico front row Akash me and basically come to the website chat we can help you through the GitLab and links and walk it through in in our regular meeting you can join us and we can basically show you what to do and give you a help plant and you can update your pages thank you Akash for the link and basically that's the place the best place is definitely metric soon because the for for reasons it's our most communication places the websites channel on chat to project or websites that websites that I don't remember the matrix address website website website double quote federal project is the metrics and yes and on the server page specifically the reason that's a little less built out in the other editions is because we were still waiting for kind of designs basically from the design team so they owe us that but we can also port the existing get fedora page just to the new you know kind of flashier format for now and and leave the existing content and then updated to the new designs as we get them come into the chat and we can discuss also you can help us on the new content maybe server pages maybe there's a new tools comes up for example I'm just saying out of top of my head let's just say in the server page that doesn't have cockpit but now the current cockpit is much more better maybe we can maybe you are you guys want to showcase it maybe something else so this kind of content help and other stuff also help us because it's basically what you want to future is also important as well in the website in also respective other things as well so that will be also help us a lot because I know a lot of content is there slightly some others a bit more older so some refreshments will be an amazing as well. Right so a quick morning Duffy for creating all the designs leading the design side of things and of course coming up with logo for our team that you can always pay a visit to our matrix channel to take a look at and coming to the point where you know to make sure that these websites and the contributions to them stay fresh Ashlyn has had a very good framework around the mentorship side of things that she has laid down she has been in touch with me as well as with Justin regarding the same and websites being one of those things that has taught predominantly in schools in universities as well as in art schools as well so we can employ a lot of people right to make these things happen to have maintained us for a long time so it would not just be us but we see a lot of folks coming around and staying back hopefully for contribution. Yeah that's exciting and yeah thank you very much to Mo for all the work on this I'm out of sight out of mind I'm thanking the people I can see but Mo is not here today but did a lot of amazing design work and design thinking going into this which is awesome and very appreciated we got a few more minutes sorry good there is a message also Steve said they actually discuss about refreshing the content server page in their last meeting so they have a task group that's amazing so they will they really want to change their page content basically what they say that's also important that's amazing it's going to be awesome servers also important I use it as well maybe actually I'm talking about Mo here but Emma maybe you could talk to them about their their benefits and then forward that on to the design team to draw up some benefits basically we can go rogue and just build stuff but it's often better to get the design set first to reduce iterations yes that's perfect they're next on the list anyway thanks so much cool we focused on this new website thing a lot we've got a few more minutes left it's just a websites and apps team would someone like to talk a little bit more about like other websites and apps what is the apps part of this team mean and what what kind of things are worked on around that I think I can so one of the first applications that we revamped was moat the next one was this but this one was a huge composite project of a lot of sites like particularly the frame of its own I wouldn't call it a meeting log system we have by the way but it has a lot of text meetings like I said so this is where all those text based meetings are logged there I don't know why it's called moat but it is but that was updated there's actually a meeting behind it there was a good meeting behind it you should okay it was a good meeting behind it if I can so do you want to continue so thank you for circling back to the development part of the websites it was a huge composite project and the coolest everyone who was a part of it and made this thing happen this right here will leave foundation to other components that we will be making use of in our applications as well as in the slides down the line so the view implementation with the websites and apps team has been a good factor which has influenced the CTE team the community platform engineering team of Red Hat to use ViewJS in their products as well and we would like to make use of more of these progressive frameworks so what comes next? Fedora Badges components that we will be making as well as past API the backend side of things but yeah these components that have been created as a part of this project would be used in the Fedora Badges TVAM which will be coming down the line so you stay posted this will be a big project just like the one that we have had right now and will keep all our fingers and toes crossed to make sure that it also becomes a success that's great what about FedoCal? I look at FedoCal and I think oh this is this was great when it was brand new it's still functioning so I think we can still keep with I like how this is going right now can we just fix the batch first please at least I love my I want my badges back one thing at a time okay fair enough thank you on that one there with FedoCal because there's some functionality that we've been planning on a few of our sites particularly the Flock site that's going to have some live updating calendars and whatnot so getting into FedoCal like after I think Badges is a really good next step because we can really hone and perfect our frontend and sharpen our tools there so that stuff works really smooth really clean then when we start to get more under the API side of things with Rebuild like FedoCal we'll be able to have a really tight integration between it and our frontend so we'll be able to have just more options for where we show date and time information so I think that's going to be really cool I'm glad that's on the radar yeah again I'm sorry Matthew please go first I was just going to conclude things so if you have something that's not a conclusion you should say it so I just want to say at least a little bit of a it's a little bit for you I hope that can happen I was just thinking so maybe in the Badges and systems you like graphics so I might become with you some idea about graphics in behind of the Badges so you like graphics I know that and I have a really creative idea for you and I actually prefer something that can't wait yeah is anybody else have any final thoughts, questions yeah just one quick one is just I think it was smart so this happened before I joined the project but you and Knox were picked to build this new website and I've been I was thinking we've all been thinking a lot about this kind of tech stack and I just think this could carry Fedora into the future for the next 10 years as opposed to I know there have been a lot of website revamps in the past the nice thing about this Knox and view thing now is you can scale all the way over into apps because it's a very reactive interaction heavy framework and then what we're doing here for the static pages because we don't want to be shipping a web app as our landing page is we cook it down into very straight simple HTML styles for us so that we're both using a language that a lot of people know how to write in use basically fancy HTML at the end of the day and then it can also scale all the way up to apps but it's not doing so on our website right now I just wanted to kind of connect those dots yeah that's that's great thinking ahead to a long future is nice for Fedora right back post point view chairs as well as the next combination of both of these one for the applications one for the sites while these making the use of same components will lead us to future but the one more thing that we have been emphasizing more on is documentation just to make sure that if we don't have people around we still would be able to have something that people can reach out to refer and be able to create something by themselves so we have been having efforts to it and it's not just just to develop inside of things or deploying things but rather it can be down to how to run meetings stuff like that and how to mentor people when you are well have spent some time within the team and know what the ins and outs are so documentation has been our big focus and will continue to be as we go on for a considerable point of time and well we just make it a point that anything that has to happen it needs to be documented because there will be time when we are not around and we need to make sure that people are still able to do things and not just will come up with another rewrite because right it's not a very well it's an intensive thing not good when it happens often yeah well thank you again everybody this looks amazing thank you for sharing it I'm excited meanwhile in fedora land we are talking about fedoras we talked about this framework for the next 10 years we're not quite that ambitious but we're talking about the fedora strategy overall project strategy for the next five years how we're going to advance the project both technically and in our community and social structures this on discussion fedoraproject.org under the council tag you'll find that conversation please everybody here please join us and everybody watching it this could be a community discussion that's going to be pretty intense I think for the next three months and kind of get that all set up and going this year so please join in on that and then this is the part of the call where I ask Ben what the next video meeting is and he says I'm ready for your question this time Matthew I'm ready for your question this time Matthew we will not have a video meeting in February because the council will be getting together for a face-to-face meeting so in March Akash will be back talking about a related but separate topic the web and apps community survey results that will be March 8th at the same bat time same bat channel look forward to seeing Akash and everybody else then thank you all and yeah I just can't keep saying it this is so amazing