Expandir minha barra de realizações na Comunidade.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

Esta conversa foi bloqueada devido à inatividade. Crie uma nova publicação.

SOLUCIONADO

JCR

Avatar

Employee

Question from twitter: @AEM_Dev Is it possible to configure the path to <root>/jcr:content/cq:responsive/breakpoints? This should be in the design, not the content

1 Solução aceita

Avatar

Resposta correta de
Level 2

It seems to me that it's in the wrong place out of the box.  The grid breakpoints are configured in a single language for the content, and the hardcoded CSS breakpoints are in a specific design.

i.e.
Config: http://localhost:4502/crx/de/index.jsp#/content/geometrixx-media/en/jcr%3Acontent/cq%3Aresponsive/breakpoints

CSS breakpoints: http://localhost:4502/crx/de/index.jsp#/etc/designs/geometrixx-media/clientlibs/css/grid.less

I would assume (it would seem silly not to) that all of the breakpoints for your site, for all languages would be the same.  And if they need to be changed, they should be changed at the design level, since changing one without the other breaks things.  The content doesn't know how to render itself, it just hands that off to sling to figure out, so it shouldn't have the responsibility of telling that thing downstream how to do it.

Even better would be to store the configuration with the template, since different templates could theoretically have different breakpoints.

Ver solução na publicação original

2 Respostas

Avatar

Level 10

Avatar

Resposta correta de
Level 2

It seems to me that it's in the wrong place out of the box.  The grid breakpoints are configured in a single language for the content, and the hardcoded CSS breakpoints are in a specific design.

i.e.
Config: http://localhost:4502/crx/de/index.jsp#/content/geometrixx-media/en/jcr%3Acontent/cq%3Aresponsive/breakpoints

CSS breakpoints: http://localhost:4502/crx/de/index.jsp#/etc/designs/geometrixx-media/clientlibs/css/grid.less

I would assume (it would seem silly not to) that all of the breakpoints for your site, for all languages would be the same.  And if they need to be changed, they should be changed at the design level, since changing one without the other breaks things.  The content doesn't know how to render itself, it just hands that off to sling to figure out, so it shouldn't have the responsibility of telling that thing downstream how to do it.

Even better would be to store the configuration with the template, since different templates could theoretically have different breakpoints.