Hi Ivo,

I noticed a small layout issue in the Construction template.

In the default layout, the fixed-footer class is applied to container-footer. When fixed-footer is enabled, the layout works correctly. If the class is removed, the main container still receives an inline margin-bottom.

From the DOM:

This creates empty space below the content even though the footer is no longer fixed.

The space appears above the footer because the script applies margin-bottom to #g-container-site, which is the main page wrapper. So the margin does not affect the footer itself, but the main content container. If this margin remains active when the footer is not fixed, an empty gap appears before the footer.

It seems the value is calculated in template.js, where the footer height is read and then applied via jQuery as an inline margin-bottom on #g-container-site. If I disable the Atom that loads the script, the issue disappears.

In my opinion, margin-bottom should only be applied when the footer is actually fixed. If fixed-footer is not present (or the footer position is not fixed), the inline margin should probably be removed.

As a workaround, I added a small template.js override in the custom JS folder, so the core files remain untouched. The margin is now applied only when fixed-footer is present and the footer position is actually fixed.

Could you confirm whether this is expected behavior, or if it would be worth adjusting in template.js?

Thanks.