With that, I'd like to welcome you all to downloading your donated Microsoft software. Today we are being joined by Jim Orr of Microsoft and Gregory Seeley of TechSoup. Just to introduce myself, my name is Becky Wiegand, and I am an Interactive Events Producer here at TechSoup. I'll be your facilitator for the day. And feel free to ask any questions in that chat window throughout the webinar because we also have Sarah Hiller from Microsoft and Ali Basdikian from TechSoup on the back end to capture all of those questions that you have throughout the duration of the webinar. And we will raise those up during Q&A and also maybe throughout the webinar depending on what comes in. In addition to myself and Sarah and Ali, we have our presenters for the day, Jim Orr, who is a Senior Product Manager of Worldwide Licensing and Pricing at Microsoft. And we have Gregory Seeley who is a supervisor here at TechSoup in our client services department. Here's our agenda for the day. We will be looking at a little bit about TechSoup in case you're not familiar with who we are. We'll talk about the Microsoft donation program through TechSoup. We will tour the Volume Licensing Service Center, and we will talk about things like software assurance benefits that come with your donated TechSoup software, or Microsoft software through TechSoup. And then we'll have time for Q&A. So to jump into who is TechSoup, we are part of TechSoup Global. We are working toward the day when every nonprofit, library, and social benefit organization has the technology, resources, and knowledge they need to operate at their full potential. And what that means to us is that we want to make sure that you other nonprofit organizations, which we are as well, have the access to software, hardware, donated materials, donated online services, as well as educational resources like this webinar and our articles, blog posts, newsletters to help you make the best decisions about your technology. We are a 501c3 nonprofit as well, and you can read on the screen a little bit about the impact that our work has made in partnering with companies like Microsoft and Adobe, Symantec, and many others around the country and around the world. If you haven't been to our website in a long time, we launched a new site earlier this year and you'll get to see some view of that today during this webinar. And hopefully it will help you walk through things a little bit easier so that you can not only request donated software, but fulfill those donation requests and install them and use them to your most effective abilities. So before I hand it off to Gregory, have you requested donated software through TechSoup before? And in particular, have you requested donated Microsoft software? Take a moment just to answer that question for us because that will help us understand what experience you already have as our audience today in using our site. Many people may have done it but maybe two or three years ago when we had a different website so we hope that this will be informative and will help answer questions. Give just another moment for people to click the screen and I'll go ahead and show results. So about 67% have requested Microsoft donations or have requested software through TechSoup, not necessarily Microsoft, but that's great to know. So hopefully this will be familiar but we also hope that you'll learn something new today as well. So to get us started, I'd like to introduce Gregory Sealy who is a supervisor here at TechSoup in our client services department who walks people through this process on the phone day in and day out and can help answer your questions. I forgot to mention earlier, we also have Tim who is from our client services department on the back end who may also be answering questions for you particularly if you have questions about your account or how to log in or your organization status with TechSoup. So thank you so much for joining us Gregory. Thank you Becky. So yes, the Microsoft program through TechSoup is extremely large. Microsoft has been very generous to us. It's been a vanguard of helping out nonprofits and we're very proud to have to work with them. And both the Microsoft program which has expanded greatly since it's been in and we at TechSoup have tried to keep up with that and to make it easier to navigate and to find information about Microsoft, both products that they offer and any kind of support and structure of their program. So first of all again, if they are our most generous partner, the program is more complicated because it is so big and so generous. Most of our partners we are going to fiscal year. This is not the case with Microsoft. It is a unique partner in that sense. Organizations in this case can request up to 50 licenses and you have 10 of the 53 title groups and up to 5 server licenses in 2 years which means you can get up to 50 licenses to say office or of an operating system. And again I will show you where to find that information in a little bit when we get to this site here. As far as the cycle is concerned, Microsoft reset everything July 27th of 2011. So if you have a request history with TechSoup, that date becomes the new start. The first request you place after that date becomes the start of your cycle. And if you've already placed one since that date, that date is going to be the cycle. Every 2 years it will turn over. There is no limit on how many requests would be placed in this 2 year cycle. That is a huge change from the previous structure of the program. It's current one, you can come back every single day and request in here, the only limit is going to be the quantity. The 50 licenses and up to 5 server titles. If that really is a problem, there are some organizations which have multiple locations and may actually be able to register more than one location, please contact us if you feel that might be your case. And finally, the requesting Microsoft through TechSoup is a 4-step process. We're about to walk you through all 4. I'm going to do the first 2 and then Jim from Microsoft will tell you through the last 2. The first is you're going to request the product or products you desire at TechSoup.org. I'm going to walk you through that in a second here. You're going to receive your fulfillment email with the authorization license numbers in the link to Microsoft's Volume License Service Center. Again, I'll show you that email and what it looks like and how to go. And then we jump to the center Jim will take over. You're going to access the downloads and download the ISO image to a disk at the service center. And using that disk and the licenses from the email, you're going to install your right and activate your product. So let's go through a little bit here what's involved. This, as you saw previously, is the new layout of the homepage for TechSoup.org. One of the things you're going to notice here, and I've got a little arrow here where you're going to point, each of these tabs is interactive, very interactive. When you hover it over, you're going to get it. It's going to splash the page with a drop-down giving you all kinds of options. It can be a little bit difficult when you're first starting navigating. It's very efficient. The interface is very efficient and very easy to navigate. So you're going to choose this right here, the product donors toward Microsoft is where we keep all of our product stuff. And you're going to see, and now you can see it's splashed across the screen here. You can see what the drop-down looks like. And you can see here all of our partners in alphabetical order listed out on the site here. And I've got Microsoft highlighted which is alphabetically placed here because that's what we're interested in. So we're going to click on Microsoft, and we're going to end up here at the Microsoft page. This is if Microsoft pages that have a welcome page, and then a products page. This here, I promised I'd show you, is where you find out about title groups. You've got the special tab there, but we're actually going to focus on this one right here. We're going to focus on this different thing. I apologize. I was hoping to do a live walk-through of this, and more things change the more they stay the same technology got in the way. I'm working with some screenshots, but I think I can show you everything you need to know here. So again, we're going to check on Browse by Products. This is going to take us to the second Microsoft page, the product catalog. You're going to see some products down here. When you first get here, they may not be the ones that you want. What you want to look at here is we have a two-tier drop-down menu, the kind of product, and then any selection within that product. And as you can see, I've got desktop applications and office suites in this situation right here. So if I click on that, here's my drop-down. You can see here all my different options for whatever you can get. In this case, I'm looking at, for example, Office 2013. You can see View Details. Here you get to your Edit to the Cart version here, and if you scroll down, you have it here. There's a second product in there. Just want to let people know really quickly, sorry to interrupt you, Gregory, that if they would like to view the screen a little bit larger, you can click Full Screen at the top of your page so that you can see a little bit more detail of what he's showing us right now. It's a little bit small to see, I know. So feel free to click that button so you can see better. Okay, this here, I've got two products in the cart. I didn't show this second when I apologized again. This site was being temperamental this morning, but I'm going to show you here. So now you're seeing in the cart here. And you've got your product, you've got your Quantity, which you can change. It's X here is if you want to delete this. Oh, I don't want Office after all. You can remove the product right here, and you have your price for each of your things. This is admin fee per license. You have three computers in the office. You're going to need three licenses you want to put in here, and then you can update your totals here. And the total down here is going to show you the overall price of admin fee for the total of the products. Again, I've got the Windows 8 Upgrade Edition here, and I've got the Office Professional. So let's keep going with the checkout process here. Oh yes, one more thing, the Restrictions Check. This is a two-step process because TechSoup being a donation program is all about restrictions, to whom, how much, and how often. Every program has it, and as I say, Microsoft is by far the most generous. But there's going to be Check the Restrictions Check if there's any problem with restrictions. If you have too much product or anything else, it's going to let you know. So in this case, here's the next thing. I scroll down, and here we are. Now I can proceed with my donation request. I don't have any restrictions up here, so ready to go while I proceed with our request. All right, this is the agreement section. If there's any kind of special, for example, if it's not returnable, or if it contains, if it has any of the number of special things involved with a program it's going to tell you here, this is just a nondiscrimination clause. We click I Agree, and again, you can go ahead and proceed with your donation request. All right, there's our next page here. If I scroll down, you're going to see here, this is shipping information. Now this is kind of a hardwired piece. We do TechSoup does offer some physical product. Microsoft is not among them. Microsoft used to send the media that's available through the website, and Jim will get to that in the not-too-distant future here. You're going to see this page anyway, because it's hard-coded, it's part of the system. You can go ahead and move right past it. It isn't applicable in this particular case, but we can't get rid of it. All right, onto our next thing here, payment information. I'm going to go ahead and choose check payment in this case, because I'm not actually placing a request, and I'm not going to actually put any money in. But you'd go ahead and you'd fully check the credit card information in here. Obviously you'd be choosing credit card in this case. Detail there, and you have your confirmation. Back here, that's the information which is the check, and your fulfillment email has arrived. Now when this email shows up, there are several things you need to know. First of all, this is what it looks like. One thing I was not able to include, and I apologize with title, this is your Microsoft volume license agreement with the TechSoup request number here. Key things you want to know are going to be the four things you know. First of all, if this appear, if you need any help, you need to call Microsoft or TechSoup for any assistance, or Microsoft for any assistance, these are the numbers you're going to want. Here's the TechSoup request number so we know which request it comes from. Here's the authorization and license number from Microsoft that they'll need on their end to assist you if you have a problem. Here is the magic link. This is the link you're going to have. Signing up, that's also going to be done at the same licensing center. This is the link you're going to use to go to the Microsoft website to access the second steps 3 and 4 of this process. With that, I'm going to hand it off to Jim here to take the guest back to Becky Jim to lead you to the rest of the process. Thank you so much, Gregory. We will be getting to Jim in just a moment. We had a couple of questions though from people that I'd like to raise up before we move away from your slide. We had a question from Sakina about how do you find out what happened if you are rejected? Basically you put in a request and you don't know what part of eligibility you don't meet for a product donation. Is there a way to find out what happened or to change that? How does that work? Certainly, normally speaking there's going to be some red lettering. And again, I apologize. I didn't have that information ready on hand. That's a good question. There's going to normally be some red lettering right there as you scroll down telling you what the problem it is. It could be you've exceeded your quantity limits for a particular program, or it could be that, again, quantity limits is going to be the name of Microsoft. It could be that you've already requested. The other one would be if you have requested it recently, but again with Microsoft it's probably going to be a quantity problem. It may be eligibility. If it is eligibility, and there are a couple of program areas that Microsoft deals with directly and does not use TechSoup for their nation's example of that is Education Schools. They are going to want to go directly to Microsoft. They have their own very thorough education program and do not go through TechSoup. Again, please check with TechSoup if you come across the eligibility.  If you come across something that you are not eligible for Microsoft, please contact us and let us take a look at it for you. But those are the two big ones. This could be quantity, or it's going to be eligibility. Great. Thank you, Gregory. And just to note about eligibility, we do have that eligibility checker on our website that Gregory alluded to earlier. But it is important to note that eligibility and restrictions on our donation programs are set by the donors themselves. So Microsoft or Adobe or Cisco or any of the other donor partners in our catalog, they can define we want to donate our products to domestic violence, youth groups, animal shelters, food banks. And if you are not one of those, then maybe you are not eligible. So those kinds of definitions are determined by the donor partners.  And sometimes you may look at that list and think, we actually could be three of these different things. So if you are not sure why you don't qualify or why you are not eligible for a specific donation program, definitely give us a call because it may be that you checked something off that you may be able to change in our back system if you are legitimately doing something that is equally as eligible. So definitely look into that if you are getting questions or rejections in our system for different product donation programs. We also had a couple of questions about who to contact if you want to find out if our branch of our organization qualifies for its own TechSoup account. So if you are a branch of libraries and you have 20 branches and you want to have your own account instead of having to go through one central location, for example, how does that work, Gregory? Go ahead, two ways. You can have an email us at customerserviceactechsoup.org and we will be happy to take a look at that for you. Or give us a call and I'm not going to read the number off right here. But either go ahead and give us a call or the client services department here or go ahead and send us an email. And we would love to take a look and see. We want organizations that have multiple branches or libraries are a huge part of our program. And we very much want to make sure that you are able to, as our mission says, operate your full potential. So if you have questions of any of this sort, please give us a call or send us an email. And we would love to take a look at your individual situation. Great. Thank you so much for that. So before we move on to Jim's section, I'd like to have a couple of questions to help us gauge your experience as our audience. Have you gone through the process of fulfilling, downloading, and installing software through the VLSC, the Volume Licensing Service Center before? Where is that slide? Sorry, that doesn't actually have the question on it. There we go. You can go ahead and check on your screen whether you've done that process before. Now it changed names a few years ago. It used to be called the eOpen Center or something like that, eOpen was the website through Microsoft. So maybe you've gone through eOpen. It has changed and I think it's quite a bit easier to use as the VLSC and has more access to benefit information. And Jim is going to walk us through and show us some of how that looks in a moment, but it helps us to know if you've been in there before. So I'm going to give just another moment since we have about 25 people who have not responded and clicked on their screen. I'll give you a second to weigh in. So it looks like 63% of our participants say that they have not. So this is great because Jim's section will be brand new and hopefully familiarize you with what the VLSC has to offer as far as your downloads and also benefits that come with your donated Microsoft software through TechSoup. So I'd like to go ahead and introduce Jim who is our Microsoft Volume Licensing Service Center expert for today. He manages volume licensing assets and works with the worldwide licensing and pricing programs through Microsoft. So Jim, thank you so much for joining us. Thank you, Becky. So first I'd like to say how happy I am to be here. I'm very proud to work for Microsoft which has had a very strong donation spirit to the community and to different organizations. And they're very good about matching gifts. And for those of you that worked on the old eOpen when that product was moved into my product, it was very fulfilling to be able to help get these products out. So I work on the Volume Licensing Service Center. What exactly is that? That's our way of delivering product to customers that buy in multiple groups. So it's very easy to go to a store shelf and pull down a CD in the books when you buy one. If you buy 50 or 100 of those, you probably don't want 50 copies of the manual. Nobody reads those anyway. So to that end, we go to the Volume Licensing Service Center. And for some reason, my clicking next is not moving the slide forward. There we go.  How do I do it? This is where I hope to help walk you through that. We designed Volume Licensing Service Center or VLSC to help people access their license information in one location, view all their agreement information, their purchase information, information about their organization, easily access licenses, and view assigned products and keys and downloads. Essentially it is designed for everyone from the enterprise to the donated software solution. So it has a broad base that it covers, which means unfortunately that some of the things on there won't always be connected with your open license donation. However, the majority of the site will, and I'll try and walk through the pieces that wouldn't necessarily be covered so that they won't be as confusing. And next is Very Slow. No problem, Jim. I can go ahead and click through for you if it's not wanting to work on your end. Yeah, it doesn't look like it's working very well. There we go. So as was covered earlier into getting started, you'll apply with TechSoup and get registered and get your product. And then you will need a current version of Internet Explorer to get onto our site. Those are available online easily at Microsoft.com, Internet Explorer, so easy to get to. Then you will need a valid business address and a Microsoft account. Now what's the difference there? So your business address is the address that you use for your charitable organization. So any communication there, it's important to use that address because that will tie you to support. The Microsoft account is what we use for the logon. Now the Microsoft account for some of you that have had Hotmail for a long time is the same as what used to be called the live account or a passport account. It's used with Hotmail and it's our way of authenticating you are the person that you say you are so we can tie your agreement to the individual so that you can log on. The business email address needs to be the one that's listed on your open order so whatever you placed with TechSoup has to be the same so make sure that's there. And that will walk you through the registration process. And it's a link in the email you get from Microsoft. You click on it with the business email address it will send you a quick note verifying the information and this is how we prevent piracy and the loss of your data. So we keep it very smooth. So to clarify for our users they will get an email from TechSoup with a fulfillment information and they will also get an email from Microsoft with a VLST information and the email address used for both the requesting and for the VLST needs to be the same. And if they have an address that is from an old user at their office or a co-worker they need to get in touch with TechSoup to help get that changed or add somebody new to their account. Thank you Becky. So let's go into the look and feel of VLST. There are two looks to the site. The site is HTTPS, colon, www.microsoft.com slash licensing slash service center. When you first log in you will receive this non-signed in site. This is what we send everybody to. It's a default sign in page. You will click on the sign in button which I carelessly covered up right over here. And that will log you in to your account which will connect you to the service center. So we've tried to simplify the site for those of you who were part of the old process. It's simply got the home page which is this page. One of the important things that I will note on here on the home page and this is a great section is this training section or learn more. Under that you say find training resources and there are a series of half a dozen or so videos that will walk you through everything from administering the site which would be under here and how to add new users or approve users to manage the site for you, to how to manage your essay subscriptions, and how to download softwares and keys. So if at any time after this presentation you still have some questions or are still not quite clear, this is a great place to go. These videos are very short between 2 and 4 minutes long, but they give you screenshots and they will walk you through that quick reminder on how to get back onto the site. At this top menu here we have licenses. This is where you would go to see your open agreement that you have purchased through TechSoup and shows you all the agreements that you have listed. So if you have multiple they will all show you up here and show you their current status. Fortunately with donations of our open agreements they all come with two years of what we call essay or software assurance. I will go through some of those details a little bit later in the program, but that is also accessible right here from the home page. And then the big one that I am going to go through here is downloads and keys. This is where you go to actually get your product. Subscriptions is not so much part of your program but unfortunately because I have to cover every program under the sun, the subscriptions end up being there, and then the administration piece. And then there is of course a help piece if you have any specific questions. There is a pretty good FAQ as well and the training videos. So I have jumped ahead of myself in the look and feel, but here are again the menu bars and everything that you see. Again I can't recommend more. One thing I didn't mention on these training videos, they have also been translated into multiple languages. So if you watch the video you can also see the text of the video in up to 12 different languages. So we tried to make it very accessible for all different languages and cultures. Let's skip right over to the downloads and keys because this is where you go to get your product. So you purchased a product, you now log on to the site, you click on downloads and keys. Now I have opened up an agreement that shows every product under the sun. You will purchase something specific like say Office. Well under Office that authorizes you to all of the components of Office which would be Word, Excel. And so you would only show, we have some 147 different products from Microsoft available, but you will only see the ones under your agreement under Open which is great. It will filter those products down for you. From this page you can find out more details about each product. So you get a description of it. You get a download option for it and the product keys. So the product keys are the 5 by 5 set of numbers. So it's 5 sets of 5 numbers that will allow you to activate that product once you've downloaded so that you can run it in your environment. The VLSC website has older versions of software. The standard products are one version back from the previous release of the product. So that gives us in currently Office situation we've got Office 2013 that just released. Office 2010 will be on the site, and Office 2007 will also be on the site. Office 2003 is temporarily on the site, but we'll be going away shortly because as products get older in nature they get prone to have more open windows for attack. We tend to try and roll off the older products as we go along. That keeps you safe from viruses and bugs as well as the longer a product is out there the more vulnerabilities the bad guys tend to find in them. So we tend to upgrade, give you new features, functionalities, but we also upgrade the protections on the product that protect your environments. So we definitely recommend that you move up as soon as you can to the newest version. We do realize that when you do some customizations and things like that that you will eventually probably need to stay on an older version while you get your users trained and moved up. So that's why we supply the older versions of the products. So I'll go through and I'll click on a description of the product to show you what this was like. This is Excel 2010. It shows you the version. It gives you a brief understanding of what's included in this download so that you know what you're selecting with a two-year essay benefit, software assurance benefit. You actually have the rights to upgrade for the next two years to the current version of the product as well as if you need to run the previous version of the product you can downgrade to say 2010 from 2013. So this will describe the product. Next we move to the download and if you click on download and it gives you some brief explanations on download purchase. We have moved away from providing media and moved towards this download option only simply because it makes it easier for us to provide more donated software and we reduce that expense of the media. We make one place at every download and it makes it a lot easier to share for us. So the download option, you'll notice that there's a download method. It has the download manager and the other option is download directly from the website. The difference between the two, the web downloads and the download manager, is something called an ActiveX Control. We recommend Download Manager with the ActiveX Control because that allows you to, if you have a problem with your connection and it breaks off midway through the download, to pick up your download right where it left off instead of having to start over what you do on the web download. We do realize that some lockdown environments require no ActiveX, so that's why we offer the other option. We also offer select languages. Many of our products come in up to 27 different languages and then we offer an operating system between 32 and 64-bit. Many of the operating systems are moving to 64-bit because it allows you to use more memory and allows your computer to be more powerful. But if you're working on some older hardware or an older system, then the 32-bit may be a better option for you. So we give both of those options in the Download section. Now the download comes down as what we call in the industry an ISO or ISO file format. Now we created them in a standard ISO format or ISO format because it makes it easily transportable. You download it. There's plenty of software out there to take an ISO format and throw it on directly onto a CD or a DVD. And that allows you to then plug that into multiple computers whether they're connected or not to do your installs for all of your licenses. The ISO format can be confusing to some, but TechSoup has an excellent documentation on how to use the format, where to get tools to open up the format, how you'd install it on their website. So further on in the presentation we'll have that link to how to get that information so that you can use that going forward. The last piece is the product keys. So these allow you to activate the product. For all of your Open, you will have something called the KMS key, and this allows you to enter the product information and activate that product. So this would be the same key that if you bought a retail version of the product comes on the inside cover that allows you to activate a product. And this is how we know that one version of the product is being used. So this is the same for all of your installs. So one key will activate all of the downloads that you have installed across your products. You can, if you choose to, export all of your keys into an Excel spreadsheet at one time. So everything that's covered under your agreement will be in your spreadsheet. I do highly recommend that you encrypt that spreadsheet because that is the keys to your software. So keep that under tight control from your environment. Do not email your keys please. Once you've emailed keys around, they tend to get lost or distributed elsewhere. And these are only for the products that you've downloaded. So they are very product specific. Some products will show up without keys required. Those are what we call pre-authorized products that have the installs pre-installed. So if there is nothing that shows up in this key section, don't worry, just go ahead and install the product and it will go ahead and install through there. And this would be an example of no keys assigned. So this product key for Office Standard 2010, there's a link in this tool to get the number there or retail products don't require the keys. So there are three types of examples that would not require keys. So if you see those, you should get a pretty good definition, say for no product key required or what you have to do to get additional activation keys from this location. And it will show you and walk you through that. The other section I'd like to cover in addition to downloads is Software Assurance Benefits. One of the nice things about our donations is they come with two years of Software Assurance. Software Assurance gives you several benefits including allowing you to plan through new product versions. It gives you access for deployment services through software upgrades, some e-learning for users. There is something called the Home Use Program which is great for Office. So what the Home Use Program is, it allows you to, if you've got a copy and license for your users in your organization, they can use this Home Use Program to also get a copy for home. And that use is available to them for as long as your SA agreement lasts, so up to two years from your agreement, and as long as that person works for your charitable organization. So that's a great benefit as part of SA. You've got something called License Mobility. This is a little confusing, but what it means is that if you say partnered with another company to run your technology, your servers, or things like that, and they were going to put your software on their servers, this License Mobility in SA allows you to have them install and run the software for you. Several other key things, the cold backup and disaster recovery is an excellent benefit that allows you to get a clean place to go get your software back in case the worst happens. And then we have a product called TechNet which is an excellent technical product that allows you to get really detailed questions on different products, on how to do things in a multi-user environment. So if you have confusions, you want to automate an Excel spreadsheet. TechNet would be the place to go to get those questions and answers. So those are all a great program. So if we go to the Software Assurance tab, this is what you'll see. Now, because this is designed for all programs, not all of these benefits are available to the donated software. However, I've included a list, and there's included on the TechSoup website a list of your Software Assurance benefits that are granted with the donated software. This list here is what you'll have. So what you would do, and let's say we wanted to do the home use program for Office because I had some workers, but they're volunteers in my organization. We have a license when they're in the office, but when they're working at home knowing that sometimes work does follow you there, they'd like to use the same copy of Office, and they can use the home use program. So you'd click on the home use program. It will walk you over to select your agreement that it's authorized for. So I've blanked out the actual agreements here because they are actual agreements that I stole the screenshots for, but you select the agreement that you want to apply your home use to. In this case, it would be the one that covered Office. Then it will take you over to your benefits summary page. This summary page will actually tell you all the benefits that you're eligible for and how many of them you've used. So if you have 25 copies of Office, you would have 25 home use authorizations. You can assign those out however you may using this, and it shows you what's active, what the history is, the terms and conditions behind it, and a description of the home use program. So if I click on that home use program, then I would go in and it would say, well, for what organization do you want to authorize this for? And it then generates the domain that you're authorizing against, and you can send out to your users exactly how they would set up. And they would log on to our home use site. They'd enter in their email address with your domain attached to it, and that would tell us that they are authorized to use it. So it's a great benefit that we try and authorize through this program. You get it for two years, and it's one of the add-on features that just comes with the package that you really should take advantage of. After two years there are ways to renew Software Assurance. You can renew it through the standard methods of Software Assurance, which is about one-third of the market value of the product to continue on for an additional two years of Software Assurance. Or you can go back to TechSoup and order another product. It's a two-year program, so the cycle works well with TechSoup, but there may be reasons why going through Software Assurance is a better solution for your organization. So we have both the option to go through TechSoup to buy a new product or a renewal of your SA agreement. So definitely it would be worth contacting your open-value reseller for charitable resellers to see which is the best option for you. The important thing to remember though is you need to renew before the expiration of the agreement because there is unfortunately no grace period. So if you choose to renew, that's something you need to do right away. Now for additional resources, again I wanted to point out that we've got some great training videos on VLSC and TechSoup has some other excellent videos on Software Assurance as well as definitely excellent descriptions on using VLSC and how to get your software. So at that point I think I'll turn it back over to Becky. Thank you so much, Jim. That was really informative. And we actually had somebody saying that they're downloading their Office 2013 right now with the help of this event. So we're glad that this has been helpful. Just to clarify a couple of things really quickly around Software Assurance, it is chock full of really excellent benefits that come for no additional cost with your donated Microsoft software with the exception of server products. So any other products, Office Suites, Visio Project, any of those products including operating systems come with Software Assurance through our donation program with Microsoft. Server based products do not. So just keep that in mind. And in talking about how to renew Software Assurance that's largely mostly relevant to organizations that have a lot of licenses. So maybe if you're only using 5 or 6 or 10 or 15 of your Microsoft licenses that may not be something you would need to do, but we wanted to make sure that that information was available for you. The home use program, the learning resources, e-learnings available, TechNet, access to all of these great things are available at no additional cost to you through Software Assurance. And you can access those in the VLSC where Jim showed it to you. We also ran a webinar on this topic that highlighted some of those in more detail. So if you're interested in that, we can include a link to that in the follow-up email that you'll receive later this afternoon. We have a whole bunch of questions that have come in, so I would like to go ahead and get some of those answered. So we had a question from Barbara. This is for Jim asking, what happens if you're using a Mac? Do you need to be running Internet Explorer to access the VLSC, or can you use a different browser? So you can use different browsers, and we have tested several. However, they don't always work exactly like we intended. So most of the time you can do almost everything on Internet Explorer. The one problem on the Mac that we do run into occasionally is the ISO format. Macintosh does have different products for opening those up, but those are available. There's also several forums out there that will help you walk through those. Those products are fairly easy to get and install. Microsoft is actually the world's leader in selling Macintosh software, believe it or not. We're very happy with that platform. And Office is by far one of the best suites available out there, so definitely it's a good use. But there are occasionally the gotchas. The one thing you will have to do if you're downloading, however, is you won't be able to use the download manager. You'll have to download via the web. Great, thank you. So we had a question that was a follow-up about software assurance that came in, and I actually will try and field this, but I'd invite either of you, Gregory or Jim, to respond as well. Carol asks, so based on what you just said about software assurance, we order, say, three Office products. We would have three home use programs. Is that correct? Instead of buying individual products, can we just get multiple licenses for a lower fee? Technically, you're supposed to have a license for every machine you're running, and you're supposed to be running it at your home computer using the same license, same employee, same information. And if you no longer work for the organization, you're supposed to uninstall it. That license is the same license essentially that you would be using on your Office machine. So having three licenses that you requested for a donation program doesn't give you really free access to three other licenses to install elsewhere. Home use is really to make it easier for staff of organizations to access the same product on a home machine, but it does belong to the organization, and it is the same license number. Do you guys concur with my response to that, Gregory and Jim? That's correct. It is a one for one, so it's one person who has a use in Office, can also use it at home. They're not actually considered separate licenses. It's just the ability to make it portable. Right, so it just extends that license. And the home use program I believe costs $10 to extend to your home computer. So keep that in mind, but it's not entirely free, but it is less expensive than having to request another donated license of most products. We also have a question from Elise. If we get rid of a computer, can you transfer your product key to a new PC? This came in actually from a few different people. What happens if you retire a computer or uninstall the program? Can you use it on a different machine? You absolutely can. One thing I will remind everybody is that when you do, and of life, a computer, be sure to wipe that computer completely clean, because not only do you send off licenses of our product, which is an issue, but not really that important, what you could potentially do is send off information about the people that provide help to your organization, and you never want to do that. So if you completely wipe those machines before decommissioning them, then you preserve the sanctity of your donors and your people that are helping with your organization. So make sure you definitely purge the systems, but then you have use of that license. It is portable between machines. And even portable, if someone leaves your organization, you can use that license for the new person that comes in and fills that position. Great. Thank you for clarifying that. We have a question from Jeremy that asks, if we buy Office 2013, can we activate an Office 2010 license through VLSC? If somebody needs it for backwards compatibility? Yes. So part of the SA benefits is downward downgrade rights, which means that you can buy a 2013 and you can install 2010 instead. So that is totally acceptable, and that is the recommended way to do it. If you choose to buy Windows 8 and then install Windows 7, that is also available to you. So those options are definitely available. Great. And that, like I said, for backwards compatibility might be something you need to do if you have a legacy critical piece of software that doesn't work with the newer software that you've just received you may want to downgrade. So Michael asked, I want to put in an order before leaving for a two week vacation. Can one wait before continuing with any other actions once the fulfillment email has been sent? And there are two different fulfillment emails, the one from TechSoup and the one from VLSC. So I guess it would help to clarify on both ends if he requests through TechSoup and doesn't go any further and gets a fulfillment email, can that email just sit there while he's on vacation, or is there a timeline by when he needs to take action? So a bit of a complicated question, but there's no actual timeline that you have to do it. However, remember that your license starts the moment you sign the contract. So your two years will begin then as soon as you've signed and purchased the product.  Take your vacation and install it after the fact, but your two-year agreement does start at time of purchase. Great, thank you. We don't want anybody for growing vacation just to install software. That's no fun. Carol asks, do downloads have to be on a CD or DVD, or can it be sent to a flash drive? We do address this in the article that Jim mentioned on ISO files that one, we recommend that you put it on a DVD or a large flash drive, not a CD because it may not fit. But CDs don't hold a whole lot of data. So DVD, but it also can be to a flash drive. I went ahead and took care of that one. Let's see what else we have here. We have John asking, a product we downloaded showed two different key types. What's the difference and which one do you use? But we actually have quite a few questions coming in about how do you know if you're picking the right version because they see multiple products listed even though they may have only requested one. They don't know to get the 64-bit or multi-language packs. Is there anything to help people know which thing to download? So let's start with the 64-bit versus 32-bit. That is really dependent on your computers themselves. Some of the older computers only run 32-bit software. The new computers can run 64 or 32-bit. So if your computer operating system is 32-bit, you are required to download the 32-bit version to run it. 64-bit gives you some access to extended memory so you can get to larger size files and things work a little bit faster. So if you have a 64-bit, I really recommend the 64-bit versions of our products. But either way, you should be finding the 64-bit environment. As far as the different versions, I did see one question about the K and the N. As many of you have heard, we have had our run-ins and discussions with different government agencies in the US and the European Union. Some of those require us to do special builds for those country regions specifically in Europe. So the K and the N are designed specifically for European and Asian markets. So if you are looking for any product that has those different versions on it, then here in the States or anywhere in North America or South America, for example, you just need the standard version. You don't need any with the special designators. As far as key types, there are several types of keys. And actually there is a help file on one of my slides. Let's see if I can find it very quickly. So for product key types, we have several types and it describes what each key type is versus a KMS or MAC key, which are the two types that you would use. The MAC key is primarily for large environments. We are talking several hundred systems. So in most cases, you are going to be with the KMS unless you have got a very large organization. So if you aren't sure which one you are going to use, in the key section and actually in all of the sections of VLSC, there is this little question mark at the top of each header. Those question marks give you some key information for some of those things. And this describes the KMS key versus a MAC key and when you would use it. The most important thing to know is if you have a MAC key, you need to have a server that can activate it local. So that's why it's for large enterprise environments and not necessarily for the open environment that you would be working in. Great. Thanks so much for that, Jim. And we know there are a lot of questions about different software types. And so we have an article from TechSoup on 32 versus 64-bit as well. We'll make sure to include some of those resources in the follow-up email that we send out. And we have a couple of those resources highlighted here about the ISO files. You will get the email with this PowerPoint so you can click on these links. We won't post them in the chat since they aren't clickable, but we will send that out later this afternoon. I'd like to go ahead and thank our presenters today. Thank you, Gregory, and thank you, Jim, for all of your great information on how to walk through this process. We hope that this has been helpful for you. You will be able to view this full recording at your convenience if you want to see anything more clearly and pause it and walk through the process on your own when you're actually requesting your donations or getting them fulfilled through the VLSC. So thank you, both of you, and thank you to ReadyTalk who helps us promote and sponsor these webinars each week. You will be prompted when this webinar closes with a post-event survey. So please take a moment to tell us what you thought and help us improve our webinar program. Five equals excellent, one equals poor. So please give us your honest feedback so we can make them better for the future, and join us again at TechSoup in the future. Thanks so much, everyone. Have a terrific day.


Thank you for all coming to the session. My name is Jibran Jhaaz. I'm a part-time Drupal contributor for last 13 years according to Drupal.org. It has been nine years since my first session in Australia at Drupal South Melbourne 2015, and I have been living in Sydney for past seven and a half years, and this is the first Drupal South in the city since then. It's a long time. I'm very proud and honored to be presenting this session today. I'm a Drupal solution architect at my day job and as a part of my job, I also lead a team technically and provide technical solutions. Hence the session to be or not to be a tech lead. Maybe I'm not happy with my job. But this talk is not just for tech leads. It is for any technical role in which your main focus is not to help. So first, I would like to begin acknowledging the traditional honors of the land on which we meet today. I would also like to pay my respect to elder past present. I'm originally from Pakistan and my first language is Urdu. So I would like to welcome you all and say Khushamdid. Khushamdid means welcome in Urdu. Khush means happy in this context well, and Amdid means arrivals, but in this context come. The origin of this word is from Persian language. So like it's not the key word in Urdu. Let's get started. So the main question is to be or not to be a tech lead. The purpose of this talk changed a lot since I proposed this session. At first I thought I'm going to convince everyone in the room to become a tech lead because my job is awesome. Then I had few discussions about this topic. So I started considering some other aspects during that. As the title shows, it's an opinion piece formed based on my personal experience as a developer. This talk is about personal journey. I took to become a technical lead and no two personal journeys are the same. One can be a tech lead without starting as a developer, but since I started as a developer, this talk is from that perspective. The aim here is to start a discussion, prompt an internal monologue, or maybe motivate some of you in this room to start considering being a tech lead. Here's the disclaimer. This talk is based on my opinions as well as opinions of my peers. So feel free to agree or disagree with me. This talk is also based on personal stories of people I have worked with. Some of them are currently present in this room. So please don't be alarmed if it all sounds familiar. No need to hide your faces. We are going to have heart to heart about this topic, these topics, and we'll touch the topic of mental health and well-being at workplace as well. And lastly, you get to witness my thought process throughout this journey. For me, it's very exciting and nerve-wracking at the same time. So to begin with, let's first look at the developer's journey. When you start a career, even with a technical degree or diploma, you still have to learn a lot to be able to get up to speed. You don't know what to learn and where to learn from, but slowly it changes and you start getting the hang of things. You get to know what to learn. Then when you become a mid-level developer, that's when you become a mid-level developer. When you are starting to become comfortable with your skill set, you have the confidence to talk to stakeholders and command the situation, that's when you become a senior developer. But as a senior developer, you still have to keep learning. When you start driving and dictating technical discussion, that's when you start stepping into technical lead role. Let's discuss different types of developers. We have a lot of developers here. Just to oversimplify in my career, I have come across three types of developers. Some of them are thinkers, some of them are talkers, and some of them are both thinker and talker. If you are just a thinker and you don't ask a lot of questions, then it's a problem. If you are just a talker and you don't think, then it's a bigger problem. So it is important to find right balance and you have to move between being a thinker as well as a talker. This is not necessarily personality traits of an individual, because there are a lot of Drupal contributors who are introverts in their personal life, but they have big voices in the Drupal community. So let's discuss some of the traits of being a developer. I have worked with the developers in the past who are really speedy but make a lot of mistakes. And on the other hand, I have worked with the developers who are particularly fast, but are not particularly fast and really meticulous about their work. Again, as a developer, you have to find the right balance for this. And it all depends on the quantity and the quality of work as a developer you have to produce. With ever-changing landscape of technology, another important trait is adapting and implementing new skill sets along with the freedom and time to fail and improve. The other side of the story is what teams' expectations are from you as a developer. Communication is the key.  So communicate your timelines, your struggles, and your successes. As you progress along in your career development, you start getting into building more and more complex systems with a lot of moving parts. So ability to break down big pieces in smaller chunks is really important. Similarly, sizing and estimation is also very important skill. It allows the rest of the team to plan their work better. As a developer, helping others is also a very important part of the job. It improves team skill and their confidence in you. On the other hand, it helps you to see the problem from a different perspective. Once you have the confidence of the team, you can start taking calculated risks with all these additional responsibilities picking and choosing what to focus on at what time is really important. If you can't self-organize yourself, then ask your team for the support to help you organize better. Also learning and adopting from your previous work is very important and it directly helps you improve. Let's say you have become a senior developer and can perform all this roles and responsibility. So what's next? You can branch out. In an ideal Scrum team, you should be able to do anyone's job. So learn to be a delivery lead, a business analyst, quality shoulder, UI designer, UX expert. You can learn new technologies and just keep on improving and keep learning new frameworks and new languages. You can champion a new skill, for example leadership skills, development skills or planning skills. Create or define new stuff, start a new product or define existing products. Or you can be a storyteller and you can switch to content writing. Share the stories and help others to learn from it. Or just be a salesperson. You can go into business side of things and help winning new projects. Or you can just become a tech lead and work with all of the above and then some lead attack team come up with tech ideas and design new solutions. But becoming a tech lead comes with its own drawbacks and benefits. It is no doubt going to be a bigger challenge than your previous roles. You will have more responsibilities and you have to communicate a lot more. And this one is a killer but you have to do a lot of context with it. With all of these added responsibilities you have to make a lot more decisions and there will be a lot more expected from you. Because all of this more and bigger stuff you will have less time to do the development work or work on your personal development. Just like a developer as well as with the developer trades these are some valuable trades as a tech lead. Build a team around yourself. Support them. And in term ask for their support. In this role you need to talk to a lot more people and some of them will be known technical so it helps to talk tech without talking about technology. Because you are going to make a lot more decisions you should always have rational behind them to back your decisions. In some situations you have to make a final call and let others know. And sometimes you have to back up from your decisions and eat a humble pie. There are some of the things required of you as a tech lead. You need to be a lot more calmer, more patient and in your approach. There will be times when you have to deal with insane situations so letting the sanity prevail is very important. You need to manage your time better block out part of your days and to get stuff done. Sometimes situations plays out itself and so situation management is also very important. In some of those situations you have to make hard calls and as it is said in the great superhero movie of recent time Madame Web when you take responsibility you will gain powerful abilities hence the more power because you have more responsibilities and don't hesitate to share the responsibilities as sharing is caring. Let's talk about some of the personal stuff. While you are doing all these things you have to stay on top of your mental health and make sure you are not burning out. Talk to like-minded people at your work do some non-work related activities with them maybe take up drinking take breaks when you feel you need a break find a hobby, maybe gardening video games, read something spend some quality time with your friends and family and take a look at yourself and evaluate what is going right and what is not and then make a decision based on those observations be honest and make smart choices. So let's say you have champion all these things and you are very successful tech lead where do you go next from here? You can move horizontally in your career and become a technical manager, technical director or a technical officer. You can also move vertically in your career go into more management and leadership roles you can start your own company and here's the buzzword and come up with an idea for your startup or you can just stay tech lead and if none of the above works out you can always go back to being a developer so here are some action items for the folks in the room who wants to be a tech lead in the future the technology is constantly evolving around us so we have to evolve ourselves as well and then evaluate the best way to improve yourself is to have discussions with helpful peers listen to the people and learn think about all these aspects and have an internal monologue and when opportunity presents itself take a leap of faith and go for it so in conclusion I want to share a small story last year we had a new position open up for our solution architect and technical lead role at the time we had a really good senior developer working with us me along with the fellow tech lead were trying to convince them to help step into this new role and they were reluctant to avail the opportunity we had several discussions with them and they were finally convinced but during those conversations I realized I went through the same thing when I was stepping into this role two years ago so I thought the topic is what discussing with the larger community since the release of Drupal 8 has become easier to build bigger and more complex websites to build bigger and more complex websites using Drupal we need folks to keep an eye on bigger picture while leading tech teams in the right direction so we need more tech leads in Drupal ecosystem and you can be the one thank you and shukria thank you jibran that was very nice my question is sometimes people kind of consider tech lead and solution architect sort of similar roles so in your opinion or with your observations what is sort of big difference between those two roles or can they be interchangeable depends on your organization you are working with if you have like large group of developers and they need technical direction then of course you that's a tech lead role and if you have like complex system then you have to design a lot of things then you know like solution architect kind of role but it can be both at the same time so like I have I work with developers as well as a large website so I consider both roles I'm doing both roles thank you any other questions you just mentioned how to pass and comment that in the ideal scrum team you should be able to do anyone's job so what does that sound we have a team where we have a lot of specializations could you speak a little bit more of that oh yeah so it's like in a scrum team work shouldn't stop if someone you can hot swap people that's the idea so like just fill in the gap so understand what a delivery lead goes through during the scrum what is business analyst's job right so it's not like you will replace the role that's not the plan it's just you can hot swap and fulfill that role thanks a lot in your journey from developer to tech lead what have you found the most difficult aspect to master real answer my ego I have been a very you know like moody developer I was very adamant about you know coding standard and the way the code should be written and that has changed since I started contributing to tuple you review people's code and see you know like some of the code how good it is and how not good it is and you learn from it and sometimes you are in an awe and sometimes you are you know just why is this happening for this reason right and during that process I you know like managed to get off from that high horse of my ego and learn to be humble and to learn from the wider community as well as you know like work with the team alongside with the team and don't feel you know being a developer is highly mighty thing so you know like every team member is assigned to do their task and do their job and their job might not be you know like very interesting from your perspective but still if someone is doing their job so you have to be you know like human and you have to learn that and you know treat them equally and that's everything I learned from Drupal community as well so yeah I would say that's the biggest thing yeah I know you mentioned hobbies to run what are hobbies did you take out well I watch video games not play video games I read a lot of books recently I am into reading a lot of self-help books and then you know recently I started going to you know like concerts like Australian bands so yeah so you have technical leadership roles both within your organization and actually within Drupal community and I guess my question is how have you found balancing those two advanced responsibilities that you found that your professional work has informed for those who don't know Gibran is a subsystem maintainer for the entity reference system as well as a number of contributed projects and in Drupal core a subsystem maintainer is essentially the technical lead for that part of Drupal so how have you found first of all balancing those two have you learned things from your professional work that helped inform your contributions or vice versa yeah it's a really good question I would say like again like when you step into a community where a lot of people are in leadership role just like yourself Lee is here as well you learn from them like how they are leading discussions and how they are listening to people and how they are adapting and open to suggestions and open to you know adopting new stuff so yeah I would say you know like learn from the you know like people already there and then grow from there just don't overstep your mark like yes I'm a maintainer of few course thing in Drupal and I take a lot of pride in doing that because I earned that place like I worked hard to reach that point but at the same time it's not for me to say what is right or wrong if you go in or not go in if community has a voice same as workplace like yes I maintain a big side but doesn't mean you know like I own the side like there are a lot of moving pieces so if for some reason and I touch on that a little as well like you have to back off from your decision and you know like learn that like how to be humble and you know like stay positive actually do you miss running out yeah so before you know taking up other hobbies writing code was my hobby that's why I put the part time stuff like since 2011 till pretty much COVID till COVID happened I was like working on Drupal core on my weekends all the time and since COVID and with this job because it's like a lot of moving pieces and you know like you age as well so you need longer breaks you need longer relaxing time I do miss coding I like having discussions about you know like problems but it's difficult to find the time and like manage both things but still like the conferences like these helps a lot thank you for asking that


Okay, I'm gonna go ahead and get started. Can you believe it's 9 a.m. on the second day? First session here. All right, good morning. Good morning, DrupalCon. Welcome to my presentation, audit your theme. Slides are available on the DrupalCon session page. My name is Andrew Olson. I'm a friend and developer from the Chicago suburbs. I work for a company called Bounteous. We have a strong Drupal team, but we do more than Drupal. I've been working with Drupal since 2008, and a fun fact about me is I'm a musician, and I played in a band at La La Plusa a while back. You can, which band? They're called Bank Merrill out of Boston. I was part of the traveling choir. Love to talk more about it. It was a fabulous time. And I had a great time at the Museum of Pop Culture. Those jam rooms, oh, it was great. It was a really fun time. But I'd love to talk more about that, but we're here to talk about how to audit your theme. First, we're gonna discuss how to analyze your theme, and then I'm gonna demonstrate some helpful tools for that analysis, and then I'm gonna provide some refactor pro tips. And finally, we're gonna discuss an approach to measure your theme over time. So why did you decide to attend this session? Perhaps you fall into one of the following buckets. On the screen, you see a bucket full of delicious cherries, and maybe that was the start of your theme, or the start of your platform.  So your theme has grown a little unmanageable over time, and it's a really good time to reassess and audit your site to get some improvements out of it. Perhaps you fall into this bucket.  You've celebrated, but perhaps you had to consume a few too many of these along the way and make compromises, and right after launch, after celebrating all your successes, it might be a really good time while it's still fresh to refactor and take a look at it, and these tools will help out. Perhaps you fall into this bucket. You're stuck with it. On the screen, you'll see a cat in this orange bucket and does not look too happy. So as you get this theme, these tools and running through this analysis will really help you understand what's going on. Perhaps you have one of these buckets. It's a very large project. On the screen, you'll see a waterfall, and there's four kids with water. They're just slinging code, slinging water, back and forth at each other. Might be a good time to kind of just say, hey, slow down, let's see what's going on, get some organization and reusability out of this. Finally, maybe you're here today in this bucket. You're new to theming.  So this is a good session to just kind of get a good feel for what's going on in your theme. So regardless of which one of these buckets you're in, let's begin. So we're gonna analyze, we're gonna go through some questions to ask yourself and files to look at, and then ultimately audit is going to lead to action. The first file I suggest you look at is your theme.info.yaml file. Right away, it's gonna tell you what type of theme it is. On the screen, you're gonna see on the right, I know it's a little small, but again, I have the slides up. What you see is just an example of a base theme that's using Zerb Foundation. And this is a sub theme based off of that. So right away, what I would do is I would say, oh, if I am not familiar with Zerb Foundation, I would go out to that theme page on Drupal.org and see what versions, see if there's any enhancements or fixes that have been made to it. The other thing I'm gonna see when I'm out there is the theme actively maintained. So right away, just by looking at this, you get a lot of information. Another thing at the bottom, again, a little hard to see, but in this particular case, it's using a component library, which is using Pattern Lab. That tells me that, hey, I might have to hunt and peck for some theme, maybe some twig or some styling in other locations, just by looking at this one file, it tells you an awful lot. The next file I suggest you look at is your theme.libraries.yaml file.  It'll tell you if maybe you're using a front end framework or there's some additional complexity going on in here. It'll also tell you what external dependencies you have, if it's a CDN or if they're web fonts and they're hosted external. Maybe you wanna pull those into the site and not have that external dependency. The next file is your theme.theme file. When you open that up, again, if you're inheriting a project, you're gonna see all the preprocess hooks and all the template overrides. Just by looking at this, you're gonna just get a good gauge for how complex and different areas of the site that you should kind of keep in mind as you take on this theme. The next is you might have a breakpoints.yaml file and that's gonna tell you what screen sizes you have. If you don't have this or you haven't implemented the responsive images module, it might be a good time to do that. Be friendly to your mobile users and serve up some smaller images. So those are files for Drupal, but let's look at some additional files you might find in your theme. If your site is using automation, you're gonna see probably some files for Gulp, maybe Webpack, Grunt, Yarn. I've used all of these and each time I just hope and pray that there's a really nice readme file so I can get refocused and back into theming whichever one is being used. The other reason is why are we using Webpack? Is there a reason why we chose that over possibly a simpler Gulp implementation? So again, you're just understanding what you have at your fingertips and putting in the back of your mind and taking notes for possible enhancements. Is your site using SAS or less? I'm very partial pun intended to SAS. Or you can also see if your site is using a pattern library. Brian Perry gave a great one, great talk yesterday about internal or external, so you should definitely check that out. But again, by looking in your theme, you're gonna get a good feel for the complexity of what's going on. More questions. You're gonna look into that templates folder and see how many templates you have. How are they organized? So are they all just jammed in one folder like Bartik or are they in multiple directories? Like Umami has a components folder that has blocks, navigation and search, content folder and layout. So just get an understanding of how it's organized or maybe somebody did it and it grew over time and it's not organized and now's a good time to just reassess that. So we've gone through the files, we've gone through the folders and now we have a better understanding of our theme but let's take a big step back. You might wanna just look at the project as a whole. This talk was inspired by a project that was about three to four years old and so when I was looking at this, I wanted to look at recent analytics and see what kind of browser support. Things have changed over the past four years and I wanted to see if the users had come along and what kind of support I had. Was very surprised by the very large increase in the mobile traffic. So right away I'm looking at this through the lens of my users and how to optimize the theme. The other great thing at our agency might be another developer that took that on and I roll in to just make some enhancements as they move on. Is the original developer available for questions? One thing I love to do is ask them to navigate the site after I get a good feel for it and have them navigate the site with specific tasks. They're gonna tell you some great stories, maybe some horror stories, hopefully some success stories about why things were built in a certain way. That might actually be the start of it. Well I would have done it this way. Really the goal is to just find out how it is and why it was built that way and see if there's room for improvements and refactoring as you're going into it. The most important thing is listen, don't lead them. But at the end of that conversation kind of review their findings and tell them like oh maybe this part needed a little bit more documentation or I could not find how this section affected this section. So with all of that, your audit is gonna lead to action. So you have a good feel for what's going on, but the next part of this is I'm gonna show you some helpful tools that are really CSS focused to help you write more efficient themes. And we're gonna go over four tools. First one is called Parker. The next one's Analyze CSS. The third is a fairly new one and I'm pretty excited about called Project Wallace. And the last one is just I wanna cover Lint. So let's start with Parker. Parker's Style Sheet Analysis Tool and it runs metrics on your Style Sheet and it really helps report on the complexity and it gives you numbers that can tell you kind of how complex it is and what's going on. So how does it work? You go to GitHub and you can clone the repository. You install it locally with NPM. And again the slides are up, you can click on these links and highly encourage you to give it a try. You can measure local CSS files or remote CSS files. And the awesome, awesome thing about it is it outputs JSON. So let's take a look at the Parker JSON output. By running it, I'm gonna run it on a local CSS file. That's from a D8 project. And it's a sub theme of the Zerb Foundation theme. And just to let you know that sub theme uses a lot of the Zerb files. Just to let you know that sub theme uses a lot of the Zerb Foundation framework. So we're pretty much taking Zerb Foundation wholesale. So this is what it looks like. For the project, we used Grunt and we grunted all the theme into one CSS file. And that tells us the size of the CSS file, 192K. And then next up it tells us like rules, selectors, declarations. I'm looking out. Does everybody remember what all those are? I didn't either. So let's have a little CSS 101. Everything in the green on the screen is a CSS rule. H1 is a selector. Color is your property and the hex color is your value. So let's take that little cheat sheet, move it up into the right and let's look at these numbers again. So we have that many rules, that many selectors and declarations. Again, it's just numbers that are just kind of telling you right away what's going on by just running this quick command against your theme CSS. Pretty cool, but what are identifiers? So identifiers are not IDs. These are the measure of the parts per selector. If you look on the right hand side of the screen, an example is just one class is considered one identifier. All the way down to the bottom, you can see five identifiers. So now that you know what identifiers are, let's go back and look at that number. So really what do these values mean? Are they too high? Are they too low? Are they just right? So your mileage may vary from theme to theme. I encourage you to run this on a few projects to get a good feel for these initial numbers. But the next part of the JSON is pretty exciting. We're gonna go through it. It's really gonna help you provide insight into what's going on with how you're styling your theme. A great one is the selectors per rule. Again, keeping that cheat sheet in the top right. You want that rule to be as close to one as possible. If you have a lot of selectors per rule, it's suggesting that we're applying the same styles to a number of different selectors. If that's the case, then perhaps we could create one class to catch all the styles in this. Let's look at an example of that, of how to reduce the number of selectors per rule. So on the left, you see the styling for input boxes and a text area, basic styling, right? This is a great opportunity to write just one CSS class to reduce the number of selectors. So now, if we write this as like C for component, input text, and put all the styling in there, now we don't have to just keep adding the markup styling to it. We just add a CSS class to all the form elements right from the start. So it's a great way to reduce that kind of complexity. And if it needs a change, if design says, oh, it needs to be a thicker border or the select state needs to be different, we just do it here. So next, your identifiers per selector should be between one and two. Anything that's higher than two means that we're being too specific with that CSS rule. I'm pretty guilty of that. And we're really limiting the ability to reuse our styles. We're not writing a class-based theme. So that's why you wanna get that number between one and two, to have really class-based reusable styles and patterns. The next exciting thing is the specificity per selector. I stayed up late and just said in the mirror, specificity, so I could do this at 9 a.m. But let's look at it and see if I can keep it going with saying specificity. So what is it? Let's take a look. I know I needed a refresher as I was looking at these numbers. So you can generally read specificity values as if they were just a number. The higher the number, the more specific the rule, and the more likely it's gonna win in the style wars. That sounds really funny. So clearly a 1,000 is gonna win over a 100 style. So if you look on the screen, I have just the zeros, but on the left is an inline style. That's gonna always win over an ID. IDs are always gonna win over a class, and a class is gonna win over elements. Let's look at a few examples just to put it together. So this LI has an inline style, and it's gonna be specificity of a thousand, so I know that's gonna win. Bad idea, theming, right? We can do better. Here, the value is 113, so because we have one ID, one class, and three elements. Just one quick reminder for specificity, this isn't a true base 10 numbering system, so I could have like 0, 1, 5, 13, if it's pretty crazy, but generally this is a good rule of thumb for determining what CSS style is gonna win. At the end of the slides, I have a great CSS tricks article that I use and put these together from to help remind you of specificity, because I don't know about you, two sessions, it's gonna go away, and I'm gonna need that resource when I come back. Last things, universal selector is zeros and important is an automatic win. It's like putting it in the millionth placement. And importance win through the cascade of your style sheets. So if you had an important at the beginning and one at the end, the cascade, the one at the end is always gonna win. So speaking of importance, that's what Parker tells you. We're gonna get a little bit more to that later, but it counts the number of importance as well. So now that we know more about specificity, let's go back to these numbers. So if we look at specificity per selector, and we know that class based is like a 10, it looks like when I run this against the theme, it's a 25. So I wanna get that as close to 10 as possible. Your mileage may vary. You might have a certain section of the page that you kind of need to what I always call quarantine your styles and make it really specific so things don't bleed out of it. Like navigation, ULLI lists and navigation need to be pretty specific. So this rule is, again, just kind of a guide post. If it's super high, you know, or you run it on three different projects, hopefully these numbers start making sense. But the whole goal of this is these numbers are gonna help you understand what's going on and write a better class based flatter theme that's gonna be more reusable and shared. Another thing, the total ID selectors. Ideally is zero, again, not always the case, but as we all know, you can only use one ID per page. So again, it's not very reusable. If I use an ID on a button and there's four buttons on the page, that's not valid. So again, it's a good indicator of how many IDs you have specified. More things, Parker tells you, again, as I said, the counts up all your important keywords. What I really love about it, too, is it tells you all the total media queries and spits them out on the page for you. Again, using Zerb Foundation in this site might use a couple other, a couple other, it's using some other CSS. It's gonna grab all of those and just put them in there because I compile everything into one file. The other great thing is it covers, it counts up all your colors and spits them out as hex values. So you can go back to the design team and really dial in those four different shades of red, right? And just write one variable and get it dialed in. Pros of Parker, it helps you measure the file size. And again, when you output at JSON, we're gonna talk about this a little bit later, is it allows you to measure that over time. So it takes a cut of the size of your file at that time. It gives you metrics for that class-based theming. It allows you to find all those color values and media queries and all those importance to investigate deeper. Cons, I'll skip the first one, but it's last updated 2016. And I thought, boy, that's a little old. Is there something a little bit newer? And that led me to analyze CSS. Very similar tool. So moving on from Parker, let's talk a little bit about CSS. It does a lot of the same thing, test, weigh, and analyze your CSS to reduce that complexity that you have. Very similar to Parker. You go to GitHub, install with NPM, again, measure local CSS files, or you can point it to remote CSS files and output in tasty, tasty JSON. It tells you a few other things, but it covers a lot of it. There's great documentation on the site about these values, but it just gives you a little bit more. The thing that I like about analyze CSS is it gives you the offenders list, so it tells you the most specific value in your CSS. So then you can investigate and say, oh, this is the Instagram post that I'm getting from another third party, and I really wanna make sure all the styling inside of there is kinda quarantined to that part of the page. So the pros of it, it has additional metrics compared to Parker. I love the offenders list, and it's updated and maintained. I'm gonna move on to the third tool. Again, these 30-minute sessions go kinda fast. Go to the slides, but I wanna talk about Project Wallace. It's a style sheet analysis tool that keeps track of metrics over time. Really excited, Brian Perry sent me this at the first part of the year, and it kinda put a lot of this together. It's by a gentleman named Bart Veneman, and he's from the Netherlands. And what this does is it's an online site, and it gives you an online dashboard. The talks that I've given this talk a few times, and because it presents JSON, you can do a lot with it. What he's done is he's written this and has a website that does a lot of the same things, and he's just taking that JSON, tracking it over time, and putting it in a nice graphical form. It's really, really pretty cool. So you can go to the website. There's two different options. First is go to the website, you can create an account. Again, you give it your project, and it can create some nice graphical dashboards, and then keep visiting the site, keep giving it the cuts of the site that you want, and it helps you track it over time. He's also on the Twitters there as well, and keeps it updated and maintained. There's three ways on the site, is you analyze it by grabbing the CSS from a single webpage, so you can just put a hyperlink to that CSS file for your project. You can copy and paste raw CSS, so if you wanted to break a certain part of your theme away, if I didn't want to count all of Zerb Foundations and just look at mine over time, you could just cut that in there. And the other really cool thing, I haven't tried it out, but you can use a webhook and you make it part of your continuous integration. So all the details are up on the site, but it also has a command line interface, pretty much exactly like Parker and analyze CSS. Same thing, you just need node, install local, point at local, or remote CSS files and outputs JSON. Pros, it's got improved output. He's doing a lot of the right things, and he's also tracking it over time. He's not just saying, here's this tool, go for it. He's taking the concept of what I'm gonna get into here next is tracking over time and really understanding how you're improving over time. The cons, it's a really hard con. It's free for only one project and there's a cost to it, but again, he's giving a lot of features and benefits. So it's a very reluctant con because I think the pricing's pretty good for what you can get and what you can share with your teams. Quickly, going over lint. Linting is a process of running a program that's gonna analyze your code for potential errors.  I can't stress enough, it catches mistakes, it saves your bacon and makes you write better code. It doesn't help you write better code, it makes you write better code. So if you set it up right, you just can't run and output your CSS without fixing the mistakes and adhering to the rules that you set up in the project. So linting is great.  Again, audit leads to action. So by putting it into action, we've looked at all this, we've seen the CSS. Ideally, if it's not there already, we're gonna look and want to apply some possible atomic design principles. Maybe there was a component written and then it was just copy and pasted three times and now's the time to abstract that up and write a nice abstract class-based reusable part of the theme. Last mac structure. If it was all just piled into one CSS file, you're gonna want to, you might wanna just start breaking that out into partials. Another good opportunity to maybe start rewriting slowly those partials into BEM. Again, links at the end about all these concepts. SAS, these tools are outstanding to help you start writing variables for those breakpoints that we saw, for the colors that we saw, maybe for some fonts. Now that you've kind of rolled around in your CSS, it's a good time to see if there's mix-ins or functions you can write to, like for all the buttons, so you don't have like 50 different buttons. You can write a nice mix-in and send it your button variants in one place. JavaScript. Always, always use Drupal behaviors and include JavaScript as libraries. Yay, D8. Only include JavaScript when you need it. And as you're picking up a theme, if it's not written that way, now's a really good time to make it more better trademark. Okay, ultimately, we want to establish the metrics within our theme and we're gonna measure this over time and these tools do a great job with that. So what I'm proposing is inside of your theme folder, you make a metrics folder. And what you do is you use one of these tools, output that JSON and put it right in that metrics folder. So right away, you leave here, you make a cut of a baseline of where your theme is at, it'll measure your size, it'll measure your specificity, it'll do all of that. And then sprint by sprint, if you can put these tools as part of your automation, sprint by sprint, you can measure this the size of your CSS over time. So when the phone call rings, when the phone rings and the call says, hey, the website's slow, you can go back through and see what was the spike? Was it integrating this part of the CSS? So how did it bloat over time? Otherwise, you just say, I don't know, I think it was fine, you know. So you can capture a lot of these things. Other ideas, since it can be anything, you can put alley scores in here or just any other metrics that you wish. Lighthouse has a good export of that cut of your site at that time sprint by sprint. And then you can do cool things like maybe diff your JSON. And if you don't know, so measuring tells us where we've been and gives us clues on how to improve. Thanks. Questions?


To determine the impact of the secondary pharmacogenomic findings for these patients, we decided to start this study, which was recently published in molecular genetics and genomic medicine, and really discusses the pharmacogenetic findings that we found using whole exome sequencing on diagnostic odyssey patients. Whole exome sequencing is a test that looks at all of the genes in your genome. So some of the benefits include really not having to know which gene in particular you want to look at. So we were in the early stages of starting to use exome sequencing for the care of these patients. And what we started to realize is that there's other information contained within that no one really would know about unless you're digging through it. Because you get a lot of results back when you get an exome result, right? And within those results, we were starting to find pharmacogenomic variants listed. And of course, that wasn't necessarily related to the disease that we were searching for an answer for, but it's an important result that can be used for patients' care. In looking at our cohort of patients, of the 94 patients we evaluated for pharmacogenomic findings, the majority were young, median age of 10 years at testing. The majority also had a neurologic component to their clinical presentation. Seizures was one of the most common phenotypes described in their reason for referral. And the majority of patients had at least one pharmacogenomic variant reported on their clinical west test and one-fifth of patients were taking a medication at that time that could be impacted by that result. I think if you look at our patient population, most of these patients were, I think the average age was about 10 years of age. Usually we don't worry too much about medications when it comes to this population because they're usually not taking a large number of medications. We're usually concerned about a larger number of medications in the older population. However, through this study, what I came to realize as a pharmacist is that pharmacogenomic matters in almost all age groups. Why? Because some of our patients were taking anti-depressants. Some of them were taking anti-seizure medications. Some of them were taking pain medications. Some of them were taking muscle relaxants. All these medications or some of the medications are metabolized by some of the genes that we identify in our cohort. Meaning that pharmacogenomics could, at a certain point, help these patients who are currently taking medications in our population either make changes with either the dose or change the medication to a different medication. So one of the important considerations as we were looking through the results we got back on these patients, the testing company is reporting back the specific variant that they identify in this patient, and then referring to as one of these star alleles. But to get to the actual patient's genotype, we have to then infer if no variant allele is identified that they are the wild type or star one allele. This is not reported. It's only inferred in the absence of any other genetic variation that you would detect. So if we look at these reports and know that they're only reporting on a subset of these variants, it may not be encompassing all of the actionable variants present in the population. The star alleles become very important in pharmacogenomics because it helps to predict how a patient may metabolize a specific medication based on their genotypes. So we wanted to assess how accurate we were at inferring this star one or wild type allele as it's really important to then take that genotype to establish the metabolizer phenotype that will then be used to suggest the proper medication dosing and medication used for these patients. And what's really of note is that in the African population, the reported alleles make up a far smaller proportion of the total alleles in this population. But that the non-reported alleles are significant. So for these patients, if we were reporting on the CYP2C9 gene and did not detect any variation and were to infer that they actually had the star one allele present, the wild type allele, we may be incorrect a significant proportion of the time. And that information would be used potentially to guide therapy for those patients and could be wrong. For me, operationally was troubling because I thought here we have some information that can help in this patient's care going forward either right now in terms of informing current medications, but also in the future they can take that information with them and make sure that the people that are prescribing medications for them understand their pharmacogenomic variants and hopefully can use that to provide the right dose or the right type of medication for them. As we move along with Holoxam sequencing, our ability to interpret this data is getting better and better. So as we get this genetic variation back, we're going to know better what to do with it, what it means for this patient with regard to a genetic condition they may have, with regard to pharmacogenomics, and our ability to manage this data is going to improve with it, especially as more and more patients are getting this kind of testing. We'll get it in the right location so the right physician or care provider can use this information to guide the patient's care decisions. One of the things that we really hope as an outcome from this paper is that people become aware of that and begin to build systems to be able to address these secondary findings and make sure that they're appropriately identified within the patient's medical record and appropriately communicated to the providers that will be interacting with those patients.


Holy Bible, King James Version, Leviticus 11, Leviticus 11. And the Lord's back unto Moses, and to Aaron, saying unto them, Speak unto the children of Israel, saying, These are the beasts which ye shall eat among all the beasts that are on the earth. Whatever parteth the hoof whatsoever, parteth the hoof and is cloven-footed and cheweth the chud among the beasts that shall you eat. Nevertheless, these shall ye not eat of them that chewed chud, or of them that divide the hoof as the camel, because he cheweth the chud, but divideeth not to hoof, he is unclean unto you, and the Cony, and the Cony, because he cheweth the chud, but divideeth not to hoof, he is unclean unto you. And the hare, because he cheweth, because he cheweth the chud, but divideeth not to hoof, he is unclean to you. And the swine, though he divide the hoof and be cloven footed, yet he cheweth not the chud, he is unclean to you. Of their flesh shall ye not eat, and their carcass shall ye not touch, they are unclean to you. These shall ye eat, of all that are in the waters, whatsoever whatsoever have fins and scales in the waters, in the sea, and in the rivers, them shall you eat. And all that have no, not fins and scales in the seas and in the rivers, all that move in the waters, and of any living thing which is in the waters, they shall be in abomination unto you. They shall be even in abomination unto you. Ye shall not eat of their flesh, ye shall have their carcasses in abomination. Okay, this is about eating. What you can eat, I have no idea why I highlighted this. Creepy. We're gonna skip a few of the eating parts, the schwarver's work. And we're gonna go to, and every creeping thing that creepeth upon the earth shall be abomination, it shall not be eaten. Will you eat the bugs? You will not eat the bugs. The Bible says you shall not eat the bugs. Okay, so that's pretty important.  According to the Bible, Leviticus 11 verse 41, and every creeping thing that creepeth upon the earth shall be an abomination, it shall not be eaten. Okay, Holy Bible, King James version, Leviticus, the third book of Moses called Leviticus. Okay, and this applies to Muslims and Jews as well. Okay, number 11, Leviticus, number 11, verse 41, verse 41. Let's see if this will focus. Verse 41, and every creeping thing, right here, where are we? Right there. Right here. Okay. And every creeping thing that creepeth upon the earth shall be an abomination, it shall not be eaten. Nice find. Nice find.