This message was deleted.

Fwiw, I know that CSS is fairly basic on the “writing code” spectrum, but I must start here from a time vs. impact vs. cost perspective.

@able-island-14078 I’m a dev and I haven’t done that for several reasons : • CSS classes change, unfortunately, it’s unreliable. Any cheatsheet written 6-12 months ago would not be fully valid today. While Stacker tries to keep classes that were defined previously, it’s not fully reliable. I do not know if 1% or 20% or css classes change, causing regressions, but I know it happens from time to time. • it’s usually just faster to simply look at the code and find the class I need that finding the equivalent in a cheatsheet, assuming the classes do exist (they don’t always) • it’s a work in progress, I often ask the Stacker team to add new CSS classes for some components that don’t have any and are therefore really hard to target So, i’m kinda aware that any CSS I write today might break tomorrow. It doesn’t happen so often though, I’ve written CSS a year ago that still works fine today. :)

Hey @able-island-14078, We will look into having more styling documentation next year. What specifically would you like to see? @sticky-night-20812, I agree with you—we can and will be more customization friendly in the future.

@elegant-eve-85294 I think people would like to see examples of what’s possible, not only to prove them that it is indeed possible, but also how to do it and inspire them, give them ideas. Also, what I would personally like very much is for CSS classes to be systematically added, because asking for them to be added is time consuming and ineffective. Any element should be up for being customised, and CSS classes are the easiest way for that. And, sometimes, it needs to be smart, like for tabs, having both CSS classes for the tab’s index and the tab’s name would be useful for variety of reasons. Most of the time, a static CSS class that doesn’t change is good enough, though.

@gorgeous-queen-48490 ☝️

Also better names for the classes

@elegant-eve-85294 I think the top of @sticky-night-20812’s second post got it - I’m pretty quick at picking stuff up, but don’t have explicit experience building my own CSS before (Webflow is the extent of my experience). Show me the basic frameworks, and I can run. To be completely honest, all I’m looking to do is match the button colors and fonts to my website and emails. The PM in me would be surprised if this wasn’t most of what the CSS-shy folks wish they could do. Show me how to change those elements, and you’ll probably give me enough of the mental models necessary to go and play with the more advanced stuff. (Tangent: Making CSS feel easy would be a very cheap product-driven growth test. Pro would look much more attractive if CSS didn’t seem so knowledge-prohibitive.)

@able-island-14078 Perhaps the advanced button color matching and the font is something we could have as an appearance setting in the future, rather than asking you to enter custom CSS. You can already choose the color of the buttons and UI elements in App Settings > Appearance, but the color choice is basic. I understand how this might not be enough for companies with very distinct color schemes. Perhaps there’s something we can do for you here. Can you please reach out to support@stackerhq.com with your color and font preference along with the App URL?