I would like to ask how to manage the previous static resources.

I would like to consult the bosses" knowledge and experience in project management.
at present, the company still adopts a very traditional jsp, which does not use popular frameworks such as vue,angl,react and packaging tools such as webpack. Now we are mainly faced with the following problems

. < H2 > 1, picture library is bloated < / H2 >

now backstage people say that it takes a lot of time to pack 200m + often, especially pictures, which are especially large; there are many pictures used in the old version in the picture library, which may not be used with the iterative upgrade of the project version. but no one cleans it for a long time, so they forget what has been used and which are useless, so there are more and more pictures over time; the more difficult it becomes, the more difficult it is to organize

. < H2 > 2, some plug-ins have multiple versions < / H2 >

with the change of the company"s developers, there are several versions of many plug-ins. For example, there is a swiper3 version in the swiper; project, which should be used by my previous development. Later, I use the new swiper4 version on my page. Assuming that I leave, then the next person may use the swiper5 version, and the situation will continue to deteriorate. How should I manage these now

at the same time, these js files are also faced with the problems of the above pictures. Swiper, may be used in this version, but in the next version, it may not take a long time to use swiper,. Although these js files are much smaller than pictures, it is not a problem to keep them.

< H2 > 3Pergent CSS is difficult to manage < / H2 >

this is rather difficult. The project is quite long, almost 4-5 years old, and some have been on it for 8 years. Sometimes it seems useless that css has caused the page explosion. Naming conflicts are also a problem.
the current practice of writing css is to write the style of this project in a css file for each iteration and upgrade of the version. Then when rewriting on the old project, multiple versions of css will be introduced, and the conflict is also very uncomfortable

.

at present, these three problems are more prominent, so I would like to ask your experienced seniors, how can I manage these projects well? Or what does your company do?

in addition, if the company starts a new project, how to regulate document management? At present, a new and effective document management specification is urgently needed. If you want to start afresh, try to find out an effective management method

.
Mar.17,2022

  1. cdn access is considered for images, and images are migrated to the cloud to reduce packaging volume.
  2. 2, 3 this situation is relatively troublesome, basically consistent with my current situation, the activity page has accumulated a lot of iterative source code, so each file is disorganized. So I think refactoring will be better. Or make it configurable.
Menu