In addition to the form-based services that we currently have, it would be useful to support creating services that collect and show stats and information on a single or multiple pages. The workflow for building such a service would be analogous to the current one, only instead of a form and an action that uses the form values as inputs, the user would define an action that collects data from GIN and displays it on a page.
we could generalise this to have reader, writer, and amend types of services:
Writer actions are what we have now: They take input and use it to make changes to the main service (Form input -> Writer job -> Main service changes through API calls).
Reader actions would read from the main service and display information to the user (Reader job -> Read data through API calls -> Page output).
Amend actions can do both (Reader job -> Read data through API calls -> Display form based on data -> Form input -> Writer job -> Main service changes through API calls).
In addition to the form-based services that we currently have, it would be useful to support creating services that collect and show stats and information on a single or multiple pages. The workflow for building such a service would be analogous to the current one, only instead of a form and an action that uses the form values as inputs, the user would define an action that collects data from GIN and displays it on a page.
we could generalise this to have reader, writer, and amend types of services:
This would enable #5 and #11.