You are here

Home » API reference » Spaces 7.3

README.txt in Spaces 7.3

Same filename in this branch
  1. 7.3 README.txt
  2. 7.3 spaces_customtext/README.txt
  3. 7.3 spaces_og/README.txt
  4. 7.3 spaces_dashboard/README.txt
  5. 7.3 spaces_taxonomy/README.txt
Same filename and directory in other branches
  1. 6.3 spaces_dashboard/README.txt
  2. 7 spaces_dashboard/README.txt
Spaces Dashboard 3.x
--------------------

The Spaces Dashboard module provides a "Dashboard" feature that can be used in
space type. The "Dashboard" is intended to be a page, or set of pages, where
space administrator have the ability to modify the content and arrangement.

Content is made available to the Dashboard using the core blocks system. Not all
block will show up as options for users, the dashboard must be told what blocks
it should offer. The dashboard feature offers a settings page in each space
where block availability can be configured. 

By default all dashboards will inherit the dashboard settings of the dashboard
in the so-called 'site' space. To target block availability settings at the
correct space type its important to understand how a particular spaces inherits
it's settings. A particular spaces has three source of a individual settings,
what has been set for the particular space, the setting of that space's preset,
the site wide setting. To make certain blocks available to spaces of a certain
type you must add this setting to a spaces preset. If neither the space itself
nor the preset includes a setting for which dashboard blocks are available the
site setting will be used.

Note: Spaces settings inheritance & spaces presets are covered in detail in the
main spaces module README.txt

File

spaces_dashboard/README.txt
View source 
  1. 

  2. Spaces Dashboard 3.x

  3. --------------------

  4. 

  5. The Spaces Dashboard module provides a "Dashboard" feature that can be used in

  6. space type. The "Dashboard" is intended to be a page, or set of pages, where

  7. space administrator have the ability to modify the content and arrangement.

  8. 

  9. Content is made available to the Dashboard using the core blocks system. Not all

  10. block will show up as options for users, the dashboard must be told what blocks

  11. it should offer. The dashboard feature offers a settings page in each space

  12. where block availability can be configured. 

  13. 

  14. By default all dashboards will inherit the dashboard settings of the dashboard

  15. in the so-called 'site' space. To target block availability settings at the

  16. correct space type its important to understand how a particular spaces inherits

  17. it's settings. A particular spaces has three source of a individual settings,

  18. what has been set for the particular space, the setting of that space's preset,

  19. the site wide setting. To make certain blocks available to spaces of a certain

  20. type you must add this setting to a spaces preset. If neither the space itself

  21. nor the preset includes a setting for which dashboard blocks are available the

  22. site setting will be used.

  23. 

  24. Note: Spaces settings inheritance & spaces presets are covered in detail in the

  25. main spaces module README.txt