Under what circumstances should the website page be changed to a static webpage for publishing?

The static WEB interface enters the final step, which allows administrators to select projects for static access by sub-portal and sub-location, mainly the home page. The efficiency is very high. The static project is set according to XML, a website administrator can complete static publishing of thousands of home pages within several minutes. However, when I entered the page turning part, I thought for a whole day and thought that the path of the previous few days may have gone wrong.

To know where the error is, you 'd better first see why the WEB interface should be static. I don't care if the so-called failure to turn WEB interfaces into static pages is poor technology for more than two years. In fact, static pages are only due to search engine requirements today. In other words, if there is not a huge access pressure on the search engine, but just a human click, there is no need to consider static provision of dynamic web pages. This is the reason why the road may go wrong, because static homepage can reduce the access pressure for people. For search engines, if the page tip is also provided in pseudo-static form, it doesn't matter if the homepage is used, because the search engine searches the entire website along the link. If the homepage is static, it is no help to relieve the pressure on search engines. If all the alienated webpages are static, how can they afford the project, including editing users' websites?

The reason for making the homepage static is mainly related to the bad website design practices in China: the homepage is always very big and full of rubbish that nobody can see. Therefore, if the audience always comes to the home page, the load on the home page is dozens of times that of the subsequent pages. Static content saves resources. But in fact, the current trend, or the general trend of foreign websites, is to use a streamlined small homepage, so static is not much necessary; if the access load comes from the search engine, it is unnecessary.

So what content should be provided on a static webpage? The webpage can be roughly divided into three categories: one is a navigation webpage, which has few changes and is suitable for providing static pages; the homepage of foreign websites is generally in this form; the second is the content classification list and summary webpage. These are relative to the book directories. If they are frequently updated, static webpages are difficult to do, mainly because there are too many content to be updated in real time, it is generally suitable for dynamic web pages. Third, content pages, such as the content of articles, are rarely accessed and rarely changed, and are suitable for changing to static web pages. The common homepage of Chinese websites is to confuse the first and second types of functions. The function of my system is to convert the first class to static at present, which is quite useful. However, it is not appropriate to change the second class to static. This is where I am wrong.

"Converting a dynamic page to a static page" seems simple, but you only need to do it to know what is appropriate and what is not appropriate.