Huge thanks for the great feed back, really appreciate it. Regarding the UI colours and icons - we wanted to show overall how the brand creates a visual founda

Huge thanks for the great feed back, really appreciate it. Regarding the UI colours and icons - we wanted to show overall how the brand creates a visual foundation for the rest of the syste. This is something that is a standard in other fields ofc, but due to the lack of designers (and especially non-technical ones) in oss, this step is often gets missed. Therefore, the whole concept basically tries to show why current visual brand limits the whole system. This being said, both UI and icons are non-final and are mainly for presentation purposes. For the icon matter the best thing would be to: - introduce some basic guides that can be easily followed by community and app developers - create an icon basis (like first 100 icons for the default icon pack) - introduce some automatic icon switch. For some icons these guides can be applied automatically with adjusted padding and sizing. Regarding the logo we always need to think of: - how dynamic we want it to be - context defined I noticed that frequent criticism so far was about logo either feeling imbalanced or being too simple. First of all it is not imbalanced technically, but it is indeed built this way that creates stronger visual dynamic than something more standard like git logo. Coming back to logo simplicity - we need this for a higher brand versatility, at the same time keeping it efficient. The more complicated the logo, the more time it would take to adapt it to various contexts (and sometimes the higher skill it requires). For community-maintained system having a complicated logo would make no sense cause it would just create hours and hours of extra work and design blockers in the future.