Next basic thing is a universal trigger

One single HTML file allowing to create a basic structure = layout of the displayed part, its dynamics, creating menus, working with "subpages" without page refresh (no flashing), without GET calls, with a generic global stack (structured variable {} ).

After exiting/leaving the "subpage", it needs to release its code, its variables and set the desktop partitioning to some default state.

Translations are extra scripts. There has to be some basic generic one, and then it has to be able to add data for the current "subpage" and then remove the code again after leaving it.

Next, we must verify the user's identity against the Active Directory account. The applications are designed for a corporate environment = intranet. Authentication can certainly be modified in other ways and the framework can be used outside the corporate environment.

"Subpages" are JavaScript files. To make the logic work, you need to generalize the behavior. The solution is to create three procedures ... start, work, stop ... or for special cases resize.

Data exchange with the server is done so that the volume of data is as small as possible and only necessary data flows, no html code ... the solution used is JSON, AJAX and POST .. never GET is used.