Clarification: intended usage of src/assets/homepage/*.css.tmpl (template vs build output) + mobile layout impact

[hagaybar]

Hi team,

I am opening this issue following guidance from an active Primo support case (08311602 - NDE IN MOBILE), in order to get clarification on the intended and supported usage of these customization files.

We are using the Primo NDE customModule and noticed that in the upstream repo there are homepage-related files under:
src/assets/homepage
with the suffix .css.tmpl (containing variables/mixins).

In our local/customized environment, these files currently exist as .css (e.g., homepage.css), and are included in our deployed customization package.
We are not sure whether:

1. .css.tmpl files are intended as examples/templates only, or
2. there is an expected/official build step that transforms .css.tmpl into deployable CSS (and if so, where that is documented).

Practical context:

• On mobile, our landing page showed horizontal scrolling.
• When testing with no customization, the mobile layout behaves correctly.

Questions:

1. Are customers expected to rename/convert .css.tmpl files to .css and compile them (resolve variables/mixins) before deployment?
2. If there is an official build process that outputs .css from .css.tmpl, can you point us to the documentation or the recommended workflow?
3. If .css.tmpl is not intended for deployment, would you consider adding a short note in the repo/docs to clarify this and prevent accidental deployment?

Thanks in advance for guidance.