---
# System prepended metadata

title: Templates + Ecoverses

---

# Templates + Ecoverses
With the support for multiple ecoverses, the current way in which templates are supported by the platform needs to be refreshed.

In this case we are primarily interested in the templates for ecoverses. Templates for users and organisations are out of scope.

## Givens:
* Multiple templates: it should be possible to use multiple templates, so that different ecoverses can have different templates
* Stored with the ecoverse: the template for an ecoverse should be stored with the ecoverse
* Associate at instantiation: at least for now, the template to be used should be defined at the moment the ecoverse is instantiated
* Multiple levels: the template should support multiple levels of challenges

## Design notes
Each ecoverse template should have a name.

Sample template:
```"ecoverse-templates":
    [
        {
            name: "default",
            challenge: {
                type: "ecoverse",
                allowChildren: true
                    context: {
                    ecosystemModel: {
                        enabled: false
                    }
                }
                challenge: {
                    type: "challenge",
                    allowChildren: true
                    context: {
                        ecosystemModel: {
                            enabled: false
                        }
                    }
                    challenge: {
                        type: "opportunity",
                        allowChildren: false
                        context: {
                            ecosystemModel: {
                                enabled: true,
                                actor-groups: ["stakeholders", "users"]
                            }
                        }
                    }
                }
            }
        }
    ]
```


Note that the template has multiple levels.

Each challenge would then store and have available its own template information. As the hierarchy is traversed each challenge is assigned its own subset of the original template.

Template information to be stored and retrieved as JSON i.e. no strong typing. 

The domain model would need to be enhanced so that the template for a given entity could be retrieved. 