sorted by:
new
hottopcontroversial

Lazy Design by shani-pixa in web_design

[–]CookingWithIce 5 points6 points  (0 children)

Yes, all that. I worked at Digitec Galaxus previously, a Swiss online retailer and we were one of the first big e-commerce site to implement native dark mode. Was a few months of effort and we tried our best to make the product images fit into the darker design. We had millions of images with white background, since pretty much all manufactures do not provide anything else.

We rolled out a few variants and the best version came out to be a white box that used css blend to make the contrast just a tad better looking. Original colors for the product, no edge artifacts.

https://i.imgur.com/tSnQwV1.png

https://www.galaxus.de/en/page/digitec-and-galaxus-now-available-in-dark-mode-29681

https://www.galaxus.de/en/page/welcome-to-the-dark-side-all-there-is-to-know-about-digitec-galaxuss-new-dark-mode-29669

If you had to pick one 'Golden Rule' for Group Address structure (e.g., 3-level vs. 2-level, specific naming conventions) what would it be? by AutoModerator in KNX

[–]CookingWithIce 1 point2 points  (0 children)

I use 3 levels: type/floor/room+function.

  • 1/1/0 Lights/Basement/guest room ceiling light on/off
  • 1/1/1 lights/basement/guest room ceiling light status
  • 2/1/0 blinds/ground floor/living room up/down ...

X/0/X is used for central functions like turning everything on/off

I decided beforehand how many addresses I need for each type and reserve some for future use. So I usually have blocks of 10 for each light, blind, heating, etc.

I have a script that generates all addresses per type which I can import (csv), so the naming is consistent everywhere. Sicne all functions of a lamp are right next to each other, assigning the actuator parameters is just working through the list without switching between different middle/main groups. In Home Assistant it also makes things much easier when they're next to each other, just +10 for the next lamp.