Fixes and preparing for field types and prefilling docs
This commit is contained in:
parent
de03e4776b
commit
db80cb1c34
|
@ -1,5 +1,10 @@
|
||||||
---
|
---
|
||||||
sidebar_position: 1
|
sidebar_position: 1
|
||||||
|
description: View details about the field types
|
||||||
---
|
---
|
||||||
|
|
||||||
# Field Types
|
# Field Types
|
||||||
|
|
||||||
|
import FieldTypes from '../commons/_markdown-field-types.md';
|
||||||
|
|
||||||
|
<FieldTypes />
|
|
@ -90,7 +90,7 @@ Every section must have a `System` field of the following types: `Title`, `Descr
|
||||||
|
|
||||||
:::
|
:::
|
||||||
|
|
||||||
### Desctiption Templates form
|
### Description Templates form
|
||||||
|
|
||||||
Each section can have one or more **description templates** attached to it. When you 'attach' a [description template](/docs/documentation/administration/templates/) to a blueprint, every [plan](/docs/category/plans) that inherits from that blueprint must have a [description](/docs/category/descriptions) that inherits from that template. More details will follow. You can add a description template by clicking on the `Add Description Template` button. For every template you add, a new form part appears where you can specify everything about the template attachment. You can also delete one template clicking on the `delete` icon on the right end of its form.
|
Each section can have one or more **description templates** attached to it. When you 'attach' a [description template](/docs/documentation/administration/templates/) to a blueprint, every [plan](/docs/category/plans) that inherits from that blueprint must have a [description](/docs/category/descriptions) that inherits from that template. More details will follow. You can add a description template by clicking on the `Add Description Template` button. For every template you add, a new form part appears where you can specify everything about the template attachment. You can also delete one template clicking on the `delete` icon on the right end of its form.
|
||||||
|
|
||||||
|
|
|
@ -1,5 +1,6 @@
|
||||||
---
|
---
|
||||||
sidebar_position: 3
|
sidebar_position: 3
|
||||||
|
description: View details about the prefilling sources
|
||||||
---
|
---
|
||||||
|
|
||||||
# Prefilling Configurations
|
# Prefilling Configurations
|
|
@ -1,5 +1,10 @@
|
||||||
---
|
---
|
||||||
sidebar_position: 2
|
sidebar_position: 2
|
||||||
|
description: View details about the semantics
|
||||||
---
|
---
|
||||||
|
|
||||||
# Semantics
|
# Semantics
|
||||||
|
|
||||||
|
import Semantics from '../commons/_markdown-semantics.md';
|
||||||
|
|
||||||
|
<Semantics />
|
|
@ -0,0 +1 @@
|
||||||
|
{}
|
|
@ -0,0 +1 @@
|
||||||
|
TODO: Add info about field types
|
|
@ -0,0 +1 @@
|
||||||
|
TODO: Add info about semantics
|
|
@ -1,8 +1,8 @@
|
||||||
# Administration
|
# Administration
|
||||||
|
|
||||||
There are a lot of tools developed that can help administrators better manage a lot of aspects of the application or get a better idea about the usage of the platform.
|
There are a lot of views developed that can help administrators better manage and configure a lot of aspects of the application or get a better idea about the usage of the platform.
|
||||||
|
|
||||||
These tools will be described in this section.
|
These views will be described in this section.
|
||||||
|
|
||||||
import DocCardList from '@theme/DocCardList';
|
import DocCardList from '@theme/DocCardList';
|
||||||
|
|
||||||
|
|
|
@ -11,3 +11,6 @@ There are a lot of views in the application available only for users that are gi
|
||||||
- **Tenants**: Being able to control the tenants of the platform. Think of tenants as different organisations that can use the application independently at the same time without the need of different deployments.
|
- **Tenants**: Being able to control the tenants of the platform. Think of tenants as different organisations that can use the application independently at the same time without the need of different deployments.
|
||||||
- **Notification Templates**: Being able to modify the structure of notifications sent to users based on different events.
|
- **Notification Templates**: Being able to modify the structure of notifications sent to users based on different events.
|
||||||
- **Languages**: Being able to add support for more languages or modify existing ones.
|
- **Languages**: Being able to add support for more languages or modify existing ones.
|
||||||
|
- **Reference Types**: Being able to configure static or external data sources that are made available as autocomplete fields on the forms of the platform.
|
||||||
|
- **Plan Blueprints**: Being able to control the blueprints available for [plans](/docs/category/plans).
|
||||||
|
- **Description Templates**: Being able to control the templates available for [descriptions](/docs/category/descriptions)
|
|
@ -1,5 +1,6 @@
|
||||||
---
|
---
|
||||||
sidebar_position: 2
|
sidebar_position: 2
|
||||||
|
description: View details about the conditional questions
|
||||||
---
|
---
|
||||||
|
|
||||||
# Conditional Questions
|
# Conditional Questions
|
|
@ -1,5 +1,10 @@
|
||||||
---
|
---
|
||||||
sidebar_position: 1
|
sidebar_position: 1
|
||||||
|
description: View details about the field types
|
||||||
---
|
---
|
||||||
|
|
||||||
# Field Types
|
# Field Types
|
||||||
|
|
||||||
|
import FieldTypes from '../commons/_markdown-field-types.md';
|
||||||
|
|
||||||
|
<FieldTypes />
|
|
@ -1,5 +1,10 @@
|
||||||
---
|
---
|
||||||
sidebar_position: 3
|
sidebar_position: 3
|
||||||
|
description: View details about the semantics
|
||||||
---
|
---
|
||||||
|
|
||||||
# Semantics
|
# Semantics
|
||||||
|
|
||||||
|
import Semantics from '../commons/_markdown-semantics.md';
|
||||||
|
|
||||||
|
<Semantics />
|
|
@ -0,0 +1,6 @@
|
||||||
|
---
|
||||||
|
sidebar_position: 11
|
||||||
|
description: Configure the tenant you are logged in with
|
||||||
|
---
|
||||||
|
|
||||||
|
# Tenant configuration
|
Loading…
Reference in New Issue