-
Notifications
You must be signed in to change notification settings - Fork 12
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
use shorthand properties #28
Comments
Hi! Thanks for your interest in this project. I agree, it could be shortened, but I think it also comes with some downsides. First, being verbose helps people learn a good foundation of layouts with flexbox. You learn the individual properties first, and then start combining them into shorthand if you want. Secondly, the implementation of this would feel rather clunky. For example, the I'm curious what benefits you think using these shorthand properties would provide - could you elaborate? What would you envision the implementation look like? |
The forms could look like this: container form:
items form:
This allows a clear understanding of which properties a shorthand property corresponds to. On the "markup" view, I suggest to add an option (checkbox) "do not use shortand properties" what do you think? |
Ok I see where you're headed. So maybe in the form we put section headings to divide it up, and then allow the option for shorthand in the markup... I dig it. Let me hack around on this with @davidleininger and see what we come up with! Thanks for the feedback, we appreciate it! |
Playground could use shorthand properties like:
Example:
could be shortened to:
The text was updated successfully, but these errors were encountered: