A Dashboard is a component for displaying elements on the right-hand side of the backoffice UI area.
The Umbraco backoffice consists of sections (sometimes referred to as applications) which contain trees. For example, when you load the backoffice you'll see that the 'Content' section contains one tree: the content tree whereas the 'Settings' section contains a number of trees: Stylesheets, Content Types, Media Types, etc...
Both sections and trees can be created to extend Umbraco.
A property editor is the editor used to insert content into Umbraco. See here for definition.
This section will describe how to work with and create Property Editors.
A Parameter Editor is the editor used to insert values into a Macro.
This section will describe how to work with and create Parameter Editors.
The Umbraco backoffice can be configured so that the user interface runs in the user's native language. This is made possible with community generated language files, if your language is not currently supported, why not help to add support?
Backoffice tours is the integrated and interactive help for the backoffice.
A library of API Reference documentation.
Extending the Umbraco Backoffice search, customising the fields searched - replacing the searching mechanism.
Content Apps are a new concept in v8. Editors can switch from editing 'Content' to accessing contextual information related to the item they are editing.
Content Apps encapsulate companion read-only information relating to the current content item in the Umbraco backoffice.
Create a custom Database table.
Details on how to create a custom Embedded Media Provider to enable editors to embed third party media content into Umbraco via the embed button in the Rich Text Area.
Details on implementing virtual file systems for things like media which will allow you to store your files outside of the physical file system (i.e. Cloud based for example).
Developers can create their own Umbraco Health Checks and Health Check notification methods.
Information on the packaging manifest format and how assets should be packaged as a zip file for distribution