Start on Workspace::getView
Use atom.workspace.getView to construct WorkspaceViews

It returns the root DOM node of the workspace. Eventually this will
be a custom element but for now it’s just a DOM node with a
__spacePenView reference on it.
Use Workspace::getView to build PaneContainerView
Extract a ViewRegistry that can be shared amongst Workspace objects
Construct PaneAxisViews and PaneViews via ViewRegistry
Use the ViewRegistry to construct pane item views
Upgrade background-tips to fix spec failure
Isolate ViewRegistry specs
Use view providers to build views if a matching provider is available
:pencil: Document Workspace::getView
Return disposable from ViewRegistry::addViewProvider
Rename view/modelClass to view/modelConstructor in view provider specs

It’s a more technically correct term. You use a class keyword to declare
these things, but the actual objects you pass around to talk about them
are constructor functions.
Allow view providers to specify a createView factory method

If present, it will be called with the model object instead of
instantiating the view constructor directly and assigning a model on it.
This gives users more flexibility when constructing views.
Make ::getView essential because otherwise the section is empty
Delegate Workspace::addViewProvider to its ::viewRegistry
:pencil: Document Workspace::addViewProvider
Throw an exception if the same pane item is added twice in the workspace
Don’t add the same editor to two different panes in spec
Model setPlaceholderText

Less dependence on the editorView!
Don't override antialiasing in markdown