-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments on README.md #3
Comments
One more thing: responsive considerations? i.e. should folks write media queries for progressive enhancement, small to big or big to small? |
Thanks @feesh! This is all such excellent feedback! 🎉 Fixed the typos! I was feeling iffy about giving people the go-ahead with utility classes so I removed them and will try to refactor those out of our code at some point. I also went ahead and rewrote the sentence under the class naming section so that it makes sense and doesn't contradict itself (lol at me). I contributed a sentence about indentation and no trailing white space, too! I'm not totally sure about commenting, history and visually I feel like the comments with the * are more visually distinctive but would love to chat with more folks on the team about it and see what they're all comfortable with. Thanks for pointing this out!
I need to do this. We have a ton of work to do around standardizing this. Right now I'm thinking about bringing in an icon font to handle icons and svg inline images add requests so I'm not totally sure yet. Will definitely invest more thought around svg going forward. Going to expand on Accessibility in V2, I've desperately wanted to improve my own skill set in this area so now I have a reason to do some more research and testing.
I'm working on building out variable scales that are unique for desktop vs. mobile. This is how Amazon handles it and I'm hoping that we can do the same. Thank you so much 💟 |
Awesome! This is super fun to read through, thanks for sharing! Working on a styleguide proj at work, too, so pretty cool seeing your process. 😁 Related: https://twitter.com/jina/status/649651827282079744 Re: comments — I got used to the I also need to step up my accessibility game, so I'll let you know if I find any great resources. :) (One more nit, sorry — Sass is capitalized, not uppercased. I think it's not an acronym?) |
Last one I swear: "so we should alway order them" <-- always I like the way you group your CSS properties, too! Potentially stealing that one... |
I'm not sure if @feesh was getting at this or not, but the documentation says...
Then clearly contradicts itself in the example: line-height: 1.5; |
@Fauntleroy commented on Oct 16, 2015, 1:27 PM EDT:
I guess we could update this to say unit-less measurements as opposed to integers 😀. |
@jalcine 🙏 |
When you say Targeting descendant selectors should be avoided does that include Wouldn't that be redundant in some cases? |
@adekunleoduye I would use your best judgement when it comes to While I can see the appeal of styling tables with descendants, I almost never style lists with them. Does that make sense? It's Friday I'm tired as hell, lol. |
Regarding spacing, what guidelines do you have for spacing when nesting? |
Just a few things —
Typo on "hyphens"
I'm a little iffy on the utility classes, I personally prefer adding them as mixins so that the HTML doesn't end up littered with a ton of stylistic class additions, but if they're not used hella then maybe they're okay just as classes?
These two sentences seem to contradict each other — if the compiler is reordering them anyway, maybe just the second sentence is fine?
Are you also specifying two-space indentation? And maybe no white-space at the ends of lines?
Whole integers for
line-height
, or do you meanletter-spacing
too?Do you allow Sass comment styles too with
//
, or do you treat multi-line comments differently?Maybe a note about using
.svg
for any vector images or icons?Nit: double space between "HTML tag"
Also maybe a section about accessibility best practices, like making sure
<img>
have alt tags, etc? If you're expanding on the Sass syntax prefs, maybe also including recommendations around nesting, folder architecture, etc. :)http://sass-guidelin.es/ is another good resource!
The text was updated successfully, but these errors were encountered: