Question: On the AngularJS web site, what is meant by *dynamic views* when it says, "the root problem is that HTML was not meant for dynamic views"?

Answer: 
HTML Pages were initially created to serve static webpages. In other words, pages that do not rely on asynchronous interaction of some kind, to provide dynamic data from any of the following sources: databases, other sites, systems, or users.

When using dynamic design approach, anytime that you send/receive data that is done through some sort of interaction, either from the user or the website/webserver, this is considered dynamic and the page is updated dynamically *(with Angular.js in this case)*.

In Angular.js, the concept of "dynamic views" comes from the framework MV\*, which is implemented through the following elements:

1. **Model** to contain the data
2. **View** that the user is able to view and interact with data
3. **Controllers(\*)** that handle the translation from the view to the model and vice versa. *(This also includes services/factories/directives, etc.)*

This interaction enables the creation of dynamic "views" that are able to incorporate new data as needed. Dynamic sites give the feeling that the user is on the same page, but new data is able to be presented. This leads to an improved UX in most cases.

---

Further Reading: 

[Good Article on MV\* Framework](https://www.sitepoint.com/anatomy-javascript-mv-framework/)
 [Comparison of 4 MV\* Frameworks](https://www.developereconomics.com/feature-comparison-of-4-popular-js-mv-frameworks)
Content loaded dynamically, typically via ajax, or websocket. A simple view that consumes JSON service showing some data, is a dynamic view.