Components

Participation space can have the following components:

• Proposals - This component allows you to browse proposals made by citizens, make your own proposals and comment on existing proposals. In this section you can also follow the progression of a proposal, and see its status which is determined by the admin (e.g. "Accepted", "Rejected", "Evaluating").
• Meetings - This component allows you to browse meetings which are added to the system. A democratic participation space demands sharing information and physical participation from the participants, which is why certain participation spaces contain official meetings or events. These can be added to the system using the "Meetings" -component. Meetings can also have a location when the meeting can be presented on a map.
• Budgets - This component allows listing of priced projects with a defined budget to be used to these projects. Participants choose which projects they would like to execute with their own budget and this way information can be gathered of the most popular projects.
• Accountability - This component allows the municipality to publish official results and the progression of projects. In this section participants can participate in the execution of the projects by commenting them.
• Survey - This component allows gathering data about the things in the participation space. With surveys you can gather any data about the participation space's topics. The surveys are single paged and have questions that are answered with text or multiple choice fields. With the multiple choice questions it is possible to ask for a single answer or multiple answers.
• Page - This component allows creation of static content pages for the participation space. The admin of the space can define the content of the page however they see fitting.

The admin of the participation space can name these components however they see fitting, which also define how they are shown on the space's page. In this documentation the components are named with their official default names so it is clear which component is talked about.

Each component come with their own specific features, which are not exclusively described in this documentation. The features are easily found and their usage is simple from the point of the participant, because the components aimed at participants do not have many features, and the user interface by itself guides the user forward. You can get familiar with the components by getting to know them for example in a testing or a staging environment.