A business logo is measured, not assumed. A square transparent emblem, a wide wordmark, and a tall banner each get different treatment, because one layout cannot flatter all three.
Business logos arrive in every proportion: a tidy square emblem, a long horizontal wordmark, an awkwardly tall banner, a transparent PNG, an opaque JP, a photo of a sign. The lazy move is one logo slot with a fixed size and a grey chip behind everything. That slot flatters roughly none of them: it letterboxes the wide ones, crushes the tall ones, and puts an ugly grey card behind a logo that was designed to float.
Doozer caches each logo's aspect ratio and lets it decide its own treatment (businessLogoShape() / businessLogoClasses() in includes/logo-favicon.php):
chip behind it, because it was drawn to sit on any background.
the footer, where its proportion is an asset instead of a problem.
The insight is that a logo's shape carries intent — a square transparent mark wants to float, a banner wants width, a tall crest belongs low and small — and that a single slot silently overrides all of that intent. Most sites never think to measure the asset before framing it; they pick one frame and make every logo suffer it equally. Reading the aspect ratio and branching is a small amount of code that removes a whole class of "why does this look off" that no one would ever file a bug about. Same family as category-aware call intent: the shared component adapts to the specific thing it is holding, rather than forcing the thing into the component.