Decoupling should be done at all levels, so the frontend is not excluded from this. Instead of thinking end-to-end in one view, we divide things up and create features in isolation. These features are specialized in doing one thing and one thing only. This makes the individual features expert in their isolated domain, instead of trying to fit everything in a wider feature. This creates something that is more decoupled and more maintainable. It's easier to change each of these features to become even better at what they do, without worrying about breaking other features. Typically, you could divide a page up as shown in the following screenshot:

Every box represents a section of the system holding a feature. Each individual feature is put together in the larger composition.

One could create the preceding entire composition in one page and one code file, but it would be running the risk of being highly coupled together, and changing anything could easily break things that one...