A little experience in doing website refactoring

     I summarize the problems encountered when doing website refactoring:
    1. In the early days, the website was designed without a front-end architecture, which resulted in a lot of front-end js being incompatible with various browsers when the page was modified later. The front-end architecture is very The important thing is that the architecture must be carefully constructed in the early stage. It is best to rewrite a layer of front-end architecture js to deal with browser incompatibility.
    2 When we deploy to the pre-release environment, due to the difference in domain names, the URL referenced in the page is modified. There are many changes to the domain name, so it is best to use a unified header file, which is convenient for the application of public domain name variables
    . 3 Because the development environment, test environment, and formal environment are different, the configuration often needs to be changed, so it is necessary to change the relevant files for configuration and deployment. You can use maven's profile feature to deal with this problem.