Well, thanks everybody for coming to this core conversation about usability and as you see from the title we are going to talk about usability especially for side builders and administrators, and we come to that in a moment But first of all... This is my laptop. Rachel? So I'm a site builder primarily. Any code I write is usually for patches for Drupal call really, on this side. The type of stuff we're going to be talking about. I work in the UK as a freelance so if you need any work doing, give us a shout. I'm Antje, or Ifric in the Issue Queue. I'm a biologist by training. I started building lots of websites for the kind of NGOs I'm working with, and this microphone is in a weird space, and I started actually with writing documentation, and then I realised that it's really annoying to write documentation to explain people how things work when they don't quite work, so actually I'd rather improve the usability so I don't have to write documentation. So I've been part of the usability team for quite for a year or so now, and we have been talking about usability and issues about the admin menu for doing a few sessions, and I'm glad to see that there's even more people and we can show you some of the issues we still had a year ago and we still have them. But first let's ask a bit about who are you in the room actually? Who is working on core and contribe modules? Who's more side builder? Who's the front-ender or themeer? Who has to change the usability of Drupal to make it useful for your clients? Brilliant. And then we have one other question with regards to the admin toolbar that we have in Drupal. Who's using the toolbar in a horizontal line? Who's using the toolbar mainly in a vertical line? Did you know there's way more options when you put it vertically than if you have it horizontally? Which means you can actually go... You don't see a lot of these. You don't see them on the horizontal screen at the moment. You can go three levels deep without any new page load. OK, but that explains why when we write an issue nobody actually figures this out. OK, so usability. The main question is of course who's the actual user we're talking about. And in this session we talk about side builders, front-enders and advanced administrators. The side builder is usually the person who uses Drupal as a tool to build something for somebody else. So you use Drupal, but you also make it usable for somebody else. The front-ender also needs to use Drupal to actually prepare the site to match the design. Front-enders typically also need to access the display, this content type, display these fields, those issues. And the administrator are usually our clients, the users that use the website on a daily basis to do the actual work. So for them the finished Drupal site or the finished whatever you built with Drupal is their actual tool to do the work. So in the context of this session we talk a lot about the kind of more professional users, the users that have actually invested into Drupal by spending time learning it, by spending their day hours working with it. And they are also the ones that are quite often involved in the question on whether to use Drupal for the next project. I mean they are the people who have the ear of the person who is paying your invoices. They get to say whether you continue to get paid. For the people in the back just come in and sit down. There is one more chair in the front and there is space on the floor here as well. So we are not explicitly talking about the kind of first time user about the people who want to set up a website in a day or so. But we are pretty sure that the improvements we envision will also help them. But mainly we do actually talk about people that will spend their time figuring out trying to find the same page again and again, this kind of things. So what can we improve? The navigation, that's mainly the admin menu. The permissions, UI texts and UI and UX standards. Are we going to go through them one by one? Absolutely. Now, as Dries mentioned in the Dries note, there's a lot of people talking about adding new technologies there. Adding things like maybe using a JavaScript framework to make it more a richer experience doing the admin. Even if that was done, the main fundamentals need to be right. So work that continues now, even though we are using HTML to present it without JavaScript particularly, it still matters. And it will still matter even if we have the most amazing JavaScript framework in the world running the admin interface. All of the things we are going to talk about today still completely apply. So about the admin navigation, let me just give you three examples on the... Where do I make this specific admin page visible for some users? Well, you first list all users and then you go from there. That's the permissions are on the people's page, which you might know but it's not obvious. Where do I edit or translate a specific block on the page? You first go to the layout page, where the layout of the whole site is defined, and then you go to the custom block library and there you can edit or translate a block. Or where do I see all media items with media in core? Well, actually you list first all articles and pages and so, and when you have done that page load, you go to the media items. So basically what we're doing in the admin menu is we have to teach our users detours. We have to tell them that if you want to set permissions, you first need to go to people. If you want to see media items, you first go to content. If you want to change the welcome message that a new user gets in the email, you go to the account setting somewhere at the bottom of the page. So, instead of providing a predictable interface where you could say, I think I should be there. We're actually teaching people you can't go from A to B. You have to go from A through C to B. There are some easy changes for that. There are some issues for that. For example, there's an issue to actually change the content page to make it something like the structure page. So you wouldn't have to go through note content to go to media content. There's also issues about moving the permissions and roles pages to move it into configuration of the user account and not as part of the here's all users of your site. We would like to move the custom block library from block layout to the actual content because they are content entities. But in order to do that, we will also need to change the permissions because you can only go to that custom block library page to even if you want to just change the opening times of your shop for Christmas, you have to have all the permissions to move all of the blocks, to go to that tab on that page, to then have some editor type in that you're going to be close on Christmas Eve. That's not the same workflow. It also means you have to give way too many permissions to people. So we come to that later. So as an example, if you think about it, if somebody in the office at the client has the ability to change the telephone number, which is a reasonable expectation in your profile, you're also giving them the permission to move things around. If they move them around and it breaks the site, it's your fault in their minds. We know it's not, but actually it is. It's your fault, the site's broken. And coming back to the content page. You know, the content page actually acts different than all the other points in the menu item because it's actually loading a view of all nodes, which very much made sense when we moved from Drupal 6 to Drupal 7 because in Drupal 6 we had, under content, we had create content types and the content and some other things. So with the move to Drupal 7, it was decided, okay, content should just be nodes. That was fine in Drupal 7, but we're now in Drupal 8. Content is not only just nodes. Content is also media in core now. Content is any custom entity you make. But still we end up with something there. This is a screenshot from a very simple site I've been working on, that already has 10 tabs on the content page. And I can't just make menu items on the content because that page is kind of locked in. So we need to work on that. It will break some documentation that says, you find content if you click on content, but I think we need to actually accept that we break that. So this is just tabs on the content page and you have some examples. So on sites that I've built for clients recently, I've been adding entity types, which kind of new for me is great, for things like points of interest all around the world. Now, I want to have all of my content of the site in one place so it makes sense to the client. That's currently quite hard because, as you can see, it turns into this crazy mess of tabs and it doesn't make sense to the end user. One of those links is to change the whole of that content page, as it's described at the moment, to be more like structure. So what you'd have is you'd go to content and then you'd see a list of the different types of content. You would see nodes, you would see media, you would see files, you would see my custom point of interest because it's then easy as me as a module developer to add that link there. At the moment, it's kind of a mess and we need to get there. So there's an issue to actually change that. We need to communicate that well because it will mean what we want to do is encourage people to work consistently across lots of modules so that we can do that. All users care about is consistency. We can make decisions about what we think is right but it needs to be right for everything. There's more space on the floor here. People want to come in. There's still one chair here. So, yeah. Okay. Yeah, come through seriously. You can sit on the floor here and I'll try not to stand on you or anything. It's okay. It's not promising but I will try. And yeah, if you can make a bit of space in case there's any... Thanks. So, yes, as what we see when we build sites for users that it's much easier if we can provide them with something that's consistent. If I can tell them, if you want to edit something that's content, then it's under content. A block with your contact details or so should live somewhere where you can actually find it. You shouldn't have to go through other detours. So there's a number of issues that are open and that need work so you're happy to come and join us working on that on Friday during the sprint. And there's also one longer term issue. We would like to actually develop some kind of guidance for module developers to see where should I actually put my module? Because currently when you make a contrib module you can just pretty much put it everywhere. You can put everything under structure or configuration or you can make a new top-level menu item or you can spread it over the site. There's no kind of guidance which means it's also not predictable for users to find something. We don't want to go to kind of a long endless bike shedding of saying this page should live here and this page should live there. What we are trying to develop and have been discussing that in different groups since death days in Milan, I think, is if we could come up with something like five questions, does this concern users? Does this concern content that's actually produced on the production side? Is this something you actually need to access on the production side? If we can maybe find a kind of five-question pick-your-own-adventure and find a predictable way of where to place admin pages, we would probably also provide something that's more predictable for the users. And it would probably mean we could also turn off whole sections of the admin menu on the production side. Permissions and access, we'd already pointed out that there's problems with permissions. Again, let me give you three examples. Any user who needs to fix a typing error, any user who needs to edit the content of a block, can remove any block from the site. It's actually quite scary that art. Yes. I think site builders will talk to different site builders and lots of us are making a workaround. The problem is we can't move this custom block page somewhere different. I've been starting to simply duplicate that page and put it somewhere and not tell the user that they actually have this permission to change these other things and discover it because there's only one single permission for blocks. Anything you do with blocks is done with one single permission. So we can't fine tune this. It's currently done with one permission. There's an issue. They're saying that we should be changing that. Anybody who wants to edit a taxonomy term via the admin menu, for example to add images to taxonomy terms, any site where you don't have a page per taxonomy term, well, if you want to edit a term like that, you can actually change the default language of the vocabulary. That's not necessary related. I need an editor when I have a free tagging field, for example, once in a while to go in and say these two words are actually the same. I merge them or fix a typing error or add an image. I don't want them to say, this should all be in English or German, but they can. This is the page they see when they want to edit a taxonomy term. Any user who needs to access one single page on the structure, for example, the custom block library, gets 10 configuration pages without any admin items. There's only one permission that says, see admin pages that gives you access to structure, configuration and help in one go. If you don't have anything on the configuration pages, these 10 submenu items still all appear. Every single page might say, you don't have any administrative items. That means I'm providing my users with an admin menu that is cluttered with empty pages. This issue is nine years old. My experience with permissions is that the lack of not being able to fine tune these permissions means it puts the integrity of the site I'm building at risk and it's confusing the users. I can't seriously hand out a site to somebody who only needs to translate content and give them access to, maybe to remove the branding or remove the main content or so. We need to have more permissions. The usual reply is, the permissions table is already so long and so confusing. Yes, it is. I'm looking at that permission tables when I set up the site for the users. I do that once or a few times. Then I'm done with it. The editor, the administrative users that are using the site on their daily work look at this admin menu every day. Even if I'm dealing with a table from hell that goes from here to somewhere, it's still a better usability for the end product. If we can actually have more permissions, if we can have three permissions for blocks, for example, instead of just one, we should fix the permissions table. Yes, that's an issue. That's also very long-standing. It's as long as the permissions table. Yes. But if we wait for the permissions table to be fixed, we are still putting sites out where every editor, every translator can remove your branding from the site. So I think we should just live with not having the permissions tables fixed before we add... There's also a situation where you've got those conflicting issues. The thing is, we've been living with the permissions table being a bit long and kind of got away with it for probably about nine years. The other stuff was being cut out of place. It does, but because the permissions don't exist currently, and we're reticent to put them there because of the permission table, it should be the other way around. We should have the permissions, which means that we're more likely to realise that it's a proper issue with that table and do something about it. Because at the moment we kind of live with it, and maybe if we do the permissions properly, it will force our hand. More people in this room and other rooms will go, hey, let's do something about that. So how about we work on both of that parallel? We add more permissions and somebody else works on the permissions table and whoever gets first is done first. There's no reason... There might also be other options of dealing with this maybe in the... Oh, short term. Where did that go? What did you do? I'm missing a page. Oh, no. I've actually asked people on how they decide to actually set their permissions, and it's a bit like... There isn't really any kind of standards for it. So quite often we end up with a module that does an amazing amount of things, and everybody who gets access to that module can all of these things. And then stepping back and saying, ah, should we now actually remove some of them? Is an extra work, but I think it would be good if as module developers you can get some guidance on saying what extra permissions should there be? It shouldn't be just be, there's one permission and be damned and figure it out. We could, for example, say if a task is more a site building task, a task that is done before the site goes live, it might need a different permission and anything you do with the module when the site is on the production site. That would be a very simple two different permissions. You could also say if things end up on different pages, there's probably a reason for that. So if part of your functionality of the module is on one page and the other part is on another, maybe that's a reason for two different permissions because you're clearly doing two things. We could also hack something as simple as we have the bit of the help text at the top of the judgment page. Maybe we could have simply having as simple as a link here saying the access to this page is controlled by this permission and if you click on it, you just come to that permission. Now especially beginning site builders end up on the which permissions do I need to enable to get to here or there. So we quite often see in sites that are built by people who are less experienced that too many permissions are given, simply because you just want to make sure the user can act something because that's better because otherwise you get the calls or the issues on the I can't see and then you just go and say oh I give you a permission. So there might be different ways of tackling that but I think we do need them. User interface texts. That's another issue and that's text like the label on a field, the page headings, the page headings and tab headings and secondary tab headings but also the kind of blurbs on a page that explain you what this admin page does as well as all the help text or the full documentation on Drupal.org and that's a quote from a session yesterday. We find model developers and core developers saying well I'm happily sitting now in 12 hours to write this code but I'm not going to spend 30 minutes on writing any help text for it. And there's lots of good reasons for that. For example on the, well I don't actually know what to put in it. Am I making an explanation here, a documentation for my other developers? Do I explain something to a site builder? Is it something for the end user? Is it so far disconnected that it lives on Drupal.org on a white page where I've spent months and months working on this and now I sit in the front of this white page and I have to write up a documentation. I don't even know anymore what needs documenting because as a module developer I know everything inside out. I don't know which the things are that people don't know. Or it's also the, I'm not a writer, I'm a developer, I can write the code but I don't know how to write a good text that helps people along and that's even more the case if you then also have to write it in a language that's not your native language. So we have lots of UI text on the sites that are just going to end up there. We have some guidance about which words to use but they're kind of long and rambling. They're actually deaditing. So as a community we should discuss only who should actually write this documentation. How can we help those new users look at your module for the first time to maybe write a documentation that's useful for them? Also quite often when you look at a module and you're finally figured out how it works it's very hard to go back and say okay I make a patch to change this text because you continuously feel like you step on somebody's toes. Sometimes it's like even if you fix a typing error or if you say your introduction doesn't make any sense to me but it still feels like we are trending on people's toes and we should find a way of encouraging people that use our modules to actually say here's room for improvement or the other way around maybe a module developer can actually say here's my module can somebody who actually knows about writing help me with writing this text? So who are the module developers here? There was a few, wasn't there? So when you want to look for people to get involved how do you go about that currently? Do you just kind of wait for it to happen type thing? Fame. All right. It's sorry. Oh I'm just announcing across. Yeah. I'm very excited when someone comes in with a little issue and try to motivate them to help out and do a little planning on doing it. But make it nice. You don't want someone to go through a nightmare but it's like someone comes up with a little figure I think you need a figure like this but I can't write a patch yet. Let's help you out and do that. I mean the next time they don't watch it I'm already making this. Rachel can you repeat for the recording of the salient Okay so one of the things that Barthas mentioned is the fact that when somebody comes in to his issue queue he will obviously help them deal with the issue that they came with but try to take them that little bit further and engage them so that they continue to be interested in doing other things. Is that a reasonable description? Okay cool. Absolutely there's nothing wrong with having self-interest in terms of writing a a module that's okay. Okay so so who at Drupal commerce? Oh at Boyan Z. He basically told me a while ago. Could you just get to the microphone? As soon as he's speaking. So to speak on behalf of Boyan what he told me a while ago was he tries never to answer someone's question in his issue queue except with a link to a recently written handbook page that he wrote for the occasion to answer that question so we won't have to do it again next time. As a module developer how about if you actually make an issue for your own module and say this needs documentation this needs theming or this needs design how we turn the this a bit around because now it always feels on the as somebody who has done documentation you have to come to the module I don't know who needs help but what would be cool perhaps for that kind of thing is that a way to flag we need help for this on the module page rather than creating an issue many people won't look in the issue queue looking for a ticket like that but might be able to if a developer could flag in some way on Drupal.org on the module page hey I would like some people to help me write some documentation and a visual flag there so that they know the person writing the module is open to that that might stimulate people to contribute where they might be more hesitant if they're afraid of stepping on somebody's toes I really like that as an idea and there's nothing to stop you as module developers already doing that because you've got complete control over your modules introduction page however what would be nice is if it was done in a consistent manner because that way people would see it in a consistent manner and then it would come forward I think actually what I would do is turn that back on the module developers and say okay how are you going to do that how are you going to get together come up with a consistent way of doing that and do it you can do that it's going to make your life easier absolutely great you're here, you're all together get together tomorrow make it happen could make a ticket and then have some kind of icon on some kind of visual representation that everybody agrees upon and link directly to the ticket from the introduction page that way you cover both the ticketing part and the fact that it's visible but of course you'd have to be able we as a community would have to find an icon we want to use or some standard phrasing we want to use to do that I think that's one of the great things about Drupalcon is that quite a lot of you are all in one place get together, talk absolutely one of the great things about being at a big event like this is you could physically I was going to say physically grab people but that might not be quite right it's just the way I talk talk to each other, find people group of developers creating contract modules talk to each other agree, get the whiteboards agree a standard write it up I would suggest in the project Drupalorg Q would be a good place to do that agree it propose it make it happen you are more than capable and you have the authorities to do it you have the facilities to do it you just need to talk that would be amazing amazing thing to do it might be counterproductive to what we are trying here but I usually spend more time on Drupal's tech exchange than on Drupalorg documentation and I subscribe to keywords that relate to modules that are made and they are published and then try to help it because then I get the feedback either it helped them or it didn't help them and also I get to know the different use cases that people have and I get to know the documentation which I did for a module long go which is probably now a bit out at it the documentation then I don't really know who is reading this and if they understand it or not and if it relates to any use case where if the starting point where I started this thing is really a good starting point where people want to start to read or if I'm coming from the wrong direction or something and if they have some ideas and then if they actually upload a page then it's probably I'm not happy with it anyway so then it's more important that they actually explain what they want to achieve and we discussed that yesterday in a boff already as well on the that there's lots of documentation we are not quite sure for whom it actually is or what they need to know so one of the proposals was also on the maybe we should have actually a few questions that we could ask on the what does this module do does it include does it bring any new field type for example or those kind of guiding questions to actually get some documentation started for example let's talk a bit also about UI and UX standards because as I said consistency would be really great and I think in Drupal 8 we have actually included a lot of that for example the order of the cancel, save and delete button and how they should look like there are kind of standards for that but if you look on Drupal.org you'll find a page that says here are the UI standards for Drupal 7 and we need to actually see if they still apply and we should go and actually look at at Drupal.org we should actually look at our core modules whether they really all follow these UI standards because if we can make core very consistent and also explicitly say why are we doing this why do we have the add to new entity button always at the top there saying it's a primary link or it's always getting displayed in the same way then it should also be easier for contribe modules to follow that that kind of pattern, that kind of standards because we can make core very consistent and then you install a contribe module and suddenly the yes I want to delete this purge button is really big and blue and there are some other issues where you think hold on this is the other way around why is this now in one really long form while everywhere else we have several forms next to each other so if we can make core consistent we actually have something that we can point other users to for contribe modules because most users most site builders they work with contribe modules they're not only using core so we also need to make this space across the whole across the whole Drupal ecosystem we can both make Drupal core consistent but we can also write down what that consistency is it's not currently there at the moment and it hurts you I saw a good example in something that was tweeted and this is from the Apple website the Apple developer website every new user interface widget process whatever you want to call it they describe not just what it does and how to code it but they describe how to sensibly use it and what things should look like it's not it's not complicated large amounts of content it's not unreasonable for us to create and be just as good at doing this as Apple are these it's just saying put things in sensible places this bit about augmented reality well it's augmented reality use the whole screen why would you not do and it's saying reasonable things each of the kits that they do they describe what it does and how to use it as a developer all there and we can do this the only hesitation I have there is what's reasonable for one person isn't necessarily reasonable for another I was in Morton's presentation on his 11th theme and I liked a lot of what I saw that's really in some cases very different to what we're doing right now with Drupal and Drupal Core there were things I didn't like and I think I'm actually absolutely sure that there were other people in the room who had the exact same thought as me except that the stuff I didn't like they liked and the stuff I like they didn't like so we're a community while Apple is in the end a top-down company so it's easier for them to realise this because in the end there's one person who decides yes it's this way and it's a lot less obvious for us to do it I think that core should be consistent I do think that there is a danger in enforcing consistency even at core level because it might put off people as much as it helps them and I think also one of the things that we can provide is making sure that lots of the functionality actually stays in a way that it can be customised so if I don't want a certain admin if I don't want a certain menu item I should be able to just disable it that's a great thing with having views in core for example that most admin pages are views or most listing pages are views so if I need to display a certain information to my users I can do that we don't actually have to go through the what is the 80% use case for this table and fix it if we can keep things in a way that the site builders can customise it using the default tools, default widgets then it doesn't actually make any difference what kind of admin theme we put on top of it and it also means that if you build your module following these you can either put 7 on it or 11 or whatever admin themes and it shouldn't break so I would have loved to actually go through the session and say what are our UX standards how can you apply them what are the things that we are discussing in the weekly UX meeting and I still feel that we still have to actually say why do we need UI standards where do we need UI standards that live on the same kind of level and importance of coding standards I mean we have a coding standard that says a line should be 80 characters but if that would be a UI standard we would probably be in comment 267 and still discussing on whether it should maybe be in 85 or maybe 75 and said we say ok it was the old terminals that had 80 characters that's our standard it's not the only solution, it's our standard and we stick to that so we need UI and UX standards for providing a consistent user experience both for core and contrip we need to document the reasons why we're doing that quite often we have really good ideas and they're discussed and they're implemented but not necessarily written down why have we decided this what is the reason for it what might break if we do it the different way and would also help us to avoid endlessly long bike shedding and issue queues if I can say this line of code is too long it's not a question but it should just be three nouns or something like that we have a page that says do you really want to delete this thing so if we can actually point to specific standards it would actually make the issue queues more workable because at some stage you just look at an issue and think yet another comment about something that we have discussed here or there and it just goes around in circles so standards are not fixed they change over time we go through an approval process part of the community we get there and we change them and we improve them over time but at least having them gets us somewhere and then if we're finding that something is inappropriate in the future we change it we do that with the coding standards as well as it happens so we're defining some UX and UI standards simply by doing things by being the first module to do this which is not necessary we also actually document what we do I think we're getting much better and that was the governments and the UX meetings another step is on the how do we actually use them and how do we promote them and other I've been working with a module last week that was actually using a different WYSIWYG editor that was coming from some external library we think why why can't you just use the one we have why can't I point you to something and say this is our standard is there a good reason why you're not doing that and this brings us to the main question on who's responsible for usability obviously when we make when we make modules we are responsible for that but the people knowing how to write the PHP code aren't necessarily the ones or the only ones who know how to do usability testing how to write a good coherent help text they're not the only ones who can do design for example as well so I think we need to put the first of what we previously mentioned if developers can also say I've got an issue with my module that somebody should help we currently have all our issues in this kind of silos of core and this contract modules we don't really have issues that are more for the cross cutting expertise if as a designer I want to help with some visual improvements I wouldn't need to go through individual modules for usability we now using one of the text that kind of adds up as the kind of free for all and we look at anything that's tagged with usability but that is a really big mix of bags as an accessibility expert it's difficult to say which issues are, who needs help so it feels like we should actually more actively have these issues help us use this text and maybe change the issue queue to also have something where you could say okay I'm on this cross cutting expertise who needs my help that's a long term plan so who's responsible for usability well who's responsible for usability well you are everyone I don't know if you've seen this picture yet it's every single person in this room influences what that is so make sure it's done right who here has not tried to do any changes to interface text et cetera and all those type of things before anybody who's never tried to do any of that now you've all got involved in changing Drupal core interface stuff before really? or modules of a client's project forget client's project so who's tried to do anything on Drupal no one anyone not done that who hasn't who hasn't who can't remember but actually I think it's also a good point every time we repeatedly change something for a client's site it's something that probably should actually be fixed upstream and core I had one of these small issues on the content page that lists all the content on the node page it had three filters on top of it the title, the language, the publication et cetera and I realized that some said that for every single project I was moving the filters around so that they would line up with the columns underneath and at some stage I thought that's silly it's actually a patch that because it's a view as a site builder I can actually change that I can change that it's a Yamel file it's a patch in core that's simply a Yamel file that changes something so that I don't have to do this with my projects anymore which means some other site builders don't need to do this anymore either so I think everything that as site builders we repeatedly do to make it workable for our clients is probably an issue that we should try to fix upstream for that we also have the sprints on Friday but I think I mean really you can be involved in this you can do this stuff you can save yourselves having to do the same changes for every client side you have that capability it's an enjoyable experience it's an enjoyable exercise as well for those in the room that have never written a line of code in their life or used git you're the best people in the world to have things like code sprints contribution sprints because you can ask the questions and sit with someone who can turn those questions into a change that makes your life better that's why you need to work together and I think that's where we stop talking we have about 15 or 20 minutes for discussions I suppose the people sitting on the floor might now need to get up but I'm going to tell you something I'm not that tall can you hear me otherwise come stand here it's higher no thank you you don't have to leave does Drupal have the ability to do some sort of style guide in a usability sense you were talking about X line of code or whatever could you do some examples of good examples and have that as a public facing page for people it's very old it's a Drupal 7 but it is old and needs updating and you can do it I didn't mean that people need to leave I just meant that they need to make space for the microphone no actually there is an idea for together with the accessibility initiative to actually go through a few pages and check whether they fit all the accessibility standards but also our UI standards that we then can say okay this is a kind of gold standard admin page and kind of work our way through that so that you have a few reference pages to answer for the recording the question about the style guide for core interfaces if you look for search for human interface guidelines on Drupal.org there's a very outdated handbook page that has that so that would be the place that we would want to update and find a way to make it more obvious so that people like you who have the question I wonder if can find that instead of knowing in the back of their head that if once upon a time if you typed HIG, HIG, question mark and IRC like that was the only way I knew to find it so obviously it's not very discoverable. With the documentation pages got rearranged on Drupal.org so there now is a page that has this kind of documentation and that actually has the coding standards on the same level as the UI standards and in preparation for this Drupal corner I actually made a big meta issue to say that we need to go through these ones to have the human interface things in there to have screenshots from Drupal 8 to have a comparison on how should this look like and so yeah that's work that needs pages that need updating and therefore work that needs done yeah back to the thing we talked about the permissions and the long list and so on I have worked with a client and I'm going to do this out, maybe someone can see if this will work for core or if there are some application for it but we had a customer that has like 10 different roles and the roles are put on users by subscriptions, they have kind of automated flow for that but what subscription should be allowed to see and use was kind of determined by the permissions and we have this kind of functionality we call it monitoring where you could monitoring different taxonomy terms by flagging them and when we have an overview page so in order to have that functionality you actually need three permissions you need the flag and flag and also the permissions for the page overview page so when we have like 10 different of this kind of functionality that the business has kind of requirements on the CAO kind of changes mind about the subscriptions weekly so we ended up doing this kind of grouping of permissions so I have a separate page did a hook where different custom modules can define a set of permissions needed for this functionality so then you have this overview page where you can say enable monitoring and it will enable those permissions for those rules and then if you disable or remove the permissions it will move all of them and it can also check if you have two or three permissions you maybe need to fix this it's just an idea maybe something like that for like administrating taxonomy terms what permissions do I need to do this or if you need this kind of like kind of some of wizard or groupings or yeah I have not think that through but I think that could be one way to solve these problems with a long list of permissions yeah there are things like that especially if you're talking about things that are repeating so you've got lots of entities and you need separate permissions for each my immediate thinking on that would be use the group module and put the taxonomy terms in the group modules and assign them to that and then you could use the permissions per group would be something I would consider I don't know I've only had 10 seconds of hearing about the project but yeah The problem comes that users have subscription time so they should go in and out of those groups one suggestion I have for if people want to go to the sprint Friday I think you're proposing that one place to start would be this audit to go through core annotate screens if people are interested in that I think that would be a good place to start the sprint on Friday because if you have a plan for that this is a non-technical work right this should be easy to contribute to should be easy to divvy up the tasks etc so just to make it more concrete and specific that could be a good point to start the work that would be really nice if you had someone who people could head towards really that would be nice wouldn't it find and chef The usability table will be next to the accessibility table because I think we're trying to pool resources there because for example auditing pages is something that we don't want to develop nice usability patterns and then have the accessibility people look at it like that doesn't work or they develop something different parallel so there's a certain overlap as well and which is why I'm really glad to see that there's so much interest in accessibility so we can piggyback usability on that a bit as well I'm really really happy to see that this room we had a point where there wasn't enough people to sit on the floor which is great because there's clearly an interest and this is something that you clearly care about and the next step is taking that out of this room and doing something about it I think really our talk hasn't doesn't fix things it raises questions we need you to fix it and it doesn't happen by magic it doesn't happen by somebody else fixing it it only happens if you fix it and you do that together so where do people go after this week where do we find they join us on IOC or Slack or if we ever bridge it on whatever matrix they also sorry if you have who has already plans for next Tuesday evening at 9 o'clock what is time zone European standard summertime zone only one which means the rest of you can all join us in the weekly UX either IOC meeting or Google Hangout so that's a weekly meeting that's on every Tuesday evening in Europe in US it's in the morning I think for the rest also go to your local camps, go to your sprints go to the issue queue and if you see something that doesn't quite work make an issue for it because we can also only fix the things that we know that are broken or that know that could be better first look for an issue yes but yeah this is also especially to the site builders that think we are just using this and we are cursing something that is on the wrong place or turn that cursing into some productive energy and into changing it really good to see you all and really engaged actually some of the questions have been really great this is the moment when the laptop will die of lacking electricity the bus is about to run out what's up my session last year no ok so there were massive and also this thing didn't work it was like my here is my notebook it's got HDMI so you don't notice where there is things on it the conversations I'm getting I'm showing you just getting it so I'm just pulling this line and everybody would find and after a while this is a direct HDMI


Let's go, let's go, let's go, let's go. Let's go, let's go, let's go, let's go. Promote upon the letters of the population to lift the full price. Abadunia ni miko na one life. Zinga nazima kwanza baptize. Kwanza young inyo niko na half price.  Sherry Abadweza sees a free.  The middle. Two. Everybody lies. You know they love me, father. Mi te ilo mi nahati kube. One asemone bangi kube. Top team in the big propeller. Manda video me kuja Kenya. Mi prasai mai makulat, mai makulat. Make some noise everybody! Make some noise around me!


Today we're making caramel sauce. Way better than what you can get in the store. We're not using any white sugar and we're not using any dairy and there's no artificial anything in this. So we're using dates. We're using coconut milk. It is creamy and delicious. You're going to love it. You can use it on just a gazillion things. I'm Rockin' Robin and I'm going to show you how to do it right after my chef joke. We always have a chef joke. Okay so here we go with chef joke number one. What do citrus fruits use to get dates? Pick up limes. So let's start off with our dates. Okay so you are either going to find them pitted or not pitted. We're using medjool dates and they are full of nutrition, lots of fiber, calcium and potassium. If they're not pitted I have both. You're going to want to take the seeds out. You just pull it open. These are so soft already that they come right out and it's very simple to do. So we're going to do about 240 grams of dates. Or if you don't have a scale you can count out about 16 or 17 dates. I'm going to heat up a pan of water so that it's just about boiling. Just make sure it's pretty hot and then we're going to pour that right over our 16 17 dates and let them soak for just a few minutes. Make sure they're completely submerged and even take a spoon or something and just push them down. Make sure they're all covered. This is just going to ensure that they blend up nice and easy in your blender especially if you don't have a Vitamix. Time's up. Time flies when you're having fun. Okay so I'm going to pour this through a strainer, save the water. Now we want to save the water because we may be needing to use it to add back in and we want the flavor. So we want to just set the water aside. All right so we're going to place the dates into our blender and then I'm going to show you our ingredients. Next we're going to add some coconut cream. I got this at Trader Joe's and we're going to add about a half a cup. Remember you can find the written recipe below the video in the description area. Pour that right in and then we'll move to our vanilla extract. Now we use vanilla extract because it brings out the sweetness in our recipes. And then we need to add a pinch of salt. Now to give this some extra sweetness we're going to be using some maple syrup. Now we're going to blend this on high speed for about a minute or so depending on your blender. Now we want this absolutely nice and creamy. So at this point it's probably going to be too thick to to blend so go ahead and use some of that date water that we saved. And I would say add a scoop or two at a time until you get the right consistency that you want. The Vitamix is pretty loud so I always use air protection when I run it. So for me this looks a little bit thick depending on your use of course if you're using it for a dip that would work. But I want mine a little bit thinner so I'll continue to add liquid until I get a nice consistency something like this. So I'm giving it a little taste here just to see if I need to add a little more maple syrup and I think I do need a little bit more. Okay it must be time for chef joke number two. I used to love donuts but then I got tired of the whole thing. So here's the consistency that I ended up with because I want it to be pourable because I like to eat it over ice cream. That would be chocolate but vanilla also works too. Let me know down in the comments how you would serve this caramel sauce. And don't forget you can always put your caramel sauce in a squeeze bottle and that way it makes serving it so much easier. I can't wait to dig into this. The caramel sauce is plenty sweet and it's got that caramel flavor from the dates and the maple syrup and it is just delicious. Do you know what else this caramel sauce would be great on is my cookies and cream ice cream. Click the link here on the video and it'll take you right to the recipe and you can make this. It is so delicious and creamy. You'll love it. Did you enjoy today's video? Well if you did let me know by smashing the old like button for me and leave me a comment. Let me know what you think. Alright we'll see you back here next week for another rock n' recipe.


Hey guys, it's Nate, AKA the Foot Accountant. Welcome back to the channel. Today, I'm gonna be looking at some of the squads that you guys have sent to me. Looking at some starter teams and some built teams and built squads that you guys have for the starter FIFA 20. Kinda look at just what you guys have for these squads. I wanna see what you guys have planned out. I wanna kinda analyze them and kinda talk about even some trading aspects of what cards could be a little bit inflated on the market. And this is also gonna be something, I wanna do this because I wanna also show you guys that you can get a lot of information from asking a broad question and asking people to respond like this. And you can get a lot of information just by seeing some of this stuff on Twitter. You see maybe another FIFA content creator. Put a post out, show me your starter squads or show me what teams you guys are using right now. And you can kinda get a feel for maybe what some cards are gonna be OP and you just kinda get a feel for what cards people are using and what they want to use on the game. So that is an interesting thing that I think you guys are gonna be seeing through these squads. But the main thing on this video is I wanna look at some of your starter teams and see what they look like because that is a lot of the hype right now since we can't actually get on the game yet. We're so close, we are so close. What is it, five days or four days? Until that web app will be coming out. But I do wanna look at some of these starter squads. This is why I tweeted a couple of days ago. I said with all the hype, surrounding building teams for FIFA 20, show me those starter squads and then I throw an estimate of what you think they're gonna be as well. This first team coming in, we've got Anaki Williams, Brant Havertz, Vitzel and Babu, Hernandez Militaw, Mandy DeYoung-Yovic and Ariola.  So a starter squad for them is when maybe two or three days into EA access that time period in there, they're at 200, 300,000 coins that they can put into a squad. Some people, our starter squad is like 20,000 coins because everybody's in a different place so you're gonna see that we have a lot of different squads coming out here. But already, you can see we've looked at two squads already, two replies to this tweet and we have multiple players that have shown up multiple times, Mandy, Militaw and Ariola. I think you're gonna see this, these three guys, you're gonna see a ton at the start of the game. I even think you're gonna see Ariola, Militaw and Mandy, actually maybe all three of these guys are an extended portion of the game as well because they link so well, they create a great hybrid and they look to be very good cards for early game and even a couple months into the game as well. Another starter squad that's coming in from Just Die on Twitter, he's got Ben Yetter, Henderson, Arnold Gomez, Gulaski, this guy's playing phenomenal right now, by the way, in the Bundesliga. Konate, Russelian, Cyprian, Oniakuru, St. Maximon. I mean, a lot of people are looking at this card. I'm sure a lot of you guys are looking at this card. But this is a nice hybrid. This is a nice hybrid squad with some League One, some French links to a Bundesliga, left side in the defense and some Premier League as well. So we have three different Leagues coming in here for that squad. That's a bit of a more expensive squad. Here's another one coming in. This looks like an entire Premier League starter squad. You know, it might cost a little bit extra. You have Lucas Moore in there, he's gonna be hyped up. I haven't seen a lot of this card. I have not seen a lot of Toreas, but that's a solid card. That's a pretty solid card, 82 rated CDM Torea. Madison, King and Wilson, that's a pretty cheap strike force. You can tell that he's looking to spend a little bit more money in his defense with Sanchez, maybe with Gomez being a little bit more, Zasoko and Lucas Moore, than he is in the attack. So that's also something that I find interesting when looking at these squads. It's kind of interesting to see where people put their money. Everybody's different, they value defense more or they value attack more. But this is a pretty solid squad. You got some Pace with Moore, King and Wilson. You got some solid CDMs and you have some pretty good early on Premier League guys. Here's a couple of other teams. Ooh, we have some Serie A action with a little bit of some La Liga in the back as well. Ettermila Tau with some links to Allen. That's gonna be an expensive card early on. Ilisic, I haven't seen a ton of him and I haven't seen a ton of Lozano. And that honestly surprises me because I thought I would see more Lozano links to Allen. But it's kind of hard. If you think of a Serie A writeback, you don't have Cancelo anymore. Florenzi got a nice downgrade actually. Not a nice downgrade, a substantial downgrade. Let's actually look at that for a second. Serie A writebacks. I think Florenzi honestly might be the best one as of right now since Cancelo has transferred away. Yes, this is still a decent card but it's more of like a center mid card than a writeback to be honest in terms of statistics. So it's kind of hard to make a hybrid with Lozano with Allen unless you're throwing in some other Brazilians or maybe an Icon or something like that. So I think that's why you don't see a lot of Lozano and Allen right now at the moment. But you might see them later on at FIFA if they get some Informs or whatever. Here's another starter squad, another St. Maximon, another and Dombele, Gio Felix. We haven't seen a ton of him but this is, I like this squad a lot. This is cool, look at this. We have Gio Felix, a Portugal link up here, Vandebeek, Taglia Fico and then some La Liga with Prem on the right side. This is a very cool squad. Hector Herrera's got a very nice starter card as well. Vandebeek's good, Brumas probably Pacy on the left side. Taglia Fico's got a really good card here. Moso has a good one as well. Adon and Felipe to get that. Look at this boys. We have an entire, down the middle of the team it's all Atlético Madrid. This guy must be an Atlético fan. Gio Felix, Herrera, and Moso, Felipe and Adon. Spurs on the right side except for St. Maximon and then Ajax and PSV on the left. That's a cool team. That's a pretty cool team. Oh, this man was already prepared for Pookie. I put this tweet out and people responded to this before Pookie won Player of the Month but this guy, who's this guy? I love Epic wins. He was ready for Pookie and he has come out. He's gonna slot that Player of the Month card right up top with Zaha, Lucas, Mora, Gabamon, Tyson, and Ismaili. That's a nice link right there. Sasoko, Aguilar, Konate, Akanji, and Burki. That's a pretty nice backline. He's got a lot of coins in these two guys right here which is interesting because he could definitely make this team a lot cheaper if he would take out Burki and Akanji. That would lower the price of this team down a lot but I mean that's a pretty solid. Maybe around 100,000 coins, maybe a bit less. Actually probably a little bit more than 100k considering the Pookie SBC would be in there probably around 50,000 coins. Couple more teams. Here's an interesting one.  Diego Carlos, I've seen him in a few starter teams. I haven't seen Furpo. I have not seen Furpo a lot but that's a solid card. 85 pace, 75 defense, 76 physical. That's a pretty solid card for a left back in the La Liga. Of course he's got the Swiss cheese triangle over here with him, Babu, Zakaria and Akanji. That's gonna be a popular triangle that people rock with early on in FIFA. This Morales card looks very good. Kind of reminds me of Rebic in his move to AC Milan. He has a kind of a similar card to this Morales. Naki Williams of course, fast, pacey. He's gonna be expensive though at the start. That's a card that I actually wanna look up. Let's look up in Naki Williams from FIFA 17. Or excuse me, why'd I say FIFA 17? FIFA 19 because this card should be pretty comparable to what he's gonna have this year. He got a nice, actually a pretty nice stat boost. 94 pace, 80 shootings, 72 passing. He got plus two shooting, minus one on the pass, plus one on the physical. But look at this guy early game. Oh yeah, look at that. I can tell that graph is way up. Let's check this out early game. 8,000 coins for this card early game. Four star skills, three star weak foot. He's now, he got downgraded to a two star weak foot. Oh no, but he got the stat upgrade. That's interesting. So he gets downgraded on the weak foot from three star to two star. He's at high, high attacking work rates, which is interesting. Yeah, that's quite the card right there with Naki Williams. That's a straight-paced, fast-running striker.  He's got Munir. He has a pretty pacey guy at the top. Naki, Munir, Morales. Woss is a great overall center midfielder as well. That's a pretty nice team. That is a pretty nice team. Another pretty cheap team here. It's kind of hard to see. It's pretty small. Another same maximum, Wabi Saka. That's the first time I've seen him. Torea, Pulisic, Vardy, Kalibos and Sasoko. Another pretty good Premier League squad. Another team right here. What do we have? Ooh, we have some Chinese league to share with Paulino, Tyson, Ismaili. Voked, Stark and Bauman. Weiser, Delaney, Thorgen Hazard and David Neres. That's a cool squad. That's different, but that is cool. Another LaLiga squad with Naki Williams, Jalphilx, Fakir, Condogvia, Pardy. Another Eder, Militao and Mendy and Felipe. Dude, a lot of people are looking at this Felipe card. Let me look at that as well. And so this is why it's so fun to do this, boys, because I get to look at some of your guys' teams. But also you guys watching this video, get to see some of these cards that other people are looking at. So Felipe looks pretty solid. 90 jumping, 92 aggression. He's got great defensive statistics.  What if we throw a shadow on him? Shadow takes him to 76 pace with 92 defending. What about an anchor? An anchor takes him to 69 pace with 92 defending and 91 physicality, but it does not touch the stamina. But still overall, that's a pretty solid card, that Felipe card. So I understand why I'm seeing him now. He's got that Brazilian link though that's gonna be perfect for Mendy. And I do kind of like that squad. Here's a pretty low budget one. Wow, that's hard to see. That is really hard to see and I cannot zoom in on it, that's unfortunate. That was hard to see. Here's one. Jota Jimenez, Hazard Delaney, Ruben Neves. Interesting, I haven't seen a lot of him. Rubitriscio, William Bali, Angelino, Klosterman. This Delaney card looks freaking nasty to me. I think this is gonna be a card that is gonna be used for a while in foot. The Bundesliga looks fantastic this year for starter teams, but it also looks great for, let's say you run an entire Bundesliga squad, it looks very upgradable. You have guys like Royce, you have Vitzel. You have pretty solid outside backs, not the best. Right back is kind of lacking in the Bundesliga. Left back, you have Schultz and Rosilian. So those guys are solid. But there's a lot of areas inside of the Bundesliga where you could start with a full Bundesliga team.  So the Bundesliga looks like a great league for progressing a single squad in this game. So that's basically a lot of the teams that I wanted to show you guys and look at today. If you're still getting those teams kind of optimized and finalized, maybe if Pookie makes an addition into your team, I would say try to get those teams figured out here in the next couple of days. Because as we get closer and closer to FIFA 20, you're going to want to start to transfer your mind over from the squad building and the player side of things, looking at statistics and stuff. You're going to want to get that all figured out before we head into the actual meet of FIFA 20, which is going to be content on the game, playing the game and trading, of course. If you're watching this channel and I'm thinking that you probably are involved in trading at some way, shape or form. So if you get that team settled and figured out beforehand and you know what team you're going to be going with, then you can focus on some of the other stuff, trading and investing and some stuff like that. So if you guys enjoyed this video today, smash a thumbs up on it and don't be afraid to send me your teams or ask me questions on Twitter in the comments down below. Or if I'm livestreaming on Twitch, don't be afraid to hit me up with questions because I enjoy looking at these teams. They are fun. I'm still figuring out my beginning of the game team. I'm looking to get kind of a good team but it doesn't need to be that good. I want to put most of my coins towards trading but we'll be figuring that out here as we get closer to FIFA 20 and the start of the game. So if you guys enjoyed the video, smash a thumbs up on it, comment down below if you have any questions or I want to show me your team. And of course, subscribe to the channel if you are new. It's been Nate, Foot Accountant. Catch you guys later. Peace out.


Hey guys, it's Nate, A.K. The Foot Account, and welcome back to the channel.  Yes, FIVA 23. I know we are still about seven months away from another game of FIVA, and we're still in the heart of FIVA 22, but there's some huge information about FIVA 23 being cross-platform that I wanna talk about today and just kind of initial thoughts, kind of put this out there. We have this article, we have this information, kind of talking through what this means, how it could affect the game and the market in general, right? We talk a lot about the market on this channel, and we have to talk about how the cross-platform aspect of a FIVA Ultimate team would impact the market a little bit. So just kind of some preliminary thoughts based off of a couple of these articles here from this website. I'll leave all the links to these in the description. We're of course still gonna talk about FIVA 22 Silver Stars, what's going on in the market a little bit later on the video, but for starters, we have to look at this game break and information for FIVA 23 because at first I was a bit skeptical of this. I was like, man, is this article actually legit? And then I went and did some digging. I'm seeing this flying around the internet like crazy. Bleacher reports posting about this, it's getting posted everywhere, and that really makes me think that it's legit. And also I looked into this guy, Tom Henderson. He's also the same guy that had leaked information from EA Sports, leaked comments from the CEO Andrew Wilson saying that the license deal, right? That's a big thing about FIVA 23 as well. Is it actually gonna be called FIVA 23? And this is an article from last week saying that, the four letter words on the front of the box is the biggest benefit to that licensing deal to EA. So this is a legit article, this is a legit information and it's huge, right? This has been something that people have been wanting for so long and FIFA is the cross-platform nature and that is what he says inside of this article. One of the biggest changes to this year's FIFA title is that it will feature cross-play for the first time in the series history, bringing FIFA players across PlayStation, Xbox, and PC platforms together for all of the titles, game modes. Yes, that would mean Ultimate Team, Pro Clubs, everything would be cross-platform, which is a W. And we've been wanting this for so long because so many other games have moved in this direction and we were waiting for EA Sports to kind of make this switch because right now, there's a lot of things on FIFA that just seem very inconsistent and between the different consoles, especially PC, and especially market related between the different platforms on prices, on how they value SBCs, how the market reacts and stuff like that. So this is absolutely massive, right? This is huge, huge, huge information. Now, the best thing about this is, you think about FIFA and the state that it is in right now, especially in the spring months that we are, we're not the team of the season yet, we're inside of this promo that is not very hyped for everybody, it's just hyped for some people. And you think about, it'd be way easier to find games right now if I was on the PlayStation or if I was not on Xbox or not on PC, it'd be so much easier for me to find games in any different timeframe or time zone if there was just more people to search from, right? And you think about when you play Call of Duty or some of these other games that have already adapted the cross-platform nature to them, that's definitely a positive of going cross-platform, it's easier to find games, it's way easier to link up with your friends, right?  You're able to play co-op together, so that's a really cool feature. I think that's the biggest part about this, it's a W, right? It's gonna be easier to find games, easier to play with your friends, and hopefully there's no caveats to this, right? Like hopefully there's not, okay, you can't do co-op cross-console, if you wanna do co-op, it has to be on the same console, hopefully that is not an issue. And I wanna take a look at the market aspect and talk about this as well. Of course, the market on FIFA 22 has been so crazy with everything, prices being so much cheaper this year with so much more supply with preview packs and all of that, and you take a look at prices on the market and you notice that there's always some pretty big discrepancies. Now I'm gonna try to find a quick example of a card that would have a pretty big discrepancy. Let's go like, maybe for an icon, let's go like Wayne Rooney, right? Icons seem to have pretty big price discrepancies, 625,000 coins on the PlayStation and it's 840,000 coins on the Xbox and still about 600K on PC. I mean, there's always big changes and some cards on PlayStation are more expensive, some cards on Xbox are more expensive, it just depends and when you would have, I'm assuming that going cross-platform, as it says here across all title game modes, I find it really hard to believe that you would have a cross-platform game with cross-platform gameplay and separate markets. I really don't think that's possible. So that's why I'm assuming that there is gonna be a cross-platform market. Now, how would that feel, right? Of course, it'd be so much easier for E8 of price SBCs. When you take a look at some of these active challenges for SBCs, especially for like the icons, like the Desi-E SBC is 740,000 coins and 771,000 coins on the Xbox. Now, if we take a look at the Prime Desi-E card right now, he's 700K on the PlayStation, 683 on the Xbox, but there's been other icon SBCs that have been released especially for some top tier icon cards. Let's see, maybe like a little bit more expensive one like Zidane, right? Zidane is 1.8 million to do as an SBC on the PlayStation, but he's like 1.8 million to do on the Xbox as well. And he's always been a couple hundred thousand coins cheaper on the Xbox, but yet the SBC when it drops is still the same price for both consoles, right? That's where it's gonna be nice is where you have, prices on Xbox are sometimes cheaper for some of these big time meta icons. It's like the reason why I picked out that Wayne Rooney is because English icons for some reason seem to be more expensive on the Xbox, which is very interesting. So I think you'd have a way more level playing field when it comes to SBC prices. And of course it would be crazy for SBC fodder in general, you know fodder has had so many fluctuations this year and already it's so expensive right now at this very point in time on this game. And but that thing, I think that would be a benefit, right? Having the market be universal, it'd be so much easier to even remember player prices and think about, hey, this card's a good buy. Hey, this card's not a good buy. And it'd be so much easier to track if it was all together on one market. Now the market would be so competitive. And that would be the thing that a lot of people who are used to maybe the PS market, sorry, the PC market or the Xbox market would notice that the cards are just, there's so many more cards and the competition is so much higher which would, it would be crazy. It'd be really, really crazy. Trying to snipe cards would be so difficult. You add in the equation of bots in there plus, you know, tons more people from both PC and Xbox trying to maybe snipe that card at the same time. That's gonna make sniping some of these items really interesting if this were to all play through and play out. But I still think that it would be a W overall. It would take a little bit to get used to. But the fact that it'd be easier to find games, there'd be a universal market which would be a lot easier to keep track of from everybody's perspective.  You wouldn't have to remember those discrepancies. You would have one price on the market for the card and that is kinda nice. So that is the article. Again, I'll put a link down below to this if you wanna read through the full thing. There's some other cool stuff in here, right? FIFA 23 will contain both men and women's world cupboards with EA expanding its licensed partnerships. Now again, this seems to be all 100% accurate, true and correct as it's been posted around the internet a ton. Not that you can use that as the basis, but the people that are posting this out and from the track record of this Tom Henderson has been posting a lot of stuff so far. This seems to have some pretty close ties with EA. That's why we're talking about this today and that's why we can put a decent amount of trust in it that this is factual information and cover it here on the channel. So that's just kind of what I wanted to talk about a little bit related to FIFA 23. I know it's not for a long time, but you know, that's kind of the news right now and of course, content inside of FIFA 22 as we transitioned over to that is still going slower than a lot of people would like it to be since we are still inside the Silver Stars series promo. We did get a couple. Actually, I think we had three new players yesterday. We had the Marco Royce SBC. We had the center back Marcelin and we had a new objective center back as well. Those were the powerhouses released yesterday. Now again, you take a look at these card prices and you notice they are so cheap, right? I think the biggest downside of yesterday's content was the Royce is a right mid instead of a center attacking mid like some people was hoping that he would be. But again, it's a flashback to Royce's days in 2009, 2010 season with Borussia Muchengladbach where he was on the right side. So this card, honestly, this Marco Royce might be on par, if not just as good as his Champions League road to the knockout card just because of that pace. And it's a really, really good Silver item and it's 12,000 coins to do. I mean, 8,900 coins for this Marcelin center back card. Seriously, it's just so cheap, right? That's the biggest W of all the Silver content. I know it's Silver's, but that is a huge W. We did get our Origi upgrade tonight. So Origi got plus two pace. I actually have this card on my team. He went from 95 pace to 97. EA gave this card a really nice boost. He got 82 passing, 91 shooting, 90 dribbling, 89 physical. So this card looks 99 sprint speed on this item after the upgrade, 97 shot power, 92 finishing, 93 attack positioning. Dribbling stats look really good. Of course, he's still not gonna be the most agile card in the game, but that Origi upgrade plus two that happened as we expected it to is now live in the game. So that's nice. A lot of people are enjoying that upgrade on that card right there. Now also yesterday, we had a Gamble Pack, SBC. I guess you could call this a Gamble Pack, right? We had the 85 plus triple upgrade that was released. And to a lot of fodder investors' joy, I guess you could say, to their happiness, you saw a double informed requirement for this SBC. Although, informs didn't really rise yesterday because of this SBC. Now, obviously, there's nothing in packs right now, right? So opening an 85 plus triple upgrade right now, there's not a ton of hype for it. And SBC fodder is so expensive. If you actually take a look at the price of this on Footbin, it's like 60 or 70,000 coins to complete. 71K to complete this SBC for 385 rated players or above, right? Imagine opening this pack right now and getting 385 rated cards. That's literally about 36,000 coins worth of card value back. And you're turning in an SBC for 70K. So this is not a really good value SBC. As you can see, it's downvoted 70%. Now all I'll say this is we're probably gonna have a normal promo this Friday, right? And then I'm gonna do this. I'm just not gonna do it right now. You might have some silvers in the club still that you could turn into that 81 plus double upgrade if that's still available to you or potentially rabble's rewards this week. Maybe footchamps, qualifying rewards. You get a couple, 83, 84, 85 rated cards and there may be a snag and inform from the team of the week. And you can go do this SBC for less than 20K. If you have to go buy a few cards for it or even if you trade and make some coins and then afford the SBC by doing it that way. I think this SBC is a good one to save for the next upcoming promo because again, you don't wanna open this and right now in general I'd be saving all your packs anyway, right? I accidentally opened a mega pack from objectives today and I ended up, I did end up getting two walkouts but if you're getting packs from objectives or if you're getting packs from SBCs you might as well be saving those right now because there's seriously nothing in packs and we're just kind of waiting towards the end of this week as we get more information about what this next promo might be. Now, today on Tuesday, I don't really have any information about what cards are gonna be coming for the Silver Stars. We should get two to three more of those today. One of the big things about the content today is the mid icon player pick is expiring. If you have SBC fodder, I mean honestly, I'd be looking to take the cash not just because this player pick is going away, if it comes out again and gets re-released which I would be a little bit surprised with because I believe that would be like the third time that it would have been re-released because it's been out twice now, I believe. I don't exactly remember but SBC fodder is so high that I would be looking to take the cash on some of this stuff. I mean, I know again, like I said, there's still a prime icon upgrade that is out, that is non-repeatable though and I could see another icon SBC coming in today but I would start to think about selling off some of these cards that are just stupidly high in price. Harry Kane out of packs for his gold card is 80K, right? 80K, Ter Stegen's 70,000 coins and you have 88 rated cards that are 42K a piece. It's crazy, right? They're up like 15K from where they were on last Friday or 13 to 15K a piece from where they were. It's crazy how much these cards have risen. So with all the packs that are being saved up for this weekend and with a new promo coming with lightning rounds potentially and stuff like that, the prices on fodder are going to be a bubble this week. It's definitely gonna be a sell time. I'm just kinda starting to tell you that, hey, this week, especially maybe today, tomorrow, Thursday for sure, start to get that stuff out, maybe even today and tomorrow. It would be the days that I would focus on if you have some of this fodder, taking the cash on it because I feel like that's the safe play. Again, I don't know what kind of SBC they're gonna be releasing today, if they're gonna re-release that mid-icom player pick. Footshare, I did tweet out and say tomorrow will be a great day, see you guys soon. Don't know what that means. Again, you can read into that as much as you want. I'm not gonna read into it too much until we actually see some legit leaks or legit information. But that also has me taking the cash on some of my other cards that I had bought. I bought some Kakarais and I bought some Genduzis on Sunday night because when the Cyprian Silver card dropped on the game, actually a lot of these cards dropped in price, which is crazy. So I bought some Kakarais at like 215, 210,000 coins, selling these in the 230s. I got some Genduzis at 300K flat, selling these in the 320 to 330 range just because I'm gonna get some of my coins back. Now, I wanna talk road to the finals here for a second too because of course, as we look forward to the end of this weekend, we're like, yeah, Nate, I've invested in some of these road to the finals as well. What should I be doing with these cards that I've bought? Taliso's at 150, 160, right? He's 200K. Quadrado at 140, he's now 175. Denier at 60,000 coins. He is now like 100K. A lot of this stuff, I'm probably gonna continue to hold. The number one thing that is kind of the caveat this weekend is how high is this promo gonna be? Oh, we have Man of the Match card designs in here now. UECL Man of the Match, that's nice. Okay, did they just add one Man of the Match card design in your EA Sports? Wow, okay, you need to add also the Champions League card design and the Europa League because there's more than just, anyways, that needs to be added in soon if it has not been already, which I don't see it, but EA, please add more of the Man of the Match designs here into the search queue. But for road to the finals, it all depends on the promo this weekend. That's the bottom line is if the promo this weekend is really hype, there's gonna be some of these cards that drop, but then also there's gonna be some of these that rise back up into next week. So a week from now on Tuesday, we're gonna be having Champions League games again because there will be potential double upgrades on the line for cards like Tuliso, cards like Mares, cards like Kim Pembe, who have not gotten any upgrades yet, and we've been waiting for the second leg for them to get that first knockout win upgrade, or of course, to advance to the quarterfinals, which would be a double upgrade potential, right? That's where the big money on some of these cards could be and since a lot of people are probably gonna be selling off towards this weekend, some people are still gonna be selling, right? Like, look at this person here. All these Tulisos listed at three hours and 23 minutes. This is an investor. This is an absolute investor. See, second owner, no games played. Purely a sign of somebody who invested in like 15 of these Tulisos and they have them all listed and they're holding Tuliso's price at 200K, right? Because nobody else is listing under 200K. That's kind of his market value. So it's holding his price right there at the moment. But, you know, if you have, it all depends on how many coins you have too. You wanna be smart. Like, of course, I have got a lot of coins. So holding onto a few of these is not, you know, that detrimental to me. And here's one thing that was, one way that I was thinking of it as well, right? Gareth Bale right now is like 230,000 coins. And as I mentioned, Tuliso is like 150K. I bought these cards basically at their all-time low point while they were in packs. Let's say for some reason, this would be absolutely insane. Let's say Byron Luz. Let's say Byron Luz, this card is no longer a live upgradeable item in FIFA 22. All of a sudden, this card's dropping off in price because people are selling it. They're paying to sell on their investments. I'm happy with that 150,000 coin price range. Because especially for a guy like Gareth Bale, who's not expecting to get an upgrade, right? Of course, they're playing PSG in the second leg at home against Real Madrid. So, yeah, at home against Real Madrid. So there's more upside for this card like Gareth Bale. If they were to somehow come back and win the game and move on, he would end up getting a plus two and his card price would go to the moon. So kind of calculating in that potential reward was also the risk and probably the expected outcome of Bale not getting upgraded and Real Madrid being knocked out of the Champions League. I don't expect in the event of that happening that Gareth Bale would go back below 200,000 coins. I feel like people would see that card at 200,000 coins as a Gareth Bale, the only special card that he has in this game. And he might get back down right close to 200,000 coins, but I think then after that, he wouldn't really go much lower than that just because that card for 200K would be too cheap for me, people would see that and be like, okay, yes, this guy's knocked out, but if you want him for your team, his price has dropped down, it's a good time to buy because people know that there's panic selling after when a team gets knocked out of the Champions League on this type of card. So that's kind of my thought process with a Gareth Bale. I'm gonna hold it, hope for something amazing to happen and just for his card to continue to ride and rise. And I've already sold some of the ones that I wanted to get out, right? I sold my Havertz to like 250, 260 that I bought in the 220s, that was a W. I bought a Eurente today at 688, sold them for 740. I sold the Mane card a little bit too early to be honest, but if you're in the profit in general needs and you want the coins, you can take the coins. I just wanna kind of lay out that situation for you with like Gareth Bale and Taliso and stuff because it just depends, right? These are lab cards, it depends on how their teams perform, but that's part of the fun in these, right? Too, and that's why their prices fluctuate a lot on the market. Now, we'll keep an eye on them throughout the rest of this week as this new promo comes out, whatever it is, the what if promo, people talking about for birthday, we'll probably focus on that a little bit more tomorrow into Wednesday, Thursday timeframe as we actually get closer to Friday, maybe have some more leaks, loading screens, stuff like that. But for now, take the cash on some of the stuff while it's high in the market, maybe some fodder especially, maybe some of those out of pack special cards as well with new promo cards coming. You just never know what kind of items are gonna get released up or released out and always list for lazies. Take a look at this, Don Ruma, 277,000 coins for a Don Ruma that I've held on my transfer list for about a month now after a team of the year. I had five, now I'm down to three, right? Cause I got a lazy sale. So keep listing that stuff up, you'll get some sales cause the market is still high, people have coins that are going out and they're trying cards. But that's kind of a full circle on the video for today. FIFA 23 news at the top, had to talk about that cause there's a lot going on and that could impact the game a lot, right? I just wanted to get some of my preliminary thoughts and get that information to you because it is being talked about a little bit more. Then of course talk about the Silver Star series promo and again, we're just chucking towards Friday. We're really chucking towards Friday where we'll get back into the normal swing of things for a big promo. Although I did get De Bruyne, Pogba, Elanga, Cherokee, Joe Wellington. I got a lot of silver cards in the club now. Silver Star's team is looking fire. So if you enjoyed this video, put a thumbs up on it. Comment down below if you have any questions and subscribe if you're new. It's been Nathan Putter Count and I'll catch you guys later. Peace.


Can understand me When everything I do is wrong Give me hope and consolation Who give me strength to carry on The wonder of love