-
Notifications
You must be signed in to change notification settings - Fork 0
Consider moving non-layout styles to separate non-clj files #129
Comments
@mehdisadeghi is this about moving the styles to separate files to have a sort of branding style? or about moving the styles out of clojurescript. I think we should pick one of the two objectives but not both since I consider them contradictory in our case. The problem is that if we define the styles in json files then you would have to use them like
Which is a pain to use for developers. On the other hand if we define the styles in clojurescript files like
It would be very easy to use for developers but changing it would require a bit of clojurescript knowledge. |
I was thinking of moving them out of clojurescript, in a practical way. If separate style clojurescript files is the way to go I'm fine with that. The main idea is hard-coding layout while letting colors and other non-layout styles to be defined separately and modified independently. In old-fashoned web it is possible with using CSS selectors, however I don't know how one can do it in cljs or react-native. |
I think we might also be able to get around from this by having a single style variable with all styles inside. Like:
which reads much better than the one above and it not that curversome to use :) On another topic, and sorry for the ignorance. Could you explain to me what you mean by layout vs non-layout definitions? to be honest I have only bare knowledge of UI concepts so I just go and build the stuff without worriying too much about it, so obviously it is not the most structured way 😅 |
It sounds good to me.
Sure! By layout I mean any CSS rule that defines where things should be positioned/displayed. By non-layout I mean the rules that only change the aesthetics of the elements and not their existence and positioning :)
Don't worry! Me neither 😅 In some front-end projects (to the extent that I know) people use variables in sass to define brand-colors and some repetitive variables, afterwards they use those variables all over the code to style their elements. So if they change a brand color in the main file it will be reflected everywhere in the code. |
I agree with this. But I think I would wait until you show me some examples of this to get on board. PR welcome :) |
There are two types of CSS rules in our cljs files: layout rules and non-layout rules. I suggest to move all non-layout CSS rules to separate sass files or similar, where we can modify them and update branding colors and styles without having to touch clj source files.
The text was updated successfully, but these errors were encountered: