 Thank you. Any polycasters, what's up? Rob here. Welcome back to another episode of Ask Polymer. This is a little segment that we do where you send in questions on G+, or Twitter. And I do my best to answer them. OK, our first question comes from Wheatley, who asks, is it possible to use SAS with Polymer? And if so, what's the best way to go about doing that? So there's really two things to think about if you want to use SAS with Polymer. The first is that SAS needs to know about Polymer's custom property and CSS mix-in syntax. The other is that for using external style sheets or something like that, you're going to need to bundle everything into a style module. Now, for that first point, mix-ins and custom properties, there is a master bug in SAS tracking support for this. So you can check that out over here, right? Recently, SAS added support for custom properties. But if you want to use mix-ins, you're going to need to escape the mix-in code using a little bit of SAS syntax. As for wrapping things in style modules, there's a tool that our teammate Eric Bidelman created called Polystyles. I will leave a link to that down in the show notes. So you can use that with an external CSS file, bundle it all up into a style module that Polymer knows how to work with. And that way, you can use SAS and style modules in your application. So thank you, Wheatley, for that question. So our next question comes from George, who was wondering, do you recommend putting every element inside of your element's HTML file, or do you put your elements inside of other elements? So I'm assuming, George, that you're using the Polymer starter kit application boilerplate thing. So that actually comes with a little elements HTML file where we put a whole bunch of element definitions that we end up importing into our index file. So basically, what you want to do is, if you are creating your own element, that element should always list all the things that it depends on as imports at the top of its file. So if you're creating an element that depends on paper button or something like that, the import for paper button should be right at the top of your element's definition. Now, if you're then using that element in your index file, then, yeah, sure, put that element that you just defined in elements HTML. But you don't need to put all of its dependencies in elements HTML as well. Really, you can think of elements HTML as all the things that the index file depends on, basically. So yeah, elements, they import their dependencies. Anything that you're using in your index file, that can go into elements HTML. Hope that clears things up a little bit for you, George. All right, our next question comes from Jesse, who was wondering, when are we gonna get a data grid in Polymer? So that's a good question. Right now, the Polymer team is not planning to ship a bunch of new elements. We're working on a few things kind of related to framework stuff, like a router, stuff working with the URL, but we're not planning to ship a bunch of new UI elements. Instead, I think what we'd really like to do in 2016 is see more elements coming from the community, and we wanna do our best to promote those elements, because there's a lot of good stuff that's being built out there right now, but maybe everybody doesn't know about it. If you aren't familiar with it, there's a website called customelements.io, I'll link to that over here. And this is basically like, it's kind of like NPM for web components. You can go there, you can just start typing in what you're looking for, and there's a bunch of things that folks in the community have just created and published there. And so yeah, what we'd like to do is we'd like to promote some of the data grids, some of the UI components that are out there already. There's one really good one by a team called Vodin. I think it's just called Vodin Data Grid, perhaps. You can find it on that website. And for those of you out there who are thinking about building some stuff, you're thinking about sharing it, share it on customelements.io, and then ping me on Twitter, and we can try and promote it and get more people involved in the ecosystem. So thank you, Jesse, for that question. Our next question comes from Zeikz, who asks, what are the biggest barriers to adoption today, and what's on the horizon to overcome those barriers? So I think over the last year, the hardest stuff was just making sure that components worked well across browser, and that they were performant. I feel like we're starting to get to a really good place with Polymer, where those things have kind of settled down. Where it's still tough today though, is taking a bunch of components and knitting them together into an application. We're sort of missing kind of the framework pieces, if you will. And so what we're gonna work on this year is rolling out an improved router. We're gonna work on some stuff around data bindings and improved data flow through your applications, some design patterns that you can use so you can figure out how to kind of architect the whole thing together. And yeah, I think right now that's still probably the biggest barrier and stuff that we're gonna be tackling this year and rolling out and hopefully improving the story there. So thank you, Zeikz, for that question. Okay, the last question comes from Dan, who asks, how can a developer using Polymer contribute the most to the Polymer project? So there's a couple ways that I think you can go about doing that. The first is go check out some of our projects like Polymer Starter Kit, where we already have like a ton of active community involvement and look through the issue tracker, find a bug that looks like maybe it's something you could work on, maybe something nobody's working on just yet. Leave a comment and be like, hey, can I try and tackle this bug? And once you do, send us a poll request and we'll even work with you to try and if you've never done a poll request before, we'll work with you to set that up and walk you through the process. That stuff is super helpful. You can do that on Polymer. You can do that on the element repos too. If you find an element, there's a bug in it. Rather than just filing an issue, see if you can get in there and try and fix it. Also, if you're building stuff, share it with the community. I mentioned earlier, there's a site, customelements.io. I'm gonna leave the link down in the show notes, but we're really trying to get more people building components, more people sharing them there so we can all kind of benefit from each other's work. So those are kind of the two big areas that I can think of. Pitch in on some of these things, send us a poll request if you can and also share the stuff that you're building. Get it out there, get some other people using it and that way we can just grow the whole ecosystem. So thank you Dan for sending in that question. All right, so thank you for all of those awesome questions. If you out there, if you have some questions that you want us to answer, just leave them down below in the comments or you can ping us on a social network of your choosing at hashtag ask polymer. As always, thank you so much for watching and I'll see you next time. So I think over the past year or two where most people struggled was just like getting, what? God! I know I said struggled. No, no, no. I'm fine, I just struggled as I am struggling. Words, they hard to speak.