We should somehow let users know that we have two set of properties, one which tries to keep as closes as CSS references (I'm using Mozila docs here) and another which is solely focused on Bevy itself, which can be Ui or even other utilities later on.
This issue is reserved for separation on source code level,
Outcome:
split properties implementation code in two categories:
MSD CSS Properties would be in one file
the custom properties, invented for Bevy would be in separate mod, would be kept behind new "custom_properties" feature that will be enabled by default with option for disabling.
We should somehow let users know that we have two set of properties, one which tries to keep as closes as CSS references (I'm using Mozila docs here) and another which is solely focused on Bevy itself, which can be Ui or even other utilities later on. This issue is reserved for separation on source code level, Outcome: