Hi all and Stefan in particular

I am in the process of setting up a maven build for a joint frontend
(HTML, CSS, JS) and backend team (Sling / AEM).

The goals for the frontend team workflow are:

- use Node.js based tooling / frontend build (integrated using
frontend-maven-plugin - works)
- develop HTL templates and sample content (JSON via initial content
and fsmount)
- develop using SCSS and TypeScript, which is compiled to CSS and JS
by the frontend build into target/classes
- use as little maven as possible
- day to day work is done on the FS using Node.js based tooling with a
"watch" job and with live-reload or similar
- development speed is essential, i.e. changes done on FS should be
visible in a browser in < 500ms

Due to the compilation step, which generates CSS and JS in
target/classes, I would like mvn sling:fsmount to set up a FS resource
provider mapping for target/classes rather than
src/main/content/jcr_root (or maybe both, with service.ranking so that
target/classes is preferred). As far as I can see the "fsmount" goal
currently determines which configurations to create from the
filter.xml file (in case of filevault packages), but there is no way
to explicitly configure other mappings.

- Are my above assumptions regarding the state of "fsmount" correct?
- Do you think extending the fsmount config to allow for explicit
mappings would be useful?
- Do you have experiences to share with similar setups?

Regards
Julian

Reply via email to