1. Using and Configuring Dashboards
1.1. Dashboard Visibility
Dashboards are configured with a visibility, controlling who may render the dashboard and its widgets. While widgets automatically inherit the Dashboard's overall visibility, it is not possible to have a single Dashboard with Widgets configured for different visibilities.Dashboards made visible to "Unauthenticated Users" are publicly viewable at a URL similar to /registry/co_dashboards/dashboard/3. The URL can be obtained (and the dashboard previewed) by clicking the "Render" button in the index of available dashboards.
1.2. Primary CO Dashboard
One Dashboard may be flagged as Primary for the CO, via Configuration > CO Settings > Primary Dashboard. When a Primary Dashboard is configured, it will render at the CO landing page (
/registry/co_dashboards/dashboard/co:#). Note that any active CO Person (CO Member) can view this page. If a more restrictive visibility is configured for the Dashboard, the structure of the Dashboard will still render, though the Widgets will throw permissions errors rather than render. In general, if a Dashboard is set as the Primary Dashboard, it should be given CO Member visibility.
2. Dashboard Widgets
2.1. Existing Widgets
Registry Dashboards contain Dashboard Widgets
2.1.1. Dashboard Widget Plugins
2.2. Writing your own widget
Building your own plugin is a great was to get started with custom development for COmanage. Through plugins you can build powerful extensions to the existing Registry functionality. Building a Registry Plugin requires knowledge of PHP, CakePHP, and COmanage.
2.2.1. Start Here
The general documentation for building plugins can be found on the Writing Registry Plugins page. All plugins follow some standard conventions which are outlined on this page. In addition, some types have additional requirements as listed below.
2.2.2. Specific plugin details
Some additional conventions are required when writing a Dashboard Widget Plugin. See the documentation for more detail.