Sure, it can be. But it really depends on exactly what you want, which is why @nadia asked for wireframes. Or a bullet point list of everything that it’s important that the software does. Without enough data going in on what you expect it to do - including how people interact with it, how you want to be able to analyze the data (perhaps you don’t need to dig into the data in the ways I mentioned).
If standard survey analysis functionality is important, we are much better off with off the shelf survey solutions. I personally think a paid subscription to TypeForm and some design work would do the trick. You can even trigger a custom designed email with a a step by step guide for how to sign up on the platform. Typeform also has an API and supports webhooks, so technically you might be able to build an integration to send data straight to Discourse.
If I was a consultant and you were the client, this is when we’d sit down to write some “user stories” before we make any rash decisions on technical choices or start designing. My time is a bit short today and tomorrow but I might be able to help you before the Borderland. But you might want to get started yourself.
Basically, make a bullet point list of statements that start with:
- As a X I can/want to X.
- As a user, I want don’t want to spend more than 5 minutes on this survey
- As a user, I want the graphics to be smooth and the experience to be fun
- As a user, I want to see how many questions I have left
- As a user, I want to be able to opt out of getting emails after I finish the survey
- As a researcher, I need the ethics funnel to be watertight and approved
- As a researcher, I want to be able to see only the answers to a specific question
- As an admin of the platform, I want to be able to quickly update any question myself if there are mistakes
Once we have this, it becomes much easier to make a decision on how to do this. Right now we are speculating way too much.