There are many applications on vue development pages.

try to make a project, using vue+webpack, project will have a lot of pages, do not know how to develop
about pages:

  1. the number of pages is very large, ranging from hundreds to hundreds;
  2. almost every page is a separate page, and of course there is a reuse part;
  3. the main page is a menu page. Clicking on the menu item will display the subpage in the space of the current page and operate in it.

I don"t know how to develop:

  1. components, that makes the page .vue seems easiest, but it feels like there are two problems:
    a. Will it cause performance problems if there are too many component, switches on the same page? component seems to rebuild one for each switch.
    b. Because there are so many pages, will initialization be very slow, and users may only use fewer parts;
  2. multiple entrances. Feel that there will be problems:
    a. Because there are so many pages, the flexibility of the multi-entry mode will be reduced. After all, each entry has to be configured once;
    b. Use hierarchical relationships to create fewer multiple entries, that is, every 10 menus are in groups, and only 10 entries are created, but you don"t know the practicability of this model;
    c. Will this have an impact on the use of common modules?
  3. using iframe,iframe seems more manageable, but using iframe in vue-cli seems unfriendly and not easy to reference.

beginners, it may be a little obvious, but I would like to point out if there is a better plan.

Mar.17,2021

you can actually solve this problem with one solution. That is, the route is loaded lazily, so there is no need for more entries. Users click on that page and then load the js and css, related to that page. As for the performance problem, vue virtual DOM, does not have to worry about it.


use vue-router pages to be all componentized, with only one specific entry, and all other pages are decomposed into components. The completion of the
component requires you to analyze the business logic, write what you call a "page" with the same structure as a component, and then load it on demand.


Multi-page development is very simple https://codeshelper.com/a/11.


I think it's more convenient for you to do this with routing

.
Menu