An app descriptor describes an app. The descriptor assigns the app a
name, icon and implementation class. The name of the app content node
must be unique as it is used to refer to the app across the system. This
means you cannot name your own app pages since a
Pages app already exists.
This approach keeps the app descriptor very short. There is no need to
specify the below mentioned properties. The content
types and content apps frameworks automatically generate and register an
app description based on the content type definition.
You can tailor the app descriptor within the same file by adding
additional configuration which will overwrite any configuration with the
same name coming from the !content-type directive. Alternatively
create a decoration.
Label displayed on the app icon in the app launcher.
theme
optional
Name of a custom app theme.
Permissions
The permission to use an app is granted in the permissions
configuration. The subnodes are roles. This allows you to provision the
app to certain users in your organization.
In this example the helloworld app is provisioned to
travel-demo-editor and travel-demo-publisher roles. The role
property name (editors, publishers) is arbitrary - use any name you
like. The value must be a valid role name.