How should the SPA application coordinate the activity page?

for spa applications, the function of the main architecture is clear, but I still don"t understand how to coordinate some pages when doing activities.
for example,
I have a mall wapapp. On National Day and Spring Festival, there are some second kill and lottery pages. Strictly speaking, these pages do not belong to the main structure of the project, but only meet the needs within a certain period of time, but also need to share some user information, such as userid and so on. How should this kind of page be designed? Is it also updated every time you write a new route and do it for an activity, and delete it after the event ends?

Spa
May.14,2022

We here user management (login, registration) is an independent project, other including shopping malls, activities, and so on are separate projects, sharing a set of user management logic, all these projects are sub-projects under a large project (mobile project), you can reuse some service,components, and so on.


can be made into multiple entries, one entry is the main function of the project, and one entry is the active page. Shared information can be placed on localStorage.

Menu