Commas, commas commas, always the bane of a poet’s and programmer’s life. Impressive stuff. There is a lot more going on under the ACSS hood than I realised. That’s real dedication. I was watching out of the corner of one eye but the other lazy one started to go on strike and started to stare out the window… with all those VS studio windows open.
After watching this video, I realized I need to learn more about SCSS. So far, I’ve only been using basic features like nesting. I’d love to see content that covers topics like loops, maps, and JSON.
I enjoy seeing your thought process and how you fix things when you come up against a roadblock. I think once every month or couple of months would be great for this kind of stream.
Definitely super useful to see the behind the scenes. Frankly sometimes I feel like using ACSS makes me a slacker on css, so looking at the development end is super and inspiring as always with your content. Thanks!
@Gearyco Very true...I guess slacker wasn't the most appropriate term. More like "I do amazing stuff with ACSS without understanding what's going on on the back end"...say that in 1 word haha
The icon framework is incredible, and identified perfectly as a necessary step for the card framework. One idea I tried to get through in the live chat is that maybe ACSS could lean into color relationships more and more in the future. What I mean by that is that as we get more and more Modules like icons, cards, buttons, etc. configuring the framework can get convoluted if there's not a lot of consistency of variations throughout the modules (example: border has light and dark, icon has light and dark, card has light and dark, buttons have light and dark, we have light and dark backgrounds and they're not connected). The idea that dark and light are confusing concepts in most frameworks and contexts is real and I think we all struggle with it. A future where we add a utility class on a section and all our buttons, cards, icons, and links immediately look as we designed them is the future I want to live in rather than style each element individually. I think this is already happening in ACSS, but I cannot yet put my finger on how configuration can get a bit more connected although I think it should.
super useful, no doubt - however it seems to only work with physical icons elements - how about using pseudo elements and/or base64 encoded svgs?? I try to avoid loading large css and font files like font-awesome for maybe just 20 icons all over the site - do you suggest to upload those icons as svgs into the media library - as to boxed or not boxed I'm not sure whether a default setting makes sense - I e.g. use icons more as a decoration element for e.g. the post date or post tag - don't see me using boxed icons there - however if the icons more serve like a button then a boxed version certainly makes sense.
Commas, commas commas, always the bane of a poet’s and programmer’s life.
Impressive stuff. There is a lot more going on under the ACSS hood than I realised. That’s real dedication. I was watching out of the corner of one eye but the other lazy one started to go on strike and started to stare out the window… with all those VS studio windows open.
This will be sooooooooo useful. It was impressive seeing you work at *2 speed ;-) Yes, definitely do more videos like this one.
After watching this video, I realized I need to learn more about SCSS. So far, I’ve only been using basic features like nesting. I’d love to see content that covers topics like loops, maps, and JSON.
A peek into your thought process and ACSS. From time to time would be great! Thanks, Kevin.
I had fun watching this and would enjoy more of these.
I enjoy seeing your thought process and how you fix things when you come up against a roadblock. I think once every month or couple of months would be great for this kind of stream.
Definitely super useful to see the behind the scenes. Frankly sometimes I feel like using ACSS makes me a slacker on css, so looking at the development end is super and inspiring as always with your content. Thanks!
Slackers cut corners ... Smart people just work more efficiently.
@Gearyco Very true...I guess slacker wasn't the most appropriate term. More like "I do amazing stuff with ACSS without understanding what's going on on the back end"...say that in 1 word haha
The icon framework is incredible, and identified perfectly as a necessary step for the card framework. One idea I tried to get through in the live chat is that maybe ACSS could lean into color relationships more and more in the future.
What I mean by that is that as we get more and more Modules like icons, cards, buttons, etc. configuring the framework can get convoluted if there's not a lot of consistency of variations throughout the modules (example: border has light and dark, icon has light and dark, card has light and dark, buttons have light and dark, we have light and dark backgrounds and they're not connected).
The idea that dark and light are confusing concepts in most frameworks and contexts is real and I think we all struggle with it. A future where we add a utility class on a section and all our buttons, cards, icons, and links immediately look as we designed them is the future I want to live in rather than style each element individually. I think this is already happening in ACSS, but I cannot yet put my finger on how configuration can get a bit more connected although I think it should.
super useful, no doubt - however it seems to only work with physical icons elements - how about using pseudo elements and/or base64 encoded svgs?? I try to avoid loading large css and font files like font-awesome for maybe just 20 icons all over the site - do you suggest to upload those icons as svgs into the media library - as to boxed or not boxed I'm not sure whether a default setting makes sense - I e.g. use icons more as a decoration element for e.g. the post date or post tag - don't see me using boxed icons there - however if the icons more serve like a button then a boxed version certainly makes sense.
yes, just upload SVGs.
time to time will be fine... the backend of ACSS