anchor.diff:  * Core images
   * Core resources
   * Core constants
  -* More built-in gif & png images (see also uberfire-widgets-commons)
  -
  -The `uberfire-widget-markdown` module introduces the following concepts:
  +* More built-in gif & png images (see also UberFire-widgets-commons)
  +
  +The `UberFire-widget-markdown` module introduces the following concepts:
   
   * Markdown
   * Markdown type
  
positive.code: * Date range
  * Search index
  
  There is also a small submodule called `uberfire-metadata-commons-io`
  which introduces the following concepts:
  
  * Batch index
  
negative.code: UberFire Client API Concepts
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  These concepts are expressed in the `UberFire-client-api` package,
  which defines an API that's only accessible to client-side
  (in-browser) code.
  
  * Annotations
  ** DefaultPosition
  +
  Marker annotation to allow either @WorkbenchEditors or @WorkbenchScreens to declare a method that returns the default location of the component in a perspective when opened by the framework. NOTE: This is specific to the NSEW perspective type. Work is in progress to provide support for additional types of perspective.
  ** Intercept
  +
  TODO
  ** Perspective
  +Marker annotation to allow a @WorkbenchPerspective to declare a method that returns a PerspectiveDefinition object, defining the workbench perspective.
  ** SplashBodySize
  +
  TODO
  ** SplashFilter
  +
  TODO
  ** WorkbenchContext
  +
  TODO
  ** WorkbenchContextId
  +
  TODO
  ** WorkbenchEditor
  +
  A marker annotation to declare a class as being a Workbench Editor. Editors relate to specific resources within the framework, defined by their ResourceTypeDefinition.
  ** WorkbenchMenu
  +
  A marker annotation to declare a method within a @WorkbenchPerspective, @WorkbenchEditor or @WorkbenchScreen that returns a Menus object defining a menu to be shown by the framework when the perspective, editor or screen is displayed.
  ** WorkbenchPartTitle
  +
  A marker annotation to declare a method within a @WorkbenchEditor or @WorkbenchScreen that returns a String defining the title for the component.
  ** WorkbenchPartTitleDecoration
  +
  A marker annotation to declare a method within a @WorkbenchEditor or @WorkbenchScreen that returns an IsWidget object to be used as a decoration, beside the @WorkbenchPartTitle.
  ** WorkbenchPartView
  +
  A marker annotation to declare a method within a @WorkbenchEditor or @WorkbenchScreen that returns a IsWidget object representing the view (or user-interface) of the component.
  ** WorkbenchPerspective
  +
  Marker annotation to declare a class as providing a perspective definition. The definition itself is returned from a method within the @WorkbenchPerspective annotated with @Perspective. 
  ** WorkbenchPopup
  +
  Marker annotation to declare a class as being a popup that can be displayed by the framework.
  ** WorkbenchScreen
  +
  A marker annotation to declare a class as being a Workbench Screen. Screens would usually display static content, or at least content that is not dependent upon a Path within the underlying VFS. The screen could still consume external resources (e.g. query a database) however it does not integrate with the framework's use of Paths.
  ** WorkbenchSplashScreen
  +
  TODO
  ** WorkbenchToolbar
  +
  A marker annotation to declare a method within a @WorkbenchPerspective, @WorkbenchEditor or @WorkbenchScreen that returns a ToolBar object defining a toolbar to be shown by the framework when the perspective, editor or screen is displayed.
  
  * Interfaces
  ** UberView
  +
  A convenience interface to support linking a View to it's Presenter as required by implementations of the MVP pattern. Uberfire itself does not impose use of MVP.
  
  * Events
  ** ChangeTitleWidgetEvent
  + CDI Event that provide support for @WorkbenchEditors and @Workbench screens to inform the framework that their title or decoration should be updated.
  
  * Types
  ** ClientResourceType
  +
  Extends ResourceTypeDefinition which is a server-side model for a resource type; allowing @WorkbenchEditors to specify the types of resource they are capable of handling.
  
  UberFire Commons Concepts
  ~~~~~~~~~~~~~~~~~~~~~~~~~
  
  These concepts are expressed in the `UberFire-commons` package,
  which contains a mix of server-only definitions shared client/server definitions.
  
  * Clustering (server-only, see also UberFire I/O)
  