Available translations
loading results
Assets
The Assets hierarchy defines the structure of assets that a project is composed of. Any digital component of a Project may be characterised as an asset, including code files, stylesheets, images, documentation pages, tutorial pages, and so on. Assets, like Features, need to be created and maintained, thus their creation and maintenance must be incentivized.
Content
Defining assets at the project level is an excellent way to atomize the description of a project. This level of granularity allows multiple groups of Contributors to take charge of clearly delimited components, which is crucial to developing, evolving, and maintaining a vast project through massive collaboration.
The hierarchy features Asset Class nodes, an organizational device, and Asset nodes, the representation of actual assets. Both types of nodes may accept incoming Weight Votes but only Asset nodes may accept Contribution Claims.
Tip: A crucial feature of this hierarchy is the Install Assets feature available both at the top-level of the hierarchy, and at the Asset Class node level.
Install Missing Assets
Note: The Install Missing Assets feature is oriented to people maintaining Project Definition Hierarchies. You may safely skip this explanation if you are a regular user learning about governance.
Both the Assets node and Asset Class nodes support the Install Missing Assets command available on the menu. Because Asset nodes map digital files shipping with the system, the Install Missing Assets feature is designed to map files on disk into a hierarchical structures of nodes below the node where the Install Missing Assets command is run. In the resulting structure of nodes, Asset Class nodes represent folders, and Asset nodes represent files.
To run the command, you must configure the path you wish to map.
For example:
{
"folderPath": "Root/UI"
} Using the above configuration, the Install Missing Assets command creates a Superalgos Asset Class node (the root of the Superalgos folder), and the UI Asset Class node as an offspring node. Then, the contents of the UI folder are mapped as offspring of the UI Asset Class node.
Configuration
Configuration
Initial Values
These are the Initial Values for Assets configuration:
{
"folderPath": ""
} Examples
This is a list of properties featured by the Assets configuration. Expanding a property shows sample values for the property extracted from the current Workspace.
Assets Menu
The Assets node has the following Node Menu items:
The Configure menu item has the following properties:
- action: Configure
- actionFunction:
uiObject.configEditor.activate
- label: Configure
- iconPathOn: configuration
- iconPathOff: configuration
The Install Missing Assets menu item has the following properties:
- action: Install Missing Assets
- actionProject: Governance
- label: Install Missing Assets
- askConfirmation: true
- confirmationLabel: Confirm to Proceed
- workDoneLabel: Done
- relatedUiObject: Asset
- actionFunction:
payload.executeAction
- relatedUiObjectProject: Governance
The Add Asset Class menu item has the following properties:
- action: Add UI Object
- actionProject: Visual-Scripting
- actionFunction:
payload.executeAction
- label: Add Asset Class
- relatedUiObject: Asset Class
- relatedUiObjectProject: Governance
The Add Asset menu item has the following properties:
- action: Add UI Object
- actionProject: Visual-Scripting
- actionFunction:
payload.executeAction
- label: Add Asset
- relatedUiObject: Asset
- relatedUiObjectProject: Governance
The Install as Plugin menu item has the following properties:
- action: Install as Plugin
- actionProject: Community-Plugins
- askConfirmation: true
- confirmationLabel: Confirm to Install
- label: Install as Plugin
- iconPathOn: configuration
- iconPathOff: configuration
- actionFunction:
payload.executeAction
The Delete menu item has the following properties:
- action: Delete UI Object
- actionProject: Visual-Scripting
- askConfirmation: true
- confirmationLabel: Confirm to Delete
- label: Delete
- iconPathOn: delete-entity
- iconPathOff: delete-entity
- actionFunction:
payload.executeAction
Tip: When a menu item is grayed out, it means that Assets already has the required child type that the menu item may add, and only that child is allowed for that case.
Assets Children
The Assets node has the following childrenNodesProperties:
The Asset Classes node property features the following properties:
- name:
assetClasses
- type: array
- childType: Asset Class
- autoAdd: false
The Assets node property features the following properties:
- name: assets
- type: array
- childType: Asset
- autoAdd: false