 This is Jason Porter with the Red Hat developers program here at Red Hat Summit 2017 with Brian Letham. And my line just blanked out. Leslie Henson. That's right. Wow. It's only 10 o'clock. It's been a long day already. All good. And these two work on pattern fly. So it's kind of our front end kind of initiative. It plays in the same realm as a bootstrap and server foundation. Right. Yeah. Very good. And so what what it well I said I said where it is what what exactly is it and how does it differ from bootstrap. So it's based on bootstrap. The pattern fly is an open source design system. It we gear it towards enterprise web applications and it goes beyond bootstrap. So bootstrap because it's a nice foundation and it's responsive and a lot of dev teams are familiar with bootstrap. But we go a step further. We are designers and developers that work on the project. There's additional requirements that enterprise applications have that pattern fly answers those needs. Okay. Very good. Is it just for websites? Can I use it for a hybrid application? For emails? What can I use? Enterprise web apps. So we don't gear towards websites right now. It's enterprise apps. Web apps. All right. Very good. Very good. And you said it builds on top of foundation. Are we adding any components to it? It builds on top of bootstrap. Sorry. Right. Right. Yeah. So if you're a developer building your web application, you're using bootstrap and you find that bootstrap is missing in certain enterprise use cases, charting components, dashboards, some advanced foreign usages, you can bring pattern fly in at that point. You can use our pattern fly components right alongside the bootstrap components and build out your enterprise application. We also provide a bootstrap theme that tightens things up a bit, makes it a bit more better use of real estate, which is something that you want in a more enterprise style application use case than you get out of bootstrap. All right. Very good. And how does the community go about interacting with pattern fly? So we have a number of different ways that we communicate. We have a Slack channel and we also have a mailing list. We have a community meeting that we have monthly and so people... That happens on Slack? No, it's a blue jeans meeting that we have and then we also have communication on GitHub. Everything's on GitHub. That's one of the aspects of the project is design done in the open. So we have pattern fly slash pattern fly dash design repo on GitHub where we have markdown files that document all our patterns. So when we're working on a new pattern, we'll put it in as a pull request with new markdown describing what that design pattern is. We have our discussion amongst our designers and developers out there in the open for the public to follow along and participate in. So it's design done in the open, which is pretty cool. What all goes into... Say I want to create a new pattern, right? So I want to create a new pull request with the pattern. What all is entailed in that? Do I need to submit a wireframe, documentation, CSS, HTML? What all goes into that? Yeah, there's many facets to submitting to pattern fly. So if you are a CSSer and just want to do the CSS code, we'll work with you to make sure that we have the design documentation in place for that. We also have a decision tree that helps us to identify when components are common. So pattern fly is answering common problems. So we're not going to have product specific type solutions in there. So we make sure to have that conversation about is this answering the needs of multiple products across the board. Okay, if I create a pull request, is it straight CSS that I'm submitting? Or is it less or SAS? What am I going to be submitting? Right, okay. So we look at how pattern fly is implemented. I mentioned we have the pattern fly design repository, which is the collection of markdown files that describe our designs, just to describe the patterns. Then we have the CSS, which is the implementation of the visuals of the design. And then we have JavaScript, which is the implementation of the behaviors of the design. The CSS is built on top of Bootstrap. So we're using less right now with Bootstrap 3. We're already looking at building on top of Bootstrap 4, and they've made the move to SAS. So we'll be making move to SAS with them. In terms of JavaScript, we offer integration with a number of different frameworks. Our initial behaviors are implemented using jQuery plugins. We follow that on with Angular pattern fly for Angular 1 components, implementing our pattern behavior. And we've just started the pattern fly ng and pattern fly react repost to target Angular 2 plus and react framework integration. So those are new initiatives. We're forming little communities around these pattern fly repositories to encourage developers to contribute, get involved. So we've been holding open meetings with them, getting feedback. A number of developers have already started implementing pattern fly to target these frameworks. And we have a number of isolated efforts since we're trying to bring them together in these new repository-focused communities, sorry, framework-focused communities around pattern fly. If I'm doing an Angular app, you know, I know the Angular and the Ionic combination is very popular. How well does pattern fly play with the Ionic? So pattern fly would, we wouldn't really be used with Ionic. Ionic, you'd use one or the other. So Ionic provides... Ionic would be bonding components for both of them? Not really at all. The styles wouldn't mesh well. The user and actions wouldn't mesh well. We have a lot of overlapping use cases. Okay. So you would choose one or the other. Same thing with like material design, you choose one or the other. And the website is patternfly.org, right? Yeah. Very good. And anything else that you think developers would be interested in as far as pattern fly goes? I think that the project is just an interesting project because it's a place where designers and developers can work together. And so it's an interesting dynamic. It's fun. All right. All right, very good. I'll just add that we use pattern fly internally within Red Hat to build the interfaces for a number of our different products to provide a consistent user experience to our customers, to our community. And then we make it available as the open source project for our community to build their own interfaces with. And so when you build with pattern fly, you're taking advantage of all the design expertise that we have within the user experience and design team at Red Hat and leveraging all that expertise in your application. So if you're a smaller shop, building a web application, you can't really bring that design power to your company yourself by using pattern fly, you're gaining access to our efforts through the open source process. Which is pretty cool. Very good. Very good. And we said that's patternfly.org and the Slack channel once again is. So if you go to slack.patternfly.org, you can get an invite to patternfly.slack.com. Okay, very good. And your community meetings are on Blue Jeans. Yep. When's the next one of those? All of our information is posted on our community page on our website. Okay. All right. Very good. Thank you, Brian. Thank you. Thank you, Leslie. Thank you. All right.