[10:03:11] hey! [10:03:17] Hello [10:03:24] Meeting time! [10:03:29] `chassisteam [10:03:29] sfrisk: agcolom, arschmitz, arthurvr, gnarf, helen, ianmaffett, jzaefferer, michaelarestad, rxaviers, sfrisk [10:03:59] hey everybody [10:04:08] hey [10:04:12] hey [10:04:45] Agenda: https://docs.google.com/spreadsheets/d/1FUdRcAq2d8njs8KAcfQmEyoZL74SXLsLp1rtc7E9z_I/edit?usp=sharing [10:04:58] (Not quite finished, give me a moment) [10:05:48] Hi [10:07:04] Okay, first up, isaacdurazo, any update on logo stuff? [10:07:56] sfrisk sorry but no updates yet. I have been incredibly busy [10:08:01] I should have time this week [10:08:02] Totally understandable [10:08:21] we are very close and I really want to finish it [10:08:25] Life/work has a tendency of making us busy [10:09:30] Wah wah. [10:09:41] on the typography note, michaelarestad has been continuing work on the typography PR [10:10:00] if anyone has any comments on it, you can find it here: https://github.com/jquery/css-chassis/pull/67 [10:10:20] you mean https://github.com/jquery/css-chassis/pull/57 I guess? [10:10:22] Yep. Mostly picking fights with arschmitz on :focus. [10:10:31] lol [10:10:34] yeah [10:10:39] apparently I fail at linking to stuff [10:10:47] lol [10:11:03] thats the wrong PR [10:11:05] :D [10:11:17] https://github.com/jquery/css-chassis/pull/57 is the typography PR [10:11:20] I'm fully confident we'll tackle the focus issue along with adding more base type styles. [10:12:04] Upon reflection, I'm going to remove the removal of outline as well as base link styles. [10:12:17] Those should be defined at a component level. [10:12:26] Makes sense to me [10:12:34] Because arschmitz is right. Mostly. [10:12:35] marestad: my only concern is with accessability [10:12:42] lol [10:12:43] I can understand arschmitz's concern with accessibility [10:12:50] which he just typed [10:13:01] It's not a big deal with just the links, but when we start wrapping images in `a`, etc... [10:13:10] Not having the outline is bad. [10:13:24] definitely [10:13:29] marestad: even on links what if your tabing through links and using the keyboard [10:13:43] there should be a clear indication where you are in the document [10:13:46] Course you could have the project like the one I'm on, where they want outlines for buttons/regular inputs/etc [10:13:52] but HATED them on radio buttons [10:14:01] you might only be trying to get to a checkbox but its hard when you cant tell where you are on each tab [10:14:08] so there is literally no way of telling if you're focused on a radio button, because we were told to remove it [10:14:17] thats horrible [10:14:28] Oh, I fought it [10:14:31] I lost :-( [10:14:37] arschmitz: I agree about the links, but I have a better idea than stock outline for those. :) [10:15:05] marestad: like i said in my comment we do a different outline in mobile right now [10:15:13] Totally. [10:15:15] im not convinced its the best way but it does solve some problems [10:15:29] I agree it's something better handled at a component level [10:15:44] but seeing as i use it on the project im in charge of im obviously not totally against it lol [10:16:31] Cool. We'll figure it out. [10:16:46] Sfrisk: Is someone is working on form validation styling? [10:17:03] not yet, but that I feel is something that kinda needs typography in place first [10:18:26] we still need the SCSS style guide though [10:19:42] not only typography but its highly dependeany on form styles [10:19:42] Can I work on typography? [10:19:50] no, because marestad is working on that [10:19:54] there is a PR in place [10:20:03] oky [10:20:08] although, actually, I guess that's up to marestad [10:20:10] I mean you can. I can give you commit on my repo. [10:20:13] if he's got space to help [10:20:37] I can help. :) [10:20:41] you'll want to coordinate though, so you don't step on each other's shoes [10:20:43] noufal, ping me after and I'll add you. 8D [10:20:59] oky :) [10:21:43] once that lands though, we can start focusing on the other phase one stuff [10:21:58] marestad: can we have a small meeting after this one? [10:22:27] like buttons and other form elements, tables, form validation styling, etc [10:22:43] which we should be able to have a few different PRs going on at the same time [10:22:55] (yay for early awkward growing stages) [10:24:40] it's bit hard to style buttons if colors are not defined [10:24:52] sfrisk I didn't find HTML style guide in this weeks agenda [10:25:14] oops, my bad [10:25:18] but we can give user a choice to choice color. [10:25:22] today has been a bit hectic at work [10:26:00] looks like further discussion has been happening in the HTML style guide [10:26:28] It's alright I thought maybe it wasn't a priority this week hence I asked :P [10:26:58] nope, it's on the list, I've been keeping up with the discussions [10:27:00] colors in some ways i would like to reflect the final logo color variations if it works out [10:27:16] the defaults [10:27:25] arschmitz - I agree with you there, I kinda want to see what isaacdurazo comes up with this week [10:27:33] and use those colors for the basic semantic colors on the site [10:27:39] yup [10:27:46] like that blue might be a good default button color / link color or something [10:28:12] or blue is a common active color [10:28:21] yeah [10:30:23] Also some further discussion has happened on Form Validation Styling [10:30:57] I'm going to update the first message in the issue to be a bit clearer, but I agree with marestad's idea of having at least two sets of error messaging components [10:31:08] one for the inputs, and another that is messaging related [10:31:56] yeah the plugin pointed to in the issue has two formats too [10:32:02] list at the top [10:32:06] or on each input [10:32:06] yeah [10:32:29] List at the top is better option. [10:32:30] Might put at the beginning of the issue a very clear definition of done for that Issue [10:33:03] I don't think we should force list at the top, or at each input, but allow for both [10:33:16] In-context notices are super important. [10:33:33] Especially since validation needs can vary project to project [10:33:36] At the top tends to lose and disconnect from the spot the issue takes place [10:33:41] Right. [10:34:07] Especially if you have a long form [10:34:20] we shoudl really look at that plugin [10:34:27] If you have to scroll up to find your validation message, that not a great user experience [10:34:27] its the most used form validation on the internet [10:34:36] yeah [10:34:41] I think I've used it for projects before actually [10:34:44] and its the #19 piece of JS on the internet [10:35:12] noufal: We can indeed have a short meeting after this one. (sorry for delay. In two meetings) [10:35:23] lol [10:36:05] Sfrish: We can check the size of form and than applay validation styling according to it? [10:36:14] apply* [10:36:50] Gotta think outside of conventional forms. Often, in web apps, form elements are in unique places by themselves, in modals, etc. [10:37:26] we are just providing styles [10:37:30] so we wont do anything [10:37:35] Well, we won't be doing the JS side of things [10:37:39] Yep. [10:37:42] that will be up to the developer to implement [10:37:44] we just provide the style and let people do with as they please [10:38:06] we'll give them the option to use either one, so the documentation for who to write it in your html, it's up to them to implement it [10:38:29] Marestad I develop a Web app for my start-up can u see the modal design ? [10:39:43] do you want to see the modal design? [10:42:23] Hello, sorry for being late. [10:42:32] Okay, so I think next priority is definitely finalizing the color definitions and setting up a PR for that [10:42:33] very late [10:42:37] even if it's just placeholder colors [10:43:00] Yep. I was actually going to use the colors in the last mockup of the blue logo. [10:43:05] also if anyone wants to work on the SCSS style guide - we do need development on that [10:43:09] And create some semblance of a palette. [10:43:16] oo, sounds good marestad [10:43:48] I'm definitely interested in that sort of stuff too, so feel free to ping me about it [10:44:13] and Isaac is going to give us some use cases that work with that blue logo - so we should have some other "Official" colors for the pallet [10:44:23] I'll try to add a list or something like I did with the HTML style guide [10:44:32] sounds good, slayslot [10:44:42] there should be a issue already created for scss style guide [10:44:56] yes, I found it [10:45:02] also arschmitz was awesome this week, and updated naming convention, typography and grid system issues this week [10:45:21] to have a summary at the top of the page about where we currently are with discussions, since those issues were a bit long and complicated [10:46:06] Awesome. [10:46:27] especially naming conventions [10:46:46] Naming conventions is a beast. [10:46:49] yeahhhh [10:46:54] there were some feels in that one [10:47:36] as well as in icons [10:48:14] Related to icons a bit: http://slides.com/sarasoueidan/building-better-interfaces-with-svg#/ [10:48:36] SVGs are awesome [10:48:52] :) [10:49:00] true that [10:49:06] I think it will be cool to see what sort of animations we can do with the logo [10:49:32] :) [10:50:27] Also, GSoC students, as you may be aware, submissions ended on Friday, and we're in the process of picking what applications we can [10:50:46] oky :) [10:51:16] Okay thanks. [10:51:16] If we want further clarification on anything in your proposal, we'll leave a comment on your proposal [10:52:09] sounds good [10:53:07] Okay, can anyone think of anything else they wanted to bring up? [10:54:27] Going once [10:54:31] Going Twice [10:54:58] I have some question about form validation styling [10:54:58] mind explaining what are those numbers in there? http://slides.com/sarasoueidan/building-better-interfaces-with-svg#/19 [10:55:37] noufal: what sort of questions? [10:55:39] GreatDanton: thats not something for the meeting [10:55:43] ok [10:56:28] Some developer do validation from Controller how our stylling help them? [10:57:03] like a Controller in Angular.js? [10:57:22] Like MVC framework. Laravel [10:57:26] or a controller in server side? [10:57:32] yes [10:57:41] no matter how they do their validation server or client they still need mesages and styles [10:57:50] well? developer would render the message with our style [10:57:59] They would follow our standards for how to print out the validation [10:58:16] using the markup we give them to use [10:58:23] yes, what sfrisk said [10:58:32] It will be difficult for the [10:59:08] If user want validation at the top it is not the problem [10:59:32] does laravel autogenerate form markup? [11:00:11] If the develper want validation error next to the input field. it will case problem for the developer [11:00:28] yes laravel autogenrate a list for errors. [11:01:06] this really seems like something not for the meeting [11:01:14] Yeah, just what I was about to say [11:01:14] oky sorry :) [11:01:16] definitely [11:01:20] We can move it to css-chassis [11:01:28] noufal ping me later on this [11:01:36] oky sure [11:01:37] this is more of a discussion on how to get a server side language to implement Chassis, rather than Chassis itself [11:02:00] And on that note, I call this meeting to an end