An abstract component model can be used to drive an editor by providing an underlying stateful model for component implementation without the need to re-implement details, such as event listening, lifecycle and update management, etc. An implementation needs to provide objects that make up the model, some logic to listen to environmental changes and recognize when an update is needed, and a builder which can generate a lightweight version of the model based on the current “state of the world.” In addition, abstract component model is operable to support an editor such as page flow.