Development considerations
After enabling the front-end pipeline to only deploy the front-end resources in AEM as a Cloud Service environment, there is some impact on the local AEM development and you have to tweak the git branching model.
Objective
- How to have a frictionless front-end and back-end development flow
- Review the dependencies between the full-stack and front-end pipeline
Local development considerations
Transcript
After this AM project conversion, the front-end and backend development can be parallel or somewhat independent of each other. However, you have to adjust your Git flow or branching model because for the local development using AM SDK, the backend dev team still needs client lib generation via UI.Frontend module. But during cloud manager deployment, you have to skip it. So please be mindful of it and that change is specific to your development process. I hope this was helpful and now you know how to convert a standard AM project to leverage front-end pipeline. Thank you and let’s keep exploring.
Adjusted development approach
- For the local development using AEM SDK, the back-end dev team still needs clientlib generation via
ui.frontendmodule but during Cloud Manager deployment to AEM as a Cloud Service environment you have to skip it. This surfaces a challenge on how to isolate the project config changes outlined in the Update Project chapter.
A solution could be to adjust your git branching model and making sure the AEM project config changes never flow back to the local development branch the AEM back-end developers use.
- As part of an ongoing enhancement to your AEM project, if you introduce new components or update an existing component that has changes in both
ui.appandui.frontendmodule, you have to run both full-stack and front-end pipelines.
recommendation-more-help
b2a561c1-47c0-4182-b8c1-757a197484f9