Views are the most important entity, as they are what is directly requested by the client. For example, when the client request the context /main/hamburger, the object, settings and view associated with it are loaded.
The template is what is loaded around the view. This is determined by information provided by the /main/hamburger context.
The machine display mechanism diverges from most with the concept of components. Components can be though of as light-weight views, wherein they are written in PHP, but do not have an associated context object or JS controller. Components are subsets of each view, and to access a different components view, the name of the view has to be explicitly stated.
Components are never displayed on their own, they are always a part of a template or view. They are held in areas inside of templates and views. These areas act as containers for components to be loaded into.
To create called menu_space an area in a view:
As far as HTML goes, an area is really just a div that is of the _m_area CSS class who’s ID consists of _m_ appended to the front of the name provided. Areas nested inside of other areas are given ID’s accordingly. For example, an area named spaced inside of the area one would be given the ID _m_one_spaced.
To place the component called mike in the area one:
To place the component called mike, which is located in the context /show/best in the area one:
—-To note, accessing components outside of your current context is not suggested at this point as JS Controller logic is connected to the context itself.—-
To place the component called mike/great in the area spaced inside of the area one: