New Feature: Allow user to customize question used

[afarentino]

As a user of the poll single use question survey, I'd like to be able to change the question shown so that I can reuse the application for other short-lived surveys.

Acceptance criteria

• A survey admin page is added that allows the app to be reconfigured using a new question type
• The question text and form layout shown is no longer hard-coded but rather adapts based on the question used.

[afarentino]

Possibilities include Next.Js, (React) and server-side components.

[afarentino]

We also can consider, potentially introducing an AI form builder assistant similar to what Microsoft is doing inside of the Power Platform this year (with its latest enhancements to Github co-pilot and Power Virtual agents).

I don't want us reinventing the wheel here (forms are a known and solved pain point for developers with various libraries + builders) and something should be found that allows this app to quickly be re-used with a new question.

[afarentino]

Additional research links:

• https://formsflow.ai/features
• https://formsflow.ai/license-faq

What I like:

• Technology aligns around an open-source embedded platform (Form.io for example is supported by its own community and can be fully deployed in our environment). I also believe the future of "no-code/low-code" is open. Vendors that standardize around this and build components/solutions that can be easily mixed into other environments will be "loved" by developers -> as it avoids technology and vendor lockin.
• Drag + Drop Form builder is Apache 2.0 licensed
• BPMN (a standardized diagramming notation used by many business users) can be used with the Camunda Workflow engine

Potential challenges:

• With a platform as complete as this, each component used will need to be carefully reviewed to understand deployment requirements. For example, we'd want to use our sandbox MongoDB Cloud Atlas db instead of standing up our own MongoDB server.
• I created Poll as a lightweight alternative and it solves the immediate problem of quickly creating a low-cost short-term survey while minimizing development + infrastructure costs. The more components we pull in the higher the cost to deploy will be so this needs to be carefully balanced for our intended use case.

Nice-to-have: Now that poll is open-source it needs a longer-term strategy beyond a quick MVP. By becoming part of a pre-existing open-source community other developers are going to find, use, and improve it.