As a Developer, I want to be able to create forms.

[robyurkowski]

NOTE: This is challenging to our paradigm that everything content-wise is a viewable. By the nature of being 'viewable', our content is passive. A form has an action, which makes it a bit confusing, especially since its processing page will need an endpoint as well.

Question: Should this be core functionality, or would this be far more effective as a plugin/extension, so administrators can create their own forms?

[parndt]

Do we have to tackle forms in the MVP?

[robyurkowski]

I think we have to do it before first public release, but I don't think it's necessarily MVP worthy. I guess I didn't mention that all these milestones are arguable; I'm just tagging them all, and then was going to issue directions to discuss.

I'm mostly going through the feature thoughts gist from way back when and adding the features that come out of that. Some of this stuff is definitely more suited to later releases.

[knewter]

I vote forms are non-core.

[robyurkowski]

Thinking about this a second time, this isn't actually challenging to our viewpoint. This is just a viewable that submits to a non-viewable, and then displays another viewable on success (a page or a custom action). So that's a non-factor. But it's probably a good idea that this be non-core, too. It's bloat, and I'm more confident that someone else with an interest in making a ridiculously featured version will tackle it better.

[robyurkowski]

Thinking about this AGAIN for the third time, I think any sort of generator we make for the back-end will be applicable to the front end. If we scaffold out back-end stuff, why not front-end stuff? It shouldn't do much different, except perhaps generating the form in the other half of the app.

This is lower priority, but I think this sort of falls under the purview of 'generators'.

[parndt]

Tbh I don't think I want generators at first. Maybe let's prefer nice
DSLs to code generation??