You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 23, 2021. It is now read-only.
Hi,
As I know, vuetober is designed to setup a Single application, with only one index.htm delivered.
However it's hard to migrate my old website pages into new structure in short time.
If there is any way that I could make multiple pages with many entry point?
/ index.htm <- old static homepage /products/:id products.htm /users/:id users.html /app1/:all?* app1.htm <- new /app2/:all?* app2.htm <- new
Any advices will be appreciated
The text was updated successfully, but these errors were encountered:
Hi, at the moment there is not a way to have multiple entry points, but that would be a great feature! It could make Vuetober themes incrementally adoptable, rather than being all or nothing.
The bulk of our configuration magic happens with html-webpack-plugin, and writing the .htm files to disk. If we expanded upon this to look for all .htm files in a particular directory, I don't see any reason why we couldn't support multiple entry points. We could even have a directory set aside for "regular" October views, and just copy it into the appropriate output directory as part of the build process.
My time is pretty limited at the moment, but I'd love to see any experiments done with this!
Hi,
As I know, vuetober is designed to setup a Single application, with only one
index.htm
delivered.However it's hard to migrate my old website pages into new structure in short time.
If there is any way that I could make multiple pages with many entry point?
/
index.htm <- old static homepage/products/:id
products.htm/users/:id
users.html/app1/:all?*
app1.htm <- new/app2/:all?*
app2.htm <- newAny advices will be appreciated
The text was updated successfully, but these errors were encountered: