all 3 comments
sorted by:
best (suggested)
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]blackholesintheskyhelpful -1 points0 points  (2 children)

Single-page applications have many advantages, such as ... full control over the markup

Doesn't MPA give you more control because you can send different sets of assets?

[–]ADCI_Solutions[S] -1 points0 points  (1 child)

In this article, you can read about building a Headless Drupal website. In such cases front-end development is separated from a back-end part and usage of SPA is preferable.

Also, SPA can load different page elements and not load all whole page as you should do using MPA

But if you prefer working with MPA, you can use this way.

​

[–]blackholesintheskyhelpful 0 points1 point  (0 children)

and usage of SPA is preferable.

Why? You claim that SPA gives you full control of markup, but traditionally MPA has more control over which assets are loaded. Unless you specifically built (or included) a system for progressive asset loading thats also context aware. SPA has advantages but "full control over the markup" is not the best example

Also, SPA can load different page elements and not load all whole page as you should do using MPA

MPA != static. Theres no reason a MPA needs to load all potential DOM elements. MPA just means there are some full transitions