diff --git a/Projects/Governance/Schemas/Docs-Nodes/A/Asset/Asset/asset.json b/Projects/Governance/Schemas/Docs-Nodes/A/Asset/Asset/asset.json index 34a4b60a2..00bd14b07 100644 --- a/Projects/Governance/Schemas/Docs-Nodes/A/Asset/Asset/asset.json +++ b/Projects/Governance/Schemas/Docs-Nodes/A/Asset/Asset/asset.json @@ -1,13 +1,35 @@ { "type": "Asset", "definition": { - "text": "An Asset is any artifact that belongs to the project. It can be a piece of software, a configuration, a plugin, some marketing material, a social media account, etc. Users votes on assets to influence their relative weight between each other. Those weight will then influence how many token will be given to the contributors who built or mantain that asset.", - "updated": 1622986734958 + "text": "An Asset is an artifact, mostly in a digital format, that belongs to a Project. It may be a code file, a documentation or tutorial page, an image, a video, a social media account or even a post, marketing collateral, and more. To incentivize the production and maintenance of Assets, the node may receive Weight Votes. It may also receive Contributor Claims from Contributors involved in their production and maintenance.", + "updated": 1624709807952 }, "paragraphs": [ + { + "style": "Block", + "text": "Content", + "updated": 1624709759877 + }, { "style": "Text", - "text": "Right click and select the pencil button to enter edit mode." + "text": "You may cast Weight Votes on individual Asset nodes to incentivize the improvement, development, and maintenance of the said feature.", + "updated": 1624709824891 + }, + { + "style": "Text", + "text": "If you are involved in the development or maintenance of the said asset, you may place an Asset Contribution Claim and rally the Community to support your claim so that you may be compensated for your work." + }, + { + "style": "Block", + "text": "Configuration" + }, + { + "style": "Title", + "text": "Configuration" + }, + { + "style": "Text", + "text": "" } ] } \ No newline at end of file diff --git a/Projects/Governance/Schemas/Docs-Nodes/A/Assets/Assets/assets.json b/Projects/Governance/Schemas/Docs-Nodes/A/Assets/Assets/assets.json index 26b3d09da..9299b7cb9 100644 --- a/Projects/Governance/Schemas/Docs-Nodes/A/Assets/Assets/assets.json +++ b/Projects/Governance/Schemas/Docs-Nodes/A/Assets/Assets/assets.json @@ -1,13 +1,61 @@ { "type": "Assets", "definition": { - "text": "These hierarchies define the different assets Superalgos as a project has accumulated over time. Assets could be anything tangible and not only software modules. ", - "updated": 1622986422593 + "text": "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. ", + "updated": 1624708951019 }, "paragraphs": [ + { + "style": "Block", + "text": "Content", + "updated": 1624709007419 + }, { "style": "Text", - "text": "Right click and select the pencil button to enter edit mode." + "text": "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." + }, + { + "style": "Text", + "text": "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 Contributor Claims." + }, + { + "style": "Success", + "text": "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.", + "updated": 1624709216096 + }, + { + "style": "Title", + "text": "Install Missing Assets", + "updated": 1624709536566 + }, + { + "style": "Text", + "text": "Both the Assets node and the Asset Class nodes support the Install Assets command available on the menu. Because Assets map digital files shipping with the system, the Install Assets feature is designed to map files on disk into a hierarchical structure of nodes below the node where the Install Assets command is run. In the resulting structure of nodes, Asset Class nodes represent folders, and Asset nodes represent files." + }, + { + "style": "Text", + "text": "To run the command, you must configure the path you wish to map." + }, + { + "style": "Text", + "text": "For example:" + }, + { + "style": "Json", + "text": "{\n\"folderPath\": \"Root/UI\"\n}", + "updated": 1624709553788 + }, + { + "style": "Text", + "text": "Using the above configuration, the Install 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." + }, + { + "style": "Block", + "text": "Configuration" + }, + { + "style": "Title", + "text": "Configuration" } ] } \ No newline at end of file