As of 2026-05-11T07:41:19-04:00 I no longer feel this limit of 4 cells is as important as Engineering had made me believe, per some conversations I had. Nothing 'bad' is going to happen with allowing more cells if we have a justification for it (such as to reduce fragile authoring, reduce amount of code complexity).
Older ticket info
Check this documentation for how best to fix. https://www.aem.live/developer/component-model-definitions#creating-semantic-content-models-for-blocks
Also https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/field-types might be helpful.
https://bhellema.github.io/ue-modeler/ - Ben's modeler
It seems we need to have more cells per block for complex configurations in general, so 4 is not enough even if we were better at collapsing and combining some fields.
As of 2026-01-13T06:27:01-05:00 this is what we have -- I allowed for 8 for now in https://github.com/aemsites/idfc/blob/main/.eslintrc.js but we should try to revisit these and fix as much as we can.
NOTE that we'll need to re-author (or fix via crxde) any content where we change UE names.
/Users/chelms/IdeaProjects/internal-aem-eds-poc-en-idfcbank-optimization/component-models.json
422:5 error Avoid using more than 4 cells in a block, found 5 for accordion xwalk/max-cells
537:5 error Avoid using more than 4 cells in a block, found 6 for banner-item xwalk/max-cells
574:11 error Avoid using orphan collapsible field names xwalk/no-orphan-collapsible-fields
598:5 error Avoid using more than 4 cells in a block, found 8 for cards xwalk/max-cells
729:5 error Avoid using more than 4 cells in a block, found 7 for card xwalk/max-cells
806:5 error Avoid using more than 4 cells in a block, found 9 for category-nav-item xwalk/max-cells
1001:5 error Avoid using more than 4 cells in a block, found 5 for cc-hero-slider-item xwalk/max-cells
1024:11 error Avoid using orphan collapsible field names xwalk/no-orphan-collapsible-fields
1245:5 error Avoid using more than 4 cells in a block, found 5 for steps xwalk/max-cells
1338:11 error Avoid using orphan collapsible field names xwalk/no-orphan-collapsible-fields
1350:5 error Avoid using more than 4 cells in a block, found 6 for table xwalk/max-cells
1542:5 error Avoid using more than 4 cells in a block, found 5 for tabs-upi-link xwalk/max-cells
As of 2026-05-11T07:41:19-04:00 I no longer feel this limit of 4 cells is as important as Engineering had made me believe, per some conversations I had. Nothing 'bad' is going to happen with allowing more cells if we have a justification for it (such as to reduce fragile authoring, reduce amount of code complexity).
Older ticket info
Check this documentation for how best to fix. https://www.aem.live/developer/component-model-definitions#creating-semantic-content-models-for-blocks
Also https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/field-types might be helpful.
https://bhellema.github.io/ue-modeler/ - Ben's modeler
It seems we need to have more cells per block for complex configurations in general, so 4 is not enough even if we were better at collapsing and combining some fields.
As of 2026-01-13T06:27:01-05:00 this is what we have -- I allowed for 8 for now in https://github.com/aemsites/idfc/blob/main/.eslintrc.js but we should try to revisit these and fix as much as we can.
NOTE that we'll need to re-author (or fix via crxde) any content where we change UE names.