Reuse layout components across multiple locations without duplicating them

Admins want to define a layout component once and reuse it in multiple places, so that changes only need to be made in one place and stay consistent across the entire system automatically. Problem / Pain: When a complex layout component needs to appear in multiple places across the system, the only current option is to copy and maintain it separately in each location. This means that any change must be applied manually to every individual instance. Over time this leads to inconsistencies, increases configuration effort significantly, and makes it easy for instances to drift out of sync without anyone noticing. Impact / Benefit: The ability to define a reusable layout component once and reference it across multiple locations would dramatically reduce configuration effort and maintenance overhead. Changes would propagate automatically to all locations where the component is used, ensuring consistency throughout the system and eliminating the risk of instances getting out of sync. Example use case: An admin has configured a tile view for the files module with a specific set of display options. The same tile configuration is needed in several other places across the system. Instead of copying and maintaining the configuration separately in each location, the admin defines it once as a reusable component and references it wherever it is needed. When the configuration needs to be updated, the change is made once and applies everywhere automatically. Idea source: Internal suggestion Voting note: Vote for this idea if this need is relevant to you as well.