our group"s projects used to release front-end files in a back-end package. Recently, I was doing the separation of movement and movement, and I encountered a problem.
the front-end partner told me that when using vue, you shouldn"t package all the front-end content of the entire project in one front-end project. It is said that if you do so, it will lead to a page to load the content of the whole site, the speed is very slow. Therefore, their approach is to create a larger feature for each new development as a separate front-end project, to manage Git separately, and to package dist separately.
in doing so, there was no problem in the past when the front-end files were released together in the back-end package. As long as the front-end partner sends me the built files, I will put these front-end files in the back-end project and submit them for Git management. But now with static and dynamic separation, I need to provide independent Jenkins tasks to front-end partners to send front-end packages. And every time they develop a new feature, it means to create a new project on Git. Therefore, I also need to provide them with a new Jenkins task. Although this is not impossible, I always feel that there should be a better way. I would like to ask you bosses, what should we do?